> ## Documentation Index
> Fetch the complete documentation index at: https://hopsdocs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Performance review prep

> Draft review summaries from the work people actually shipped.

Managers write reviews from memory and recent work dominates. Hops reads what each person shipped over the cycle and drafts a balanced, factual summary for the manager to edit.

<Info>
  **How it runs:** Scheduled. An automation runs two weeks before reviews are due, posts a status and saves a Doc per person. You can also ask Hops any time.
</Info>

## What it does

* **Reads the work shipped.** Hops pulls the cycle's issues from Jira or Linear and merged pull requests from GitHub for each person.
* **Maps it to the leveling guide.** Work is summarized with links against the leveling guide and review template in Space context.
* **Balances the draft.** Each summary has strengths and one growth area, kept factual.
* **Covers every manager.** The scheduled run drafts summaries for each manager's direct reports.
* **Leaves the judgment to managers.** Hops drafts; the manager edits and owns the final review.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/tkB4Ie3VaZfG_Zdp/images/use-cases/hr-performance-reviews.gif?s=5c4f3ded60fe76d360d107ca2664cedc" alt="Jira connection, Hops read 6 months of Jira issues for Alex Kim and drafted a review summary" width="1440" height="810" data-path="images/use-cases/hr-performance-reviews.gif" />
</Frame>

## Ask Hops

Copy a prompt into any chat with Hops, or mention `@Hops` in a Space.

```text theme={null}
Prep the review draft for Alex Kim for the H1 cycle.
```

```text theme={null}
What did Priya Nair ship at Northwind this half, with links?
```

```text theme={null}
Which of Sam Rivera's projects map to the senior engineer level?
```

```text theme={null}
Draft review summaries for all of Dana Ortiz's direct reports.
```

```text theme={null}
Suggest one growth area for Alex Kim based on the work, not opinions.
```

Example reply:

> Review draft for Alex Kim:
>
> * Shipped 41 issues, including the billing migration.
> * Took on on-call for two quarters.
> * Growth area: earlier scoping on large projects.

## What you get

* **A post to managers** in the Space chat or Slack two weeks before reviews are due, saying drafts are ready.
* **A saved Doc per person.** Each review summary is saved to **Docs** in the Space, with links to the work.
* **A tracker.** Review status per manager can be kept in **Tables** in the Space.
* **On-demand drafts.** Ask Hops in chat any time for one person.

## Connections needed

Connect these apps. Each card opens Connections in the app.

<CardGroup cols={3}>
  <Card title="Jira" icon="jira" href="https://app.hops.ai/my-hops/connections">
    Issues each person shipped (or Linear).
  </Card>

  <Card title="GitHub" icon="github" href="https://app.hops.ai/my-hops/connections">
    Merged pull requests and reviews.
  </Card>

  <Card title="Slack" icon="slack" href="https://app.hops.ai/my-hops/connections">
    Where managers are notified.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect Jira or Linear, GitHub and Slack in **Connections**.

    See [Connections](/docs/connections/overview).
  </Step>

  <Step title="Pin the review materials">
    Create a **people-ops** Space and pin the review template and leveling guide in Space context.

    See [Spaces](/docs/spaces/overview) and [Space context](/docs/spaces/space-context).
  </Step>

  <Step title="Add the skill">
    Give Hops these instructions:

    ```text theme={null}
    You prep performance reviews. Summarize what the person shipped this cycle, with links, against the leveling guide. Include strengths and one growth area. Keep it factual.
    ```

    See [Build a skill](/docs/agents/build-a-skill).
  </Step>

  <Step title="Schedule it">
    Run each review cycle, two weeks before reviews are due. Hops drafts a summary per person, saves each as a Doc and posts to managers.

    See [Automation](/docs/spaces/automation).
  </Step>
</Steps>


## Related topics

- [HR & people ops](/teams/hr-people-ops.md)
- [Pipeline review](/teams/revops/use-cases/pipeline-review.md)
- [NDA prep](/teams/legal/use-cases/nda-prep.md)
- [Pre-call prep](/teams/sales/use-cases/pre-call-prep.md)
- [Board meeting and fundraise prep](/teams/founders-executives/use-cases/board-deck-prep.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.