How to Write an Employee Handbook for a Small Business
What a small business handbook actually needs to cover, what to leave out, and a section-by-section outline you can fill in without a lawyer on retainer.
Most small business owners either skip the handbook entirely or copy one from a friend's company, find-and-replace the name, and call it done. Both are understandable, and both create the same problem: a handbook that doesn't match how the business actually runs.
A handbook's job is narrow. It's not a culture document, a marketing artifact, or a legal shield on its own. It's the place where "how we actually do things here" is written down once, so it doesn't have to be re-explained — or re-litigated — every time it comes up.
What it needs to cover
Employment basics. At-will status where applicable, equal opportunity statement, classification of employees (exempt/non-exempt, full-time/part-time), and how pay periods work.
Time off. Vacation, sick leave, holidays, and how to request them. This is usually the section employees actually read, and it's worth getting genuinely right rather than vague — a copy-paste PTO section template covers the specific clauses (accrual, carryover, blackout dates, payout) that a vague "flexible PTO" line leaves unanswered.
Conduct expectations. Attendance, dress code if any, use of company property, and anti-harassment policy — this last one is a legal requirement to have in writing in a growing number of states, independent of company size.
Compensation and benefits basics. Not the numbers themselves, but how raises, overtime, and benefits eligibility work in general terms.
Safety and reporting. How to report an injury, a safety concern, or a workplace complaint, and to whom.
Technology and remote work, if applicable. Equipment, expected availability, and any monitoring — covered in more depth in a dedicated remote work policy if more than a couple of people work outside the office.
Separation. What happens to PTO payout, final pay, and equipment return when someone leaves.
What to leave out
State-by-state legal boilerplate you don't operate in. A five-person company in Ohio doesn't need California meal-break language. It adds length and signals the document was never actually reviewed for this business.
Policies you don't enforce. If dress code is genuinely unenforced, don't write one. A written-but-ignored policy is discoverable evidence in a dispute that policy and practice don't match.
Anything that reads like a legal disclaimer more than a policy. A handbook that's mostly liability language, with the actual workplace rules buried in the middle, doesn't get read by anyone.
A simple structure that works below fifty people
- Welcome and company overview (half a page)
- Employment basics and classifications
- Compensation, pay periods, overtime
- Time off and holidays
- Conduct and anti-harassment policy
- Health, safety, and reporting
- Technology, equipment, and remote work
- Separation and final pay
- Acknowledgment page for signature
That's a handbook a new hire can read in twenty minutes and actually retain, which is worth more than one that's comprehensive and unread.
Getting it signed
The acknowledgment page is not a formality — it's the entire point of having a written handbook rather than a set of verbal norms. It should state plainly that the employee received the handbook, is responsible for reading it, and understands it may be updated. Keep the signed copy in the personnel file, and get a fresh signature whenever you make a material change, not just a typo fix.
Updating it
A handbook that's never revised drifts from reality within a year — a new benefit gets added, a policy quietly changes, and the document stops matching what people are actually told when they ask. Review it at least once a year, and any time a policy actually changes rather than waiting for the annual pass. If the PTO policy specifically is what's shifting — a new accrual rate, a carryover cap — the PTO policy generator will draft updated language you can drop straight into the relevant section.
When to bring in a lawyer
A one-time review by an employment attorney before the first version goes out is worth the cost, particularly for the anti-harassment, classification, and termination language — these are the sections where state-specific requirements actually bite, and where a generic template is most likely to be wrong for your state. After that first review, most day-to-day updates (a new PTO accrual rate, an updated remote-work stance) don't need another legal pass unless they touch classification, leave law, or termination terms.
Distributing it so it's actually read
A handbook emailed as an attachment on someone's first day, alongside a dozen other onboarding documents, gets skimmed at best. Two things improve the odds it's actually absorbed: walking through the sections that matter most — time off, conduct, and how to raise a concern — verbally in the first week rather than assuming the document speaks for itself, and keeping a copy easily accessible afterward rather than only distributed once. A handbook nobody can find six months later when a question comes up might as well not exist.
Handling the small-team version of "everyone knows this already"
A common objection at very small companies — five or six people who all know each other well — is that a formal handbook feels unnecessary, even performative. The counterargument isn't about distrust; it's about what happens when the team doubles. The seventh and eighth hires didn't live through the informal norms the first five worked out by trial and error, and without something written down, they're guessing at rules nobody told them existed. Writing the handbook while the team is still small and the norms are still fresh is considerably easier than trying to reconstruct them later from memory once the company has grown past the point where everyone was in the room when a policy was decided.
The short version
A small business handbook should be short, honestly enforced, and reviewed yearly — not comprehensive, borrowed, or written once and forgotten. Get the time-off section right first, since it's the one people read, and build the rest around how the business genuinely operates rather than how a template assumes it does.
Frequently asked questions
Does a small business legally need an employee handbook?
Almost never as a blanket legal requirement, though specific policies — like sexual harassment prevention training in a handful of states — sometimes must be documented and distributed in writing. Below about fifteen employees, a handbook is usually about consistency and protection rather than a mandate.
How long should a small business employee handbook be?
Short enough that people actually read it. Ten to twenty pages covers a small team's real policies. A fifty-page handbook copied from a large-company template mostly signals that nobody who wrote it has read it since.
What is the biggest mistake in a small business handbook?
Writing a policy you don't actually enforce. An unenforced rule in writing is worse than no rule at all, because it becomes evidence that policy and practice diverge — which is exactly what turns a routine dispute into a legal one.
Do employees need to sign the handbook?
Yes — a signed acknowledgment that they received and read it, kept in their file, is the entire point of having one in writing. Without it, you have a document that existed, not proof anyone saw it.