How to Write a Performance Review: Guide for Small Business
How to write a performance review without HR. 7-step process, full SMB example, common mistakes, and the conversation script that makes the review land.
How to Write a Performance Review
A practical guide for small businesses without dedicated HR
The first time I had to write a performance review for a direct report, I sat in front of a blank document for ninety minutes and produced four paragraphs of recycled phrases that could have applied to almost anyone. "Strong communicator. Good team player. Takes initiative. Areas for development include strategic thinking and proactive communication." The employee read it, said thank you, and we both moved on. Three months later, when the same patterns I had glossed over became real problems, I realized the review had communicated nothing actionable. The phrases were technically true. They were also useless.
This is the central trap of writing performance reviews without HR support: most online guides give you a generic template and a list of phrases organized by competency, which feels comprehensive but produces reviews that all sound the same. The phrases are not the problem; the missing specifics are. Without concrete evidence connecting each phrase to actual work the employee did, the review becomes corporate filler that the employee forgets within days, the manager forgets within weeks, and nobody can find when it matters six months later.
This guide is different. It is written for small business owners and operators running 5-50 person companies who write reviews themselves because there is no HR team to do it for them. You will get the seven-step process I actually use, a complete SMB example showing what good looks like, the common mistakes that turn careful writing into useless reviews, and the conversation script that makes the review actually land. I built FirstHR for this audience because most performance management content assumes a level of HR sophistication small businesses neither have nor need.
What a Performance Review Actually Is
The simple working description: a performance review is the structured summary of conversations you have already been having with the employee throughout the period. The conversations should have happened in real time; the review documents the pattern. If issues are appearing in the review for the first time, the manager has waited too long to surface them.
Three things are true about every performance review that works. First, the evidence is specific. Each strength and development area includes the moment, the behavior, and the impact. Generic phrases produce no growth; specific evidence does. Second, the review does not surprise the employee. Issues raised for the first time in a formal review damage trust and rarely produce change. Third, the review spends meaningful time on development goals and the manager's commitments to support them. Reviews that focus only on past performance leave the employee with no path forward.
Most reviews fail one of those three tests. The evidence is vague ("strong communicator" with no examples). New issues appear without prior conversations ("I have been concerned about your responsiveness"). Or the goals section is thin ("continue developing leadership skills"). Each missing piece reduces the impact of the review. Missing all three is the norm, not the exception, which is why most reviews in most organizations produce nothing.
Why SMB Reviews Are Different
Most performance review guides are written for mid-market and enterprise HR managers writing reviews for employees they barely know, in companies with formal competency frameworks, calibrated rating scales, and HR business partners reviewing every word. None of that applies at small business scale. The owner-operator writing reviews knows the team intimately, has no formal competency framework, and is the only person reviewing the words.
Three implications for SMB reviews. First, generic templates are worse, not better. The team is small enough that everyone notices when reviews sound copy-pasted. A 12-person company where everyone gets "strong communicator, good team player, takes initiative" produces cynicism within one cycle. The reviews need to feel observed, not applied.
Second, the manager has direct context most enterprise reviewers do not. You have probably been in the same meetings as the employee, seen the customer interactions, read their email replies. Use this context: write reviews based on real observation, not on what HR forms expect you to evaluate. SMB reviews are a major opportunity to do something enterprise reviews cannot do, which is to be specific about real work.
Third, the review is the documentation. At enterprise scale, the formal review is one piece of a larger performance management system. At SMB scale, the review may be the only formal record of the conversation, and may eventually be the only documentation if the employee disputes a termination or promotion later. This raises the bar on specificity and legal-safe language, even though small businesses often pay less attention to those concerns. SHRM's performance management toolkit covers the broader principles, but the SMB-specific application is that every review is potentially legal documentation.
The 6 Sections of an Effective Performance Review
Every effective review contains six sections, working together. Skipping any one weakens the review; including all six in coherent form produces a document that drives behavior change.
The proportions matter. Strengths should occupy 30-40% of the review, development areas 20-30%, goals and commitments 30-40%. Reviews where strengths get 70%+ feel like soft promotion documents; reviews where development areas dominate feel punitive. The balance signals that the review is honest both ways.
For broader context on what performance reviews are and where they fit in the larger performance management practice, the performance review guide covers the full system that reviews are one part of. This article focuses specifically on writing them well.
Before You Start Writing
Most review failures happen before the writing starts. The manager begins drafting without enough evidence, without the employee's self-assessment, and without a clear summary in mind. Each missing input reduces the quality of the resulting review by 30-50%.
| Pre-writing input | Why it matters | How to collect |
|---|---|---|
| Concrete evidence (8-12 observations) | Without specifics, every claim becomes vague boilerplate. The evidence is the substance of the review | Keep a running feedback log per direct report; collect 4-6 weeks before review writing starts |
| Employee self-assessment | Surfaces context you may have missed; signals what the employee thinks is important; reduces conversation asymmetry | Send a 1-page template 2-3 weeks before the review; ask for strengths, gaps, goals |
| Peer or cross-functional input | Especially valuable for cross-functional roles; catches blind spots | Ask 2-3 colleagues for one strength and one development area; informal works fine |
| Customer or external feedback | For customer-facing roles, customer reactions are the most honest performance signal | Collect throughout the year; reference specific customers and incidents |
| Goal progress from prior review | Anchors the new review in commitments made before; ensures continuity | Pull the previous review; review goal progress before starting |
| Your own observations across the period | Your direct view of the work; harder to remember without notes | 5-10 minutes per week recording observations beats trying to remember at year-end |
The single most useful pre-writing practice: keep a running feedback log per direct report throughout the period. A simple shared doc with 1-2 sentence observations as they happen produces 50-80 specific examples to draw from at review time. The investment is 30-60 seconds per observation; the compound benefit is reviews that write themselves because the evidence is already collected. Gallup research on managers consistently finds that the strongest manager-employee relationships are built on ongoing feedback, not periodic reviews.
The 7-Step Writing Process
The process below produces reviews that drive behavior change. The total time investment is 90-120 minutes per direct report once you have practice, plus 30-45 minutes for the conversation. Skipping steps produces lower-quality reviews, regardless of how good the template is.
Two failure modes to avoid during the writing process. First, do not skip Step 2 (asking for self-input). Most managers write the review first and read the self-assessment after, which means they often miss context the self-assessment would have surfaced. Second, do not skip Step 7 (sleep on it). Reviews written and sent the same day often contain at least one paragraph the manager later regrets. The 24-hour gap is short but produces meaningfully better reviews.
Writing the Summary Statement
The summary statement is 2-3 sentences capturing the overall picture: trajectory, biggest contribution, key development area. Most managers either skip it (jumping straight into details) or pad it with vague phrases like "overall a strong year" that say nothing. The summary should stand alone if the employee reads only the first paragraph.
| Vague summary (avoid) | Specific summary (use) |
|---|---|
| Overall a strong year with some areas to develop | Maria expanded our mid-market portfolio from 18 to 25 accounts while maintaining 92% NRR. Her biggest contribution was leading the Q3 customer health review program. Primary development area: cross-functional escalation handling at the senior level |
| Made progress against goals; continuing to develop | James shipped 3 of 4 quarterly priorities and launched the new ticketing system on time, but the migration to the data warehouse slipped 6 weeks due to scope creep. Goal for next period: tighter scope discipline on infrastructure projects |
| A solid contributor with growth potential | Sarah delivered 47 PRs at an average of 1.2 review cycles each (best on the engineering team). Took ownership of the payments incident in Q3, identifying root cause within 4 hours. Ready for senior IC scope in 2027 |
| Strong year, room to grow | Tom hit 142% of quota across mid-market accounts and expanded 4 of his accounts into multi-product deals. Growth area: enterprise account preparation, particularly multi-stakeholder navigation |
The pattern: vague summaries describe sentiment; specific summaries describe what happened. The specific version names actual outcomes (24 to 25 accounts, 92% NRR, 47 PRs, 142% of quota) and the headline contribution (the customer health review program, the payments incident, the multi-product expansion). The investment to write a specific summary is 5-10 minutes; the payoff is a review that opens with substance instead of decoration.
For the broader practice of using specific phrases throughout the review, the employee review keywords guide covers categorized phrase banks for SMB reviews that you can adapt with specifics.
Documenting Strengths with Specific Evidence
Strengths are where most reviews fail by writing generic praise instead of specific observations. "Strong communicator" tells the employee nothing about what behavior earned the phrase or what behavior to repeat. Strengths section needs the same specificity discipline as development areas, even though it feels less risky to skip the specifics on positive feedback.
Each strength should follow the situation-behavior-impact pattern. The situation grounds the claim in shared reality. The behavior describes what the person actually did, in observable terms (no interpretation). The impact connects the behavior to outcomes. The pattern draws structurally on the SBI feedback model from the Center for Creative Leadership; the SBI feedback model guide covers the framework in depth.
| Strength | Situation-Behavior-Impact |
|---|---|
| Customer relationship depth | On the Acme renewal in Q3, when the CTO raised concerns about API stability, you took ownership, partnered with engineering, and produced a 90-day roadmap that closed a $40K renewal |
| Process building | You designed and implemented the quarterly customer health review process, now run across the company. The format made customer health visible to leadership in a way it had not been before |
| Mentorship | You onboarded both new CSMs hired in 2026, including weekly 1:1s and structured ramp plans. Both reached full account ownership in 8 weeks vs. the previous 12-14 week ramp |
| Technical judgment | On the Q2 architecture review, you flagged the scaling risk in the proposed approach, ran the load test that confirmed the risk, and proposed the alternative we shipped. Saved us from rebuilding 6 months later |
| Crisis response | When the payments outage hit on Friday afternoon, you led incident response within 30 minutes, identified the root cause in the API logs, and shipped a fix by end of day. Customers noticed and one renewal call cited the response specifically |
Three rules for documenting strengths. First, name the specific situation and date or quarter. Second, describe what the person did in observable terms (a video camera could have captured it). Third, name the concrete impact: customer reactions, time saved, revenue protected, team effects. Without all three, the strength becomes generic praise that the employee cannot use.
Identifying Development Areas Honestly
Development areas use the same situation-behavior-impact pattern as strengths, but with the added requirement that the issue should not be a surprise. Every development area should already have been discussed in real time during the period. The review documents the pattern; it does not introduce it.
| Development area | Situation-Behavior-Impact (with metric) |
|---|---|
| Cross-functional escalation handling | Three escalations this year (Beta in Q2, Gamma in Q3, Delta in Q4) hit engineering 3-5 days later than ideal because customer signal was not surfaced early. Goal: surface technical escalations to engineering within 24 hours |
| Strategic communication to leadership | Weekly status updates have been operationally accurate but light on strategic context. We are missing patterns that could inform product investment. Goal: include 1-2 strategic observations per week tied to specific customer accounts |
| Sprint commitment discipline | Three of seven sprints had blockers raised after the team had already been blocked for 3-5 days. Goal: surface blockers within 24 hours by including a 'risks' check at each daily standup |
| Stakeholder management | On the Q3 launch, three internal stakeholders learned about scope changes in the same week as customers. Goal: stakeholder communication plan documented at project kickoff for any cross-functional initiative |
Two patterns from these examples worth noticing. First, every development area names a metric or specific incident pattern. "3-5 days," "three of seven sprints," "same week as customers" make the issue testable rather than subjective. Second, every development area includes a forward-looking goal with a target metric. Without the goal, the development area becomes a complaint; with the goal, it becomes a development plan.
For the broader practice on giving constructive feedback that lands, including how to surface issues in real time before they become development areas in the formal review, the employee feedback guide covers the full feedback toolkit at SMB scale.
Setting Goals for the Next Period
The goals section is what turns the review from a backward-looking document into forward-looking development planning. Most reviews underweight this section, treating goals as an afterthought. The strongest reviews allocate 30-40% of their content to goals and the manager's commitments to support them.
| Vague goal (avoid) | Specific goal (use) |
|---|---|
| Continue developing leadership skills | Mentor 2 junior team members through their first 90 days, including weekly 1:1s and structured ramp plans |
| Improve strategic thinking | Develop and present a 12-month roadmap for the support function to leadership in Q3, including 2-3 strategic recommendations |
| Be more proactive in communication | Surface project blockers within 24 hours of identification through written updates in our project channel |
| Build technical depth | Complete the cloud architecture certification by Q2 and lead one infrastructure project end-to-end with measurable performance outcomes |
| Strengthen client relationships | Expand 3 mid-market accounts into multi-product deals worth $30K+ ARR each by Q3 |
The pattern: vague goals describe a direction; specific goals describe a destination with a timeline. The specific goal includes the activity, the scope, and the success measure. The investment to make a goal specific is 2-3 minutes per goal; the payoff is a goal that actually moves over the next period.
For the broader practice of writing development goals that produce growth, particularly across multiple periods, the individual development plan guide covers the IDP framework that complements quarterly and annual review goals. Goals in the review and goals in the IDP should be consistent; the IDP is the longer-arc version of what the review goals point toward.
Vague vs Specific Throughout the Review
The single largest determinant of review quality is whether the language is specific or vague. Below are common review phrases and their specific equivalents. The vague version is technically defensible and produces nothing; the specific version commits to a position and produces growth.
| Vague phrase (avoid) | Specific evidence (use) |
|---|---|
| Strong communicator | Led the Q3 client renewals project with weekly status updates that surfaced the integration risk three weeks early; saved an estimated 5 days of rework |
| Good team player | Volunteered to onboard the two new engineering hires this quarter, reducing their ramp time by approximately 3 weeks each |
| Takes initiative | Identified the duplicate-invoice pattern costing 6 hours of manual work weekly and built the screening checklist now used by the whole team |
| Detail-oriented | Caught three pricing errors in client contracts before they shipped, preserving an estimated $12K in revenue this quarter |
| Needs to be more proactive | Wait time for raising blockers averaged 4-5 days this quarter; team estimates need to surface within 24-48 hours to keep sprints on track |
| Could improve communication | Internal email response time has averaged 2-3 days; clients reported needing faster turnaround on three escalations this quarter |
| Has good leadership potential | Mentored two junior team members through their first 90 days, including weekly 1:1s and structured ramp plans, both of whom are now contributing independently |
| Reliable performer | Delivered all 14 client onboarding handoffs on time this quarter without missed deadlines, including two during the August launch crunch |
The pattern: vague phrases describe attributes; specific phrases describe events with consequences. The cost of vague language is reviews that all sound the same and produce no behavior change. The cost of specific language is the reviewer must commit to specific observations that the employee may push back on. The risk is the point. Reviews that feel safe to write rarely produce change; reviews that commit to specific observations rarely fail to.
A Complete SMB Review Example
The example below shows a complete annual review for a customer success manager at a small business. Names and specifics are illustrative; the structure and specificity discipline are what matter.
Three patterns in this example worth noticing. First, every section is anchored in specifics: account counts, NRR percentages, ramp times, dollar figures, account names. Without these specifics, the review becomes generic. Second, the development areas are named with the same precision as the strengths. The 3-5 day escalation delay is testable; the strategic observation goal is concrete. Third, the manager's commitments are explicit: budget, time, access. Without manager-side commitments, the goals become the employee's problem alone and rarely move.
Adjusting for Different Review Types
Different review contexts call for different lengths and emphases. An annual review is comprehensive; a quarterly check-in is targeted; a probationary review is evidence-heavy. The structure stays consistent (the six sections), but the depth and tone adjust to the context.
| Review type | Focus | Length | Caution |
|---|---|---|---|
| Annual review | Full-year summary + goals for next year | 600-800 words | Comprehensive but should not surprise the employee with new issues |
| Quarterly check-in | Last quarter + adjustments | 200-300 words | Targeted; 2-3 strengths, 1-2 development areas |
| Mid-year review | Course correction halfway through year | 400-500 words | Document any performance gaps early; do not wait for year-end |
| 30-60-90 day review | New hire ramp progress | 300-400 words | Trajectory-focused; avoid harsh judgments while ramping |
| Project retrospective | Single project performance | 200-300 words | Stay within project scope; do not expand to general personality |
| Probationary review | Pass/fail decision on continued employment | 500-700 words | Direct, evidence-based, legally defensible; document everything |
The single most important rule across review types: do not surprise the employee with new criticism in any formal review, regardless of length. Issues should have been raised in real time, with the formal review serving as the structured summary of conversations that have already happened. This is especially critical for probationary and annual reviews, where the formal document may become legal evidence later.
For the 360 feedback context, where multiple raters contribute input to a single review, the 360 feedback guide covers how to structure the input collection so the resulting review has consistent voice and avoids the patchwork-quilt effect of multiple raters.
For the year-end context specifically, where the review covers the full annual cycle and often informs compensation decisions, the year-end review guide covers the additional considerations for full-year reviews.
Delivering the Review in Conversation
Even the best-written review fails if it is delivered poorly. The written document is half of the review; the conversation is the other half. Most managers either skip the conversation (sending the review by email and hoping it lands) or run the conversation as a one-way reading of the document. Both approaches reduce the impact of careful writing.
| Stage | What to say | Why it works |
|---|---|---|
| Setup | "I want to walk you through your review. I'd like us to discuss it together rather than just have you read it." | Sets the conversation as collaborative, not a verdict |
| Strengths first | "Let me start with what has been working well this period." | Establishes psychological safety before any criticism |
| Each strength | "On the Q3 client renewals project, when you delivered weekly status updates that surfaced the integration risk three weeks early, we saved an estimated 5 days of rework." | Specific evidence produces real recognition, not generic praise |
| Development bridge | "There are two areas I want to discuss for development." | Two areas bounds the conversation; vague 'some things' creates anxiety |
| Each development area | "Response time on customer escalations averaged 36 hours this quarter; target is 4 hours. Let's talk about what would help close that gap." | Specifics make the issue debatable; vague phrases just feel like attacks |
| Listen | [Pause. Let them respond fully.] | Most reviews fail because the manager keeps talking; the employee's response is half the review |
| Goals together | "For next quarter, what 3-5 goals would close these gaps and build on the strengths we discussed?" | Employee-driven goals produce ownership; manager-imposed goals produce resistance |
| Manager support | "Here is what I will commit to providing: budget for X, time on Y, access to Z." | Without manager-side commitments, goals become the employee's problem alone |
| Close | "What would help over the next quarter, and what support do you need from me?" | Translates feedback into specific action and shared accountability |
The total review conversation usually runs 30-45 minutes for an annual review, 15-20 minutes for a quarterly check-in. The written document is the structured record; the conversation is where the employee processes the feedback and the manager learns context they may have missed. OPM's performance management framework offers a useful federal-government reference for how structured feedback fits into broader performance systems.
For the broader rhythms of manager-employee feedback that complement formal reviews, the 1:1 meeting guide covers the weekly conversation cadence that prevents annual reviews from becoming surprise documents.
Legal-Safe Language in Reviews
Performance reviews can become legal documents in disputes about termination, demotion, or compensation. Even at small business scale, the language used in reviews can create legal exposure. The risk is highest in three areas: protected-characteristic references, vague conclusions that cannot be defended with evidence, and inconsistent standards across employees.
| Risky phrase (avoid) | Safer alternative | Reason |
|---|---|---|
| Mature judgment | Demonstrates sound judgment when handling escalations | Avoid age-coded language |
| Energetic | Maintains consistent productivity throughout the workday | Avoid age-coded language |
| Works well despite family commitments | Consistently meets project deadlines | Avoid family-status references |
| Strong cultural fit | Collaborates effectively with team members across functions | 'Cultural fit' has been used in discrimination claims |
| Speaks well for someone with their background | Communicates clearly in written and verbal formats | Avoid national origin or accent references |
| Reliable despite their condition | Delivers on commitments consistently | Avoid disability or health references |
| Aggressive negotiator | Negotiates contract terms firmly and effectively | Gendered descriptors apply unequally; use neutral terms |
Three rules for legally defensible review language. First, every claim should be backed by specific evidence (situation, behavior, impact). Vague conclusions without evidence create exposure if the review is challenged later. Second, phrases that touch protected characteristics (age, family status, religion, national origin, disability, pregnancy, gender) should be replaced with observable performance language. Third, standards should be applied consistently: similar behavior should produce similar review language across employees, regardless of demographics. EEOC guidance on prohibited employment practices covers the broader categories of language that create legal exposure.
Common Mistakes in Writing Performance Reviews
The mistakes below appear consistently across small businesses writing reviews. All are avoidable once you understand the underlying patterns.
The pattern across these mistakes: treating the review as a one-time deliverable rather than as the formal summary of an ongoing practice. A deliverable gets produced once and filed away. A practice gets revisited regularly, surfaces issues in real time, and treats the formal review as a milestone rather than the entirety of feedback. The fix for most review failures is not a better template; it is more honest treatment of what makes feedback actually work. Work Institute research on retention consistently finds that lack of meaningful feedback is among the top reasons employees leave; reviews are one of the most concrete tools for addressing this, but only when run as practice rather than paperwork.
How to Read Self-Reviews from Employees
Most reviews include a self-assessment from the employee, written before the manager drafts the formal review. Reading self-reviews well is its own skill: most managers either ignore the self-review entirely or treat it as a substitute for their own assessment. Both approaches miss the value.
| What to look for | What it tells you | How to use it |
|---|---|---|
| Specifics vs. generics | Whether the employee is paying attention to their own work | Coach employees to write specific self-reviews; the discipline transfers to other communication |
| Strengths claimed without evidence | Where the employee may be overestimating themselves | Ask in the conversation: 'Can you give me a specific example of that?' |
| Gaps acknowledged | Where the employee already sees development areas | Use these as starting points; the employee is more likely to own gaps they have already named |
| Goals proposed | What the employee thinks they should be working on | Calibrate against business needs; goals proposed by the employee usually have more ownership than goals you assign |
| Things omitted | What the employee may not see in their own work | Use the formal review to surface what the self-assessment missed |
| Surprises | Where your view of their work differs from theirs | These deserve direct conversation; misalignment usually predicts future friction |
Three rules for using self-reviews well. First, read the self-review before drafting your review, not after. Reading after means you may have already committed to positions the self-review would have updated. Second, use the self-review as input, not as outline. Your review is your perspective on their work; the self-review is their perspective. The combination is more accurate than either alone. Third, treat divergences honestly. If the employee thinks they had a strong year and you do not, the conversation needs to surface that disagreement directly, not paper over it.
What Happens After the Review Matters Most
Most reviews fail not in the writing or even the conversation, but in the weeks after. The document gets filed, the conversation is remembered for a few days, and nothing actually changes. The review only adds value if the goals drive specific actions over the following period and the manager's commitments are honored.
| After-review action | What should happen | What usually happens |
|---|---|---|
| Goals from the review | Tracked in regular 1:1s; progress reviewed monthly | Filed in the review document; not surfaced again until next review |
| Manager commitments | Budget allocated, time scheduled, access granted within 30 days | Committed verbally, not followed through, employee notices and disengages |
| Development areas | Discussed in 1:1s; specific feedback given when patterns repeat | Mentioned once; not raised again until next review where they appear unchanged |
| Strengths | Reinforced through stretch opportunities and recognition | Praised once; no new opportunities offered, employee feels stagnant |
| Self-review observations | Followed up on in subsequent 1:1s as the employee continues working on their own gaps | Read once and forgotten by the manager |
The single biggest predictor of whether the review produces growth: do the goals show up in the next 1:1 meeting? If yes, the review is alive and driving behavior. If no, the review is filed and forgotten by week three. The next 1:1 after the review is where the practice either continues or dies.
How FirstHR Fits
The honest disclosure: FirstHR is not a dedicated performance review platform. We do not have a built-in review template, calibration software, or rating workflow. The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. Performance reviews, when you write them, will live in your shared docs, your internal wiki, or eventually in dedicated performance management software once you have grown into needing that.
That said, reviews work better when the underlying people operations are working. A team writing reviews on top of broken onboarding will spend most of the review explaining basic role expectations rather than discussing actual performance. A team writing reviews on top of consistent onboarding, clear roles, and structured 1:1s will produce reviews that drive behavior change. FirstHR exists to handle the operational HR foundation at flat-fee pricing ($98/month for up to 10 employees, $198/month for up to 50), so that owners and operators can focus on the higher-impact work of writing good reviews and acting on them.
For the foundation that determines whether someone shows up to be reviewed in the first place, the onboarding best practices guide covers what makes new hires ready for meaningful performance discussions.
For the broader management foundation that performance reviews sit on top of, the people management guide covers running a small team without enterprise overhead.
Frequently Asked Questions
How do you write a performance review for an employee?
The seven-step process: collect evidence before you start, ask the employee for self-input first, draft the summary statement first, document strengths with specific evidence, identify development areas with the same specificity, set 3-5 goals for the next period, and read it aloud before sending. Each strength and development area follows the situation-behavior-impact pattern: the specific moment, what the person did, what effect it had. Generic phrases like 'strong communicator' produce no behavior change; specific evidence produces growth.
What should I write in a performance review?
An effective performance review includes six sections. First, header and context (name, role, period, reviewer). Second, a 2-3 sentence summary statement capturing the headline. Third, 3-5 specific strengths with evidence and impact. Fourth, 2-3 development areas with concrete examples. Fifth, 3-5 goals for the next period with deadlines and success measures. Sixth, the manager's commitments: budget, time, mentor access, stretch opportunities. The total length is usually 600-800 words for an annual review and 200-300 for a quarterly check-in.
How do you start a performance review?
Start with a header (employee name, role, review period, reviewer name, date) and a summary statement of 2-3 sentences. The summary captures the overall picture: trajectory, biggest contribution, key development area. Writing the summary first forces you to commit to a position; if you cannot summarize the review in 2-3 sentences, you do not yet know what you are saying. Avoid opening with vague phrases like 'overall a strong year'; the summary should be specific enough to stand alone if someone reads only the first paragraph.
What words should I avoid in a performance review?
Avoid personality labels (aggressive, lazy, enthusiastic, difficult), age-coded language (mature, energetic, seasoned), family-status references, gendered descriptors (bossy, soft-spoken), national origin references, and 'cultural fit' phrasing which has been used in discrimination claims. Replace each with observable behavior and specific outcomes. The test: would a third party reading the review be able to verify the claim with concrete evidence? If yes, the language is safe. If the claim depends on your interpretation alone, the language creates legal exposure.
How long should a performance review be?
An annual review is typically 600-800 words. Quarterly check-ins are shorter at 200-300 words. Mid-year reviews fall in between at 400-500 words. Reviews longer than 1,000 words start losing the employee's attention; reviews shorter than 300 words usually skip components that matter (development goals, manager commitments). The right length is enough specificity to drive behavior change without burying the message. Length is a sign of care taken, not effort applied; padded reviews with generic content are worse than tight reviews with specific examples.
How do you write a good performance review?
Three things separate good reviews from forgettable ones. First, every claim has specific evidence: the situation, the observable behavior, the concrete impact. Generic praise produces nothing. Second, the review does not surprise the employee; every issue raised has already been discussed in real time. Third, the review spends meaningful time on development goals and manager commitments, not just backward-looking evaluation. The strongest reviews allocate 40-50% of their content to forward-looking development, including specific resources the manager will provide.
How do you write a performance review for a difficult employee?
Difficult employees require more specificity, not more harshness. Document specific incidents with dates, observable behaviors (not personality labels), and concrete impacts. Stay focused on performance, not personality. If the issues warrant formal corrective action, write a separate performance improvement plan rather than turning the review into a punishment document. Confusing reviews with PIPs produces both bad reviews and weak corrective documentation. Run reviews and PIPs as separate processes with different purposes.
What is the difference between a performance review and a PIP?
A performance review is a periodic backward-looking evaluation of an employee's work, with forward-looking development goals. It applies to performing employees and is part of normal management cadence. A performance improvement plan (PIP) is a formal corrective document for underperforming employees, with documented feedback patterns and a specific path to either improvement or termination. The two have different purposes and should be separate documents. Mixing them produces reviews that feel punitive and PIPs that lack legal weight.
How often should I write performance reviews?
For small businesses, annual reviews supplemented by quarterly check-ins is the practical cadence. Annual reviews are comprehensive (600-800 words covering all six sections). Quarterly check-ins are targeted (200-300 words on what changed since last quarter). Monthly is overkill for most SMBs and produces compliance fatigue. Semi-annual works for stable teams with low change. The cadence matters less than consistency: a manager who runs annual reviews well produces more growth than one who runs quarterly reviews poorly.
Should I write the review before or after talking to the employee?
Talk to the employee first. Get their self-assessment in writing (1 page) before you start drafting your review. The self-assessment surfaces context you may have missed, signals what they think is important, and reduces the asymmetry of the review conversation. Use it as input, not as a substitute for your own assessment. Reviews written without seeing the employee's perspective often miss obvious things the employee was working on or struggling with. Reviews written after seeing it are more accurate and less surprising.
Can I copy phrases from review templates?
You can use phrases as starting points, but every phrase needs specifics added before it goes in the review. 'Strong communicator' from a template is generic boilerplate; 'led the Q3 client renewals project with weekly status updates that surfaced the integration risk three weeks early' is feedback. The template phrase is the frame; the situation, behavior, and impact you observed are the substance. Copy-pasted templates produce reviews that all sound the same and produce no behavior change. Template phrases plus specific evidence produce reviews employees actually use.
Do reviews need to tie to compensation decisions?
Loosely yes, tightly no. Reviews inform compensation decisions, but the review conversation should be separated from the compensation conversation by at least 2 weeks. When reviews are inseparable from raises, employees defend their performance instead of engaging with feedback, and managers soften criticism to avoid awkward money conversations. Both conversations get more honest when separated. Have the review conversation, let the feedback land, and then have the compensation conversation when the review is no longer the active discussion.