Documents · Glossary

What is an employee handbook?

An employee handbook is one document that collects the policies, expectations and practical information a workplace gives its staff: hours, leave, conduct, safety, technology use and how to raise a problem. It is issued to every employee, usually at induction, and reissued whenever the rules behind it change.

Most workplace disputes start with somebody saying they were never told. A handbook is the cheapest proof that they were, which is why the document earns its place even in a business of twelve people.

· Co-founder

6 min read · Published

Handbook, policy and contract compared
Employee handbookA single policyEmployment contract
What it isEvery policy collected in one documentOne rule on one subjectThe agreement between employer and employee
Binding forceOnly if the contract says the policies are termsSame, and usually stated policy by policyBinding on both parties
Changed byReissuing the whole handbookReissuing that one policyAgreement, or a variation clause
What is signedAn acknowledgement of receiptSometimes an acknowledgementThe agreement itself, by both
Who it coversEverybodyEverybody the policy namesOne named employee

Who the handbook is written for

The reader is a new starter in their first week, not a lawyer. That decides the register: short sentences, present tense, the second person, and headings somebody can scan standing up in a break room. A handbook written only to survive a legal review gets skimmed once and never opened again, which defeats the reason for writing it. The useful test is whether a casual employee can find the answer to a real question, such as how to swap a shift or who to tell about an injury, in under a minute. If they cannot, the document is a filing exercise. Order matters more than length here. Put the things people need weekly at the front, the things they need once at the back, and keep the index honest so nobody has to guess which of two similar headings holds the answer they want.

Whether the handbook forms part of the contract

This single question decides how much risk the document carries. In Australia a handbook is usually expressed as policy rather than contractual promise, and most employment contracts say so directly, describing the policies as lawful and reasonable directions rather than terms. The wording cuts both ways. If the handbook is contractual, an employer who skips a step in its own disciplinary procedure can be in breach of contract; if it is not, the employee cannot sue over the missed step, though the employer still has to act reasonably. Courts have treated handbooks as contractual where a contract incorporated them by reference and the language read like a promise rather than a guide. The safe arrangement is to state the position plainly in the contract and then keep promissory language out of the handbook itself.

The floor the handbook cannot go below

Nothing in a handbook can reduce an entitlement that comes from the National Employment Standards, a modern award or an enterprise agreement. Anything it says about leave, notice, hours, breaks or public holidays has to sit at or above that floor, and where an award covers the workplace the award wins on any conflict. That is why the leave section of a well built handbook is short: it points at the award and the legislated minimum instead of restating numbers that will be wrong within a year. The sections worth writing in full are the ones no instrument sets for you. How a roster is published and how far ahead. Who approves a shift swap and by when. What the dress standard means in practice. How a complaint is made, who hears it, and what the employee is told afterwards.

The mistakes that cost employers

Three repeat often enough to be predictable. Copying a handbook from another business, which imports policies for roles that do not exist and leaves out the hazards that do. Writing fine procedural detail into a document that is reissued once a year, so the handbook contradicts what the team actually does within a month. And issuing it without recording that it was issued, which removes the only evidentiary reason to have written it. A fourth is subtler and more expensive: promising a process nobody follows. A handbook that describes three written warnings before dismissal, in a business that has never given three, is evidence against the employer rather than for it. Write the process you will actually run, then run it.

Building one as a document

A handbook is a long document, so it is planned section by section rather than written in a single pass, and it carries a cover, running headers and a table of contents. Contents are only used on a long document, and the headings have to match the contents entries exactly for the page numbers to resolve. The forty five component types cover what a handbook actually needs: headings, paragraphs, callouts in four variants for the notices that matter, tables for roster and leave summaries, timelines for an induction sequence, and a signature block when the acknowledgement page is signed rather than collected separately. One signature block party is one signer, so an acknowledgement countersigned by a manager needs two parties, not one. There are seven cover layouts and ten theme presets to pick from.

Questions people ask

Does a small business need a handbook?

There is no legal minimum head count that triggers one. The practical trigger is the first time two people get a different answer to the same question, which usually happens at about five staff. A short handbook of fifteen pages that is actually followed beats a forty page one copied from a template and ignored by everybody including the owner.

How often should a handbook be reviewed?

Once a year as a habit, and immediately whenever an award is varied, a role changes shape, or an incident shows a policy did not work. Date every version on the cover and keep the superseded ones, because the question in a dispute is what the policy said on the day, not what it says now.

Do employees have to sign the handbook?

They do not have to sign the handbook itself, but they should sign or otherwise acknowledge that they received it and had a chance to read it. An email acknowledgement with a date is enough in most cases. What matters is that the record names the version, because acknowledging an unspecified handbook proves very little later.

Can a handbook be used in a dismissal?

Yes, and it usually is. The employer relies on it to show the standard was communicated, and the employee relies on it to show the process promised was not followed. That symmetry is the reason to keep the disciplinary section modest and to avoid committing to a fixed number of warnings you may not want to give.

Should contractors get the handbook?

Give contractors the parts that apply to anybody on site, such as safety, site access, privacy and conduct, and keep the employment sections out. Handing a contractor a full employee handbook, with leave and performance review policies in it, is one of the small facts that gets pointed at later when somebody argues the relationship was really employment.

Is a handbook the same as an induction pack?

No. The induction pack is what a person needs in week one: logins, contacts, the tour, the first roster, the safety briefing. The handbook is the reference they keep. Many businesses merge them and end up with a document that is too long for induction and too transient to be a reference, so it is worth keeping the two apart.

Make one with documents

The button opens the generator with this use case already described. Change the wording to match your own.

Create a document with OneCraft

Related questions

Step by step in the builder: Create a document with AI, then Add a cover page to your document.

Sources

Written and checked by the OneCraft team. Last checked .