Writing a staff handbook that is actually worth having
Two decisions determine whether a handbook helps you or hinders you: whether it is contractual, and whether anyone has actually been given it. Both are usually made by accident.
Summarise with AI
Key takeaways
- A handbook is normally non-contractual by design — say so explicitly, or you may not be able to change it without agreement
- Disciplinary and grievance procedures must be accessible, and tribunals expect the Acas Code to have been followed
- Some particulars can be given via a handbook the person has reasonable access to, but the principal statement itself cannot be outsourced to it
- A policy nobody has been shown is not a defence — issuing it and recording that it was issued is the part that counts
Contractual or not: decide deliberately
A handbook that forms part of the contract cannot be changed without agreement. That sounds abstract until the day you want to alter the absence-reporting line or tighten the shift-swap rules and discover you are proposing a variation of terms to every member of staff.
Say which parts bind
State plainly that the handbook is non-contractual and provided for guidance, while identifying the few provisions that are intended to have contractual force — a deductions clause, or a PILON right, for example. Silence is the risky option: a handbook that looks like terms and has been relied on like terms may be treated as terms.
The policies you actually need
Start with the ones that do work, rather than the ones that pad a contents page. A short handbook that managers read beats a long one they do not.
| Policy | Why it earns its place |
|---|---|
| Disciplinary and grievance | Must be accessible; tribunals expect the Acas Code to have been followed |
| Absence and sickness reporting | Sets who to tell, when, and what evidence is needed |
| Holiday booking | Replaces the statutory notice defaults with something workable |
| Rota and shift changes | Publication notice, swaps, cover and what counts as a refusal |
| Equality and anti-harassment | Evidence of reasonable steps taken, not just intentions stated |
| Health and safety | Statutory duties, and site-specific in practice |
| Data protection | What staff data you hold and for how long |
| IT, phones and social media | The conduct issue most likely to arise without a rule |
The data protection entry should reflect the retention periods you actually operate — payroll for three years, minimum wage records for six, right to work evidence for employment plus two, as set out in how long to keep employee records. A policy promising deletion you never perform is worse than no policy.
Rota, absence and holiday policies
These three carry most of the day-to-day weight in a shift-based business, and they are where a generic template handbook is least useful.
The rota policy should say how far ahead rotas are published, how much notice of a change staff can expect, how swaps are requested and approved, and what happens when nobody can cover. That last point is not a formality — it is the question that generates the arguments. The Employment Rights Act 2025 attaches obligations to shift notice, so a policy written around vague expectations is one you will be revising anyway.
The absence policy should distinguish reporting from managing. Reporting is mechanical: who to call, by when, and what happens on day four and day eight. Managing is where care is required — statutory sick pay has been payable from day one with no earnings threshold since April 2026, and a trigger score is a prompt for a conversation rather than a decision, particularly where a disability may be involved.
The holiday policy is where you replace the statutory notice defaults — twice the length of the leave to request, the length plus a day to refuse — with something operable, and set out how competing requests for peak dates are decided. Both are covered in handling holiday requests.
Issuing it so it counts
Accessibility is the difference between a policy that helps and a document that does not. Where particulars are provided outside the principal statement, they must be somewhere the person has reasonable access to — and where a policy is relied on in a disciplinary case, the first question is whether the person could have known about it.
- Issue it during onboarding, not on request.
- Record who received which version and when.
- Re-issue when it changes, rather than quietly replacing the file.
- Keep it where staff already look — the same app as the rota beats a shared drive nobody opens.
- Apply it consistently; selective enforcement undermines the policy and the case built on it.
RosterElf's policy management handles the acknowledgement trail — who has been issued what, and who has read it — and digital contracts keep the written statement alongside it so the contractual and non-contractual documents are not living in different systems.
Keeping it current
A handbook goes stale quietly. Two changes make that concrete right now: statutory sick pay became a day-one right without an earnings threshold in April 2026, and the unfair dismissal qualifying period drops from two years to six months on 1 January 2027, with the compensatory award uncapped from the same date.
The second one is worth acting on before it arrives, because it changes how much a badly handled early dismissal costs. If your handbook describes probation as a period where "employment may be ended without formality", that sentence has a shelf life — the position is set out in notice periods and dismissal. Review annually, date each version, and keep the old ones: when a decision is challenged, the question is what the policy said at the time, not what it says now.
Policies people have actually seen
Issue policies, track acknowledgements and keep contracts and handbook versions with the employee record — in the same app as the rota.
This guide summarises good practice for UK staff handbooks and policies and is not legal advice. Contractual status and disciplinary procedures turn on the wording used and the facts of a case. Check GOV.UK or Acas, or take advice, before finalising a handbook. It does not constitute legal, HR, or professional advice and should not be relied on as a substitute for advice specific to your business, workforce, or circumstances.
Staff handbook questions
- The handbook itself is not, but several things in it are effectively compulsory — a disciplinary and grievance procedure the workforce can access, and the particulars that may be given outside the principal statement. Most employers find a handbook the tidiest way to satisfy both.
- Non-contractual in almost every case, and it should say so in terms. A contractual handbook cannot be amended without agreement, which turns a routine policy update into a variation of terms for every member of staff.
- The written statement of particulars is a day-one legal document setting out core terms. The handbook explains how things work in practice. Some particulars can sit in a handbook the person has reasonable access to, but the principal statement cannot be replaced by one.
- At least annually, and whenever the law moves. Sick pay changed in April 2026 and unfair dismissal changes in January 2027 — a handbook still describing the old positions is actively misleading to the managers relying on it.