How to Run a Performance Review Cycle in Confirm: Step-by-Step Playbook

Most performance review cycles fail in the setup, not the execution. By the time managers are writing reviews, the damage is already done: no one's clear on what they're evaluating, the questions don't connect to anything that matters, and completion rates tank because the process feels like a tax.

Confirm's review cycle builder was designed to solve this, but only if you configure it the right way from the start.

This playbook is a recipe for setting up and running a performance review cycle in Confirm that produces useful data, not just completed forms.

The Recipe at a Glance

Outcome you're trying to achieve: A completed review cycle where every manager has usable performance data, ratings are calibrated across the org, and you can identify who to promote, develop, or have harder conversations with.

Ingredients:

A clear evaluation window (the period you're reviewing (usually 6 months or 1 year))
Finalized review questions (see Step 2 for how to pick them)
Your org chart loaded and current in Confirm
Manager communication sent before launch (5 minutes; covered in Step 4)
Calibration session scheduled before you launch the cycle

Time required: 2–3 hours to configure, 2–3 weeks for completion, 2 hours for calibration.

When to use this: Twice-yearly performance cycles, end-of-year reviews, or any point where you need a structured evaluation of the full org or a team.

When NOT to use this: For a single direct-report performance conversation. That's a 1:1, not a cycle. Confirm's continuous feedback module handles that separately.

Step 1: Open the Cycle Builder and Set Your Window

In Confirm, go to Performance → Cycles → New Cycle.

The first decision is your evaluation period. This is the date range you're reviewing, not the dates the cycle runs.

Setting	What it controls	Common mistake
Evaluation start date	Beginning of the performance period	Setting this to today instead of 6 months ago
Evaluation end date	End of the performance period	Leaving this blank (defaults to today; usually correct)
Cycle open date	When managers can start writing	Setting this too early before questions are finalized
Cycle due date	When everything must be submitted	Setting this without checking your manager's calendar

The most common setup error: confusing "when we're reviewing" with "the period we're reviewing." The cycle runs during your review window, but it covers the past evaluation period.

If you're running a mid-year review in July 2026, your evaluation period is January–June 2026. Your cycle runs July 7–25.

Step 2: Choose Your Review Questions (The Decision That Matters Most)

Confirm lets you customize review questions, and this is where most HR teams overthink it.

The goal isn't comprehensiveness. It's signal. You want questions that:

Produce data you'll actually use in calibration
Are answerable by a direct manager without coaching the answer
Connect to how your company defines performance

The 4-question structure that works:

*One rating question: Overall performance on a defined scale (Needs Improvement / Meets / Exceeds / Exceptional, or similar)
One impact question: What did this person accomplish in the evaluation period?
One growth question: What should this person develop in the next 6 months?
One potential question: Is this person ready to take on more?

That's it. Confirm supports longer questionnaires, but four well-chosen questions produce better calibration data than twelve questions no one reads carefully.

To set this up: In the cycle builder, go to Questions → Edit. You can use Confirm's question library or write your own. For each question, choose whether it's rated (numeric or label scale), text, or both.

Pro tip: Enable the "Manager can view AI draft" toggle. Confirm's AI will generate a draft review for each direct report based on their history in the system: past feedback, goal completion, ONA data. Managers can edit or discard it, but it cuts average writing time from 45 minutes to 12.

Step 3: Configure Who Reviews Whom

Confirm pulls from your org chart automatically, but review it before launching. HR teams routinely find:

Employees with no manager assigned
Recently promoted managers who now have direct reports
People who changed teams mid-cycle (who should review them?)

In Cycle Settings → Reviewers, you can:

Confirm auto-assigned manager-to-direct-report pairings
Add skip-level visibility (VPs can see their managers' reviews)
Enable peer reviews if your process includes them
Flag any 360s needed for employees without a direct manager

Fix org chart gaps now. Discovering them after launch means manually reassigning reviewers mid-cycle, which confuses everyone.

Step 4: Send the Manager Brief Before You Launch

Don't launch without a 3-paragraph note to managers explaining:

What the cycle is, how long it runs, what they need to do
Where to find the AI drafts and how to use them (optional, but reduces inbound questions by 70%)
One sentence on calibration: let them know it's coming and that ratings should be defensible

Confirm lets you send this directly from the cycle builder (Launch → Manager Communication → Preview & Send) or export the list and use your own email tool.

Managers who feel surprised by a review cycle produce worse reviews. This note takes 5 minutes and prevents 40% of the issues that show up in HR inboxes during a cycle.

Step 5: Monitor Completion and Chase Early

Once the cycle is live, check completion in Performance → Cycles → [Your Cycle] → Progress.

Confirm shows completion by manager, team, and department. The view you want is sorted by due date proximity with completion rate descending. That shows you who's behind and how far.

Standard chase schedule:

T-7 days: Remind everyone (Confirm sends automated reminders, but a personal note from HR or their manager moves it faster)
T-3 days: List of managers at 0% completion: escalate to their manager
T-1 day: Final push; offer to extend individual deadlines for documented exceptions

A 95%+ completion rate is achievable in most orgs. Completion below 80% means something in the process broke (too many questions, unclear instructions, or a manager who didn't understand what was expected).

Step 6: Run Calibration Before You Close the Cycle

This is the step most teams skip. Don't.

Calibration is a session (usually 60–90 minutes) where managers and HR review ratings together to catch two specific problems:

Rating inflation: One manager's "Meets Expectations" is another's "Exceeds"
Bias: Employees who are visible, vocal, or similar to their manager get rated higher than people who do equivalent work quietly

Confirm's calibration view (Performance → Calibration) shows everyone's ratings on a distribution curve alongside their ONA influence score. If someone is in the bottom third of ratings but top quartile of network influence (people across the org seek out their input, who others rely on for decisions), that's a flag. Either the rating is wrong, or there's something worth understanding.

Calibrate before reviews are finalized and shared. Changing a rating after someone's seen it creates more damage than the original error.

Step 7: Close the Cycle and Share Results

When calibration is complete and you're satisfied with the data, close the cycle in Performance → Cycles → [Your Cycle] → Close Cycle.

Confirm will:

Lock submissions (no more edits)
Generate manager summary reports
Flag any employees with no final rating for your review

From here, you can:

Export to CSV for integration with your HRIS or comp planning tool
Share individual review summaries with employees (manager controls visibility)
Feed data into Confirm's talent grid for promotion and succession planning

What Good Looks Like vs. What Derails It

What works	What breaks it
4 focused questions with a clear rating scale	12+ questions that take 2 hours to answer
Manager communication sent 3+ days before launch	Launching cold with no context
Calibration scheduled before launch day	Calibrating after reviews are already shared
AI drafts enabled for managers	Expecting managers to write from scratch
90-day post-cycle follow-up on development plans	Treating the cycle as the endpoint

What Happens After the Cycle

The review cycle is the start of the development conversation, not the end of it. Once ratings are finalized, use Confirm's data to:

Flag employees for individual development plan conversations, especially anyone who rated "Meets" but has high ONA influence
Identify high-potentials for accelerated development
Trigger promotion decisions for anyone ready to level up

The cycle closes. The development work begins.

FAQ

How long should a performance review cycle run?

Two to three weeks is the standard in Confirm. Shorter cycles see rushed, lower-quality reviews. Longer cycles lose urgency and completion rates drop. If your org is large (500+ employees), give managers more time, but set a hard final deadline for calibration.

Can Confirm run multiple cycles at once?

Yes. You can have separate cycles for different teams, departments, or employee types. This is common for companies with multiple review schedules (engineers on one cycle, sales on another).

What if a manager misses the deadline?

Confirm flags late submissions in your progress dashboard. For genuine exceptions, you can extend individual manager deadlines without affecting the rest of the cycle.

How does ONA data show up in reviews?

If your Confirm account has ONA enabled, you'll see a network influence score on each employee's profile. During calibration, this appears as a secondary signal next to their performance rating; not a substitute for the rating, but a data point worth noting when there are gaps.

Should employees see their own reviews?

This is a configuration choice, not a default. Most HR teams share review summaries with employees after calibration and manager delivery. The sequence matters: calibrate first, then share with the manager, then share with the employee — never share with the employee before the manager has delivered the feedback in conversation, not in advance.