Performance review template: turn real work into fair feedback
Use this performance review template to turn real work into fair feedback, guide review conversations, and set clear goals with practical next steps.
A performance review template is a shared structure for turning work evidence and feedback into a fair conversation. It ends with clear next steps. For small teams, it works when it is simple enough to prepare before the meeting and specific enough to connect feedback to real examples.
In small teams, performance is rarely tidy. One person may handle customer support in the morning and product research after lunch. Another may carry coordination work that never appears in a roadmap. If the review depends on memory, recent problems can feel larger than steady progress.
Performance review template you can copy
Copy this template into a shared document and keep each answer brief and specific. Ask the employee and manager to prepare their notes before the meeting. During the conversation, agree on the next goal, the support needed, and a date to review progress.
Performance review — [Employee name]
Employee and role: [Name and role]
Reviewer: [Manager’s name]
Review period: [Start and end dates]
Work completed: [What were the main projects, tasks, and responsibilities during this period?]
Impact: [What changed for the team or customer?]
Evidence: [Links to work, results, and relevant feedback]
Strengths: [Which contributions or behaviours should continue?]
Growth area: [What could improve in the next review period?]
Next goal: [What outcome should the employee work toward next?]
Support needed: [What help, resources, or decisions are needed to reach that goal?]
Follow-up actions: [Agreed actions, with an owner and deadline for each]
Progress check: [Date to review progress together]
Start with evidence before feedback
The weakest performance reviews can sound confident and still feel unfair. Praise without examples feels nice for a moment. Criticism without a clear situation gives the person nothing practical to change.
Start with evidence from the review period. Go back to the work itself and choose examples that show what really happened. "You did a great job" should connect to a specific result worth repeating. "You need to communicate better" should point to a real moment. Maybe context arrived too late, or the next step was unclear. You are making the conversation specific enough that both people can discuss the same reality.
Use a simple base like this:
Field | Example |
|---|---|
Review period | January–March |
Role | Backend engineer |
Main work | Billing API and payment retries |
Strongest contribution | Stabilized retry logic during the March traffic spike |
Hardest part | Two payment providers changed APIs mid-sprint |
Evidence | PRs, incident notes, on-call rotation |
Next focus | Document the retry flow so the team can debug it without her |
Once the structure is in place, the manager no longer has to reconstruct three months from memory. The teammate can bring their own examples into the conversation.
Share the template before the meeting
A template works better when both people see it before the meeting. Otherwise, the review can feel like a live exam. The manager arrives with notes, and the employee reacts in real time.
Send the template a few days before the meeting. Ask the teammate to fill in their side first, with examples of proud work and places where they felt blocked. The manager can then add their own notes.
This changes the tone, turning the conversation into a comparison of perspectives rather than a surprise verdict. If both people name the same issue, the next step is easier. If they see the same period differently, the meeting has a clear place to begin.
Be careful with ratings
Ratings can make reviews easier to compare, but they often pull attention away from the actual work. If you use a scale, keep it simple and define each level clearly. "Meets expectations" should mean the same thing for every manager.
For small teams, a written example is often more useful than a number. Instead of giving a score for ownership, describe one situation where the person took responsibility. Add one place where the next step was unclear.
If results depended on pricing decisions or product readiness, discuss those dependencies alongside the employee’s contribution. Base the rating on what the employee could reasonably influence.
Make next steps visible
A performance review should end with something the team can return to later. Turn each follow-up into a visible task with an owner and a review date. If the review produces several follow-ups, turn feedback into an action plan. Record the agreed actions, owners, deadlines, and how progress will be checked.
For example, replace "Write clearer updates" with "Post a short launch status every Friday until the release." The person then knows what better looks like. If the person wants to grow into project ownership, name the project and the first responsibility.
The follow-up should be specific enough to check later without reopening the whole review conversation. A small table is usually enough:
Next step | Owner | When to review |
|---|---|---|
Document the retry flow for the team | Matt | End of next sprint |
Lead the first review of the new billing integration | Matt | Before product review |
Flag dependency changes earlier in the task thread | Matt + manager | Weekly check-in |
Keep the review anchored in real examples. Traits like “proactive” or “reliable” only help when they are tied to specific work. Recent problems can also take up too much space in the conversation. Check the full review period before turning one bad week into a performance pattern.
Use Vaiz to connect reviews with real work
Performance conversations are easier when the document points back to actual work. In Vaiz, you can create a review document and reference the relevant tasks inline. After the meeting, new tasks capture follow-up goals.
This gives feedback a visible trail. The manager can return to the examples behind the discussion. The teammate can see the next step in the same workspace where daily work continues.
Once you have clear next steps, the same evidence helps the team decide what to focus on next quarter without rebuilding context from scratch.
Try this setup with your team in Vaiz →
