A handbook is the answer key to the questions every employee asks in the first month: when do I get paid, how do I ask for time off, what happens when something goes wrong. Below is the full 12-section outline with what each section covers and how to fill it, plus the ten mistakes that get small-business handbooks in trouble. Fill it in, have a lawyer look at it, then hand it out with a signed acknowledgment. The full HR Ops Kit turns this outline into a fill-in document with 93 placeholder fields, linked at the bottom. For a hire who starts before the handbook is finished, the onboarding checklist template covers their first 90 days.
How to use this page: read the 12 sections, note which ones your business already answers somewhere (or nowhere), then draft yours in a text file with [BRACKETS] around every blank. The bracket habit matters more than the wording: search for "[" before you publish, and no placeholder survives to the signed copy.
This is not legal advice. A handbook is a policy document, and employment law sets the floor under it: some policies are legally required to be written a specific way where you operate, and state rules differ on everything from final-pay timing to required notices. Have a qualified employment lawyer review your finished handbook before you give it to employees. Nothing in a handbook (or this page) should create a contract of employment; say plainly that employment stays at will where your law allows it.
One page. Why the company exists, who to ask when the handbook does not answer something, and the two sentences that matter most: the handbook is not an employment contract, and employment is at will (where applicable law permits). Keep it short enough that people read it.
Who the handbook covers and how people are classified:
How people treat each other, customers, and company property. Write the short version first ("treat people well, be honest, do the work, protect the company's stuff") and then the specifics: attendance honesty, dress and behavior for the role, what counts as a conflict of interest, and your rules on outside work or moonlighting. If a rule would embarrass you to enforce, cut it now.
The section that gets looked up most, so make it boring and exact:
Paydays (weekly, biweekly, monthly), the deductions that appear on a paycheck, and timekeeping: who records hours, on what system, and what to do about a missed punch. Add the expense rules: what is reimbursable, receipts above what amount, and how fast. Wage notice requirements vary by state, so this is a section your lawyer should read line by line.
How reviews work (how often, by whom, on what form), what good performance looks like in your business, and what happens when performance slips: the conversation, the written warning, the improvement window. Say how raises and promotions are decided, even if the answer is "annually, at review, based on the written rubric." Vagueness here turns every raise into a negotiation.
Where problems go. Name at least two people an employee can report to (their manager plus one more, in case the manager is the problem), promise a real response timeline, and state that retaliation against a good-faith report is itself a violation. Small teams skip this section most often and need it most: without it, the loudest voice in the room becomes the policy.
How resignations work (notice expected, final pay timing per your state's law), what company termination involves, and the exit process: equipment return, account access, final paycheck, and what you will say in a reference check. Writing this down before you need it is what keeps a bad week from becoming a worse month.
The basics: report injuries same-day and to whom, where first-aid supplies are, and emergency exits for the actual workplace. Then the specific hazards your business has (ladders, kitchen equipment, driving, machinery), your drug and alcohol rules, and what happens if a prescription affects someone's ability to work safely. Keep an incident log, not a memory.
If anyone works from anywhere: who is eligible, agreed hours and core availability, the security minimums (company accounts stay in company systems, lost devices reported same day), and who pays for what equipment. Remote or hybrid policies fail when "agreed with your manager in writing" is left out, so put the writing requirement in the section itself.
What the company does not publish (customer lists, pricing, processes, financials) and the rule against sharing or taking it, which continues after employment ends. Cover customer data handling, the company's right to access its own systems and equipment, and any photo or publicity consent. Anyone with broader agreements (NDA, invention assignment) still follows those too.
The last page, signed and returned, kept in the personnel file. What it covers is below.
The acknowledgment is one signed page, detached from the handbook and filed. It records four things: the employee received the handbook, read it, understands the policies are not an employment contract and can change with notice, and knows to ask a named contact when something is unclear. Signed, dated, with the handbook version and effective date written on it.
What it does not do: sign away anyone's legal rights, convert at-will employment into a contract, or settle a dispute by itself. What it does do: moves "I never saw that policy" from your-word-against-theirs to a filed page with a date on it. Collect it in the first week, chase every missing one monthly, and store it in the personnel file, not a drawer.
A 3-person business needs the conversations the handbook forces: paydays, time off, phone use, what happens when someone quits. Whether that lives in a signed 12-section document or a 2-page memo is a judgment call, and the lawyer-review bar is the same either way. The moment you hire person 4 or 5, write it down; that is when "we never talked about it" stops being a valid excuse and consistent treatment starts mattering legally.
You can draft one, and a generic template gives you the skeleton. What you cannot safely do alone is the state-specific layer: required wage notices, leave laws, final-pay rules, and the exact at-will language for your state. The working pattern: draft from a template, then pay a lawyer for one review pass, then re-use that approved skeleton for years with annual updates. One review costs less than one unemployment claim fought on bad paperwork.
Long enough to answer the real questions, short enough to be read. For most small businesses that is 10 to 20 pages. If a section does not change a decision someone will make, cut it. You can always add sections when a situation repeats.
Send the new version with the changes summarized at the front, collect fresh acknowledgments, and keep the signed old versions on file. The acknowledgment's "policies can change with notice" line is what makes this work, which is why it belongs in every version.
Print the PDFs or edit the text file; everything is plain and fill-in by design. Templates only, not legal advice: have counsel review before you hand policies to employees.
Full HR Ops Kit - handbook + 4 more templates, 93 fill-in fields →one-time · PDF + editable text file · instant download · templates only, not legal advice