Employee Recognition
16 mins to read

Performance Review Templates: 2025 Guide for HR

Last updated: October 19, 2026
Copyable performance review fields, sample rating scales, feedback scripts, and guidance for choosing, adapting, and rolling out review templates.

What is a performance review template? (Clear definition + why it matters)

A performance review template is a structured form with questions, rating scales, and guidance. It standardizes how managers and employees evaluate performance.

Labels vary and may be used interchangeably. Useful working distinctions are appraisal as the formal assessment, review as the discussion and record, and evaluation as judgment against criteria. Choose fields by the review’s purpose, not the label alone.

Use a shared format to record expectations, observable examples, and rating rationales. These records provide a common basis for review and calibration discussions.

Jump to: Choose a template · Copyable forms · Rating examples · Feedback examples · Rollout · Privacy · Metrics · FAQs

How to choose the right template (by scenario, role, and cadence)

Use this decision guide to pick a performance review template for your goal, cadence, and audience, then adapt its fields to the work being reviewed.

Start with the scenario, then tailor by level and industry. Small, generalist teams can start with one competency-based form and a short goals section, adding detail where the work or review purpose calls for it.

Scenario fit: annual vs quarterly vs probation vs compensation check-ins

Choose the scenario first—your template follows.

For monthly check-ins, adapt an existing form to about one page with 1–2 competencies, a few relevant metrics, and next actions.

  • Annual or semiannual: Use a comprehensive employee performance review template with goals, competencies, and calibrated ratings. Add a self-evaluation and peer/360 input where appropriate. Summarize sustained achievements and 2–3 multi-quarter projects across the longer review period.
  • Quarterly or mid-year: Use a lightweight check-in template focused on OKR progress, blockers, and 1–2 development priorities; avoid rating bloat. Copyable fields: Review period; goal/OKR progress; evidence and employee context; blockers and needed support; next actions and owners; next check-in date. Adapt goals to workload (Acas guidance for Great Britain).
  • Probation/90-day: Treat 90 days as an example, not a universal duration. Adapt the form to the role and applicable process; record job expectations, training, evidence, and policy-dependent next steps. A form is not a complete dismissal procedure.
  • Compensation check-ins: Separate from performance reviews when possible; use a structured template with documented criteria, pay equity checks, and no off-script promises.

Role/level fit: IC vs manager vs executive; new hire vs tenured

Match competencies to the role and seniority.

  • Individual contributors (IC): Emphasize execution, quality, collaboration, and learning agility; use 1–5 behaviorally anchored rating scales (BARS).
  • Managers: Add people leadership, coaching, hiring, and team health; include team outcomes and engagement indicators.
  • Executives: Focus on strategy, cross-functional impact, organizational health, and business results; include stakeholder feedback.
  • New hires vs tenured: For new hires, weight onboarding milestones and role proficiency; for tenured, weight strategic projects and sustained impact. An optional ramp pattern is 30/60/90-day checkpoints with shorter weekly conversations between them. Adapt timing to the role and applicable process; these are planning examples, not required review dates or employment-decision rules.

Industry fit: sales, engineering, customer success, support, and operations (what to customize)

Customize metrics and anchors so ratings map to real work.

  • Sales: Add quota attainment, pipeline hygiene, win rate, and forecast accuracy; include deal review evidence.
  • Engineering: Add code quality, delivery predictability, technical scope, and reliability ownership; include PRs, incidents, and design docs.
  • Customer success: Add NPS/CSAT, retention/renewals, expansion, and adoption; include account plans and risk mitigation steps.
  • Customer support: Consider CSAT, first-response and resolution time, knowledge contributions, and observed customer-handling behaviors such as clarifying needs and explaining next steps. Adapt criteria to the role rather than rating personality.
  • Operations: Consider process reliability, on-time delivery, cost control, risk management, and cross-functional coordination; adapt measures and evidence to the role’s responsibilities.

Six inline performance review forms (copy and edit)

The six forms below are inline, editable starting points—not supplied downloads. Copy the relevant fields into a new document or spreadsheet, then save or export using your chosen application's supported options.

Adapt the fields, prompts, and any rating options to your role, review purpose, and applicable process; they are not universally required fields.

Annual performance review template (editable + sample fields)

Use this employee performance review template to run a comprehensive annual or semiannual appraisal.

  • Employee info: Name, role, level, department, review period, manager.
  • Goals/OKRs: List objectives, key results, outcomes vs targets, comments.
  • Competencies (BARS 1–5): Communication, Ownership, Collaboration, Impact, Role-specific.
  • Achievements: Top 3–5 outcomes with evidence (links, metrics).
  • Growth areas: 1–3 development opportunities with action plans.
  • Overall rating: 1–5 with behavior summary; calibration notes.
  • Next-period goals: 3–5 draft OKRs with measures.
  • Sign-offs: Employee, manager, date; acknowledgement of receipt and discussion, not necessarily agreement with the assessment.

To use: Copy these fields into your doc and keep your scale consistent. Include a self-evaluation section for two-way feedback. Align examples to your competency language to keep ratings comparable.

Hypothetical review-to-follow-up example—replace the details and date: Evidence: Two customer replies missed the agreed response window. Employee context: Incomplete handoff notes. Agreed action/owner: Employee logs missing details at handoff. Support: Manager provides a checklist and reviews two cases. Measure: Complete notes and timely replies in the next five cases. Next check-in: November 6 (example date). Share the record for employee comments. This illustrates workload-relevant objectives and shared records discussed in Acas guidance for Great Britain.

Self-evaluation template (questions grouped by competency)

Use this self-evaluation template to reflect on results, evidence, and questions for the manager meeting.

Results and impact

  • Which outcomes are you most proud of this period? What evidence supports them?
  • Where did results fall short? What did you learn?

Collaboration and communication

  • Describe a time you improved team alignment or unblocked others.
  • What feedback have you sought and how did you use it?

Ownership and execution

  • How did you prioritize and manage trade-offs?
  • Which commitments slipped, and what will you change next time?

Growth and craft

  • What skills improved most? Where do you want training or mentorship?
  • Which projects will stretch you next period?

Goals

  • Propose 2–3 OKRs for the next cycle with measurable KRs.

Tip: Ask for specific examples and links to artifacts (docs, dashboards, tickets) to ground claims. Bring these records to discuss evidence and context.

Peer and 360 feedback templates (observed-behavior prompts)

Use this 360 feedback template to collect specific, actionable input.

Prompts

  • What is one behavior this person should keep doing? Include an example and impact.
  • What is one behavior this person should start or stop? Include an example and a suggested next step.
  • When collaborating with this person, what helps or hinders team outcomes?
  • Optional: Rate collaboration effectiveness on a 1–5 anchored scale.

Rater guidance

  • Focus on observed behaviors, not traits.
  • Avoid loaded words; use concrete situations and impacts (SBI: Situation–Behavior–Impact).
  • Skip areas you have not observed.

Use the responses to discuss observed patterns and examples, rather than treating a score as a complete assessment.

Before collection, explain the purpose, expected responses, and who will see raw feedback or summaries—including whether input informs development or other review decisions. Describe the actual confidentiality and anonymity arrangements; do not promise anonymity. After synthesis, select a development action with the employee, agree support, and schedule a follow-up discussion. CCL's implementation guidance emphasizes clear expectations, confidentiality arrangements, and development follow-through.

Probation review template (90-day example; adaptable fields)

Use this probation review template as a documentation starting point for job expectations, training, and discussion. Adapt the duration and reviewers to the role and applicable process.

  • Role scope: Job description essentials and performance standards.
  • Training/support provided: Onboarding plan, mentors, resources.
  • Evidence of performance: Specific examples, dates, artifacts.
  • Ratings against expectations: Meets / Partially meets / Does not meet; behavior anchors.
  • Review timing: Agreed period, milestones, check-in dates, and responsible reviewers.
  • Decision and next steps: Possible pass, extension with a plan, or termination under the applicable process and policy; none follows automatically from the elapsed period or a signature.
  • Employee response: Comments, relevant context, and the contact or route for requesting further review under the applicable process.
  • Employee acknowledgement: Summary of discussion, receipt date, and signatures where appropriate; acknowledgement is not agreement with the assessment or decision.

Hypothetical filled onboarding review: All details, metrics, and the next-90-day period below are illustrative, not reported results or an employment-decision rule. Replace them with your own evidence and agreed timing.

  • Goal KR2: Close onboarding tickets within 2 business days. Actual median: 1.3 days.
  • Collaboration: Meets—partnered with the customer success lead to document a new escalation path; handoffs fell by 18%.
  • Next 90 days (example period): Shadow 2 enterprise calls, own a minor feature release, and complete intermediate product training.

Note: Keep facts objective, tie feedback to job duties, and follow local laws and company policy. Obtain appropriate review before decisions; documentation alone does not establish legal compliance. Acas guidance for Great Britain says dismissal requires a fair procedure and should be a last resort, not a form output.

Corrective action review template (PIP-aligned)

Use this PIP-aligned template to address persistent gaps fairly and transparently.

  • Performance concerns: Specific behaviors, dates, and business impact.
  • Expectations and standards: Observable criteria to meet.
  • Support and resources: Training, coaching, tools, frequency of check-ins.
  • Milestones and dates: Agreed targets, evidence, and a reasonable review period; choose check-in frequency for the situation.
  • Consequences: Possible next steps under the applicable process if expectations are not met; a missed milestone does not automatically establish a termination decision.
  • Employee response: Comments and relevant context; contact or route for requesting further review under the applicable process.
  • Signatures: Employee and designated reviewers, including HR where appropriate; dates and acknowledgement of receipt or discussion, not necessarily agreement.

Keep check-ins documented and focused on evidence, not intent, using the agreed schedule. Discuss the plan and share the record with the employee. This form does not complete an applicable fair procedure. Acas guidance for Great Britain calls for a reasonable timeline and support, and treats dismissal as a last resort requiring a fair procedure; follow the requirements and policy applicable to your situation.

Compensation check-in template (pay equity guardrails)

Use this compensation check-in template to structure sensitive pay conversations and protect equity.

  • Reason for discussion: Cycle timing, market adjustment, promotion review.
  • Evaluation inputs: Performance rating, scope change, benchmarks, comp bands.
  • Decision framework: Internal equity, market data, budget, location factors.
  • Proposed action: New base/bonus/equity or no change with rationale.
  • Communication plan: What to share now vs after approvals; effective date.
  • Documentation: Notes, approvals, and audit trail.

Guardrails

  • Separate performance and pay discussions when possible to reduce noise.
  • Do not promise changes before approvals; use documented criteria and ranges.
  • Run equity checks by cohort (role/level/location) before finalizing.

Behaviorally anchored rating scales (BARS) with examples

The anchors below are illustrative sample language, not validated rating instruments or universal performance standards. Adapt behaviors and expected scope to the role, level, competency model, and company values before using a 1–5 scale.

To build your own anchors, select 3–4 job-relevant observable behaviors for a competency and identify work artifacts that show them, such as sprint updates, feedback records, or decision notes. Distinguish meets from exceeds through role-appropriate scope and measures, not adjectives alone.

Hypothetical collaboration contrast: Adapt the behaviors, time allowances, and throughput measure below to the role and available evidence. These are sample anchors, not validated standards or reported results.

  • Meets expectations (3/5): Shares updates in sprint reviews, incorporates peer feedback within the same sprint, and unblocks teammates by pairing for up to 2 hours weekly.
  • Exceeds expectations (4/5): Convenes cross-team sessions to resolve dependencies, documents decisions, and improves team throughput by more than 10% over two sprints.

1–5 scale anchors for core competencies (communication, ownership, collaboration, impact)

Use these sample anchors to describe what 1–5 looks like across core competencies.

Communication

  • 1: Frequently unclear or late; others must rework due to miscommunication.
  • 2: Basic updates but missing key details; inconsistent channels.
  • 3: Clear and timely with appropriate detail; adapts message to audience.
  • 4: Anticipates information needs; simplifies complexity for cross-functional partners.
  • 5: Sets communication standards for the team; drives alignment across org levels.

Ownership

  • 1: Misses agreed follow-ups; needs frequent reminders to complete commitments.
  • 2: Completes assigned tasks but escalates late; limited follow-through.
  • 3: Delivers commitments reliably; flags risks early and proposes fixes.
  • 4: Proactively improves systems; owns outcomes beyond immediate tasks.
  • 5: Shapes strategy and mobilizes others; creates durable improvements.

Collaboration

  • 1: Works in silos; resists feedback.
  • 2: Participates but misses handoffs; narrow perspective.
  • 3: Seeks input, supports teammates, and meets shared goals.
  • 4: Unblocks others and resolves conflicts constructively.
  • 5: Builds high-trust networks; elevates team performance and culture.

Impact

  • 1: Limited measurable results; misaligned work.
  • 2: Inconsistent results; impact not durable.
  • 3: Meets goals with clear, measurable outcomes.
  • 4: Exceeds goals; improves key metrics with scalable solutions.
  • 5: Transforms outcomes across teams; outsized business impact.

Role-specific anchors: sales (quota/pipe), engineering (quality/velocity), CS (NPS/renewals)

These function-specific anchors and sales attainment cutoffs are unvalidated examples. Adapt them to role scope, level, local targets, and the context behind the results.

Sales (Quota Execution)

  • 1: <50% attainment; pipeline hygiene poor; forecasts unreliable.
  • 2: 50% to <80% attainment; inconsistent discovery; deals stall.
  • 3: 80% to <100% attainment; clean CRM; reliable forecasting.
  • 4: 100% to <120% attainment; high win rate; proactive multi-threading.
  • 5: 120%+ attainment; mentors others; repeatable playbuilding.

Engineering (Quality and Velocity)

  • 1: Frequent defects; misses estimates; low code review quality.
  • 2: Occasional regressions; limited test coverage; ad-hoc delivery.
  • 3: Predictable delivery; solid tests; code meets standards.
  • 4: Improves reliability; reduces cycle time; raises bar in reviews.
  • 5: Drives architecture upgrades; measurably boosts team throughput and quality.

Customer Success (Retention/Advocacy)

  • 1: Accounts churn without mitigation; poor risk visibility.
  • 2: Late escalations; limited adoption plans.
  • 3: On-time renewals; clear health scores; documented success plans.
  • 4: Expansions through value realization; proactive exec alignment.
  • 5: Portfolio-level retention gains; creates reference customers and playbooks.

Examples and scripts: how to give fair, actionable feedback

These manager scripts are illustrative wording with hypothetical circumstances, not attributed quotations. Adapt them to open the discussion, describe observed evidence, and agree next steps. Replace sample details with your own examples and supporting artifacts.

Positive start + constructive phrasing (before/after scripts)

Communication example

  • Before: “You need to communicate better.”
  • After: “In the Q3 launch (Situation), the status email lacked the risk on vendor delays (Behavior), which surprised stakeholders on rollout day (Impact). Going forward, include risks and owner in weekly updates (Next step).”

Strategy example

  • Before: “You’re not strategic enough.”
  • After: “Your roadmap focuses on near-term fixes; to hit our adoption goal, add one-quarter-ahead bets with success metrics and dependencies.”

Opening script

“Let’s start with highlights I’ve seen and those you’re proud of. Then we’ll cover two growth areas with examples and agree on support and next steps.”

Self-evaluation exemplars: strengths, growth areas, goals

These are hypothetical self-evaluation examples, not employee quotations or reported results. The 38% result, Stripe dashboard reference, goal metrics, and May 15 date are illustrative; replace them with your own evidence and appropriate goals.

Strengths example

“I led the billing refactor that cut payment failures by 38% (Stripe dashboard). I coordinated with Support to validate edge cases and wrote a runbook for incident response.”

Growth area example

“Two project estimates slipped due to integration risks I flagged late. I’ve added risk reviews to kickoff docs and will pilot story-pointing with QA to improve predictability.”

Goal example (OKR-aligned)

Objective: Improve onboarding activation. KRs: Increase D7 activation from 42% to 60%; reduce setup time from 20 to 10 minutes; ship in-app checklist v2 by May 15.

Implementation guide: prep, rollout, and calibration

Adapt this rollout plan to your organization. Pilot the forms, collect feedback, and review how managers use evidence and rating anchors before expanding the process.

Pre-work: align competencies and OKRs; manager training checklist

Prepare shared competencies, evidence fields, and manager practice, then revisit them based on the pilot and each review cycle.

  • Align on 4–6 core competencies and 1–3 role-specific ones; attach BARS to each.
  • Map OKRs to the review: auto-pull status where possible; avoid duplicate data entry.

Before each review: Agree when to exchange material—for example, the employee might submit a self-evaluation one week before the meeting. Both parties should prepare supporting evidence such as dashboards, tickets, PRs, project docs, and customer feedback. The employee should summarize results and context; the manager should compile outcomes against OKRs/KPIs and observed behavior examples aligned to the rating anchors.

Share a short agenda in advance: highlights; goals and results; competencies and behaviors; strengths and growth areas; the development plan; and next-period priorities.

Manager training checklist

  • Practice SBI feedback and bias mitigation (halo/horns, leniency, recency).
  • Calibrate with sample reviews before go-live.
  • Optional AI support: Use only authorized tools and approved handling for sensitive review material. Check summaries and themes against source evidence before sharing; assess identifying details and intended recipients (ICO identifiability guidance).

Calibration meeting agenda + variance analysis worksheet

Use calibration to compare rating rationales against shared anchors and discuss differences in evidence and context.

Agenda

  1. Confirm rating scale and anchors.
  2. Review rating patterns and outliers by team/level; do not change ratings to meet a distribution quota.
  3. Allow evidence-based discussion; 10–15 minutes per outlier is an adaptable planning example.
  4. Align on final ratings and promotion nominations.
  5. Document rationale and follow-ups.

Variance metrics

  • Mean and standard deviation by team/level.
  • Calibration variance: Percent of ratings changed; 10–25% is an optional local planning example, not a quota or validated benchmark.
  • Gap checks: Compare average ratings by gender/location/underrepresented groups and investigate differences. Before sharing, assess whether subgroup details or comments identify people to recipients; removing names alone is insufficient (ICO guidance).

Worksheet inputs

  • Pre- vs post-calibration ratings, comments, evidence links, and decision notes.

Timeline: pilot, feedback, full rollout, and governance

The schedule below is an illustrative planning option. Adapt dates, pilot size, and training time to your organization and review requirements.

  • Week 0–2: Draft templates, anchors, and guidance; legal review for probation/PIP sections.
  • Week 3–4: Pilot with 1–2 teams; run a mock calibration; collect feedback.
  • Week 5: Update templates; publish how-to guides; train managers.
  • Week 6–8: Full rollout; support hours and office hours; monitor completion and variance.
  • Post-cycle: Debrief; log learnings; version templates and store in a central repository with access controls.

When to evaluate software: Documents or spreadsheets may still suit a lightweight cycle. Evaluate alternatives if chasing submissions, compiling review material, collecting multi-rater feedback, or preparing calibration becomes a bottleneck.

Compare requirements for reminders and approvals; multi-rater/360 collection; analytics and calibration views; granular permissions and audit logs; integrations with your HRIS, SSO, chat, and document tools; and goal/OKR/KPI tracking. Assess these against your actual workflow and access needs rather than assuming an upgrade is necessary.

Privacy, DEI, and compliance essentials

Build privacy, accessibility, and job-related documentation into templates and training, adapting them to applicable requirements. These practices do not replace a fair procedure: Acas guidance for Great Britain, for example, says dismissal requires one and should be a last resort.

Probation and corrective action: documentation and legal considerations

  • Tie feedback to job duties and objective evidence; avoid personal traits.
  • Record training and support provided; include dates and artifacts.
  • Agree reasonable timelines, measurable expectations, and check-in frequency for the situation; discuss understanding and employee context.
  • Follow jurisdictional rules on notice, representation, and termination.
  • Set reviewer roles, including HR where appropriate, under the applicable process. Record employee comments and the route for requesting further review. Acknowledgement confirms receipt or discussion, not agreement with the assessment or decision.

Data retention, localization, and accessibility best practices

  • Set a retention schedule by record type and purpose, considering applicable requirements. Separately, collect only information needed for the defined purpose.
  • A recommended review packet includes completed self/manager forms, goals/OKRs and results, evidence links or attachments, calibration notes where applicable, and the follow-up plan. Apply this section’s purpose, access, and retention guidance to each component.
  • Limit access to authorized reviewers with a defined need; review permissions and access logs. Consider both the information and its recipients before sharing (ICO identifiability guidance).
  • Use inclusive, plain language; offer accessible formats and screen-reader-friendly docs.
  • Localize competencies and examples where needed; avoid idioms and culture-specific references.

Measure impact: KPIs to track review quality and fairness

Track a small set of KPIs to identify questions for each cycle. Compare like periods and populations; record denominators, survey response rates, and role/tenure context. Follow up with qualitative explanations for differences. Scores or demographic gaps alone do not prove fairness or ROI; ROI also requires costs and attributable benefits.

Completion rate, cycle time, calibration variance, sentiment, promotion parity

Use these KPI definitions for your operating dashboard. Choose any targets locally; the numbers below are optional examples, not validated benchmarks.

  • Completion rate: On-time submissions as a share of expected submissions; an illustrative local target is ≥95%.
  • Cycle time: Days from kick-off to final sign-offs; reduce admin drag each cycle.
  • Calibration variance: Percent of ratings changed; monitor outliers by team/level.
  • Sentiment: Post-review survey on clarity and fairness; an illustrative local target is ≥4.2/5.
  • Promotion parity: Compare promotion rates by demographic and location; investigate gaps beyond role/tenure mix. Before sharing subgroup reports, assess identifying details and recipients—not just whether names were removed; see privacy guidance.

Continuous improvement loop: iterate templates with data

  • After each cycle, review metric trends and appropriately protected feedback. Removing names alone does not establish anonymity; assess comments, subgroup details, and what recipients could link to individuals (ICO guidance).
  • Update anchors where confusion was highest; add examples to tricky competencies.
  • Trim questions no one uses; auto-fill data from OKRs/HRIS to cut repetition.
  • Re-train managers on two weak areas (for example, evidence quality, hard conversations).
  • Version templates and changelog updates for transparency.

FAQs about performance review templates

What should be included in a performance review template?

A strong performance review template covers the essentials needed for fair, comparable evaluations.

Include:

  • Role and review period details.
  • Goals/OKRs with outcomes and evidence.
  • 4–6 core competencies with 1–5 behaviorally anchored rating scales.
  • Achievements and growth areas with specific examples.
  • Overall rating and calibration notes.
  • Next-period goals and development plan.
  • Sign-offs and date stamps.

Which rating scale is best (and when)?

Choose the simplest scale that still supports calibration and decisions.

Four ordered categories (1–4) have no single central category; five (1–5) allow a central category that can be defined as Meets expectations. Decide whether that central category fits your review decisions. Category count alone is not evidence of faster calibration or less bias.

  • 1–5 with BARS: Offers more rating distinctions, but requires clear role-relevant anchors and shared interpretation; the samples here are not validated bias-reduction tools.
  • 3-point (Below / Meets / Exceeds): Simpler to complete and discuss, but less granular; consider whether that is enough for your review decisions.
  • Narrative-only with anchors: Useful when qualitative impact needs explanation; include behavioral examples and decision criteria so reviewers have a shared basis for discussion.

How do I adapt templates for remote teams?

Make your templates evidence-first and async-friendly to reflect how remote work gets done.

  • Make evidence link-first: docs, dashboards, tickets, and recordings.
  • Add prompts about async communication and time-zone handoffs.
  • Encourage more peer input to replace lost hallway context.
  • Use written summaries before the live conversation so people can process and respond thoughtfully.

Explore Our Latest Blog Posts

See More ->
Ready to get started?

Use AI to help improve your recruiting!