The Small-Business Employee Handbook: What Belongs in It (and What Doesn't)

Why a small company needs one at all

Plenty of founders treat the employee handbook as something you write once you hit a hundred people — a binder nobody reads, full of HR boilerplate. That instinct costs small employers money. The handbook is where you set expectations in writing, deliver the notices the law actually requires you to give employees, and — critically — establish the policies you'll be measured against if a termination, a wage claim, or a discrimination charge ever lands. When an employee says "nobody told me," the handbook is your answer. When it's missing, their version of events fills the gap.

This is a practical guide to what a small employer's handbook should contain and, just as important, what to leave out. It is not legal advice; handbook requirements vary by state and headcount, and a one-time review by an employment attorney for your jurisdiction is cheap insurance against an expensive policy.

The at-will statement and the disclaimer — get these exactly right

Two pieces of language do more legal work than anything else in the document:

• The at-will employment statement. In almost every state, employment is at-will by default — either party can end it at any time, for any lawful reason. But careless handbook language can accidentally create a contract that overrides at-will. Phrases like "permanent employee," "you will only be terminated for cause," or a rigid progressive-discipline sequence ("we will always issue three warnings before termination") have all been read by courts as binding promises. State at-will clearly and don't undercut it elsewhere.
• The non-contract disclaimer. The handbook should say plainly that it is a statement of current policy, not an employment contract, and that the company may revise it. Pair it with a signed acknowledgment page that each employee returns — that signature is your proof they received it.

What actually belongs in the handbook

A useful small-business handbook is lean. The core sections:

• Equal employment opportunity and anti-harassment. A clear EEO statement, a definition of prohibited harassment and discrimination, and — most importantly — a complaint procedure with more than one person to report to (so an employee never has to report misconduct to the person committing it). A real, followed complaint process is a genuine legal defense; a policy you don't follow is worse than none.
• Time off and leave. Your PTO and accrual rules, holidays, and any legally mandated leave (sick leave, FMLA if you're at 50+ employees, state family-leave programs). Don't restate the whole policy twice — write it once and get the accrual mechanics right (see writing a PTO policy and getting accrual right).
• Pay and timekeeping basics. Pay periods, overtime eligibility, and the expectation that non-exempt employees record all hours accurately. This is where exempt-vs-non-exempt classification lives in practice (see exempt or non-exempt FLSA classification); a handbook that blurs it invites overtime claims.
• Conduct and the big-ticket policies. Code of conduct, attendance expectations, a clear technology/acceptable-use and confidentiality policy, and — if you do safety-sensitive or federal-contract work — your drug-and-alcohol policy.
• Safety and required notices. Workplace safety basics and any state-specific notices your jurisdiction mandates be distributed to employees.

What to leave out (or keep elsewhere)

The most common handbook mistake isn't omission — it's overstuffing:

• Operational procedures that change constantly. Software logins, the expense-reimbursement portal, the parking arrangement — these belong in an onboarding wiki, not a policy document you have to formally reissue every time the vendor changes.
• Individualized compensation details. Specific salary bands or bonus formulas don't belong in a document every employee reads; keep compensation structure in a separate, managed place.
• Anything that reads as a guarantee. Re-read every "always," "guarantee," "permanent," and "career path" — each is a place a promise can leak in.
• Overly specific progressive discipline. Keep discipline language flexible ("discipline may include, up to and including termination") rather than a fixed staircase you'll regret in an egregious case.

Keeping it from going stale

A handbook nobody updates is a liability with a date stamp. The discipline that keeps it alive:

• Review annually, and immediately when a law changes (a new state sick-leave mandate, a minimum-wage change, a leave-law expansion).
• Re-acknowledge on material change. When you revise a substantive policy, redistribute and collect fresh signed acknowledgments — the old signature doesn't cover the new rule.
• Make acknowledgment part of onboarding. The cleanest way to guarantee every new hire receives and signs the current version is to make it a dated step in the same onboarding workflow as the day-one paperwork — so the acknowledgment is tracked, not hoped for.

The bottom line

A small-business handbook earns its keep by doing three unglamorous things well: setting expectations in writing, delivering required notices, and giving you a documented, consistently applied policy to point to when something goes wrong. Keep it lean, protect the at-will language, build in a real complaint procedure, leave the fast-changing operational stuff out, and re-acknowledge it whenever it changes. The companies that get burned aren't the ones with imperfect handbooks — they're the ones whose handbook promised something they didn't deliver, or who couldn't prove the employee ever received it.