What it is for
A handbook exists to make the organisation's answers consistent. Without one, the same question gets different answers from different managers, and employees learn that outcomes depend on who they ask.
It is also evidence, and this is the part organisations underweight when drafting. A handbook is a written statement of what the employer says it does, produced by the employer, and it will be read back to them in any dispute about what someone was entitled to expect.
Those two purposes pull in different directions. Consistency argues for saying more; evidence argues for saying only what the organisation intends to be held to. The resolution is not to say less but to say accurately: describe what actually happens rather than what would sound good.
What belongs in it
- How the organisation works day to day: hours, attendance, leave application, expenses, equipment.
- Conduct expectations, with the disciplinary and grievance routes cross-referenced rather than reproduced.
- The policies employees actually search for: leave, notice, working from home, travel, reimbursement.
- Who to contact for what, which is the single most-used part of most handbooks.
- How the handbook itself is changed, and how employees are told.
What does not belong is a restatement of statutory entitlements. Those come from statute, they change, and a handbook that paraphrases them acquires a maintenance obligation it will not meet. Reference them and hold the detail in one place.
Aspirational material about values is not harmful in itself and is worth keeping short. A handbook whose first ten pages are culture statements trains employees to skip to the part they needed, and they will skip past things that mattered.
Where it does not govern
A handbook is not the top of the hierarchy, and treating it as though it were causes real errors.
Statutory entitlements apply irrespective of what it says, and a handbook term that reduces one does not take effect. Where standing orders apply, under section 28 of the Industrial Relations Code, 2020 to an industrial establishment with three hundred or more workers, they govern the conditions of service they cover and an inconsistent handbook does not displace them.
The contract also outranks it for the terms the contract sets. Where a handbook and an appointment letter disagree about notice, the letter generally governs, and the disagreement itself is a defect worth finding before someone else finds it.
This is an argument for the handbook being explicit about its own status: which parts are contractual, which are policy the employer may change, and what happens when it conflicts with an individual contract.
The maintenance problem
Most handbooks fail here rather than at drafting.
They are written carefully, issued, and then diverge from practice as the organisation changes. Policies are added without removing what they replaced. Statutory references date. Named contacts leave. Commitments about review cycles, training budgets or progression stop being met while remaining in print.
The last is the damaging one. A general disappointment is forgettable; a specific written promise that was not kept is not, and employees can quote it.
| Failure | Consequence |
|---|---|
| Statutory paraphrase left to date | Confidently wrong guidance, relied on by managers |
| Superseded policy left alongside its replacement | Two answers to the same question, both official |
| Commitments no longer honoured | A documented broken promise rather than a vague grievance |
| No version control | Nobody can say what the policy was on the date something happened |
Version control is worth more than it costs. Disputes are about what the rule was at the time, and an organisation that can only produce the current handbook cannot answer that.
Making it usable
A handbook nobody reads still has to be findable, because it is consulted at the moment a question arises rather than read end to end.
- Make it searchable, and available to people without a company laptop or email, which is where a large part of the workforce is often excluded.
- Write each policy so it can be read on its own, since nobody reads the surrounding context.
- Date every policy and keep superseded versions retrievable.
- Tell employees when something changes, in a way that does not depend on them re-reading the document.
- Review annually against what actually happens, and delete what the organisation has stopped doing rather than leaving it in.
Deleting is the underused move. A shorter handbook that is true is more useful, and considerably safer, than a comprehensive one that is partly fiction.
Frequently asked questions
What should an employee handbook contain?
How the organisation works day to day, conduct expectations with the disciplinary and grievance routes cross-referenced, the policies employees actually search for, who to contact for what, and how the handbook itself changes.
Should a handbook restate statutory entitlements?
Better not to. Statutory entitlements change, and a paraphrase acquires a maintenance obligation the organisation will not meet, producing confidently wrong guidance. Reference them and keep the detail in one place.
Does a handbook override an employment contract?
Generally the contract governs the terms it sets, so where a handbook and an appointment letter disagree on notice the letter usually wins. The disagreement itself is a defect worth finding first. Where standing orders apply they govern the matters they cover regardless.
Why is an outdated handbook a problem?
Because it documents commitments nobody is keeping. A vague disappointment is forgettable; a specific written promise that was not honoured can be quoted back. Deleting what the organisation has stopped doing is safer than leaving it in print.
How should handbook changes be managed?
Date every policy, keep superseded versions retrievable, and tell employees when something changes rather than relying on them re-reading. Disputes turn on what the rule was at the time, which an organisation holding only the current version cannot answer.
How Engage keeps policy current
Engage holds policies with their effective dates and keeps superseded versions retrievable, so the question of what the rule was on a given date has an answer. Because employees reach them through the same app that carries payslips and leave, the part of the workforce without a company laptop is not excluded from the policies that apply to them.
See policy management in Engage