
A performance review template is a repeatable framework for recording performance evidence and guiding a discussion. It may include results, competencies, strengths, development needs, employee comments, goals and support commitments.
A strong template promotes consistency while allowing enough space for job-specific evidence. It separates observed behavior from assumptions and connects ratings to defined expectations. The completed document should help both manager and employee understand what happened during the review period and what comes next.
Choose a consistent rating scale if ratings are required. For example:
| Rating | Definition |
|---|---|
| 5 — Exceptional | Consistently delivers results significantly beyond the defined requirements |
| 4 — Exceeds expectations | Frequently goes beyond requirements with strong, reliable results |
| 3 — Meets expectations | Consistently fulfills the established requirements of the role |
| 2 — Partially meets expectations | Meets some requirements but improvement is needed in defined areas |
| 1 — Does not meet expectations | Does not meet essential requirements despite clear expectations and support |
| N/A | Insufficient opportunity or evidence to evaluate |
Define the scale before the review period whenever possible. A “3” should represent successful performance, not an unofficial failure. Every rating should be supported by specific evidence, and employees in comparable roles should be assessed against consistent criteria.
Use this concise form when the organization needs a basic record of results and future priorities.
Employee information
Employee name:
Job title:
Department:
Manager:
Review period:
Review date:
Performance summary
Most important responsibilities during this period:
Major accomplishments:
Commitments not completed and relevant context:
Overall rating, if used:
Core areas
Quality and accuracy — Rating/evidence:
Productivity and execution — Rating/evidence:
Communication — Rating/evidence:
Collaboration — Rating/evidence:
Reliability — Rating/evidence:
Next steps
Continue:
Improve or change:
Goal before next review:
Support the manager will provide:
Employee comments:
Use this before a manager review to collect the employee's perspective and surface accomplishments that may not be visible.
Role and review period
Employee name:
Job title:
Review period:
Results
What were your three most important goals or responsibilities?
What results did you achieve? Include evidence or metrics where appropriate.
Which accomplishment are you most proud of, and why?
What did not go as planned? What did you learn?
Ways of working
How did you contribute to team or organizational priorities?
Describe one example of effective collaboration.
Describe one difficult decision or problem you handled.
Development and support
Which skill did you strengthen?
Where would additional practice, information or feedback help?
What support or resources do you need from your manager?
What goals do you propose for the next period?
Employee summary:
Use this lightweight template for regular conversations so the annual review contains fewer surprises.
Quarter:
Employee:
Manager:
Progress since the previous check-in
Goals completed or on track:
Evidence of progress:
Priorities that changed:
Key learning:
Current work
Highest-priority deliverables:
Risks or roadblocks:
Decisions needed:
Workload or capacity concerns:
Feedback
One behavior or result to continue:
One specific adjustment to make:
Employee feedback for the manager:
Commitments before the next check-in
| Commitment | Owner | Due date | Success measure |
Use this format to assess progress halfway through an annual cycle and adjust goals that are no longer relevant.
Employee and review details
Name and role:
Manager:
Review period:
Goal review
| Goal | Original success measure | Current status | Evidence | Adjustment needed |
Strengths demonstrated
Strength:
Example:
Impact:
Development priority
Skill or behavior:
Current evidence:
Desired standard:
Practice or action:
Manager support:
Review date:
Second-half priorities
Priority:
Priority:
Priority:
Employee comments:
Use this comprehensive template to summarize the full review period and establish the next cycle's expectations.
Review information
Employee name and title:
Department:
Manager:
Review period:
Date:
Results against goals
For each goal, record the original expectation, result, supporting evidence and rating if applicable.
| Goal | Expected result | Actual result | Evidence | Rating |
Role competencies
Job knowledge — Evidence/rating:
Quality — Evidence/rating:
Execution — Evidence/rating:
Communication — Evidence/rating:
Collaboration — Evidence/rating:
Judgment and problem-solving — Evidence/rating:
Customer or stakeholder focus — Evidence/rating:
Overall assessment
Most significant contribution:
Consistent strengths:
Most important development area:
Overall rating and rationale, if used:
Next review period
Goal 1 and success measure:
Goal 2 and success measure:
Goal 3 and success measure:
Development action:
Manager commitment:
Employee comments:
Acknowledgment/signatures, if required by policy:
Use this during onboarding to evaluate clarity, integration and early progress rather than expecting full-role mastery immediately.
Employee:
Role:
Manager:
Checkpoint: 30 / 60 / 90 days
Role clarity
Does the employee understand the role's main responsibilities?
Are success measures clear?
Which expectations need clarification?
Onboarding progress
Required training completed:
Systems or processes learned:
Relationships established:
Early contributions:
Performance observations
What is going well?
Where is additional practice needed?
Is the employee receiving enough feedback?
Are tools, access and documentation adequate?
Employee perspective
What has been different from your expectations?
What remains confusing?
What would help you contribute more effectively?
Next checkpoint plan
Priority:
Success indicator:
Support owner:
Date to revisit:
Use this to collect focused observations from colleagues. Ask reviewers to comment only on work they directly observed.
Person receiving feedback:
Reviewer relationship or project:
Observation period:
What work did you complete together?
What did this person do that helped the team or project succeed?
Provide one specific example of effective communication or collaboration.
What behavior could make future collaboration more effective?
What should this person continue doing?
Is there relevant context the manager should understand?
Evidence standard: Describe observed behavior and impact. Avoid personality labels, rumors or comments unrelated to job performance.
Use this immediately after an important project while decisions and results are still fresh.
Project details
Project:
Employee role:
Project dates:
Reviewer:
Intended outcome:
Delivery assessment
Scope owned by the employee:
Result delivered:
Quality evidence:
Schedule and budget performance:
Stakeholder feedback:
Ways of working
Planning and prioritization:
Risk management:
Communication:
Collaboration:
Adaptability:
Retrospective
What worked well?
What would improve the next project?
What conditions were outside the employee's control?
Which lesson should be applied elsewhere?
Follow-up action and owner:
Use this for roles with defined quantitative targets. Metrics should be interpreted with context and should not replace qualitative judgment.
Employee:
Period:
Manager:
| Goal or KPI | Definition | Target | Actual | Data source | Context | Status |
Analysis
Which results were strongest, and what contributed to them?
Which target was missed, and what factors contributed?
Did metric definitions, data quality or priorities change?
Were results achieved in a sustainable and appropriate way?
What leading indicator should be monitored next?
Next-period goal
Goal:
Baseline:
Target and date:
Data source:
Key actions:
Dependencies:
Use this to evaluate both team outcomes and the behaviors required to lead people fairly and effectively.
Manager:
Team/function:
Reviewer:
Period:
Business and team results
Priority outcomes:
Results and evidence:
Resource or operating constraints:
Leadership areas
Sets clear expectations — Evidence/rating:
Gives timely, useful feedback — Evidence/rating:
Makes fair and transparent decisions — Evidence/rating:
Develops team capability — Evidence/rating:
Delegates appropriately — Evidence/rating:
Supports inclusion and respectful work — Evidence/rating:
Manages risk and accountability — Evidence/rating:
Communicates organizational context — Evidence/rating:
Team indicators
Retention or staffing context:
Engagement themes:
Internal development or promotion:
Delivery and quality trends:
Development plan
Leadership behavior to strengthen:
Action:
Evidence of progress:
Support from the reviewer's manager:
Use this separately from, or alongside, a performance rating to discuss future growth without implying a guaranteed promotion.
Employee:
Current role:
Manager:
Discussion date:
Career direction
Work the employee wants to do more of:
Skills the employee wants to build:
Possible future roles or responsibilities:
Time horizon:
Current evidence
Strengths relevant to that direction:
Experience already demonstrated:
Gaps to address:
Employee interests that require further exploration:
Development actions
| Action | Skill or experience | Owner | Target date | Evidence of learning |
Possible actions include a stretch assignment, mentoring, job shadowing, formal training, presenting work, leading a meeting or practicing a skill with feedback.
Manager commitments:
Employee commitments:
Date to revisit:
Templates improve consistency by prompting reviewers to cover comparable evidence and expectations. They save preparation time, make conversations easier to structure and create a record of goals and support commitments.
They can also improve feedback quality. A well-designed form asks for examples, impact and future action rather than encouraging unsupported labels. For employees, receiving the template in advance can reduce uncertainty and allow thoughtful self-reflection.
Write “Sent weekly risk updates before the leadership meeting” instead of “Has a good attitude.” Observable examples are easier to understand and act on.
Explain why the example matters: “The early update allowed finance to correct the forecast before the review.” Impact adds meaning without exaggeration.
Review goals, work samples, metrics, stakeholder feedback and notes from prior check-ins. Do not rely only on the most recent event.
Evaluate employees against documented role requirements, not against different personal preferences. Review language for bias and confirm that similar performance receives similar treatment.
Replace “Improve communication” with a clear next step, such as “Send a decision summary with owner and due date within one business day of each project meeting.”
Development is not solely an employee obligation. Record what access, coaching, training or priority decisions the manager will provide.
Positive result: “Jordan completed the inventory migration two weeks before the revised deadline and documented the validation process, allowing the operations team to reconcile records without additional support.”
Constructive feedback: “Three monthly reports required corrections because source definitions were not confirmed before analysis. Before the next cycle, Jordan will use the approved data dictionary and complete a peer check; the manager will arrange access to the reporting specialist.”
Goal: “By December 15, Priya will lead two customer-discovery sessions and produce a findings summary using the team's approved research template. Success will be measured by completion, stakeholder review and documented application of at least one insight.”
Saving all feedback for the formal review
Using personality judgments instead of work evidence
Allowing one recent event to dominate the entire period
Rating people against unwritten expectations
Giving identical generic comments to every employee
Ignoring circumstances outside an employee's control
Treating metric achievement as the only measure of performance
Promising a promotion or compensation change without authority
Recording sensitive personal information unrelated to the job
Using a signature as proof that the employee agrees, unless policy explicitly defines it that way
Dokie can help managers and employees turn approved performance information into a structured review presentation, self-evaluation or development-plan deck. Users can organize goals, evidence, achievements, feedback and next steps in a consistent narrative that is easier to discuss during a review meeting.
Dokie also supports editable slides and PowerPoint export, which can help HR teams present review frameworks or managers summarize team-development plans. Protect confidential personnel information, restrict access appropriately and verify every rating, quotation and metric against authorized records before sharing.
Organizations may use annual or semiannual formal reviews supported by more frequent check-ins. The right cadence depends on the role, organization and policy, but important feedback should not wait for a yearly meeting.
No. Some organizations use narrative feedback and goal discussions. If ratings are used, define the scale, train reviewers and require evidence for each judgment.
Include major responsibilities, outcomes, evidence, lessons, development needs and proposed goals. Provide context without overstating results or avoiding responsibility.
Organizations should follow their policies and applicable law. Managers should involve HR before using a review for corrective action and should not introduce serious concerns for the first time without prior feedback when earlier communication was possible.
That depends on the organization's policy and wording. Many forms use a signature only to acknowledge receipt and discussion, not agreement with every statement.
Use job-related criteria, collect evidence across the entire period, compare similar roles consistently, seek appropriate calibration and review language for subjective or identity-based assumptions.