In most small businesses, pay review season works like this: someone asks for a rise, the founder checks what feels affordable, negotiates privately, and moves on. It works until the day two employees compare payslips — and they always eventually do — and discover that the quieter one earns less for the same job. At that point you do not have a pay problem; you have a trust problem and, potentially, a legal one. A structured pay review cycle is how growing businesses replace ad-hoc negotiation with something they can explain and defend.
Why ad-hoc pay decisions stop scaling
Below ten people, informal pay is survivable. Beyond that, three failure patterns appear. Negotiation bias: pay drifts towards whoever asks loudest, which correlates with confidence, not contribution — and often with gender and ethnicity, which is where legal exposure begins. Compression: new hires arrive at market rate while loyal staff fall behind, because nobody reviews the whole picture at once. No memory: decisions made in corridors leave no record, so next year's decision starts from scratch and inconsistencies compound.
A pay review cycle fixes all three by deciding everyone at once, against criteria, with a record.
The legal frame you are working inside
Pay is one of the most legally dense areas of employment. The anchors:
Equal pay. The Equality Act 2010 gives employees the right to equal pay with a comparator of the opposite sex doing like work, work rated as equivalent, or work of equal value — unless you can show a genuine material factor that is not itself discriminatory. Unequal pay between men and women doing similar jobs is a claim with up to six years' arrears. You do not need 250 employees or a formal audit for this to apply to you.
National minimum and living wage. Check every pay decision against current rates — the National Living Wage applies to workers aged 21 and over, with lower bands for younger workers and apprentices. Rates change every April; always verify on GOV.UK rather than relying on memory. Remember that deductions, unpaid working time and salary sacrifice can pull effective hourly pay below the legal minimum even where the headline salary looks safe.
Discrimination more broadly. Pay decisions influenced by part-time status, maternity, disability or any protected characteristic create indirect discrimination risk even where equal pay law is not directly engaged. The practical shield is the same one as everywhere in HR: objective criteria, consistently applied, written down.
Contractual commitments. If your contracts or handbook promise an annual review, that promise is contractual. "Review" does not guarantee an increase — but skipping the review entirely can be a breach.
The five-step cycle
Step 1 — Set the pot first. Decide the total affordable increase before looking at individuals: a percentage of payroll grounded in the business's actual position. Deciding the pot last — by summing individual promises — is how budgets break.
Step 2 — Benchmark roles. You do not need a salary survey subscription to sanity-check pay. Job boards show live market rates for comparable roles; your own recruitment experience tells you what you had to pay last time. Group roles into broad families and levels, and note where existing pay sits against the market. Pay attention to any role where retention is critical and pay is visibly behind.
Step 3 — Apply written criteria. Typical defensible criteria: performance against objectives (from your performance framework, if you have one), market position, scope growth, and — carefully — length of service. Write the criteria down before reviewing anyone, then score everyone against the same list. The criteria are your answer when someone asks "why did they get more than me?"
Step 4 — Run the equity checks before finalising. This is the step SMEs skip and regret. Lay the proposed outcomes side by side and ask: are people doing similar work being treated consistently? Are there gender patterns in the outcomes? Are part-time staff pro-rated fairly rather than penalised? Has anyone on maternity or long-term sick leave been quietly excluded from the cycle — because excluding them is both unlawful and common? Twenty minutes with a spreadsheet here is the cheapest legal defence you will ever buy.
Step 5 — Communicate individually, in writing. Each employee gets a letter: the outcome, the effective date, and — where there is no increase — the honest reason and what would change the answer next cycle. "No rise because money is tight and here is how the business is doing" builds more trust than silence or a vague promise. Keep the letters; they are the record.
The awkward cases
The counter-offer resignation. When a valued person resigns for money, matching it may be right — but recognise it as a market correction, not a reward for threatening to leave, and check what it does to internal equity before you say yes. Staff talk; a counter-offer that leapfrogs loyal colleagues will be known within the month.
Pay freezes. Freezing pay is lawful unless contractually promised otherwise, but communicate it early, honestly and once. A freeze discovered via a payslip breeds the resignation letter you feared.
Founder's instinct vs the framework. The owner should absolutely apply judgement — the framework exists to make sure judgement is exercised consistently and with the equity checks done, not to remove it.
Template: pay review decision record
Pay review cycle [year] — decision record
Cycle dates: Pay pot approved (£ / % payroll):
Criteria used (tick): [ ] performance [ ] market [ ] scope growth
[ ] service [ ] other:
Roles benchmarked against: (sources)
Equity checks completed: [ ] gender [ ] part-time [ ] family/sick leave
[ ] NMW/NLW compliance at new rates
Per employee:
Name / role / current salary:
Proposed salary / effective date:
Criteria applied and evidence:
Manager recommendation / final decision:
Letter issued (date):
Pay review checklist
- Total pay pot set from business affordability before individual decisions
- Roles benchmarked against live market evidence
- Written criteria applied to everyone, including those on leave
- Equal pay and gender-pattern check across outcomes
- Part-time staff treated proportionately
- All outcomes above current NMW/NLW rates, including after deductions
- Contractual review promises honoured
- Every outcome confirmed in an individual letter with reasons
- Decision record retained for next cycle
- Gender pay gap reporting obligation checked if headcount nears 250 (GOV.UK)
The practical takeaway
Pay is the message employees remember longest. A structured cycle turns pay from a series of private negotiations into a visible system — one that rewards contribution, survives comparison between colleagues, and stands up if it is ever examined formally. The spreadsheet and the letters take a day or two a year. The alternative costs more, just later.
If you want help designing a pay review cycle that fits your business size and budget, 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.
Most onboarding advice is about belonging: buddy systems, welcome lunches, culture decks. That matters — but it is not what this article is about. This is about the unglamorous compliance work that must happen in a new starter's first days and weeks, because when it does not, the consequences are not awkward — they are fines, invalid insurance, unlawful deductions and unenforceable terms. Culture onboarding can be improvised. Compliance onboarding cannot.
Before day one: right to work
The single most time-critical task is the right to work check, which must be completed before employment starts. You have three lawful routes:
- Manual check of original documents (passport, biometric residence permit, the accepted lists on GOV.UK).
- Digital check via a certified Identity Service Provider for British and Irish passport holders.
- Home Office online check for those with digital immigration status, using the employee's share code at gov.uk/prove-right-to-work.
Whichever route you use, keep a dated copy of the evidence — that copy is your "statutory excuse" against a civil penalty. Employing someone without a valid check can attract civil penalties of up to £45,000 per illegal worker for a first breach and £60,000 for repeat breaches under the Immigration, Asylum and Nationality Act 2006, with criminal liability where you knew or had reasonable cause to believe. For time-limited permissions, diarise the follow-up check before expiry. This is the one onboarding task where "I'll sort it next week" is genuinely dangerous.
Day one: the written statement
As covered in our companion piece on contracts for first hires, every worker must receive their written statement of employment particulars on or before day one (section 1, Employment Rights Act 1996). If your contract doubles as the statement and is signed before start, you are compliant. If the contract is "in progress" while the person starts work, you are not.
Week one: payroll, pension and tax
Payroll setup. Get the new starter's P45 or have them complete the HMRC starter checklist (the successor to the P46). Without it, emergency tax codes mean your new hire's first payslip is wrong — a terrible first impression and a deduction headache.
Auto-enrolment assessment. Every employer must assess each worker for pension auto-enrolment from day one of employment. Workers aged 22 to state pension age earning over £10,000 a year must be enrolled into a qualifying scheme; others have rights to opt in or join. Duties start on day one — postponement is possible for up to three months, but only with a formal notice to the worker. The detail lives with The Pensions Regulator. If your first hire is also your first auto-enrolment duty, set the scheme up before the start date, not after.
P46-era habits die hard. A surprising number of small employers still ask new starters for "their P45 or nothing" and leave them on emergency code for months. The starter checklist exists precisely so the hire is not punished for a previous employer's paperwork speed.
Statutory Sick Pay readiness. Check the payroll can handle SSP correctly. Note that the Employment Rights Act reforms include changes to SSP — notably removal of the waiting days and the lower earnings limit — so verify the current SSP rules on GOV.UK rather than assuming the old three-waiting-days pattern still applies.
Week one: policies and acknowledgements
You cannot hold someone to a policy they have never seen. In week one, the new starter should receive — and acknowledge in writing — at minimum:
- the disciplinary and grievance procedures (a legal particular if not in the statement itself);
- health and safety policy (legally required in writing if you have five or more employees — Health and Safety at Work etc. Act 1974, section 2(3));
- data protection / privacy notice for employees (UK GDPR Article 13 transparency obligations apply to staff data from collection);
- IT, expenses and any policy that could later justify a deduction or a disciplinary decision.
"Acknowledged in writing" can be as simple as a signature sheet or an HR-system click-through. What matters is that you can prove it two years later.
DBS and other checks. Only run Disclosure and Barring Service checks where the role is eligible — most office roles are not. Over-checking is its own compliance problem.
Month one: the rest of the foundations
- Emergency contact and personal data collected and stored securely, access restricted.
- Holiday entitlement confirmed in writing for the current leave year (pro-rated for part-year starters).
- Equipment and expenses recorded: what was issued, the policy on return.
- Probation reviews scheduled (if your contract has probation — it should) before the diary fills up.
- Training records started: induction training, mandatory safety training, anything regulatory. If it is not recorded, in law's eyes it often did not happen.
Template: first-week compliance tracker
New starter compliance tracker
Name / role / start date:
BEFORE START
[ ] Right to work check completed — method: manual / digital IDSP / online
Evidence copy stored (location): Follow-up check due:
[ ] Signed contract = written statement received before day one
WEEK ONE
[ ] P45 received or HMRC starter checklist completed
[ ] Payroll record created; tax code verified on first payslip
[ ] Auto-enrolment assessment done / postponement notice issued
[ ] Policies issued and acknowledged (list): disciplinary, grievance,
H&S, privacy notice, IT, expenses
[ ] Employee privacy notice provided
[ ] Emergency contact details collected and stored securely
[ ] Holiday entitlement for leave year confirmed in writing
[ ] Equipment issued recorded
MONTH ONE
[ ] Probation reviews scheduled (dates):
[ ] Mandatory training completed and recorded
[ ] DBS / other checks completed ONLY if role-eligible
The practical takeaway
None of this is difficult. All of it is sequential, dated and provable — which is exactly why it fails when it lives in someone's memory. Turn it into a checklist attached to every hire, whoever is hiring, and the compliance layer of onboarding stops depending on anyone having a good week.
If you are hiring your first employees — or you suspect your current onboarding would not survive an HMRC or Home Office visit — 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.
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.