Guide

The employee handbook: what to include and how to write it

An employee handbook is the single document that answers "how does employment work here?" — hours, leave, pay, conduct, and how to raise problems — so that every employee gets the same answer and the company can prove it gave one. It is not a legal contract (and should say so where local practice requires), but it is evidence: in disputes, the handbook plus the employee’s acknowledgment of it is often the company’s primary exhibit. Both purposes reward the same virtue: a short handbook that people actually read.

What belongs in

Working basics — hours, breaks, schedules and how they are set, remote/hybrid rules, overtime expectations.
Leave — annual leave, sick leave, public holidays, parental and special leave; how to request each and what happens with unused balances.
Pay mechanics — pay dates, how overtime and premiums work, expense reimbursement, who to ask about payroll errors.
Conduct — the code of conduct core: respect, safety, conflicts of interest, and the anti-harassment commitment with its reporting route.
Data and equipment — acceptable use, security basics, what monitoring exists (stated honestly), personal data handling.
Problem routes — how to raise a grievance, how disciplinary matters proceed, and the appeal path. Employees follow processes they know exist.
The acknowledgment page — signed or digitally confirmed, stored per employee. A handbook without acknowledgments protects no one.

What to leave out

Everything that changes monthly (names, org charts, tool guides — link to living documents instead), everything aspirational that operations contradict (a "flexibility" chapter above a rigid scheduling reality damages trust and, in dispute, credibility), and everything copied from a template that does not describe your company — tribunals and employees both notice when the handbook’s company and the actual company differ. The test for every paragraph: is this a rule we really apply, stated the way we really apply it?

Tone, length, and maintenance

Write it in plain second-person language ("you can request leave by…"), keep it as short as completeness allows — for small companies that is commonly 10–20 pages, not 60 — and date every version. Review annually and when law or practice changes; each revision needs re-acknowledgment for the changed sections and version history kept, because "which handbook was in force that March" is a question that eventually matters. Store the handbook and its acknowledgments in the employee-records system — in EmployDB, policy documents and per-employee acknowledgments live in the employee file with dates, which is exactly the retrievability the handbook’s evidentiary job requires. This article is informational, not legal advice; several jurisdictions mandate specific handbook content — check locally.