PerfCopilot
Get started
HomeDocs
Documentation

Everything you need to write a fair review.

From your first connection to a sealed, delivered review. Set up PerfCopilot, connect your tools, and generate your first cited draft.

Set up your organization

PerfCopilot is a manager-led performance review platform. You'll set up an organization, invite the people you manage, connect a few signal sources (GitHub, Slack, Jira, etc.), and start running review cycles.

This guide walks you through the first 10 minutes.

Create your account

Head to app.perfcopilot.com/onboarding and create an account with your work email. You'll set a password and (recommended) enable 2FA from /account?tab=security once you're in.

The first user to sign up for an organization becomes its owner — they have full admin rights, including billing, member management, and the ability to delete the organization.

Set your organization's timezone

Cycles snap to local-time week / month / quarter boundaries based on the organization's timezone. So if your team is on US Eastern, a "weekly" cycle runs Monday 00:00:00 EDT to Sunday 23:59:59 EDT — not UTC midnight.

Set this once at /admin?tab=settings. Changing it later re-aligns future cycles only; past cycles keep the boundaries they were created with.

Why it matters: signals (commits, messages, tickets) are bucketed into cycles by the cycle's window. A wrong timezone shifts everything by a few hours and a Friday-night ship can land in the wrong week.

Pick your review cadence

Most teams pick one of:

  • Weekly — Monday-to-Sunday cycles. Best for fast-moving teams, leading indicators, and managers who want a continuous check-in rhythm.
  • Monthly — first-day-to-last-day of each month. The default for most knowledge-work teams.
  • Quarterly — Q1 / Q2 / Q3 / Q4. Closer to traditional perf review timing.
  • Custom — any window. Useful for project-based reviews ("reviews for the migration sprint") that don't fit a standard cadence.

You can also run multiple cadences at once — e.g. weekly cycles for fast feedback plus quarterly cycles for the formal review of record. A peer review or manual note authored on, say, May 5 attaches to the weekly, monthly, AND quarterly cycle whose windows cover that date. See Cycles for the full mechanics.

Next steps

Once your org is set up, the standard onboarding flow is:

  1. Invite your team
  2. Connect your first integration (GitHub is the fastest)
  3. Create your first review cycle from /admin?tab=cycles and run Sync All to pull in signals.
  4. Generate your first AI review.

If you get stuck at any step, email support@perfcopilot.com.

Next Invite your team