The short answer
A useful handbook explains how work happens: who approves leave, how pay is checked, what conduct is expected and where employees raise concerns. It should fit your company’s actual practices and applicable employment framework. Copying another employer’s policies can create contradictory promises or unlawful restrictions.
Start with the questions employees actually ask
Collect the questions managers answer repeatedly: who approves time off, when salary information is checked, what to do when a document expires, and how to report a problem. These are the decisions a small business should make explicit first.
Identify the employment framework and existing contracts before writing. Use the applicable authority’s guidance to verify requirements; MOHRE provides official employer and employment resources. [1] A handbook is an operating reference, not a way to replace the law or remove contractual rights.
What belongs in the first version?
- Working arrangements, attendance and the approval route for changes.
- Leave requests, required records and a clear decision owner.
- Payroll inputs, salary-change authorisation and how to raise a pay query.
- Conduct, conflicts of interest, confidentiality and acceptable system use.
- A safe way to raise concerns and a fair escalation process.
- Document handling, access to personnel data and responsibilities when employment ends.
Replace vague rules with usable workflows
‘Leave needs approval’ leaves four unanswered questions: where is the request sent, how far ahead should it be submitted, who decides and where is the decision recorded? Write those steps in plain language, then check whether managers can actually follow them.
Avoid automatic disciplinary or deduction wording copied from a template. Have sensitive clauses checked against the applicable framework. Separate the policy statement from internal manager instructions, and give employees a version they can understand.
How do you roll out a handbook without confusion?
Give the document a version date, a named owner and a contact for questions. Review it against contracts and existing promises before issuing it. Explain the changes, let people ask questions and record acknowledgement; a signature is not evidence that a contradictory clause became valid.
Keep approved changes in one place rather than allowing different managers to circulate their own copies. Review after a meaningful operational or regulatory change and when a recurring dispute reveals ambiguity. Do not label a policy ‘compliant’ merely because a template provider used that word.
A quick test before you issue it
- Can a new hire find the leave and pay-query process in under a minute?
- Does every recurring process name a decision owner and a record?
- Do the handbook, contract and actual practice agree?
- Have jurisdiction-specific and sensitive clauses been checked?
- Is there one current version, and can staff access it?
Questions worth answering
Is a handbook the same as an employment contract?
No. They serve different purposes. The handbook explains workplace processes; contractual terms and applicable rules still need to be respected.
How long should the handbook be?
Long enough to answer real recurring questions clearly. An accessible short document with reliable workflows is more useful than a long template no one uses.
Official sources
Source pages checked 10 October 2026. Numbered references in the guide correspond to the sources below.
Your next step
Choose the support that fits this decision. Each link takes you to the relevant service page.
This guide is practical preparation, with official sources where relevant. Company-specific requirements need an assessment of your circumstances. How these guides are prepared.
