How to Write an Employee Handbook People Actually Read

What is an employee handbook, and how is it different from policies?

An employee handbook is a readable guide to working at your organisation. It explains your purpose and values, answers the questions people ask in their first months, and summarises your main policies with links to the full versions. It is not the only document people need, and much of the confusion in handbook projects comes from mixing four kinds of document that change at different speeds.

Keeping these apart is the single most useful design decision you will make. If software instructions sit inside a policy, every tool change becomes a formal policy change. If contract terms are copied into the handbook, you may not be able to update the handbook without changing contracts. Whether your handbook is contractual depends on its wording and on local law, which is one of the first questions to ask a qualified adviser.

What should an employee handbook include?

A good handbook is short enough to read in one sitting, usually 25 to 40 pages for a mid-size organisation, and organised around the questions employees actually ask. Write the headings as questions and lead each section with the answer.

Clear expectations matter more than they look. Gallup has reported that only about half of employees strongly agree they know what is expected of them at work, and it treats that clarity as a foundation of engagement. A handbook that answers everyday questions plainly is one practical way to help.

• A welcome from the leader, with your purpose in one sentence
• How the handbook works: which version applies, where it lives, and that full policies and local law take precedence
• Values, with what each looks like in practice
• Your first weeks and probation
• When and where you work, including flexibility and out-of-hours contact
• Pay, expenses and benefits
• Time off, with a table linking to each leave policy
• Health, safety and wellbeing
• How we treat each other, and several ways to raise a concern
• Technology, data protection and AI use
• Performance and learning
• What happens if things go wrong: grievance and disciplinary
• Leaving
• Country information and a policy index
• An acknowledgment page

How do you write an employee handbook step by step?

Most handbook projects fail through order, not effort: writing before scoping, drafting before checking what exists, launching without telling managers first. The eight steps below put the work in a sequence that avoids those traps. Each step produces something concrete you can show to a leader or an auditor.

How many policies does a small business need?

Fewer than the long lists suggest, chosen for your size, your countries and your risks. A practical approach is three tiers. Core policies protect people and set the basic deal from the first hire: code of conduct, anti-harassment, speak-up, working hours, leave, sickness, data protection, health and safety, grievance and disciplinary. Recommended policies matter as you add managers, countries or hybrid work: flexible work, expenses, IT use, social media, AI use, conflicts of interest and performance. Optional policies depend on your work: drug and alcohol testing where lawful, volunteering, sabbaticals.

Risk changes the tier. A 30-person firm that holds payment data should treat information security as core. A firm whose people deal with customs agents or public officials needs anti-bribery controls early. If you employ people in more than one country, write a global core that never promises less than local law, and put local entitlements and procedures in country addenda with matching policy numbers.

How do you make a handbook easy to read?

Plain language is now an international standard rather than a matter of taste. ISO 24495-1, published in 2023, sets out governing principles and guidelines for plain language documents, and US federal guidance on the Plain Writing Act of 2010 remains a useful free resource for anyone writing for a broad audience.

In practice, seven habits do most of the work. Use readability formulas such as Flesch Reading Ease as a smoke alarm, not a judge: a score of 60 or more usually reads as plain English for adults, but it cannot tell you whether a policy is accurate, kind or complete. Test drafts with two or three employees who were not involved by asking them to find the answer to three real questions.

• Lead each section with the rule, then explain why
• Use 'you' and 'we' instead of 'employees are required to'
• Keep the average sentence under 20 words
• Choose everyday words: use, before, if
• Write headings as questions people ask
• Use numbered steps and tables for entitlements
• Give one example for every rule that needs judgement

Can you use AI to write an employee handbook?

Yes, as an assistant. Microsoft and LinkedIn's 2024 Work Trend Index, a survey of 31,000 people in 31 countries, reported that 75% of knowledge workers used generative AI at work and 78% of those users brought their own tools. Your employees are probably already using AI, which is a reason both to use it carefully in the handbook project and to include an AI use at work policy.

AI is genuinely useful for organising notes into a template, rewriting dense text in plain language, comparing two policies for contradictions, and drafting FAQs and quiz questions. It must not decide what a rule is or whether something is lawful. AI tools can produce confident references to laws or sections that do not exist, so mark every legal statement in a draft and verify it with a reliable source or a qualified adviser. Never paste employee names, case details or confidential plans into a tool your organisation has not approved for that data.

A good AI use policy answers six questions: which tools are approved for which data, what people must check before relying on output, when to disclose AI use, what AI can never decide alone (hiring, pay, discipline and other decisions about people), who owns the output, and how to ask for a new tool. Because the technology and the law move quickly, review it every six months.

How do you launch a handbook and get acknowledgments?

Treat the launch as a change, not a broadcast. Brief managers two weeks before, give them the FAQ first, and ask them to cover the main changes in team meetings. On launch day, send a short email from a leader that explains why, lists the five biggest changes, links to the handbook rather than attaching it, and gives a clear deadline.

An acknowledgment records that a person received the handbook and had the chance to read it. Make it meaningful by listing what changed and adding three to five short comprehension questions, then track completion by team so you can follow up where it is low. Plan for groups a standard email misses: shift workers without company email, people on leave, new joiners, people who need accessible formats and people who read another language more comfortably. In the UK, for example, GOV.UK explains that some employment information can sit in other documents employees can reasonably access, which is one reason the handbook's home and access matter.

What are the most common employee handbook mistakes?

The same handful of mistakes turns up in handbook after handbook, whatever the size of the organisation. Almost all of them come from treating the handbook as a one-off writing task rather than a system with owners, versions and feedback. The table pairs each mistake with the habit that prevents it.

How often should you update an employee handbook?

Review every policy at least once a year, fast-moving ones such as AI use every six months, and start an early review whenever the law changes, the business changes, an incident shows a policy failed, or questions about one policy keep coming. Keep a questions log and a change log: the first tells you where the handbook is unclear, the second shows which version applied on any date.

Speak-up and harassment policies deserve particular care at review. The CIPD notes that a clearly defined whistleblowing policy helps build a culture in which concerns are raised early. If you are developing the judgement these reviews need, the HR Business Partner and Employee Relations Judgment assessment on AssessAll can show your starting point, and a Jobulary development plan can turn the gaps into a plan.

The Employee Handbook and Policy Builder from Bodhih Training gives you a workbook that flags overdue reviews, logs questions and changes, and tracks acknowledgment by team, alongside 33 policy templates and an 8-week project calendar.