Do you need an employee handbook? What UK law actually requires

So someone's asked you, right, "do we actually need an employee handbook", and you've gone away to check, and now you're here. Fair enough. The honest answer is no, not exactly, but also kind of yes, and I promise that makes sense in a minute.

Because here's the thing nobody tells you upfront: there's no law that says "thou shalt produce a handbook." But there IS a pile of stuff that has to exist somewhere, in writing, whether you fancy doing it or not. A handbook is just... a tidy place to put all that stuff. That's it. That's the whole pitch.

Is an employee handbook a legal requirement?

No. Straight answer, no hedging needed on that one. There's no rule that names "the handbook" as a required document.

What there IS, is a bunch of individual legal requirements that need writing down somewhere, and a handbook happens to be a sensible home for them. Contract terms can live in an employee handbook or on a company notice board, so the government itself basically nods at handbooks as a valid place to keep this stuff. And ACAS notes that a contract can include things like "the organisation's code of conduct" and other policies, which is exactly the sort of material a handbook tends to hold.

So think of it less as a legal box to tick, and more as, I dunno, a filing cabinet with a friendlier font.

Handbook vs contract vs written statement

This is where people get tangled, so let's untangle it a bit.

Your employees and workers are legally entitled to a written statement of employment particulars. That's a specific, defined thing, and it's important to know that it's not the employment contract itself. The contract is bigger than the statement. The statement is just the bit that has to be written down and handed over.

Timing matters here too. The principal statement, the core bit, has to land on day one. The wider statement, the rest of it, has to follow within 2 months of the start of employment.

Now, where the handbook earns its keep: the wider statement can cover things like disciplinary and grievance procedures, and day-one details on sick pay, leave, and notice can actually sit in a separate document, as long as it's genuinely accessible, such as on the employer's intranet. If you're pointing employees elsewhere for details, you need to be specific about what those documents are and where to find them. Vague gestures towards "the system" won't cut it.

One more thing worth knowing: if you change any of this stuff later, you've got to notify the change within one month of making it. Not "eventually." A month.

And because contracts and handbooks blur together so easily, GOV.UK is pretty clear that you should make clear which parts of a contract are legally binding and which aren't. This matters more than people think, and I'll come back to it later because, honestly, it's the bit most handbooks get lazy about.

What must be in writing

So, beyond the written statement itself, Acas also flags that the standards of behaviour expected from employees should be written down. Conduct standards, basically. What's okay, what isn't.

Disciplinary and grievance procedures need the same treatment. Acas is pretty blunt about this: these rules should be set down in writing, be specific and clear. Not vague vibes about "we'll sort it out." Actual, specific, written procedure.

You're starting to see the shape of it now, I think. None of these individual requirements says "put me in a handbook." They just say "be written down, be accessible, be specific." A handbook is just a convenient answer to all three at once.

Disciplinary and grievance: the Acas Code

This deserves its own bit because it's got real teeth.

The Acas Code of Practice on disciplinary and grievance procedures is, in its own words, the minimum an employer should follow. Minimum. Not aspirational, not a nice-to-have.

Here's the bit that should make you sit up: breaching the Code doesn't automatically create legal liability on its own. But, and this is a big but, employment tribunals will take the Code into account when they're looking at a case. So even where breaching it doesn't create liability on its own, it's what a tribunal looks at when deciding who was being reasonable.

And the practical sting: tribunals can adjust compensation by up to 25 per cent, either up if the employer unreasonably failed to follow the Code, or down if the employee did. So getting your disciplinary and grievance procedure written down, clearly, properly, isn't just tidy admin. It's the difference between a bad day and a genuinely expensive one.

Health and safety paperwork

Switching gears slightly, but still very much in "must be written down" territory.

Every business needs a health and safety policy, full stop, regardless of size. But once you hit five or more employees, you must write your policy down. Below that you still need a policy, just not necessarily a written one, though I'd write it down anyway.

You also need to share it, and share any changes to it, with your employees. Not just file it away somewhere and hope osmosis does the rest.

Two more bits of paperwork that need to be visible, not just written: your employers' liability certificate needs to be displayed where employees can access it, whether that's a physical noticeboard, a website, or an intranet. And you need to either display the HSE-approved law poster or hand out the equivalent leaflet to each worker.

Worth flagging too: there's a planned duty, from 30 October 2026, requiring employers to take all reasonable steps to prevent sexual harassment of their employees. Worth keeping an eye on, even if it's not live yet.

What to include in a handbook

So, pulling this together. A sensible handbook usually ends up holding the conduct standards, the disciplinary and grievance procedure, the health and safety policy, and pointers to wherever the sick pay, leave, and notice details actually live if they're kept separately.

The one thing I'd genuinely push you on: label each policy as contractual or not. Explicitly. In the document itself. Because otherwise you end up in a mess where nobody, including you, knows whether changing the dress code counts as a breach of contract or just an update to guidance. GOV.UK's steer on this is clear, you need to make clear which parts of a contract are legally binding. Do that labelling now and you save yourself a proper headache later.

Keeping it current

Handbooks rot if you leave them. Date every policy. Keep one current version, not six slightly different PDFs floating around in various inboxes. And when something changes, actually announce it, don't just quietly swap the file and assume people will notice.

Given the Employment Rights Act 2025 is phasing in over time, this is worth treating as an ongoing bit of admin rather than a one-off project you finish and forget. Review it. Again. And again after that.

This is general information, not legal advice, so check Acas or GOV.UK for guidance specific to your own situation.