Few people look forward to performance review season. Managers dread writing them, employees dread reading them, and too often the result is a form full of vague praise, a rating nobody understands, and no real change. Yet a well-run review is one of the most useful conversations a manager can have: it connects someone's daily work to what the business needs, recognizes what is going well, and sets a clear direction for what comes next.
This guide covers how to design and run performance reviews that are fair, useful, and defensible, even if you are a small team without a dedicated HR department.
Start with what the review is for
Before choosing a form or a rating scale, decide what you want the review to accomplish. Most small businesses want some combination of:
- Feedback: a clear picture of strengths and areas to improve
- Alignment: agreement on goals and priorities for the next period
- Development: skills to build and opportunities to grow
- Decisions: input into raises, promotions or, occasionally, corrective action
Trying to do all four in a single annual meeting is hard. Many teams separate the development conversation from the compensation conversation, or at least discuss them in different parts of the meeting, so employees can actually hear the feedback instead of waiting for the number.
Choose a cadence that fits
Annual reviews alone are rarely enough. By the time the meeting happens, half the year's examples are forgotten. Common approaches:
| Cadence | Best for | Watch out for |
|---|---|---|
| Annual formal review | Compensation decisions, year-end summary | Recency bias; surprises if there were no check-ins |
| Semi-annual review | Growing teams wanting more frequent alignment | Admin load if forms are long |
| Quarterly check-ins | Fast-moving startups, shifting goals | Can become box-ticking without clear goals |
| Ongoing 1:1s plus annual summary | Most small businesses | Depends on managers actually holding the 1:1s |
Whatever you choose, the golden rule is the same: nothing in a formal review should be a surprise. If a problem is serious enough to appear in a review, it should have been raised when it happened.
Define clear, job-related criteria
Fair reviews start with clear expectations. Each employee should know what good performance looks like in their role before the review period begins. Good criteria are:
- Job-related. Tied to the actual duties of the role. A current, accurate job description helps; the AskHrAI job description generator can help you write or update one.
- Observable. Based on results and behaviors, not personality traits like "attitude" or "culture fit."
- Consistent. The same criteria apply to everyone in the same role.
- Measurable where possible. Sales targets, ticket resolution times, project deadlines, quality measures.
A simple structure works well for most teams: two or three sections covering results (what was achieved against goals), how the work was done (collaboration, communication, reliability), and growth (skills developed, goals for next period).
Reduce bias in the process
Reviews feed into pay and promotion decisions, so bias in reviews can become a discrimination problem under Title VII, the ADA, the Age Discrimination in Employment Act and state laws. Common biases to guard against:
- Recency bias: overweighting the last few weeks. Fix: keep a running log of examples through the year, and ask employees to submit a self-review with their own highlights.
- Halo and horns effects: letting one strong trait or one mistake color the whole review. Fix: rate each criterion separately with its own evidence.
- Similarity bias: rating people who are like you more favorably. Fix: calibrate ratings across managers.
- Inconsistent language: describing similar behavior as "assertive" for one person and "abrasive" for another. Fix: review the wording, not just the rating.
- Penalizing protected leave: marking someone down for absences that were protected under FMLA, ADA, or state sick leave laws. Fix: evaluate the work done, and adjust goals for approved leave.
Calibration does not have to be elaborate. In a small company, it can be a one-hour meeting where managers walk through proposed ratings and ask, "Would we rate someone else with the same results the same way?"
Write reviews that are actually useful
The written review should give the employee something to act on. A few practical rules:
- Lead with specific examples. "You rebuilt the onboarding workflow and cut setup time for new clients" is more useful than "great work this year."
- Describe the impact of the behavior, not just the behavior.
- Be direct about gaps. Softened language like "could consider occasionally improving" leaves people unaware there is a real problem, and it weakens your record if you later need to take corrective action.
- Keep it about work. Leave out comments on age, health, family plans, personal life or anything tied to a protected characteristic.
- Agree on two to four goals for the next period, each with a measure and a date.
Run the conversation well
The meeting matters as much as the document. A simple agenda:
- Open by explaining the purpose and structure of the meeting.
- Ask for the employee's view first. What went well? What was hard? What do they want to do more of?
- Share your assessment, starting with strengths, then areas for improvement, with examples.
- Discuss differences openly. If they disagree, listen. You may learn about context you missed.
- Agree on goals and support for the next period.
- Close with next steps, including when you will check in.
Give the employee a copy and the chance to add written comments. Have them acknowledge receipt.
Connect reviews to pay carefully
If reviews feed into raises, make the link transparent and consistent. Define how ratings translate into increase ranges, then check results across the team for unexplained gaps by gender, race or other protected characteristics. A periodic check with the AskHrAI pay equity tool can flag patterns before they become a problem. Many states also have pay equity laws stricter than the federal Equal Pay Act, so a consistent, documented process helps.
Performance review checklist
- Goals and criteria set and shared at the start of the period
- Running notes of examples kept throughout the period
- Employee self-review requested two weeks before the meeting
- Draft review checked for specific examples and neutral, job-related language
- Protected leave and accommodations accounted for
- Ratings calibrated across managers
- Meeting scheduled with enough time for discussion
- Next-period goals documented with measures and dates
- Signed acknowledgment and employee comments filed
- Follow-up check-ins on the calendar
Key takeaways
- Decide what your reviews are for and design the process around it.
- Use clear, job-related, consistent criteria and real examples.
- Build simple bias checks into the process, including calibration.
- Nothing in a formal review should be a surprise.
- If reviews drive pay, make the link consistent and check the results.
Want help drafting a review or turning your notes into clear, neutral feedback? Try the AskHrAI HR assistant.
This article is general information, not legal advice. Employment laws change and vary by state and city — confirm details with your state labor department or an employment attorney.