Fair performance reviews for small business: a simple, repeatable process
Fair performance reviews start long before the meeting. This guide shows small business owners how to set clear expectations, keep a running record, spot common rating biases such as halo and recency, write the review and run the conversation, with a fairness checklist.

Few tasks make small business owners more uneasy than performance reviews. Done badly, they feel like a once-a-year verdict based on whatever happened last month. Done well, they are a calm, useful conversation that helps people grow and helps you run a better business.
Fairness is the part that matters most. People accept tough feedback when they trust the process, and they resent even gentle feedback when it feels random. This guide gives you a simple, repeatable way to run fair performance reviews without a large HR function.
Think of reviews as a cycle, not an event
The US Office of Personnel Management (OPM) describes performance management as a cycle with five stages: planning (setting expectations), developing (building capability), monitoring (tracking performance over the period), rating (appraising it) and rewarding (recognizing contributions). The stages are listed on OPM's performance management page. OPM also says that engaging in the process helps employees understand expectations, receive feedback and grow in their careers.
The review meeting is only the rating stage. If the first four stages are missing, the meeting will be a surprise, and surprises feel unfair.
A small-business version of the cycle
| Stage | What it looks like in a team of 5 to 30 | |---|---| | Plan | Each person has three to five written goals for the year or quarter | | Develop | Training, coaching or stretch work agreed and scheduled | | Monitor | Short one-on-ones every two to four weeks, with notes | | Rate | A written review against the goals, once or twice a year | | Reward | Recognition, raises, bonuses or new responsibility, decided on the same evidence |
Step 1: Set clear expectations
You cannot fairly rate someone against expectations they never saw. Write down, for each role:
- The main outcomes the role owns (see the job description guide).
- What "meets expectations" looks like in plain words.
- How success is measured: numbers where they exist, examples where they do not.
Share it at the start of the year and update it when the job changes.
Step 2: Keep a running record
Memory is the biggest threat to a fair review. A guide from the Graduate School USA on rating biases advises recording typical performance as well as extraordinary incidents, observing performance on many occasions, and separating observation from judgment until the appraisal is completed.
Keep a simple file per person. After each one-on-one or notable event, add a dated line:
- What happened (facts, not opinions).
- The effect on the team, the client or the result.
- Any feedback you gave and how it was received.
Also note praise. Good work is easy to forget by December.
Step 3: Know the common rating biases
Even careful managers fall into predictable traps. The Graduate School USA article on rating biases describes several, which I have summarized below with practical fixes.
| Bias | What it is | A simple counter | |---|---|---| | Halo | Rating someone high across the board because they excel at one thing | Score each goal separately against its own evidence | | Recency | Giving too much weight to recent performance | Use your running record across the whole period | | Leniency | Overusing the high end of the scale | Compare ratings against written examples, not against feelings | | Central tendency | Clustering everyone in the middle | Ask yourself what evidence would justify a higher or lower score | | Similar-to-me | Rating people higher because they resemble you | Review your ratings across the team for patterns and ask what drives them |
The source recommends being aware of personal biases and basing conclusions on direct observations and documented examples, treating inferences with caution because they are more prone to error and bias. Its specific counters are the halo and recency fixes; the other fixes in the table are common-sense extensions.
Step 4: Write the review
Use the same form and the same rating scale for every person in the same kind of role.
- Start with the goals. For each goal, write the evidence and a rating.
- Add strengths. Two or three, with examples.
- Add one or two development areas. Specific and actionable.
- Agree next goals. Ideally written together.
- Keep the language neutral. Describe behavior and results, not personality. "Missed three client deadlines in March" is better than "careless."
Ask each employee to complete a short self-review first. It shows how they see their work and surfaces misunderstandings before the meeting.
Step 5: Run the conversation
Before the meeting
- Send the written review or at least the agenda a day ahead.
- Book enough time: 45 to 60 minutes.
- Choose a private place or a quiet video call.
During the meeting
- Start with the purpose and the structure.
- Go goal by goal. Share the evidence, then ask the person's view.
- Listen more than you talk. If the employee gives new facts, be willing to revise.
- Finish with agreed next steps, dates and support you will provide.
After the meeting
- Send a short written summary.
- Put follow-up dates in your calendar.
- Keep copies with employment records.
This is general information, not legal advice. If a review might lead to discipline, termination or a pay decision tied to a protected characteristic, speak to an employment lawyer or adviser familiar with your state's rules.
A fairness checklist
- Every person had written expectations.
- Ratings come from a dated record, not from memory.
- The same form and scale are used for similar roles.
- Each rating has at least one concrete example.
- You have checked for halo, recency, leniency and similar-to-me patterns.
- Pay and reward decisions follow the same evidence as the ratings.
- The employee had a chance to respond, and their comments are recorded.
- Nothing in the review surprises the employee, because feedback has been ongoing.
Common mistakes
- Annual surprise. Problems raised for the first time in the review feel like ambush.
- Rating the person, not the work. Stick to outcomes and behavior.
- Comparing people against each other. Rate against the role, not against colleagues.
- Mixing the review with pay talk. If you can, hold the development conversation first and the pay decision shortly after, so the first can be honest.
- No follow-through. Agreed training or support that never happens costs you trust.
- Skipping reviews for small teams. A short, regular review still beats none.
Where WorkBOS fits
WorkBOS includes performance appraisals as part of HR, so goals, reviews and history can sit alongside the rest of an employee's record rather than in separate files. You can use tasks and the calendar to schedule one-on-ones, surveys and forms to collect self-reviews and feedback, and roles and permissions to keep reviews visible only to the right people. Everything is recorded in the audit log. See the features, pricing, docs or the Academy. For pay decisions, it helps to keep your records in order too.
Frequently asked questions
Q: How often should I run performance reviews? A: Many small teams do a short check-in monthly or quarterly and a written review once or twice a year. The right rhythm is the one you can keep up consistently.
Q: Should reviews be tied to raises? A: Pay decisions should rest on the same evidence as the ratings, but many managers hold the development conversation first and the pay conversation soon after, so people hear feedback calmly.
Q: What if an employee disagrees with the rating? A: Listen, ask for their evidence and be willing to adjust if they show facts you missed. Record their comments on the review.
Q: Do I need a formal rating scale? A: A simple three- to five-point scale with plain descriptions is enough. The important part is using the same one for everyone in similar roles.
Q: How do I keep reviews fair if I like some people more than others? A: Use written goals and a dated record, score each goal separately, and check your ratings across the team for patterns.
Sources are linked in the text above: US Office of Personnel Management and Graduate School USA.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →