Somewhere between ten and thirty employees, every growing business hits the same wall. The founder used to know exactly how everyone was performing because they worked beside them. Now there are managers, a second site or a remote team, and the founder's answer to "how is she doing?" is a shrug. The instinct is to buy an appraisal system. The better answer is to build a performance framework — and the two are not the same thing.

An appraisal is an event. A framework is the year-round rhythm of expectations, feedback and evidence that makes the event almost redundant. ACAS's guidance on managing staff performance points the same way: performance management works when it is continuous, not annual.

Why the annual appraisal fails small businesses

The traditional annual review fails for three structural reasons. First, recency: a review in March judges January to March and guesses at the rest. Second, surprise: any feedback that first surfaces at an annual meeting is feedback withheld for months — the employee hears "you've been underperforming since June" as an ambush, and they are right. Third, paperwork gravity: a big annual form consumes the manager's energy on completion rather than conversation, and the form becomes the deliverable.

The fix is not a better form. It is a shorter loop.

The three-layer framework

A performance framework that fits a 10–100 person business has three layers, and none of them requires software.

Layer 1 — Clear expectations, set once per cycle. Every role has a written answer to "what does good look like this year?" — three to six objectives tied to the business plan, plus the behavioural standards expected of everyone. The discipline is specificity: "improve client satisfaction" is wallpaper; "achieve a client retention rate above 90 per cent, measured quarterly" is an objective. Expectations that live only in a manager's head cannot be managed against and cannot be defended later.

Layer 2 — Regular check-ins. Monthly or fortnightly one-to-ones between each manager and their direct reports, thirty minutes, with a standing agenda: progress against objectives, obstacles, support needed, and anything on either side's mind. The check-in is where performance is actually managed — praise given in the week it was earned, concerns raised in the week they appeared. A one-line written note after each check-in creates the evidence trail without a form.

Layer 3 — A light annual or biannual review. With layers 1 and 2 running, the formal review is a summary, not a revelation: objectives scored, pay and development decisions connected to evidence already gathered, next cycle's objectives set. Nobody should ever be surprised by their own review. If they are, layer 2 has failed.

The management habit that makes it work

The framework above is simple, which is not the same as easy. The failure point is always the same: managers skip check-ins when delivery pressure rises, and the rhythm dies quietly in month three.

Two things prevent this. First, calendar discipline: check-ins are booked as recurring meetings and moved, never deleted. Second, manager training: most first-time managers in SMEs have never been taught to give feedback. A two-hour session on structuring a performance conversation — describe the behaviour, its impact, the standard, then listen — pays back within weeks. ACAS's guidance on having difficult conversations is a sound free starting point.

When performance genuinely falls short

A good framework's real test is how it handles the person who is not meeting it. Because expectations are written and check-ins documented, underperformance is visible early — and early is when it is cheapest to fix.

The informal stage comes first: the manager names the gap plainly in a check-in, agrees specific improvement actions and support, and sets a review point in four to six weeks. Note it in writing. Many cases end here, which is exactly the point.

If the gap persists, you move to a formal capability procedure — which must be fair in the same way a disciplinary is: written invitation, specific concerns with evidence, the right to be accompanied at hearings (section 10, Employment Relations Act 1999), a chance to respond, staged warnings with improvement periods, and an appeal. The ACAS Code of Practice covers capability as well as conduct. And before any capability process, ask the two screening questions that change everything: could a health condition or disability be a factor (triggering the duty to make reasonable adjustments under the Equality Act 2010), and has the person ever actually been trained for what you are measuring them on? If either answer is yes, address that first — tribunals will ask both questions of you.

Dismissal for capability with under two years' service has historically been lower-risk, but the Employment Rights Act reforms are moving unfair dismissal towards a day-one right with a statutory initial period — check the current position on GOV.UK. The safe habit, whatever the service length, is the same: documented expectations, documented support, documented warnings.

Template: the one-page check-in note

Check-in note — [employee] / [manager] / [date]

1. Progress since last check-in (against objectives):
2. Obstacles / support needed:
3. Feedback given (recognition or concern — specific, behavioural):
4. Actions agreed — owner and date:
5. Wellbeing / anything else raised:

Five lines, five minutes, filed somewhere searchable. Twelve months of these notes is a performance record that no contested appraisal can match.

Framework setup checklist

• □ Three to six written, measurable objectives per role per cycle
• □ Company-wide behavioural standards written down
• □ Recurring one-to-ones in every manager's calendar
• □ Check-in note template in use; notes stored and retrievable
• □ Managers trained to give specific, behavioural feedback
• □ Light annual review that summarises rather than surprises
• □ Informal improvement stage defined (actions, support, review date)
• □ Formal capability procedure aligned to the ACAS Code
• □ Health/disability and training screening questions asked before formal action
• □ Pay and development decisions linked to framework evidence

The practical takeaway

Performance management is not the annual meeting; it is the accumulated weight of clear expectations and honest, timely conversations. Build the rhythm, train the managers, keep the notes — and the difficult cases stop being difficult, because everyone saw them coming and had the chance to change the ending.

If your managers are carrying performance issues they do not know how to raise, or you want a framework your team will actually use, book a discovery call with The People Powered at start a conversation with The People Powered.

This article is general guidance for employers, not legal advice on a specific case.