Most performance reviews fail before they start. You wait until the annual review to tell someone they're underperforming. You use vague language ("communication skills need work") that means nothing to the employee. You have no written record, so next year you can't remember what you discussed.
Remote performance reviews fail even faster. You can't observe someone's work in real time. You don't see if they're struggling. You can't coach them in hallway conversations.
The fix: a written, structured performance review that happens quarterly, uses specific evidence, and gives the employee a clear path forward.
This template is designed to be filled out in 30 minutes and used year-round. Copy it. Use it. Improve it based on your actual needs.
---
Why Most Performance Reviews Fail
Before we get to the template, understand what breaks them:
1. No written record. You have a conversation, forget half of it, and next quarter can't remember what was discussed. The employee does the same thing. Then when you need to document a firing or demotion, you have nothing.
2. Vague feedback. "You need to improve your communication" or "You're not a team player" are unmeasurable. The employee nods and leaves with no idea what to actually change.
3. Once-a-year timing. If you review someone once a year, you miss the chance to redirect them when it matters. Good feedback happens in real time, documented quarterly.
4. No tie to actual outcomes. Reviews that say someone "isn't meeting expectations" but never define what the expectations were are legally risky and demoralizing.
5. Different standards for different people. One employee gets "exceeds expectations" for hitting 80% of their goals, another gets "meets expectations" for hitting 90%. Your standards are all over the place.
The template fixes these by being specific, evidence-based, written, and repeatable.
---
The Performance Review Template
Copy and paste this for each employee. Fill it out once per quarter, or annually if quarterly feels like too much.
---
PERFORMANCE REVIEW
Employee: [Name] Review Period: [Dates] Reviewer: [Your name] Review Date: [Date completed]
---
PART 1: GOALS REVIEW
At the beginning of this review period, we set these goals:
| Goal | Expected Outcome | Achieved? | Notes | |------|------------------|-----------|-------| | Goal 1 | [What success looks like] | Yes / Partial / No | [What happened] | | Goal 2 | [What success looks like] | Yes / Partial / No | [What happened] | | Goal 3 | [What success looks like] | Yes / Partial / No | [What happened] |
Overall Goals Rating: (Circle one) - 5 - Exceeded: All or nearly all goals achieved, with measurable impact beyond scope. - 4 - Achieved: All goals achieved as defined. - 3 - Partially Achieved: 50-75% of goals achieved, or some goals partially completed. - 2 - Minimally Achieved: Less than 50% of goals achieved. - 1 - Not Achieved: Goals not achieved; significant misalignment with role expectations.
Context: [Why did goals succeed or fall short? External factors? Resource constraints? Roadblocks?]
---
PART 2: COMPETENCIES
Below are core competencies for this role. Rate [Employee] on each. Use the rubric:
- 5 - Exceptional: Consistently performs at the highest level, mentors others, sets the standard.
- 4 - Strong: Consistently meets or exceeds expectations; reliable.
- 3 - Proficient: Meets role expectations; competent and dependable.
- 2 - Developing: Below expectations; showing improvement but not yet proficient.
- 1 - Needs Improvement: Significantly below expectations; immediate focus needed.
A. Communication
Definition: Clearly documents work, asks clarifying questions, responds to messages promptly, explains decisions, listens to feedback.
Rating: (Circle one) 5 / 4 / 3 / 2 / 1
Evidence: - [Specific example of strong or weak communication] - [Example from Slack, email, or documentation they've written] - [How they've handled a misunderstanding or question]
---
B. Reliability
Definition: Delivers on commitments, meets deadlines, maintains consistent output, shows up for meetings, owns follow-through.
Rating: (Circle one) 5 / 4 / 3 / 2 / 1
Evidence: - [How many deadlines did they miss? How many did they hit?] - [Specific project or deliverable they were responsible for] - [Pattern of responsiveness or lack thereof]
---
C. Output Quality
Definition: Work meets or exceeds the standard for the role; attention to detail; requires minimal rework; customer/stakeholder satisfaction.
Rating: (Circle one) 5 / 4 / 3 / 2 / 1
Evidence: - [Specific work product or project] - [Customer or stakeholder feedback] - [Revisions needed, or if none, why quality is high]
---
D. Initiative
Definition: Identifies problems without being told, proposes improvements, takes on work without waiting to be asked, continuous learning.
Rating: (Circle one) 5 / 4 / 3 / 2 / 1
Evidence: - [Examples of problems they've identified] - [Process improvements they've suggested or implemented] - [Learning or growth they've pursued]
---
Summary Competency Rating
Average the four ratings above. This is your overall assessment of how they're performing in the role.
Overall Rating: [Sum of 4 ratings / 4] - 4.0-5.0: Exceeding expectations - 3.0-3.9: Meeting expectations - 2.0-2.9: Developing / needs improvement - 1.0-1.9: Significantly below expectations
---
PART 3: DEVELOPMENT
What's Working Well
What is [Employee] doing that we want more of? Where are they strong?
- [Strength 1]
- [Strength 2]
- [Strength 3]
---
What Needs Improvement
Where can they grow? What's preventing them from moving from "meets expectations" to "exceeds"? Be specific.
- [Area 1: The specific behavior or skill]
- [Area 2]
For each, state: What does good look like? How will we measure improvement?
Area 1: [What they should do or improve] - Current state: [How it is now] - Target state: [How it should be by next review] - How we'll measure it: [Specific evidence we'll look for]
Area 2: [What they should do or improve] - Current state: [How it is now] - Target state: [How it should be by next review] - How we'll measure it: [Specific evidence we'll look for]
---
Goal for Next Review Period
Based on performance this period and development areas, here's the focus for the next [3-12] months:
Goal 1: [Specific, measurable outcome] Goal 2: [Specific, measurable outcome] Goal 3: [Specific, measurable outcome]
These goals should be: - Achievable (not a stretch so far they're demotivating). - Clear (the employee should understand exactly what success is). - Measurable (you can point to evidence of achievement). - Tied to role expectations or business needs.
---
PART 4: MANAGER NOTES & EMPLOYEE RESPONSE
Manager Notes (Confidential)
Any additional context for your files. This is for you and HR, not necessarily shared with the employee.
- [Assessment of whether they're a keeper, flight risk, promotion candidate, etc.]
- [Concerns or opportunities you're thinking about]
- [Next steps (if any) in terms of warnings, improvement plans, or promotion track]
---
Employee Response & Acknowledgment
Share this review with the employee. Ask them to read it and respond. Their response should include:
- Acknowledgment: Do they agree or disagree with this assessment? Why?
- Context: Anything they want the record to show about this period?
- Commitment: What will they do to address development areas in the next period?
Employee Name (print): ___________________________
Employee Signature: ___________________________
Date: ___________________________
Employee Comments:
[Space for them to write]
---
How to Use This Template
Frequency: Quarterly for new employees or those on performance improvement plans. Annually for solid performers.
Timing: Set a specific date (e.g., first Friday of April, July, October, January) and do them all at once.
Prep: Before the review, collect evidence. Save emails, Slack threads, finished work. Know what you're going to say.
The conversation: This template is your outline. Sit down (or video call for remote). Walk through it together. Ask their perspective. Make it a conversation, not a monologue.
The follow-up: Send them a copy. File a copy. Check in quarterly on development goals, even if you're not doing a full review.
Don't wing it: Using this template every time means your feedback is consistent, fair, and defensible.
---
Common Pitfalls to Avoid
Recency bias. Don't base the entire review on the last month. Look at the full period.
Comparing to others. Rate them against the job expectations, not against their peers. "Alex is better than Jordan at X" is unfair and creates resentment.
Vague language. "Good job" or "needs to improve communication" are useless. Use specific examples.
Sandbagging surprises. If someone is underperforming, they should hear about it before the review. Reviews should confirm what you've already discussed, not shock them.
Overstaying in development. If someone is in the "developing" category for two reviews and making no progress, that's a performance improvement plan (PIP), not a development area.
Forgetting to document the conversation. Keep your notes. If the employee disputes the review later, you have a record.
---
Making This Sustainable
One review takes 30–45 minutes to complete. Four employees = 2–3 hours total per quarter. That's worth it for clarity on who's working and who isn't, and for building a company culture where feedback is normal and expected.
Use the same template every time. Your consistency will improve. Your feedback will get sharper. Your employees will know exactly where they stand.
The Performance Standard has deeper frameworks for calibrating performance across teams, handling tough conversations, and building improvement plans—but this template is the foundation. [If you need help rolling this out or building a feedback culture at scale, we can help.](tantaholdings.com/consulting)
---
Related reading: - [How to Give Feedback to Employees: A Framework That Works](how-to-give-feedback-to-employees) - [Remote Employee Performance Management Guide](remote-employee-performance-management-guide) - [How to Manage Remote Employees Effectively](how-to-manage-remote-employees) - [How to Manage a Virtual Assistant Effectively](how-to-manage-a-virtual-assistant-effectively)