How Many Hours Will This Review Cycle Really Take?

Why First-Time Managers Underestimate Review Time by 50-100%

Almost every first-year manager plans their review cycle based on one number: the conversation. "I have six people, that is six hour-long meetings, so six hours." Then the actual cycle hits and they discover the conversation is roughly 20% of the total work.

What they forgot: the hours of reading self-assessments and 360 feedback, the time to reconstruct six months of memory into a narrative, the writing itself (which for an honest, specific review takes 2-3 hours per person, not 30 minutes), the calibration meeting where ratings get debated, and the post-review follow-up notes. Together these add 4-6 hours per person on top of the conversation. For a six-person team, the total cycle is closer to 35-45 hours than six.

The Four Phases of a Review Cycle

1. Preparation. Re-reading your notes, skimming projects from the period, reading the employee's self-assessment, synthesizing 360 feedback if collected. 30 minutes for a light review, up to 3 hours for a thorough one, per person. Most managers skip this phase and pay for it by writing reviews that sound generic.
2. Writing. The actual document. For a standard review this is 2 hours per person if you are writing something specific and useful, 30 minutes if you are copy-pasting from a template. The first produces a conversation that changes behavior. The second produces one the employee will skim and forget.
3. The conversation. 30-90 minutes per person. Include 10-15 minutes of prep time for the conversation itself on top of the document prep (different mental context). This is the only part of the cycle that actually helps the employee, so protect it.
4. Follow-up. Sending the final document, noting any commitments, booking follow-up conversations, logging development plan items. 15-60 minutes per person. Usually skipped, which is why commitments made during reviews rarely get tracked.

How to Use This Calculator With Your Boss

The single most useful thing this calculator can do is give you language for a conversation you probably have not had. Run the numbers, take a screenshot, and send this to your boss before review season starts:

"Based on this time estimate, the review cycle for my team will take approximately X hours over Y weeks. To do it properly (not quickly, properly) I need one of the following: reduced meeting load during that period, permission to defer [specific project] by a week, or explicit air cover on [deliverable]. Which of these is easiest for you to support?"

This works because you are not asking for time off. You are presenting the operating cost of a quality process and asking your boss to help you protect it. Managers who run reviews on top of their full workload deliver bad reviews, burn out, or both. Our article on managing up as a new manager covers how to turn requests like this into routine conversations, not one-time begs.

Why This Year's Cycle Will Be Your Hardest

First-cycle managers pay a one-time tax that compounds savings for every future cycle. You are building the notes system, the writing template, the calibration rhythm, and the memory of how long each phase actually takes. Second cycle, with the same inputs, typically runs 20-30% faster because you are not rebuilding the scaffolding.

The highest-leverage investment you can make this cycle is not in the reviews themselves. It is in the system that makes the next cycle cheaper: one running doc per direct report, updated 10 minutes a month, becomes 70% of your review prep done before cycle even starts. This is the single highest-ROI habit in management, and almost nobody does it. Our Team Goal Setting Workbook includes the monthly check-in templates that feed directly into review prep.