‍

Most employee handbooks are written by lawyers, for lawyers, and stored where no one looks at them. They cover everything technically, get acknowledged on day one, and disappear. The problem this creates is operational — when a question comes up, no one consults the handbook because nobody can find it or face it.

‍

Explore Annaizu’s shift planning and availability for a more efficient and compliant way to manage this area.

For employers looking to streamline operations, Annaizu’s shift planning and availability can support a more efficient and compliant workflow.

‍

A useful handbook is the opposite: written for the team, structured for the question, kept current and stored where people already look. It will not replace contracts or specialist policy documents, but it will become the first place staff turn — which is the whole point.

‍

What a handbook is — and is not

An employee handbook is a single, accessible document that explains how things work at your business. It is not a contract, and it is not a substitute for specialist policy documents (disciplinary, grievance, equality, health and safety). It is the layer above those — the everyday answers, signposted to the formal documents where needed.

The right test is: when a worker has a question on a Tuesday afternoon, can they find the answer in under 90 seconds?

Decide who you are writing for

Before writing a word, picture the reader. A new starter on day three. An experienced team member who needs to refresh themselves on the holiday-request process. A manager looking up the disciplinary stages. The handbook should serve all three — but the dominant voice should be the new-starter voice, because they need it most and read most carefully.

Use plain English

Plain English is the single biggest predictor of whether a handbook gets read. Specific rules:

• Short sentences. Aim for around 15 words on average.
• Active voice (" you must request leave" rather than " leave must be requested").
• Concrete examples wherever a process is explained.
• Defined terms only where strictly necessary; avoid jargon.
• Numbers and dates spelled out clearly.

If a paragraph cannot be understood by someone outside HR, rewrite it.

Structure for the question, not the policy

The most-read handbooks are organised around what the worker wants to know — " how do I book holiday?" — rather than around the underlying policy hierarchy. A workable contents structure:

• Welcome and the basics (purpose, contacts, opening hours).
• Your first month (induction, training, probation).
• Your day-to-day (rotas, breaks, dress code, reporting absence).
• Pay and time off (payslip, holiday, sickness, family leave).
• How we behave (conduct, equality, social media, customer interactions).
• Health, safety and food safety (emergencies, accidents, hygiene).
• Performance and progression (1:1s, reviews, training, promotion).
• Leaving (notice, references, final pay).
• Useful documents (links to the full policies).

Cover what people actually ask

List the ten questions your team has asked most often in the past year. Make sure each one has a clear, findable answer in the handbook. That alone makes more difference than any structural decision.

Make it visual

A handbook is not a novel. Use:

• Clear headings and sub-headings.
• Short paragraphs.
• Bullet points where genuinely useful.
• Simple diagrams for processes that benefit from them (e. g. how to request holiday).
• Photos of real team members (with permission).

The visual layer signals that the handbook is meant to be read.

Keep it short — and link out

An over-long handbook is unread. Aim for a document that can be skimmed in 20 minutes and read in full in an hour. Link out to specialist policy documents — disciplinary, grievance, equality — for the legal detail, rather than reproducing it in full.

Put it where people already look

The most beautiful handbook is useless if it lives in a folder no one opens. Store it inside the platform staff already use to check rotas and HR documents. Annaizu's employees portal is exactly that: the rota, the time and attendance records, the HR documents and the handbook all sit in one place.

Add a search function or a clear contents list at the front. Make sure the most current version is the only one accessible.

Acknowledge it formally

Workers should formally acknowledge the handbook on induction and again whenever significant changes are made. Annaizu's HR software handles digital acknowledgement, with a date-stamped record per worker for every version they have signed off.

Review it every year

An out-of-date handbook is worse than no handbook. Set an annual review date, get team feedback on what is and is not clear, and update accordingly. UK employment law shifts often enough that a yearly review is the practical minimum.

Common mistakes

• Letting the lawyer's draft go out unchanged — the legal accuracy is preserved but the readability is gone.
• Including everything from every specialist policy and ending up with a 90-page document.
• Storing it somewhere staff do not naturally look.
• Never updating it.
• Making it look like a corporate compliance document rather than a useful guide.

‍

Conclusion

‍

An employee handbook earns its keep when staff actually use it. Plain English, structured around what people want to know, kept short, stored where the team already is, acknowledged formally and reviewed every year — that is the recipe. Combine it with the right tooling — Annaizu's employees portal and HR software — and the handbook stops being a legal artefact and becomes a working document.

‍