How to Write a Performance Review: Guide for Small Business

The first time I wrote a performance review for a direct report, I stared at a blank page for ninety minutes, then produced four paragraphs of recycled phrases: "Strong communicator. Good team player. Takes initiative." Three months later, the patterns I had glossed over became real problems. The review had communicated nothing actionable. Every phrase was true. None was useful.

This is the central trap of writing performance reviews without HR support. Most online guides hand you a generic template and a list of phrases organized by competency, and every review built from them sounds the same. The phrases are not the problem; the missing specifics are. Without evidence from work the employee actually did, the review becomes filler that the employee forgets within days, the manager forgets within weeks, and nobody can use when it matters six months later.

This guide starts from the specifics instead. It is written for small business owners and operators 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 small business (SMB) example of what good looks like, the common mistakes that turn careful writing into useless reviews, and the conversation script that makes the review land.

FirstHR exists for exactly that reader. Most performance management content assumes a level of HR sophistication small businesses neither have nor need, and I built the product for the people that content leaves out.

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. Those conversations should have happened in real time, and the review writes down the pattern they revealed. If issues are appearing in the review for the first time, the manager has waited too long to surface them.

The naming varies and the document does not. Employee evaluation, performance appraisal, employee review, and performance review all describe the same thing here: a written assessment of a period of work, delivered in a conversation. Writing an employee evaluation is the same task, whether you start from a blank page or from an evaluation form.

Every performance review that works passes three tests. First, the evidence is specific: each strength and development area names the moment, the behavior, and the impact. Second, nothing in it surprises the employee, because every issue was raised when it happened. Third, it spends real time on development goals and the manager's commitments to support them, so the employee leaves with a path forward and not just a verdict on the past.

Most reviews fail at least one of those 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"). 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 reviewing employees they barely know. Their companies have formal competency frameworks, calibrated rating scales, and HR business partners checking 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.

That changes the job in three ways. First, generic templates are worse, not better. The team is small enough that everyone notices when reviews sound copy-pasted. A small 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, you have direct context most enterprise reviewers lack. You have probably sat in the same meetings as the employee, seen the customer interactions, and read their email replies. Use that: write from what you observed, not from what an HR form expects you to evaluate. That is the major opportunity of a small business review: being specific about real work, which an enterprise review cannot do.

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.

Guidance from the Society for Human Resource Management (SHRM) on documenting performance ahead of a termination says to keep the record short and dispassionate, and to base it on observed behaviors rather than character judgments. At small business scale your review is often the only record there is, so that is the standard it has to meet.

The 6 Sections of an Effective Performance Review

Every effective review has the same six sections, and each one does a job the others cannot. Skip one and the review weakens; include all six and you get a document that actually changes behavior.

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.

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 shows up in the draft as vagueness the manager then has to write around.

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.

Frequency is what makes the log worth keeping. According to Gallup research on managers, employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers do not, so the same habit that produces review evidence also produces the ongoing feedback that carries the rest of the year.

The 7-Step Writing Process

The seven steps below produce reviews that drive behavior change. Once you have some practice, the process takes 90-120 minutes per direct report, plus 30-45 minutes for the conversation. Skip a step and the review gets worse, however good your template is.

Watch for two failure modes while you write. The first is skipping Step 2, asking for self-input. Most managers write the review first and read the self-assessment afterward, so they often miss the context it would have surfaced.

The second failure mode is skipping Step 7, sleeping on it. The 24-hour gap is short, but it produces meaningfully better reviews: it is where you catch a paragraph you might otherwise regret sending.

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 summaries describe sentiment; specific summaries describe what happened. The specific version names actual outcomes (18 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). Writing one takes 5-10 minutes, and it gives you a review that opens with substance instead of decoration.

Documenting Strengths with Specific Evidence

Strengths are where most reviews fail, because the reviewer writes generic praise instead of specific observations. "Strong communicator" tells the employee nothing about what behavior earned the phrase or what behavior to repeat. The strengths section needs the same specificity discipline as development areas, even though skipping the specifics feels less risky 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 is adapted from the Center for Creative Leadership's SBI (situation-behavior-impact) feedback model.

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.

Two patterns in these examples are 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.

Writing Constructive Feedback That Lands

Constructive feedback works in a review when it describes a behavior, names the effect it had, and points at a change the person can actually make. The failure mode is rarely harshness. It is feedback aimed at the person instead of the work: "not proactive enough" gives nothing to act on, while "blockers surfaced 4-5 days late" does.

Three habits keep the tone honest without softening the message. Write the behavior before the judgment, so the employee can check the facts before reacting to the verdict. Attach one concrete next step to every gap you name. And separate what you observed from why you think it happened, then ask about the cause rather than assert it. Our feedback examples cover more phrasing patterns.

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 goals describe a direction; specific goals describe a destination with a timeline. Each specific goal names the activity, the scope, and the success measure. Making a goal specific takes 2-3 minutes, and it is what gets the goal to actually move over the next period.

Examples of Performance Review Goals by Role

A good performance review goal names the work, the number that proves it happened, and the date it is measured against. The examples below cover the roles small business owners ask about most often. Each one is written so that at the next review, neither of you has to interpret anything to know whether it landed.

Every goal in that table passes the SMART test without anyone having to recite the acronym at the employee: specific work, a measurable number, a target you both believe is reachable, relevance to what the business needs next, and a date.

Write each goal in plain language first, and use SMART afterward as a checking tool. The SMART goals template has a worksheet if you want the structure on the page in front of you.

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.

The pattern: vague phrases describe attributes; specific phrases describe events with consequences. Vague language costs you reviews that all sound the same and produce no behavior change. Specific language has a cost too: you have to commit to observations the employee may push back on.

The risk of pushback 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 are worth noticing. First, every section is anchored in specifics: account counts, NRR percentages, ramp times, dollar figures, account names. 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. Maria knows what she will get from her manager, not only what is expected of her.

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.

One rule holds across every review type: no new criticism in any formal review, whatever its length. Every issue should already have come up in real time, so the formal review only summarizes conversations that have already happened. This matters most in probationary and annual reviews, where the document may later become legal evidence.

Delivering the Review in Conversation

Even the best-written review fails if it is delivered poorly, because the conversation does as much work as the document. Most managers either skip the conversation (sending the review by email and hoping it lands) or run it as a one-way reading of the document. Either way, the careful writing lands with less force.

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.

The order of the conversation matters more than its exact wording. SHRM guidance on conducting a performance review sets out five steps: convey positive intent, describe specifically what you have observed, state the impact of the behavior, ask the employee to respond, and agree the next steps. The same article cites Gallup research finding that just one in five employees agreed their company's performance practices motivated them.

Setting Up the Review Meeting

Book 45 minutes for an annual review and 20 for a quarterly check-in, in a private room or a video call with cameras on, and never stacked between two other meetings. Tell the employee what the meeting is a few days ahead, so they arrive prepared rather than braced for bad news.

Send the written document the day before, or read it together in the room. Both work and the choice is about the person. Sending it ahead gives a quiet processor time to absorb the detail and turns the meeting into discussion instead of reading. Reading together suits someone who would otherwise spend the night rereading one sentence.

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.

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, religion, national origin, disability, pregnancy, gender) or family and caregiver status (protected under some state and local laws, and a pregnancy or sex-discrimination risk under federal law) should be replaced with observable performance language.

The third rule is consistency: similar behavior should produce similar review language across employees. When two people do the same thing and read two different verdicts, the gap invites the question of what else set them apart.

Federal law spells out what may not set two employees apart. According to guidance on prohibited employment practices from the Equal Employment Opportunity Commission (EEOC), it is illegal to discriminate because of race, color, religion, sex (including transgender status, sexual orientation, and pregnancy), national origin, age (40 or older), disability, or genetic information, and those characteristics may not be taken into account in decisions about discipline or discharge.

Your headcount decides how much of this reaches you in the first place. According to the EEOC small business guidance, the laws it enforces start at different sizes: 15 or more employees for Title VII of the Civil Rights Act, the Americans with Disabilities Act, and the Genetic Information Nondiscrimination Act; 20 or more for the Age Discrimination in Employment Act; and the federal Equal Pay Act from the first employee.

Because the Equal Pay Act starts at the first employee, a review written at a five-person company still carries weight in an equal pay dispute.

Common Mistakes in Writing Performance Reviews

The mistakes below show up again and again when small businesses write reviews. Every one of them is avoidable once you see the pattern behind it.

What these mistakes share is treating the review as a one-time deliverable rather than 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 one milestone rather than the whole of feedback. The fix for most review failures is not a better template; it is feedback that keeps happening between reviews.

The research points the same way. According to Gallup, employees are 3.6 times more likely to strongly agree that they are motivated to do outstanding work when their manager gives feedback daily rather than annually. The review is one concrete tool among the practices that retain people, but only when it is run as practice rather than paperwork.

Training Managers to Run Reviews

Performance appraisal training does not need a course at small business scale. When you hand review writing to your first managers, give them this process, the evidence log, and two of your own past reviews as worked examples, then read their drafts before those drafts reach anyone.

Three rater habits are worth naming in that first sitting, because they distort a review quietly. Recency, where the last six weeks stand in for the year. Halo, where one strong quality colors every other line. Leniency, where everyone lands slightly above average because the alternative is an uncomfortable conversation. Reading the drafts side by side before anything is sent catches all three.

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.

Getting value from a self-review comes down to three rules. First, read it before drafting your review, not after; reading it afterward means you may already have committed to positions it would have changed. Second, use it as input, not as an outline. Your review is your perspective on their work and the self-review is theirs, and the combination is more accurate than either alone.

The third rule is to 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.

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.

Reviews themselves live somewhere else for now. When you write them, they will sit 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, predictable pricing, so that owners and operators can focus on the higher-impact work of writing good reviews and acting on them.

Frequently Asked Questions