Does a small company legally need an employee handbook?

A handbook itself is rarely mandatory, but several of the policies inside one often are, and which ones depends entirely on where your people work. Anti-harassment policies, working time and leave terms, and health and safety obligations are commonly required, and some jurisdictions require specific policies once you cross a headcount threshold. The practical answer is that the handbook is optional and the policies are not, so write the policies and collect them somewhere findable.

How long should an employee handbook be?

Short enough that a new joiner reads it in one sitting, which in practice means somewhere between ten and twenty five pages for a company under two hundred people. Anything longer is a document people scroll past and then claim to have read. If you find yourself writing a procedure that changes every quarter, that belongs in a living document elsewhere, not in the handbook. The handbook holds the things that are true for everyone and change rarely.

Should the handbook be part of the employment contract?

Usually not, and this matters. If the handbook is contractual, you cannot change it without going through a variation process with every employee. Most employers state explicitly that the handbook is a statement of policy rather than a term of the contract, with the exception of any specific policies that are expressly incorporated. Get that wording checked locally, because the effect differs between jurisdictions and getting it wrong makes every future update expensive.

How do we prove that someone read it?

Issue it as part of onboarding, ask for an acknowledgement, and record the acknowledgement against the person with the date and the version they saw. That last part is what people forget: an acknowledgement of an unversioned document proves nothing two years later when the policy has been rewritten twice. A system that files documents against the record with an audit trail turns this from a memory into evidence you can produce.

How to write an employee handbook

Most first handbooks are written in one of two ways, and both are wrong. Either someone downloads a fifty page American template and finds and replaces the company name, producing a document full of policies that do not apply to anyone who works here. Or nobody writes one at all, and the rules exist as a set of precedents held in the founder’s memory, applied inconsistently, and discovered by employees one at a time.

The point of a handbook is narrow and worth stating: it is where a person finds the answer to a question about how this company works without having to ask another person. That is it. Everything about how to write one follows from that.

What it is for, and what it is not for

A handbook is a statement of policy, not a contract, not a culture deck, and not a procedure manual.

It is not the contract, because contractual terms live in the employment agreement and changing them requires a variation process with each employee. Most employers state explicitly that the handbook is policy rather than a contractual term, with any exceptions expressly named. Get that wording reviewed locally, because it determines whether your next update costs an email or a negotiation.

It is not the culture deck. Values belong somewhere, and that somewhere is not the section a person reads when they want to know how much notice they need to give for annual leave.

It is not the procedure manual. Anything that changes quarterly, such as which tool you use for expenses or who approves what this month, goes in a living internal document. The handbook holds the things that are true for everyone and change rarely, because a handbook that needs reissuing every quarter is a handbook nobody reissues.

The sections that earn their place

Here is a structure that works for a company between ten and two hundred people. Ten sections, each short.

1. Welcome and how to use this. Two paragraphs. What this document is, what it is not, who to ask when the answer is not here, and how it is kept up to date.

2. Working arrangements. Hours, whether the company is office, hybrid or remote, expectations about availability across time zones if you have people in more than one, and how any of that is agreed and changed. If you run a distributed team, HR for a distributed multi-country team covers the practicalities that belong here.

3. Leave and time off. The single most consulted section, and the one most often vague. Leave types, whether entitlement accrues or is granted annually, carry-over rules, public holidays and how they differ by location, notice for requests, and who approves. Write it properly once. The leave policy guide sets out the decisions, and the leave policy generator will produce a draft you can edit in your browser.

4. Pay and expenses. Pay date and cycle, how pay is reviewed and when, what expenses are reimbursable and the approval route, and how to claim. You do not need to publish the pay bands here, though you should know what they are. The salary band calculator turns a min and a max into quartiles if you are building your first ones.

5. Conduct and the standards everyone is held to. Anti-harassment and anti-discrimination, conflicts of interest, use of company systems, confidentiality, and what happens when someone reports a concern. In India, this is where your anti-harassment policy under the POSH Act sits, and there are specific obligations that come with it; POSH compliance for a small team covers what those are.

6. Data, devices and security. What you do with employee data and what employees must do with company data. Device rules, password practice, what happens on a lost laptop, and the basics of who can see what. This section is doing double duty: it tells employees the rules and it is evidence when a customer asks how you train staff. HR data security and compliance is the fuller reference.

7. Performance and development. How performance is discussed, on what cadence, and how that relates to pay. Being explicit that ratings and compensation are separate conversations is worth a sentence, and a light performance review process explains why.

8. Health, safety and wellbeing. Proportionate to your context, and required in more places than founders expect, including for remote workers in several jurisdictions.

9. Raising a concern and grievances. How someone raises an issue, to whom, what happens next, and the alternative route if the issue involves their manager. A grievance route with only one door is not a grievance route.

10. Leaving. Notice on both sides, what happens to leave balances, what documents the person receives, and what they need to return. Setting expectations here removes most of the friction later; the offboarding checklist is the operational version of the same content.

What to leave out

Policies for laws that do not apply to you. The downloaded template problem. If you have no US employees, you do not need US federal leave provisions, and having them signals that nobody read the document.

Anything you will not enforce. An unenforced policy is worse than no policy, because it establishes that policies here are decorative and it creates an inconsistency you will be asked about the first time you do enforce it.

Country-specific detail in the main body. If you employ in three countries, put what is common in the handbook and the local variations in a short annexe per country. A single document trying to be true everywhere becomes true nowhere.

Numbers that change. Contribution rates, tax thresholds, statutory limits. Reference the concept and let the payroll partner hold the number, for the same reason we do not print rates on this site: they change, they vary by state, and a stale number in a handbook is a promise you did not mean to make.

Multi-country, without three handbooks

The pattern that works is one core handbook plus a short local annexe.

The core holds conduct, data and security, performance, how concerns are raised, and the general shape of leave and working arrangements. The annexe holds what is genuinely local: statutory leave entitlements, public holidays, notice periods, and any policy the jurisdiction requires. That way an update to the anti-harassment policy is one edit rather than three, and a change to Indian statutory leave does not require reissuing the document to your UK team.

If you are heading toward a second country, what breaks when you hire in a second country covers the things that go plural and why the handbook is only one of them.

Issuing it, and proving it was issued

A handbook nobody acknowledged is a handbook that does not help you.

Issue it as part of onboarding, alongside the contract and before the first day rather than in week three. Ask for an acknowledgement. Then record that acknowledgement against the person with the date and, critically, the version they saw. An acknowledgement of “the handbook” proves very little once the handbook has been rewritten twice.

This is a small thing that is annoying to do by hand and trivial to do with a system. In the Capstan core, documents are collected as part of the onboarding checklist, filed against the person, and every action lands in an activity log with the actor and the timestamp on it, exportable by your own admin without asking anyone. When a customer, an auditor or a tribunal asks whether the policy was issued and when, that is a lookup rather than a search of three inboxes.

Keeping it alive

Set a review date and put it in your HR compliance calendar rather than trusting that someone will notice the document is stale. Once a year is enough for most of it, with an out-of-cycle update whenever a policy actually changes.

Version it visibly. Put the version and the date on the first page, and keep the previous versions rather than overwriting. When someone asks what the carry-over rule was in 2025, the honest answer requires the 2025 document to still exist. This is the same argument as everywhere else in HR record-keeping: the value of a record is that it can be read as it stood at a date, not only as it stands today.

And re-issue it when it changes. A handbook update that nobody was told about is a policy change nobody agreed to, which is the situation you wrote the handbook to avoid.

The shortest useful version

If you have ten people and no handbook, do not write ten sections this week. Write four: leave, conduct and anti-harassment, data and devices, and how to raise a concern. Those four cover the obligations most likely to actually apply to you and the questions most likely to actually be asked.

Add the rest as the company gets big enough for them to matter. A four-section handbook that is accurate and read beats a forty-page one that is downloaded and ignored, and unlike the forty-page one it will still be true next quarter.

How to write an employee handbook people actually read