How to create a company handbook: steps, template and tools

This page may contain affiliate links from which Blur Studio earns commissions.

What to include, and what to leave to a lawyer

A handbook generally has three kinds of content, and they need different levels of care. Culture and expectations: what your company actually values, how decisions get made, communication norms, this is yours to write and should sound like your business, not a generic template. Practical, day-to-day information: how to request time off, who to contact for IT or payroll questions, how the office or shift schedule works, also yours to write, and the section new hires will reference most often. Legally sensitive policy: at-will employment language, anti-discrimination and harassment policy wording, leave entitlements, termination procedures, and anything touching your specific jurisdiction's labor law. This section should be reviewed, if not drafted outright, by an employment lawyer familiar with where your business operates, since the wording here carries real legal weight and a mistake can be costly in a dispute. Don't let a free template or AI-generated draft substitute for that review on this specific section, even though it's fine for the rest of the handbook.

A template outline

Welcome and culture: a short welcome message, company mission or purpose in plain language, how the company is organized. Employment basics: employment classification, work hours and schedule norms, pay schedule, the legally reviewed at-will and related language. Time off and leave: vacation, sick leave, holidays, any leave required by your location's law, written clearly with real numbers, not vague "as needed" language that creates ambiguity later. Conduct and expectations: dress code if relevant, communication norms, the legally reviewed anti-discrimination and harassment policy. Day-to-day practical info: who to contact for what, how to report an issue, how performance reviews work. Acknowledgment: a signed confirmation that the employee received and read the handbook (how to get staff to sign that they read it), with a date, which matters for both compliance and simply knowing who's actually seen the current version.

Tools

For a very small team, Notion or Google Docs, both free, work fine: a single document or page, organized with the headings above, shared with new hires and updated as policies change. Trainual, a platform for writing up your company's processes, policies and training material in one place and assigning it to staff with completion tracking, is a step up once you want to confirm staff actually read specific sections, not just received the document, with e-signature support for the acknowledgment step on its higher tiers. It doesn't publish fixed pricing, quoting after a demo based on team size. Check current pricing for your team here. Dedicated handbook builders exist too, purpose-built around digital handbooks with signature tracking and automated update notifications, worth considering if the handbook itself, rather than broader process documentation, is your main need. Whichever tool you pick, keep the legally sensitive sections in a format your lawyer can review directly, a plain document or exported PDF, rather than locked inside a tool's proprietary editor where getting a redline back and forth becomes awkward.

A worked example: the time-off section

Take one section, time off, through the full process. A manager drafts the practical details in plain language: how many vacation days per year, how far in advance to request time off, who approves it, and what happens if two people on the same team request overlapping dates. That draft goes to an employment lawyer specifically to check it against the business's location's legally required sick leave, which in many places sets a statutory minimum separate from whatever vacation policy the company chooses, and the lawyer flags that the draft's "unlimited unpaid time off at manager discretion" language could create inconsistent treatment across employees if not applied carefully, a liability risk the manager drafting it wouldn't necessarily have known to watch for. The final section keeps the manager's plain-language practical instructions almost unchanged, with the lawyer's specific correction folded into the legally sensitive clause about discretion and consistency. This is the right division of labor: the manager wrote what employees actually need to know day to day, the lawyer caught the one clause that carried real legal exposure.

A worked table of contents for a 25-person company

To make the template outline above concrete, here's what an actual table of contents looks like for a 25-person retail and warehouse business. Section one, welcome, covers a short note from the owner, what the company sells and to whom, and a simple org chart showing who reports to whom. Section two, employment basics, covers full-time versus part-time classification, standard shift patterns for each role, pay schedule and method, and the lawyer-reviewed at-will language specific to the state the business operates in. Section three, time off, lists exact vacation accrual rates by tenure, the state's required sick leave minimum alongside the company's own more generous policy, and the specific process for requesting time off during the business's two annual peak periods. Section four, conduct, covers the dress code for warehouse versus customer-facing staff separately, since the two roles have genuinely different practical needs, communication norms for the team messaging app, and the lawyer-reviewed anti-harassment policy. Section five, day to day, lists who to contact for payroll questions, IT issues and facilities problems by name and role, plus how performance reviews are scheduled and structured. Section six, acknowledgment, is the signature page. Listing it out like this makes an otherwise abstract structure concrete enough to copy directly, the section headings barely change between businesses, only the specific content inside each one does. A business with a single location and one shift pattern can collapse sections three and four into shorter versions of the same headings, while a business spanning multiple states needs to split the lawyer-reviewed sections by jurisdiction rather than writing one version and assuming it covers every location equally, since leave entitlements and at-will language genuinely differ state to state even within the same country.

Keeping it current

A handbook with outdated policy information is worse than no handbook, since staff reasonably assume it's accurate and act on it. Assign a specific owner, usually whoever handles HR or office administration, responsible for updating it whenever a policy actually changes, not on a fixed schedule alone. Review the legally sensitive sections specifically whenever your location's employment law changes or your business crosses a headcount threshold that triggers new requirements, both are easy to miss if nobody's explicitly watching for them. Re-collect signed acknowledgments whenever a material change is made, not just at hiring, so you have a current record of who's actually seen the latest version. A simple practice that catches most staleness before it causes a real problem: whenever any policy outside the handbook changes, like a new benefits provider or a revised dress code, add "update the handbook" as an explicit step in that change's own process, rather than relying on someone remembering to circle back to a separate document later.

How does Blur Studio approach company handbooks?

Most small businesses can build and maintain a solid handbook with a free document tool and a lawyer's review of the legally sensitive sections, no special software required. Where this becomes a custom conversation is when handbook acknowledgment needs to connect to something else automatically, like new policy versions triggering a re-signature requirement across your whole team the moment they're published, rather than someone manually tracking who's seen what. If that's genuinely your situation, happy to talk it through, and if a document tool plus legal review is enough, I'll say so. The time-off example above is a useful pattern to repeat for every section of your own handbook, draft the practical content yourself, then send only the genuinely legally sensitive clauses for review rather than the whole document every time.