The Employee Handbook From Scratch: What Goes In, What Doesn't

60-Second Summary

A good handbook is the shortest document that answers 90% of repeated employee questions.
Split it: ~25 pages of policy + a living wiki of operational how-to's. Don't mix them.
Nine sections are regulator-relevant — those need legal review, the rest can be voice-led.
Version, date, and re-acknowledge annually. A handbook without a date is a handbook without authority.

Most employee handbooks fail one of two ways — too long to read, or too thin to defend. This is the operating spec for a handbook that does both jobs at once.

What a handbook is for

A handbook serves three audiences: a new employee who needs orientation, a manager who needs a defensible answer, and a regulator who needs to see your written policy. Each section should be auditable against those three uses.

The recommended structure

Three-tier structure

1
Tier 1 — Handbook (PDF + signed)
Policy. Regulator-readable. ~25 pages. Re-acknowledged annually.
2
Tier 2 — People wiki
Operational how-to's, FAQs, links to systems. Living document, no signatures.
3
Tier 3 — Manager playbook
Internal — scripts for hard conversations, escalation paths, decision rights.

Why three tiers

If you put operational how-to's in the handbook, you'll re-issue it every quarter. If you put policy in the wiki, you'll lose every dispute that hinges on what the policy 'really was'. Separate them.

The 9 regulator-relevant sections

Equal opportunity and anti-discrimination — required in almost every jurisdiction
Anti-harassment and reporting channels — must include a non-retaliation clause
Code of conduct and disciplinary procedure
Working hours, overtime, and rest-period rules
Leave (annual, sick, parental, bereavement) and accrual rules
Health, safety and incident-reporting procedure
Confidentiality, IP, and data-protection obligations
Acceptable use of IT, AI, and company resources
Termination, notice, and grievance procedure

These nine should be written or reviewed by an employment lawyer in your primary jurisdiction. Everything else in the handbook can be in your own voice.

Voice and tone

Handbook voice that ages well

Plain language, second person ('you'), short sentences
Examples for ambiguous rules
Explain the 'why' for unusual policies
Acknowledge what we don't yet have

Don't

Corporate-speak, latin abbreviations
Lists of prohibited behaviours without context
Anything that contradicts a public statement
Promises ('We always…') that you can't keep

What does NOT belong

Org chart and team rosters — they go stale instantly
Vendor list, software list, login URLs — these belong in the wiki
Performance review form text — those evolve faster than the handbook
Comp bands or pay ranges — confidential and time-bound
Anything that reads like a marketing brochure

Versioning and re-acknowledgement

Every handbook page should carry a version, an effective date, and a 'last reviewed' date. Re-issue annually with a redline summary of what changed, and require every employee to re-acknowledge electronically. Store the acknowledgements with the employee record.

Where to host it

Single canonical source (HRIS handbook module or a versioned PDF on a known URL)
Searchable from day-1 onboarding portal
Mobile-readable — most first reads happen on a phone, not a laptop
Translated to working languages for any office with > 25 employees

References

GitLab Handbook — a public reference — GitLab
SHRM — Employee Handbook Toolkit — SHRM
Holloway — Employee handbook patterns — Holloway

Written by Pawan Joshi.Sources cited inline.

First published 16 Jun 2026See site changelog →