A workable performance review template needs only five fields: a goal recap, evidence-backed achievements, a behavioural competency rating, two development priorities, and next-period objectives. Those five fields give managers enough structure to write a defensible review without turning the form into a second HR project. Everything else belongs in a separate HR record, not in the form a manager fills out.
You likely came here for a usable form, not another theory of performance management. The template below was designed backward from manager completion, with a target of under 30 minutes per direct report, and the example later in this piece is an anonymized composite rather than a copied employee record.
Most templates fail not because they ask the wrong questions, but because they ask too many. Here is what changes when the form gets shorter and sharper:
- The strongest template keeps the manager writing in five fields and pushes optional HR detail out of the core form.
- A review becomes easier to submit when every rating needs one piece of evidence, not a long narrative.
- Individual contributors, people managers, and senior leaders can share the same template if different fields get more room.
- The same review record should feed calibration, compensation input, and development planning without asking managers to re-enter the same facts.
What performance review template should managers use?
Use a one-page review with five required sections, each capturing one decision-ready piece of information. The form should support feedback, ratings, development, and next goals without adding extra admin on top.
Copy-paste performance review form
The first field asks the manager to restate the goals that were active during the review period. This prevents the review from drifting into general impressions and gives the employee a fair starting point for the conversation, which sits at the centre of the CIPD's current performance management guidance.
The second field asks for key achievements with evidence. One outcome per line, attached to a metric, a customer signal, a project milestone, or a stakeholder example where one exists. If a manager cannot name evidence, the achievement does not belong in the review.
The third field covers a competency rating with behavioural anchors. Keep it focused on observable work behaviour, because managers submit faster and calibrate better when they do not have to translate vague traits into defensible judgments later.
The fourth field names two development priorities. This is not a training catalogue; it is the skill or behaviour that would most improve the employee's next six months. The fifth field sets next-period objectives, so the manager and employee leave with the next goals already visible instead of writing a separate plan after the meeting.
Why five fields are enough
Five fields cover the full decision chain: what was expected, what happened, how well it was done, what to work on next, and what to aim at. Anything beyond that lives more naturally in a goal system, a 1:1 record, or a development plan than in the review form itself. If you want a wider pack with annual, probation, and project variants, our collection of role-based review templates is built around the same five-field spine.
How can managers finish reviews under 30 minutes?
Treat under 30 minutes as a design target for the written review, not a proven industry average. The template reaches that target by making managers choose evidence, ratings, and next actions instead of writing a full essay from memory.
Manager time is the adoption problem the template has to solve. Many organisations still rely on managers to turn scattered goals, notes, and memories into a finished review, even though only 26% of organisations report that managers are very or extremely effective at enabling people performance. That gap is not closed by adding more fields.
The form should remove the slow fields first. Long open-text boxes create hesitation. Repeated questions create copy-paste fatigue. Separate systems make managers rebuild the same story for HR later. A faster review asks for one clear goal recap, one evidence-backed achievement section, one anchored rating, one development focus, and one next-period plan.
The practical rule is simple. If a field will not help the manager give feedback, justify a rating, or start the next goal cycle, it does not belong in the core template. HR can still collect richer data elsewhere, but the manager-facing form should protect completion before it protects completeness.
What we'd cut first: the "additional comments" box, the duplicated self-assessment summary, and any field that asks the manager to summarise something the rating already says. Those three together usually save the most minutes per review without losing decision quality.
How should the review template change by role?
Keep the same five sections across roles, but change how much space each one gets. Individual contributors need more room for delivery evidence, people managers need more room for team outcomes, and senior leaders need more room for strategic results.
For an individual contributor, the achievements field expands because the strongest evidence usually sits in delivered work. UCI HR's individual-contributor performance criteria name goal accomplishment, job mastery, innovation, and enterprise contribution as the core dimensions, and those map cleanly into a longer evidence section with a tighter development field.
For a people manager, the competency and development fields expand. The review should not only ask what the team delivered. It should ask how the manager set expectations, coached people, handled accountability, and helped team members grow.
For a senior leader, task-level detail compresses and the connection between goals and organisational results expands. A leader review should show how the person led change, aligned people, used resources responsibly, built coalitions, and delivered outcomes beyond their own direct work.
| Role | Section that expands | Section that compresses | Evidence the manager should bring |
|---|---|---|---|
| Individual contributor | Achievements with evidence | Development priorities (kept to one concrete action) | Delivered work, quality signals, job-mastery examples, collaboration |
| People manager | Competency rating and development priorities | Personal task delivery | Team outcomes, coaching examples, accountability moments, growth of reports |
| Senior leader | Next-period objectives tied to organisational results | Task-level achievements | Change led, coalitions built, resource decisions, business outcomes |
How should review data feed calibration and pay?
The review record should become the evidence packet for calibration, the input for compensation decisions, and the starting point for development planning. Managers should not have to rewrite the same rating rationale in three separate places.
For calibration, the template should preserve the preliminary rating, the evidence behind it, and the manager's short rationale. That gives the calibration group something concrete to compare across teams and reduces the chance that the loudest voice in the room replaces the best-documented performance story. The same evidence-first logic sits behind our calibration meeting templates, which reuse the review record rather than asking managers to assemble a second packet.
For compensation, the template should provide the performance input without turning the review conversation into a pay negotiation. Only 9% of employers do not use performance ratings to determine merit increases, so ratings will inform pay in most organisations. Employees still need a development conversation that does not collapse into a salary discussion.
For development planning, reuse the development priority and the next-period objective. If HR has to copy these into a separate plan after the review, the process adds admin and loses momentum at exactly the point where the employee expects action.
What rating anchors make performance reviews fairer?
Fairer anchors describe behaviour someone can observe and evidence someone can check. They should explain what a solid rating looks like before they describe exceptional or underperforming work.
A useful anchor tells the manager what the employee did, how well they did it, and what evidence supports the judgment. The U.S. Office of Personnel Management guidance on performance standards says these standards should be objective, measurable, realistic, and clearly recorded, and that descriptive standards should specify who judges the work and which factors they look at. Personality labels miss that test because they push managers back toward impressions.
The middle rating needs special care. If managers read the middle as mediocre, they inflate scores to avoid demotivating strong employees. If they read it as solid performance, they use the scale with less defensiveness. Define the middle as "good solid performer" in the anchor itself, not in a separate guide that nobody opens during the review.
The anchor should also name the factors that matter for the role. Quality may matter most in one job, timeliness in another, and cost-effectiveness when the person controls budget or resources. Once the anchor is clear, our phrase library for review writing helps managers find wording. Phrases should support the evidence, never replace it.
What does a completed performance review look like?
Use an anonymized composite, not a real employee record. The point is to show how a weak review turns into a useful one when the manager adds goals, evidence, anchors, and next actions.
The "before" version feels familiar: the manager writes that the employee did good work, communicated well, and should keep developing. That kind of review sounds positive but gives HR little evidence, gives calibration nothing to compare, and gives the employee no clear next step. Gallup reports that only 23% of employees strongly agree they have a clear definition of exceptional performance in their role, which is exactly what a vague review reinforces.
| Field | Before (weak version) | After (five-field version) |
|---|---|---|
| Goal recap | "Worked on the customer onboarding project." | "Reduce onboarding handover time from 14 to 7 days by end of H1." |
| Achievement with evidence | "Did good work on onboarding." | "Cut average onboarding handover to 8 days; CSAT on first-30-day survey rose from 7.4 to 8.1." |
| Behavioural rating | "Communicates well." | "Solid: documented every handover step, flagged blockers in weekly review, asked for input from two peer teams." |
| Development priority | "Should keep developing." | "Lead the next cross-team retro to build facilitation experience." |
| Next-period objective | (missing) | "Bring handover to 6 days and shadow one customer kickoff per month." |
Real reviews are not good public examples because they contain sensitive employee data. Use a composite, label it clearly, and let the structure carry the lesson.
A review form managers finish
The most useful template is not the one with the most fields. It is the one where evidence stays alive after the conversation ends. When the same five fields support feedback, calibration, pay input, and development follow-up, the form stops being paperwork and becomes the shared record of performance.
That only works when each field has a downstream job. Manager adoption improves when HR removes duplicate entry before asking for better review quality, and the review conversation itself gets stronger when the written form already contains the evidence and the next-period action.
Start with the one-page version for your next cycle and check whether managers can complete one review in under 30 minutes. If evidence still lives across 1:1 notes, goals, and project tools, move the same fields into Sprad so managers edit one review record instead of rebuilding it from scattered data.
Frequently Asked Questions (FAQ)
How long should a manager spend on one performance review?
Aim for under 30 minutes per direct report on the written review. Treat that as a practical design target rather than a proven industry average, because independent data on exact per-form completion time is limited. If managers need longer, the template probably asks for too much narrative or forces them to gather evidence too late.
What rating scale works best in a performance review template?
A three-point or five-point scale usually works best when the middle rating is clearly defined as solid performance. The scale itself matters less than the behavioural anchors attached to it. Managers need to know what observable work belongs at each level before they can rate consistently across a team.
Should compensation be discussed in the performance review?
Performance ratings can inform compensation, but the pay discussion should not take over the development conversation. Mercer's employer data shows that most organisations still use ratings for merit decisions. The safer workflow is to capture the rating and rationale in the review, then handle compensation in a separate decision process.
How many goals should a performance review carry forward?
Four to six active goals is a practical upper range for most employees. APQC's 2025 survey found that most employees have four to six goals and that 71% feel their goal count is just right. A review template should carry forward only the objectives the manager and employee can actually discuss and track.
Can AI write a manager's performance review?
AI can draft a performance review, but the manager should own the final judgment. In Europe, AI used for employment and worker management sits in a high-risk category, so human oversight, traceability, and clear documentation matter. The safest use is to let AI prepare evidence and wording while the manager checks accuracy and fairness.
Should employees complete a self-assessment first?
Yes, a self-assessment helps when it adds evidence the manager may not have seen. Keep it short and connect it to the same goals, achievements, development priorities, and next objectives as the manager template. If the self-assessment becomes a second full review form, it adds work without improving the conversation.



