FirstHR

Performance Review: A Practical Guide for Small Business

Performance reviews for small business: types, process, how to write them, examples, and a practical playbook without enterprise overhead.

Nick Anisimov

Nick Anisimov

FirstHR Founder

Performance
24 min

Performance Review

A practical guide for small businesses, demystified

The first performance review I ever ran ended with the employee in tears and me apologizing for things I should have said six months earlier. She was not a weak performer. She was not unreasonable. She was just hearing, for the first time in a 14-month tenure, that her communication style had been frustrating the team. I had noticed it in month two. I had said nothing. I had let it accumulate until the formal review forced me to bring it up. By that point, no amount of careful framing could undo the fact that she had spent over a year doing things I considered problems without anyone telling her.

Most small business owners I talk to have a version of that story. Performance reviews feel like enterprise overhead, so they get scheduled once a year, written the morning of the conversation, and delivered with all the accumulated avoidance of the previous twelve months. The employee leaves the conversation either bewildered (why did no one say this earlier?) or vindicated (I knew this was coming, and you confirmed why I have been looking elsewhere). Neither outcome is what the review was supposed to produce.

This guide explains what a performance review actually is, how to run one well, the types that matter for small businesses, and the practical playbook for doing this without an HR department. I built FirstHR for small businesses, and most of what follows comes from running and mis-running performance reviews myself. The honest disclosure up front: FirstHR does not currently include a performance review module; this article is topical authority, not a product pitch.

TL;DR
A performance review is a formal documented evaluation of an employee\u2019s work over a defined period (usually quarterly or annually). It is one event within the broader practice of performance management; without ongoing feedback between reviews, the review itself fails. For small businesses, the practical mix is weekly 1-on-1s, quarterly written check-ins, an annual summary, and a 90-day review for every new hire. This guide covers types, process, how to write reviews, examples, the small-business playbook, common mistakes, and compliance considerations.
Why This Matters
Roughly half of employees who leave their jobs cite the relationship with their direct manager as a primary reason (Gallup). The performance review is one of the most concentrated moments in that relationship: it is when the employee finds out, in writing, how their manager really sees their work. Get it right and the relationship strengthens. Get it wrong and the resignation timeline starts.

What a Performance Review Actually Is

Definition
Performance Review
A performance review is a formal documented evaluation of an employee's work over a defined period, usually a quarter or a year. It covers progress on goals, observed behaviors, contributions to the team, areas of growth, and decisions about compensation, development, or continued employment. The review is the formal documentation point within the broader practice of performance management; it closes one cycle of work and opens the next. Reviews are also called performance appraisals or performance evaluations; the three terms are largely synonymous, with minor variations in academic and HR contexts.

Three things a performance review is not, despite frequent confusion. First, it is not the entire performance management practice. The review is one event; the practice is the year of conversations and feedback that lead up to it. Treating the two as synonyms is the most common conceptual mistake in the field. Second, it is not a surprise event. Anything an employee hears for the first time at a review represents a manager who avoided the conversation when it would have been useful. Third, it is not a paperwork compliance exercise. The forms support the practice; they are not the practice itself.

The simplest framing: a performance review is the formal moment where the manager and the employee agree, in writing, on how the past period went. It is the documentation that protects the company legally, anchors compensation decisions, and creates continuity from one cycle to the next. Done well, it produces alignment on what comes next. Done badly, it produces defensiveness, recency bias, and surprise resignations.

Performance Review vs Performance Management

The single most important distinction. Performance management is the entire ongoing practice: setting expectations, monitoring work, giving regular feedback, supporting development, and reviewing performance at a defined cadence. The performance review is just one event within that practice. Treating the two as synonyms produces the "annual review with no real management between reviews" pattern that dominates most small businesses.

DimensionPerformance ReviewPerformance Management
Time scopeA defined event (annual, quarterly, etc.)Continuous, year-round
OutputA documented recordBehavior change, development, engagement
Frequency1-4 times per yearDaily and weekly
Primary purposeDocument for decisionsHelp employees do their best work
What fails without itCompliance, fairness, legal defensibilityEngagement, retention, development

The right way to think about the relationship: performance management is the year of conversations and feedback that lead up to the review. The review is the formal documentation point that closes one cycle. A review without management is paperwork without practice; management without reviews is conversation without documentation. Both are needed. The performance management guide covers the broader practice in depth.

Why Performance Reviews Matter

The honest case for performance reviews comes down to three failure modes that show up reliably when they are absent or poorly run. These failures are not theoretical; they are the predictable outcomes of running a business without a real review practice.

The first failure is unfair compensation decisions. Without a documented review, raises and bonuses get decided based on recency bias, personal relationship, and whoever happened to be most visible to leadership in the weeks before the decision. The team eventually notices. Trust erodes. The second failure is surprise resignations. Top performers who never hear they are appreciated assume the lack of feedback means they are coasting unnoticed; they take a recruiter call and leave. The third failure is the unfireable underperformer: the manager has noticed issues for months but has no documented record, so the eventual termination decision either drags on or creates legal risk. Real reviews prevent all three.

The Cost of Avoiding Reviews
Companies that run real performance reviews report measurably lower regrettable turnover and higher employee engagement (Gallup). The mechanism is not the review itself; it is the discipline the review forces. The review only works because of the year of feedback and conversations behind it.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

Types of Performance Reviews

Six main types dominate the field, each with different strengths and use cases. Most small businesses use a combination, not a single type exclusively. Below is a practical breakdown of when each works and when it does not.

Annual reviewOnce a year. Most common, most criticized. Documents the year for compensation and HR records. On its own, it is not performance management; it is the legal documentation that closes the year.
Quarterly reviewEvery three months. The strongest standalone cadence for small businesses. Frequent enough to catch issues early, infrequent enough to reflect real progress on goals.
Continuous feedbackOngoing real-time feedback in weekly 1-on-1s. Not a separate review type as much as the foundation that makes formal reviews work. Without this, every formal review surprises someone.
360-degree reviewInput from manager, peers, and direct reports. Powerful for development, risky for compensation. Useful at scale; usually too political to run well below 25-30 employees.
Project-based reviewTriggered by a project completion rather than the calendar. Common in consulting, agencies, and engineering. Closely tied to the work itself.
Probationary / 90-day reviewSpecific to the first 90 days of a new hire. The single most consequential review in any employee’s tenure. Sets the precedent for everything that follows.

Choosing the Right Mix

The instinct most small business owners have is to pick one type and run it religiously. Resist the instinct. The practical mix that works for most small businesses combines several types: weekly 1-on-1s as the foundation (continuous feedback), quarterly written check-ins (formal documented reviews on a fast cadence), an annual summary (the longer view tied to compensation), and a 90-day review for every new hire (the probationary documentation). This combination produces real-time feedback, frequent enough documentation to catch issues, and the formal annual artifact required for compensation and HR records.

Company sizeRecommended cadenceWhat to skip
Under 10 employeesWeekly 1-on-1s + annual summaryQuarterly formal reviews (overhead), 360-degree (too political)
10-25 employeesWeekly 1-on-1s + quarterly written + annual summary + 90-day for new hires360-degree formal reviews, dedicated software
25-75 employeesAbove + lightweight 360 for senior roles onlyCalibration committees, 9-box grids, forced ranking
75-150 employeesAbove + structured calibration across managersForced bell curves, full enterprise review software
150+ employeesFull structured system with calibration, talent reviews, integrated softwareContinuing to operate informally

The pattern across all sizes: more frequent informal feedback beats less frequent formal reviews. The annual review remains the legal documentation standard, but on its own, it is not performance management. The companies that get the most value from reviews are the ones that combine formal cadence with continuous feedback throughout the period.

The Performance Review Process

The review process has four phases: preparation, the conversation itself, documentation, and follow-up. Most failures happen in preparation. A review that is well-prepared mostly runs itself; a review that is written the morning of the conversation produces all the predictable problems of recency bias and missed context.

Preparation: The Two-Week Lead Time

Schedule the review at least two weeks in advance. Send a calendar invite with the date, the duration (60-90 minutes for an annual; 45-60 for a quarterly), and the self-assessment template. Ask the employee to complete the self-assessment before the meeting. Two weeks gives both sides time to think. Last-minute reviews produce defensive employees and unprepared managers.

During the lead time, the manager writes the review using the running document of notes from weekly 1-on-1s throughout the period. If the running document exists, the review writes itself in 30-45 minutes. If it does not, the review will be heavily biased toward the last two weeks of the period, which is the single most common quality problem. Write your review before reading the self-assessment; reading it first anchors your perception.

The Conversation

The review meeting itself runs best with a consistent structure. Open with the period's goals and the actual outcomes, with concrete examples. Move to observations on behaviors and contributions, both positive and corrective. Discuss the gap between the self-assessment and the manager assessment, which is often the most useful part of the conversation. End with development priorities for the next period and confirmation of next-period goals. Reserve the last 10 minutes for the employee to ask questions or raise concerns; these often surface the most important context.

Documentation and Follow-Up

After the conversation, update the review document with notes from the discussion: any commitments, development plans, decisions, or concerns raised. Both parties acknowledge in writing that the conversation happened. Schedule the next quarterly check-in or 1-on-1. The review is not over until the documentation is complete and the next cycle is scheduled.

How to Write a Performance Review

The writing itself is where most reviews succeed or fail. A good performance review is specific, evidence-based, and free of surprises. The structure below is what works for most small businesses.

What a strong performance review includes
  • A summary of the period’s goals and the actual outcomes, with specific examples
  • Observations on key behaviors and contributions, with concrete situations the employee will recognize
  • Honest assessment of areas of growth, framed as forward-looking development priorities
  • The employee’s self-assessment summarized and the gap between self and manager view discussed
  • Documented development priorities for the next period
  • A clear connection (if applicable) to compensation, promotion, or other decisions
  • Both parties’ acknowledgment that the conversation happened and the content was discussed
Common writing failures
  • Vague language (“great teammate,” “could improve communication”) with no specifics
  • Recency bias: only the last two weeks of the period appear
  • First-time feedback that the employee has never heard before
  • Praise inflation that makes the next time you give honest feedback feel disproportionate
  • Mixing the development conversation with the compensation conversation
  • Numeric ratings without supporting narrative explanation

The Specificity Standard

The single most important quality of a good review is specificity. "Sarah is a great teammate" is filler. "Sarah's handling of the customer escalation in March, where she stayed late to coordinate with engineering and shipped a workaround within 48 hours, is the kind of ownership we want more of" is a review. The first version produces no behavior change and damages credibility. The second produces a clear signal about what the company values and reinforces the specific behavior that demonstrated it.

The same standard applies to corrective feedback. "Could be more proactive" is not feedback; it is filler. "In the May roadmap meeting, when the customer feedback came up, you waited for me to summarize the implications instead of leading the conversation; I would like you to take the lead on the customer-facing summary in the next meeting" is feedback. The specificity makes it actionable; the lack of specificity makes it vague enough to be either ignored or interpreted as personal.

The Behavioral Test
Before finalizing any line in a review, ask: could the employee turn this into a specific action they take or stop taking? If yes, the line is useful. If no, rewrite or delete it. The test takes 10 seconds per line and catches roughly 80% of the most common writing failures.

Examples and Phrases for Performance Reviews

Examples and phrases are the most-searched part of any performance review topic, and most published collections are generic enough to be useless. The pattern that works: phrases that name a specific behavior, ground it in a situation, and connect it to a future expectation. Below are examples in that pattern across common review categories.

Strong Performance Examples

CategoryExample phrasing
Quality of work“The customer onboarding documentation you produced in Q3 is now used by the entire support team. Specifically the troubleshooting flowchart cut average ticket resolution from 4 hours to 90 minutes.”
Initiative“You identified the data inconsistency in the billing system before any customer reported it and led the cross-functional fix without being asked. That is the level of ownership we expect at the next level.”
Collaboration“In the cross-team launch in October, you were the connective tissue between engineering and marketing. The launch went on schedule because you held the timeline together when it was slipping.”
Communication“Your weekly project updates have become the model the rest of the team copies. The structure (decisions made, blockers, next checkpoint) is what the company needs more of.”
Customer focus“The way you handled the angry customer in March, calmly walking through the issue and following up daily for a week, retained an account we were about to lose. That account is now our largest reference.”

Areas of Growth Examples

CategoryExample phrasing
Delegation“I noticed you took back the design work from the contractor twice in Q2 because the output was not exactly how you would have done it. The trade-off is your time. Next quarter, the goal is to coach the contractor through one revision rather than redoing the work.”
Communication timing“The Q2 customer churn issue surfaced to me through Slack three days after you knew about it. Going forward, raise issues of that magnitude within 24 hours so we can address them together.”
Strategic thinking“Your tactical execution is consistently strong. The growth area is connecting tactical decisions to longer-term implications. Next quarter, I would like you to write a one-page strategy memo for each major initiative before kickoff.”
Feedback delivery“You give honest feedback in private 1-on-1s. The growth area is giving the same level of feedback in real time during meetings, when the rest of the team can also benefit. I will model this in the next planning session and ask you to do the same.”
Boundary setting“You are answering Slack messages on weekends consistently. The team copies what they see; if you are working weekends, others feel they should too. Next quarter, I want to see weekend Slack volume drop by half.”

Notice the pattern across all of these: specific situation, specific behavior, specific expected change. This is the structure that makes feedback actionable. Generic phrase lists ("exceeds expectations," "meets expectations," "needs improvement") without this structure are filler that produces no behavior change.

Phrases by Performance Level

Most managers need help with the language for honest feedback at different performance levels. The phrases below are starting points, not scripts; the specificity test still applies. Adapt each to a real situation the employee will recognize.

LevelExample phrasing
Top performer“You consistently deliver beyond what the role requires. The Q3 customer migration is a good example: you scoped the work yourself, identified risks I had not seen, and shipped on time without escalation. This is the level we want to reward and to use as a model for the rest of the team.”
Meets expectations“You reliably deliver what the role requires. The Q3 product release shipped on time at the quality we expected. The growth area for next quarter is taking on one stretch responsibility: leading the cross-functional planning meeting, owning a customer escalation end-to-end, or scoping a small initiative independently.”
Mixed performance“Your technical work is consistently strong. The growth area is communication: in three of the last four cross-team projects, the engineering team learned about timeline slips after they had already happened. The expectation for next quarter is raising risks within 24 hours of identifying them, in the team channel, not in private DMs.”
Underperforming“The work this quarter has not met the bar for the role. Two specific examples: the Q3 deliverable shipped 6 weeks late with quality issues that required follow-up work from the rest of the team, and the customer-facing communication in the August incident was not at the standard we need. We will discuss a structured improvement plan in our next 1-on-1.”
New hire (90-day)“The first 90 days have been a strong start. You have ramped up faster than expected on the technical side and have begun contributing to architecture conversations. The growth area for the next quarter is owning a customer-facing project end-to-end, with me available for support but not driving.”

What Not to Say

Some phrases do active damage. They are clich\u00e9s that signal lack of thought, or they encode subjective judgments that read as personal rather than performance-based. Avoid the categories below.

Phrases to avoid in performance reviews
  • “Not a culture fit” (subjective; often mask for unconscious bias; weak documentation in legal contexts)
  • “Lacks executive presence” (vague; not tied to specific behavior; unfair to people whose communication style differs from leadership’s)
  • “Just needs to be more proactive” (vague; gives no specific behavior to practice)
  • “Has potential” (without specifics, sounds like “not delivering yet” with no path forward)
  • Generic phrase-list language copied from a vendor template (the team can tell)
  • Praise inflation: calling everyone a “rockstar” or “A-player” when the actual performance does not warrant it (devalues the words for the people who actually earn them)

Performance Review Tips That Matter

Below are the tips that consistently make the biggest difference in review quality, drawn from running and watching reviews across many small businesses. These are not the only useful tips; they are the ones that compound the most.

Tips for the manager
  • Write the review before reading the self-assessment, not after; reading the self-assessment first anchors your perception
  • Open the conversation with a specific recent contribution; do not lead with criticism even when criticism is the bulk of the review
  • Use the 80/20 ratio: spend most of the conversation on what the person should keep doing and grow, not on what they should stop doing
  • When delivering hard feedback, name the behavior, the situation, and the expected change; avoid making it about the person
  • Pause for the employee to react; resist the urge to fill silence with more feedback or qualifiers
  • End with a clear ask: what specifically will be different next quarter, and what support will you provide to make it possible
Tips for the employee receiving the review
  • Prepare your self-assessment honestly; calibration gaps with your manager are a feature, not a bug
  • If feedback feels unfair, ask for the specific situation that prompted it; vague feedback should always be challenged
  • Take notes during the conversation; emotional moments make memory unreliable
  • Do not negotiate the review document in real time; ask for a few days to digest and respond in writing if needed
  • Separate the feedback from the relationship; the feedback is about specific behaviors, not about you as a person
  • Ask for one specific commitment from your manager (more support, clearer expectations, removal of a blocker) that would make the next quarter easier
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Performance Reviews for Small Business

Most published material on performance reviews assumes the reader works at a Fortune 500 with a dedicated HR team and review software. The frameworks are designed for organizations where consistency across thousands of managers is the central problem. None of these assumptions hold at small business scale, where the manager is usually the founder or the operations lead, the team is small enough to know each other, and review software is overhead the company cannot afford and does not need.

The version that works for small businesses is dramatically simpler. The full system fits in a shared document per employee, plus a calendar reminder for weekly 1-on-1s, plus a quarterly review template. No software, no calibration committees, no 9-box grids.

The Small Business Review Stack

ComponentToolTime investment
Weekly 1-on-1 notesShared Google Doc per employee5-10 min after each 1-on-1
Quarterly review templateGoogle Doc or Notion template30-45 min per employee per quarter
Annual review summarySeparate document, references quarterly check-ins60-90 min per employee per year
90-day review for new hiresSeparate template specific to probationary period60 min per new hire
Self-assessment templateSame template structure for consistency30 min for the employee to complete

The total time investment for the manager: roughly 6-8 hours per employee per year, distributed across the year. That is less than the time most small businesses spend on a single hiring loop, and it is the highest-leverage HR practice the company can run.

The One-Page Quarterly Template

The quarterly review document fits on one page. Two pages maximum. The template structure that works:

One-page quarterly review template
  • Header: employee name, role, period, manager
  • Goals from last quarter and actual outcomes (with specifics)
  • Top 2-3 strengths demonstrated this quarter (with specific examples)
  • Top 1-2 areas of growth (with specific examples and forward-looking framing)
  • Self-assessment summary and notable gaps with manager assessment
  • Goals and development priorities for next quarter
  • Both parties’ acknowledgment that the conversation happened

The discipline of fitting on one page forces specificity. Long reviews drift into corporate language and filler; short reviews force the manager to pick the points that actually matter. The team also reads short reviews; long reviews get filed and forgotten.

Running Performance Reviews Without an HR Department

Most small businesses do not have a dedicated HR department. The founder or operations lead plays both roles: designing the review framework and running it with their direct reports. This has trade-offs in both directions. The advantage: there is no friction between framework and practice; the same person owns both. The disadvantage: the framework gets built quickly, often without the legal and consistency considerations a dedicated HR person would catch.

The practical recommendation for a small business without HR: use a simple, externally-validated template (the one-page version above; the SHRM or OPM templates) rather than inventing your own. Spend the time you save on the actual practice, which is where the real value comes from. The small business HR guide covers the broader fit.

The Owner-as-Reviewer Risk

The single biggest risk in running reviews without HR is the owner-as-reviewer problem: the founder reviews everyone, which means the founder's biases, blind spots, and personal preferences become institutional. There is no calibration check. Employees who happen to align with the founder's working style get strong reviews; employees who do not, even if they are equally productive, get weaker ones. Over time, this homogenizes the team in ways that hurt long-term performance.

The mitigation: write down review criteria before writing reviews. List the behaviors and outcomes the role is responsible for, in order. Score against those criteria, not against general impression. Ask one trusted senior team member to read the review draft before delivery and flag anywhere the language sounds personal rather than performance-based. This adds 15 minutes to the process and catches the most common bias problems.

What worked for me
At one of my early companies, I caught my own bias only because a senior team member read a review draft and asked, "why does this read so differently from the one you wrote about Marcus last quarter, when their numbers are basically the same?" She was right. I had been more critical of one person because their style differed from mine. After that, I made the criteria-first approach a non-negotiable habit. The reviews still reflect my judgment, but the judgment is anchored in observable behavior, not in personal preference dressed up as performance feedback.

The Annual Review

The annual review is the most common performance review type and the most criticized. It deserves both. As the only formal review a company runs, the annual is wildly insufficient: it surfaces feedback months too late, suffers from severe recency bias, and turns into a ritual everyone dreads. As the capstone of a year of weekly 1-on-1s and quarterly check-ins, it works exactly as intended: a documented summary of conversations that already happened, tied to compensation and longer-term planning.

The mistake is treating the annual review as the entire performance practice. The fix is to keep the annual review (it is the legal documentation standard at most companies) but pair it with quarterly check-ins and weekly 1-on-1s that do the actual work of feedback and development throughout the year.

Annual Review Structure

The annual review covers the same elements as the quarterly review but at a longer time horizon and with the addition of compensation and longer-term planning. Standard structure: summary of the year's goals and outcomes, review of the four quarterly check-ins (referenced as documented evidence), longer-term development trajectory, compensation discussion (or reference to a separate comp conversation), and goals for the year ahead. Length: 2-3 pages, conversation 60-90 minutes.

The honest test for whether your annual review is working: at the end of the conversation, does the employee say anything that surprises you? If yes, the quarterly check-ins are not real; they should have surfaced the surprise earlier. If no, the cycle is working.

The Employee Self-Assessment

The self-assessment is the most underused tool in performance reviews. Done well, it improves review quality dramatically: the employee's perspective surfaces before the manager has anchored the conversation, and the gap between self and manager view becomes the most useful part of the discussion. Done badly (or skipped), it produces a one-sided review where the manager talks and the employee receives.

The Self-Assessment Template

The self-assessment template
  • What did you accomplish this period? Top 3-5 contributions, with specifics
  • What did you struggle with this period? What would you do differently?
  • Where do you want to grow in the next period? Specific skills or scope
  • What feedback do you have for your manager?
  • What feedback do you have for the team or company more broadly?
  • Anything else you want to discuss in the review conversation?

The self-assessment is sent to the employee with the calendar invite for the review and is expected back at least three days before the conversation. The manager reads it after writing their own review, not before. The order matters: reading the self-assessment first anchors the manager's perception and reduces the value of comparing the two perspectives.

Reading the Gap

The gap between the self-assessment and the manager assessment is the most useful part of the review. If the employee underrates their performance and the manager rates them higher, the conversation surfaces hidden contributions and addresses imposter syndrome. If the employee overrates their performance and the manager rates them lower, the conversation surfaces the calibration gap that needs addressing. Either way, the gap is the substance; the matching parts are confirmations.

Performance Review Questions That Matter

The questions you ask in a review shape what gets discussed. Most published lists of review questions are generic enough to be useless; the questions below are calibrated for a real conversation that produces useful information rather than ritual answers. Adapt them to the specific employee and situation.

Questions to ask the employee
  • What are you proudest of from this period? Walk me through the specific situation.
  • What is one thing you tried that did not work, and what did you learn from it?
  • Where do you feel most stretched right now? Most under-utilized?
  • What is the single biggest blocker to you doing your best work?
  • If you had my role for a week, what would you change about how the team operates?
  • What is one piece of feedback for me as a manager that I have not heard yet?
  • What do you want to be doing 12 months from now? What needs to happen between now and then to make that real?
Questions to ask yourself before writing the review
  • If this person resigned tomorrow, what would I genuinely miss? Would the company be measurably worse off in specific ways?
  • What feedback have I been holding back that I should have given months ago?
  • Am I evaluating against the role’s actual requirements, or against my personal preferences and working style?
  • What did this person do that I did not see coming? What does that tell me about their potential?
  • Where am I being too generous because I like the person? Where am I being too critical because their style differs from mine?
  • If I had to defend this review in court tomorrow, would the documentation hold up?

The third question on the manager list (am I evaluating against the role's requirements or against my personal preferences) catches the single most common bias. Founders and operators often promote people who work the way they themselves work, and unconsciously penalize people whose style differs even when the outcomes are equally strong. The question is uncomfortable because the honest answer is often "I am penalizing this person for not working like me." Catching that pattern at the writing stage prevents the review from becoming a vehicle for unconscious bias.

Legal and Compliance Considerations

Performance reviews are legal records. Inconsistent or absent documentation creates risk in termination cases, discrimination complaints, and audits. Three compliance areas matter for any company with 15 or more employees, the threshold for most federal anti-discrimination laws.

Equal and Consistent Application

Review practices must be applied consistently across all employees. Selectively running reviews for some employees but not others, or applying different standards to different demographics, can become evidence in discrimination complaints. The fix is to document the practice clearly and apply it consistently. The EEOC small business resources cover the basic anti-discrimination framework. The human resource laws guide covers the broader compliance landscape.

Documentation as Legal Record

Review documents become legal records in employment disputes. The standard for documentation: the assessment is based on observable performance, applied consistently, and tied to job-related criteria. Subjective judgments ("not a culture fit," "does not have leadership presence") are weak documentation; specific behavioral evidence ("missed three of four quarterly goals; received negative feedback from two team members in documented 1-on-1s") is strong documentation. The SHRM guidance on conducting great performance reviews covers the standard practice in depth.

Performance Improvement Plans

When a review surfaces serious underperformance, the standard practice is to put the employee on a Performance Improvement Plan (PIP): a written document specifying the gaps, expected improvements, timeline, and consequences if improvement does not occur. PIPs serve two purposes: giving the employee a real chance to improve, and creating the documented record needed if the employment relationship eventually ends. PIPs done badly (vague, punitive, set up to fail) create legal risk. PIPs done well give a fair shot and document the process honestly. The employee relations guide covers the broader practice.

Federal Frameworks Apply Earlier Than You Think
Title VII (the main anti-discrimination law) applies to companies with 15+ employees. The ADEA (age discrimination) applies at 20+. The FMLA applies at 50+. Most small businesses cross at least one of these thresholds long before they have an HR department. The Department of Labor FLSA resources cover the wage and hour rules that often intersect with review decisions about compensation.

Common Performance Review Mistakes

The mistakes below are patterns I have seen repeated across dozens of small businesses. None of them are unfixable. All of them are avoidable if you know what to watch for.

Surprising the employee with feedback they have never heard beforeAnything that surfaces for the first time at a review represents avoided conversations. The review should summarize feedback the employee has already heard. If you find yourself wanting to share new criticism at the review, the criticism should have been shared months ago in a 1-on-1.
Writing the review the morning of the conversationA review written in 30 minutes is a review based on recency bias. The events of the last two weeks dominate; the contributions of months 1-10 disappear. The fix is the running document: a few sentences after each 1-on-1 throughout the period. The review then becomes a summary of an existing record, not an act of memory.
Tying every section of the review to a numeric ratingNumeric ratings (1-5, 9-box) are useful at scale for calibration but counterproductive at small scale. They reduce nuanced feedback to a single digit and make managers reluctant to give honest input. Use ratings only where they connect to a real decision (compensation, promotion); skip them everywhere else.
Mixing the development conversation with the compensation conversationThese are different conversations with different stakes. Mixing them poisons both: the growth conversation becomes about positioning for compensation; the comp conversation becomes about generic potential. Separate them by at least a few weeks; ideally by a quarter.
Using vague feedback that gives the employee nothing to act on“Be more proactive” is not feedback. Specific behavioral feedback (“in last week’s customer call, when the security question came up, you deferred to me; next time, take the lead and I will jump in if needed”) gives the employee a clear behavior to practice. Vague feedback feels safe to give and produces no change.
Letting the annual review be the only formal performance conversationAn annual review without quarterly check-ins is a year of avoidance compressed into 60 minutes. It is the single most common dysfunction in small business performance practice. Add quarterly written check-ins between annual reviews, even if they are short.
Skipping documentation because the team is small enough that you remember everythingYou do not remember as much as you think. Memory bias toward recent events is well-documented; the contributions of month 2 do not survive in detail to month 11. The running document is what protects against this, and it also protects the company legally if a termination decision is ever challenged.
Copying enterprise review templates wholesaleThe 9-box grid, the calibration committee, the 12-page review form: all of these are enterprise mechanisms designed for organizations with thousands of employees. At 30 or 80 people, they are bureaucratic overhead the team will quietly ignore. Use the principles (clear expectations, regular feedback, documented assessment); skip the corporate machinery.

The meta-pattern across all eight mistakes: treating the review as the entire performance practice rather than as the documentation of an ongoing practice. The annual review becomes a high-pressure event because it has to do all the work the year of conversations should have done. The fix is not to write better annual reviews; it is to run real performance management throughout the year so the review becomes a low-pressure summary.

Tools and Templates

The tooling question for performance reviews is heavily oversold by software vendors. The honest answer for most small businesses: under 30-50 employees, you do not need dedicated review software. A shared Google Doc or Notion template per employee is enough. Above 50-75 employees, dedicated software starts to add value (calibration across managers, integration with compensation, historical tracking).

StageRecommended toolingWhy
Under 25 employeesGoogle Doc or Notion template per employeeFounder runs everything; software is overhead
25-50 employeesStructured templates with consistent format across managersNeed consistency across teams but not yet at scale that justifies dedicated software
50-150 employeesLightweight performance review software OR robust template systemMultiple managers need consistent practice; HR person typically joins the team in this range
150+ employeesFull performance management platform integrated with HRISMultiple teams need calibration, executive visibility, integration with compensation

The mistake to avoid: buying performance review software in the hope that the software will create the practice. It will not. Tools amplify habits; they do not create them. Build the habit with a simple template, then upgrade only when manual tracking becomes the bottleneck.

Where FirstHR Fits (Honest Disclosure)

FirstHR does not currently include a performance review module. The platform handles employee onboarding, employee profiles, document management, training modules, org charts, and the operational HR foundations that small businesses need. Performance reviews themselves run in your shared docs or your wiki. FirstHR's role is to handle the surrounding infrastructure: clear employee records (so the review has a basis in documented role expectations), onboarding flows that set the right standard from day one, and the organizational data that informs reviews. The onboarding best practices guide covers the foundation that makes the 90-day review work.

FirstHR is built for small businesses, with flat-fee pricing ($98/month for up to 10 employees, $198/month for up to 50), so that the founder can focus on the higher-leverage work like running real 1-on-1s and writing genuine reviews rather than wrestling with HR infrastructure. The HRIS systems guide covers the broader HR foundation.

Where Performance Reviews Are Going

The field is shifting in three observable directions. Small businesses can usually skip ahead to where the field is heading rather than starting with where it has been.

The first shift is from annual to continuous. The annual review as the centerpiece has been declining for years; companies that have made the shift to quarterly check-ins plus continuous feedback report better engagement and faster issue identification. The reason is simple: feedback close in time to the work produces behavior change; feedback delivered six months after the event produces defensiveness.

The second shift is from numeric ratings to narrative assessment. Many large companies have either eliminated or dramatically reduced their use of forced rankings and rating scales. The reasoning: ratings consume management time on calibration debates that produce poor differentiation, and they discourage the honest feedback that drives improvement. The trend is toward narrative assessment (what specifically did this person do, with examples) rather than numeric assessment.

The third shift is from HR-owned to manager-owned. The traditional model placed HR at the center; the emerging model places the manager at the center, with HR providing tools and frameworks. This shift requires investing in manager development, which is why leadership development has become the leverage point for healthy review practice at scale. The OPM performance management framework reflects this shift in the federal context, and the small-business version follows the same logic at smaller scale.

What This Means for Small Businesses
Small businesses can skip ahead to the modern model. You do not have decades of accumulated review process to dismantle. You can start with quarterly check-ins, narrative assessment, and manager-owned practice from the beginning. The companies that win in the next decade will be the ones whose review practices match the actual pace of modern work, which is faster than annual cycles and more nuanced than 1-5 ratings.

The Long View on Performance Reviews

The honest case for performance reviews at any company size is not that they are magic. They are not. They are a structured way to do something most managers should do anyway: assess how the past period went, document the assessment, and use it to inform what comes next. Done well, reviews make this rhythm visible and shared. Done badly, they bury the rhythm under bureaucratic theater that signals process compliance without producing real outcomes.

The teams that get the most value from reviews are the ones that run a simple version consistently for years. After several cycles, the review becomes the natural capstone to the year of conversations rather than a high-pressure event. Surprises disappear. Compensation conversations become anchored in evidence. Top performers feel seen; underperformers receive the structured feedback they need to improve or move on. None of this is achievable through a single annual review; it is achievable through the year of practice that the review documents.

For the broader practices that connect to performance reviews, the performance management guide covers the ongoing practice the review documents, the leadership development guide covers the manager skills that make reviews work, the people management guide covers the day-to-day practice, and the 30-60-90 onboarding plan guide covers the new-hire window where the 90-day review most directly shapes the precedent. The development goals for work guide covers the goal-setting that anchors review conversations.

Key Takeaways
A performance review is the formal documentation of how an employee has performed over a defined period. It is one event within the broader practice of performance management, not the entire practice.
For small businesses, the practical mix is weekly 1-on-1s, quarterly written check-ins, an annual summary, and a 90-day review for every new hire. Total time investment: 6-8 hours per employee per year.
The single most important quality of a strong review is specificity. Vague phrases produce no behavior change; specific behavioral evidence produces real change within weeks.
Anything an employee hears for the first time at a review represents a year of avoided conversations. The review should summarize feedback that has already been delivered.
Self-assessments improve review quality dramatically. Read them after writing your own review, not before; the gap between the two is the most useful part of the conversation.
Federal anti-discrimination laws apply at 15-20 employees. Documentation discipline needs to exist before any compliance challenge, not after.
Do not buy performance review software before building the practice manually. Tools amplify habits; they do not create them. Build the habit first; add tools when manual tracking becomes the bottleneck.
Separate the review conversation from the compensation conversation by at least a few weeks. Mixing them poisons both; the review becomes about positioning for the raise, and the comp conversation becomes about generic potential.

Frequently Asked Questions

What is a performance review?

A performance review is a formal documented evaluation of an employee’s work over a defined period, typically a quarter or a year. It covers progress on goals, observed behaviors, contributions to the team, areas of growth, and (often) decisions about compensation and development. The review is one event within the broader practice of performance management; it is the formal documentation point that closes one cycle and opens the next. A review without ongoing feedback throughout the period is usually a poor review.

How do you write a good performance review?

A good performance review is specific, evidence-based, and free of surprises. The structure that works for most small businesses: start with the period’s goals and the actual outcomes, with concrete examples. Cover observed behaviors and contributions with specific situations the employee will recognize. Address areas of growth honestly, with examples that have already been discussed in 1-on-1s. End with development priorities for the next period. Avoid vague language (“great teammate”), recency bias (only mentioning the last two weeks), and any feedback the employee is hearing for the first time.

What are the main types of performance reviews?

Six main types dominate the field: annual review (yearly, the most common), quarterly review (every three months, the strongest cadence for small businesses), continuous feedback (ongoing, the foundation under formal reviews), 360-degree review (input from manager, peers, and direct reports), project-based review (triggered by project completion rather than calendar), and probationary or 90-day review (specific to new hires). Most companies use a combination. For small businesses, the practical mix is quarterly written check-ins, an annual review, and a 90-day review for every new hire.

What is the difference between a performance review and performance management?

Performance management is the entire ongoing practice: setting expectations, giving feedback, coaching, and reviewing. A performance review is one event within that practice: the formal documentation point at a defined cadence (annually, quarterly) where performance is assessed and tied to decisions about compensation, promotion, or development. Reviews without management are paperwork without practice; management without reviews is conversation without documentation. Both are needed, and the review becomes meaningful only when the management around it is real.

How often should performance reviews happen?

The most effective small-business cadence combines several layers: weekly 1-on-1s (real-time feedback), monthly written notes (documented progress), quarterly formal check-ins (full review of goals and development), and an annual summary (compensation and longer-term trajectory). Companies that only review annually consistently produce surprised employees, weak documentation, and avoidable turnover. Companies that combine weekly conversations with quarterly written check-ins produce the strongest outcomes.

What should you say in a performance review?

The strongest performance review covers four things: (1) specific accomplishments tied to the period’s goals, with concrete examples; (2) observations on behaviors and contributions, both positive and corrective, with situations the employee will recognize; (3) honest discussion of areas of growth, ideally framed as forward-looking development priorities rather than backward-looking criticism; (4) clear next-period priorities both parties have agreed on. Avoid filler praise, vague concerns, and any feedback the employee is hearing for the first time.

What is a 90-day performance review?

A 90-day performance review is the formal evaluation at the end of a new hire’s probationary period. It covers what they have learned, how they have contributed, the manager’s observations, and the formal decision about whether the employment relationship continues, often called “passing probation.” The 90-day review is the single most consequential review in any employee’s tenure because it shapes the precedent for every subsequent review. Done well, it sets a clear standard for ongoing performance conversations. Done badly, it teaches the new hire that reviews are perfunctory.

Can small businesses run performance reviews without an HR department?

Yes, and most do. The practical version of performance reviews for a small business without dedicated HR: a one-page review document per employee, run quarterly, with a longer annual summary. The founder, owner, or operations lead writes the review based on a running document of notes from weekly 1-on-1s. Reviews without HR are not lower quality; they are often higher quality because the manager is closer to the actual work. The risk is inconsistency across managers, which gets larger as the team grows past 25-30 employees.

What is a self-assessment in a performance review?

A self-assessment is a written evaluation that the employee completes about their own performance, usually before the manager’s review. It typically covers what they accomplished, what they struggled with, where they want to grow, and feedback for the manager. Self-assessments improve review quality because they surface the employee’s perspective before the manager has anchored the conversation. They also reveal gaps between how the employee sees themselves and how the manager sees them, which is often the most useful part of the review conversation.

What is a 360-degree performance review?

A 360-degree review collects feedback from multiple sources: the employee’s manager, peers, direct reports (if applicable), and sometimes customers or cross-functional collaborators. The goal is to give a multi-perspective view of performance rather than relying solely on the manager’s view. 360-degree reviews are powerful for development conversations because they surface blind spots. They are risky for compensation decisions because the input can become political. Most companies use 360 reviews for development only, separately from compensation.

What is a performance improvement plan (PIP)?

A performance improvement plan is a structured written document used when an employee is underperforming. It specifies the gaps, the expected improvements, the timeline (usually 30-90 days), the support the manager will provide, and the consequences if improvement does not occur. PIPs serve two purposes: giving the employee a real chance to improve, and creating the documented record needed if the employment relationship eventually ends. PIPs done badly (vague, punitive, set up to fail) create legal risk and damage trust. PIPs done well give a fair shot and document the process honestly.

How do performance reviews affect compensation?

In most small businesses, performance reviews directly inform compensation decisions: raises, bonuses, equity refreshes. The honest practice: connect the review to compensation but do not run them in the same conversation. The review itself focuses on performance and development. The compensation conversation, ideally weeks later, references the review as one input among others (market data, company financials, role evolution). Mixing them in one conversation poisons both: the review becomes about positioning for the raise; the comp conversation becomes about generic potential rather than specific evidence.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial