The employee handbook is one of those documents founders treat as a formality until it stops being one. A reasonable-looking template gets downloaded from the internet, lightly edited with the company name, sent to new hires for acknowledgment, and filed away. Two years later, somebody in legal is asking why the handbook still says “8-hour workdays” when the workforce is fully remote across eleven states, or why the at-will provision is missing the phrase that makes it enforceable in California, or why the harassment policy doesn’t include the kind of reporting procedure that several states (New York being one of the earliest) have required for years now.
That’s the bad version. The good version: a handbook that’s been built to actually do its job, which is to protect the company from foreseeable legal exposure, set expectations clearly enough that employees can self-serve, and stay current as the law changes underneath you.
Most templates miss what actually matters. This post is about what to put in the handbook, what to leave out, and the operational sections that the typical “free employee handbook template” gets wrong.
What an employee handbook actually does
Three things, in priority order.
Legal defense. A well-constructed handbook is your evidence that the company communicated its policies clearly, applied them consistently, and gave employees notice of their rights and obligations. In litigation — wrongful termination, discrimination, wage-and-hour — the handbook is one of the first documents subpoenaed. Either it helps you or it doesn’t.
Expectation setting. New hires get hundreds of small questions in their first 60 days. How does PTO work? What’s the expense reimbursement policy? What’s the dress code? Without a handbook, every question becomes a Slack message to a founder or manager. With one, it’s a search-and-answer.
Compliance documentation. Several federal and state laws require specific notices in writing, with employee acknowledgment. The handbook is the natural place for those notices. Missing one creates compliance liability that’s easy to avoid and embarrassing to explain.
What the handbook is not: a values document, a culture deck, or an aspirational manifesto. Those can exist separately if you want them. The handbook should be operational, defensible, and updated frequently.
The sections that actually matter
Below is the structure we use for Series A/B clients. Every section is here because it earns its place — either legally required, operationally necessary, or both.
At-will employment statement
The first substantive section. States that employment is at-will, that nothing in the handbook is a contract, and that the handbook can be modified at the company’s discretion. Specific phrasing matters in some states (California, Montana). Get this wrong and you’ve potentially created an implied employment contract that limits your ability to terminate.
Equal employment opportunity statement
Required by federal law and most state laws. Should list protected classes by state — not just the federal ones. New hires from New York need to see different language than new hires from Texas. A handbook with only the federal EEO statement is technically compliant in some states and meaningfully under-compliant in others.
Anti-harassment and anti-discrimination policy
This is the section that gets read in litigation. Must include: definition of harassment, reporting procedure with named recipients (not just “report to HR”), assurance against retaliation, and the company’s investigation process. Several states (New York, California, Illinois, others) require specific elements that go beyond federal minimums. Static templates almost always miss state-specific requirements.
Wage and hour policies
Exempt vs. non-exempt classification. Overtime eligibility. Timekeeping expectations for non-exempt employees. Meal and rest breaks (state-specific: California is extensive). Pay frequency. Final paycheck timing on termination (also state-specific). Wage statement requirements.
The wage-and-hour section is where most startups have hidden exposure. We’ve seen multiple companies misclassify engineers as exempt, fail to pay the proper overtime to non-exempt operations staff, or miss the California meal-break rules that produce real penalty exposure.
Leave policies
PTO, sick leave, parental leave, jury duty, bereavement, FMLA, state-specific paid family leave, military leave. Each requires its own section. State-specific paid sick leave is the most commonly missed — a growing number of states and cities have mandated paid sick leave that’s separate from PTO.
If the company has unlimited PTO, the policy needs to address how it interacts with state-mandated sick leave (you can’t satisfy California’s sick leave requirement just by saying “we have unlimited PTO” — the structure has to be explicit).
Remote work policy
This section barely existed before 2020 and is now critical. Should address: eligibility, expense reimbursement (some states require this; California most aggressively), home office stipends, equipment, security requirements, and the all-important state-of-residence reporting requirement (employees must notify HR before moving to a new state).
Code of conduct and ethics
Drug and alcohol policy. Workplace violence. Conflicts of interest. Outside employment. Confidentiality and IP. The IP assignment provision should be cross-referenced with the IP assignment language in the offer letter — and they should not conflict.
Acknowledgment of receipt
The signed page at the back. Confirms the employee received the handbook, agrees to abide by it, understands employment is at-will, and acknowledges the company can update the handbook. In some states this acknowledgment is what creates enforceability for specific provisions.
What most templates miss
The free handbook templates floating around the internet do a competent job of the federal-baseline sections. Where they fall short:
Multi-state specificity. A handbook for a single-state company is a different document from a handbook for a company with employees in 12 states. The latter needs state-specific addenda for at least California, New York, Massachusetts, Illinois, Washington, Colorado, and any others where you have significant headcount. Each state has its own paid sick leave rules, its own meal/break rules, its own anti-harassment training requirements, its own final-paycheck timing.
Operational policies. Templates often miss expense reimbursement, equipment, business travel, remote work, social media, and bring-your-own-device. These aren’t legally required but they prevent 80% of the routine policy questions employees ask.
Updating mechanics. Templates are static documents. A real handbook needs a version-control approach: who owns updates, what triggers a review (state law changes, federal regulatory shifts, internal policy changes), how often the full handbook is reviewed (annually at minimum), and how updates are communicated and re-acknowledged.
Employee leave interactions. The interaction between FMLA, state paid family leave, employer-paid parental leave, short-term disability, and PTO is the messiest part of the leave universe. Templates rarely handle it well. The result: employees ask managers, managers guess, the company applies the policy inconsistently, and the inconsistency is what produces legal exposure.
The actual reporting procedure. A harassment policy that says “report to your manager or HR” is weaker than one that names specific recipients (the People Ops Manager, the CEO, and an external hotline) with contact details. The specificity is what makes the policy defensible.
The state-by-state problem
A handbook is not a static document because employment law is not static. Roughly:
- Major federal employment law changes once every 5-10 years. Manageable.
- Major state employment law changes constantly. California passes a significant volume of new employment laws each year — typically more than any other state. New York, Illinois, Washington, Massachusetts, Colorado, Oregon, and others are similarly active.
- City-level employment ordinances exist in NYC, SF, Seattle, Chicago, Philadelphia, and others, and they add another layer.
Once you have employees in 5+ states, the maintenance burden becomes a real workstream. The two practical options:
- Employment counsel reviews the handbook annually, with state-specific addenda updated as needed. Cost: typically $5K-15K per annual review, depending on state count and complexity.
- A handbook subscription service that maintains state-by-state language and pushes updates. Cost: typically $2K-5K per year. Less customized but covers the baseline. Your employment counsel or benefits broker can recommend a specific service.
We don’t have a single platform we endorse — the right answer depends on complexity and counsel relationships. What we do recommend: pick one path and commit. The failure mode is “we’ll update it later” turning into a three-year-old handbook with five states’ worth of stale policies.
When to use a template, when to use counsel
Templates are fine when:
- You’re under 10 employees, all in one state
- The state is not California, New York, Massachusetts, Illinois, or Washington (the high-complexity states)
- You haven’t yet had any real employment issues
Counsel becomes necessary when:
- You have employees in 3+ states, or any one of the high-complexity states
- You’ve crossed 25 employees (when several state laws on harassment training, paid leave, and other items kick in)
- You’re hiring senior leadership and need executive-level offer letters with confidentiality, non-solicit, and IP terms
- You’ve had any employment dispute, complaint, or termination dispute in the last 12 months
- You’re preparing for a fundraise, audit, or M&A event where employment compliance will be diligenced
The handbook is one of the cheapest places to spend a few thousand dollars on legal review. The downside risk of getting it wrong is much larger than the cost of getting it right.
How often to update
Annually at minimum. Plus event-triggered updates:
- New state of employment (whenever you hire the first person in a new state)
- New federal regulation taking effect
- Changes to internal policies (PTO, remote work, parental leave, etc.)
- After any employment dispute that exposed a gap
- After any compliance audit or insurance review that flagged something
Each update requires: revised handbook, change-log communicated to employees, and a fresh acknowledgment signed. The new acknowledgment is what makes the updated provisions enforceable. Skipping the re-acknowledgment is one of the most common process failures we see.
For companies in the 25-50 employee range, this means roughly 2-4 handbook updates per year. Above 50 employees and across more states, expect 4-8 updates per year.
The threshold moments
A few specific points where the handbook needs deliberate attention:
- First hire in California. California requires several specific provisions and addenda. Treat this as a handbook event, not just an onboarding event.
- First hire in New York. New York has its own anti-harassment training and complaint-procedure requirements that the handbook needs to reflect.
- Crossing 15 employees. Federal civil rights statutes (Title VII, ADA) attach. The EEO statement needs full coverage.
- Crossing 20 employees. ADEA (age discrimination) attaches.
- Crossing 50 employees. FMLA, EEO-1, ACA Applicable Large Employer status, and a number of state-specific obligations attach. See the broader compliance picture in multi-state employment compliance and the operational obligations triggered around this size in the planned 25-employee threshold post.
Plan the handbook update around the headcount threshold, not after.
When to bring in operator support
The handbook itself can be handled by employment counsel and a competent HR ops hire. Where founders typically benefit from outside operator input:
- Scoping the policies (PTO structure, parental leave, remote work) to match company culture and stage without over-promising
- Coordinating handbook updates with payroll provider configurations so that policy and execution stay aligned
- Designing the broader HR infrastructure that the handbook sits inside (offer letters, equity grant procedures, onboarding flows, performance management cadence)
- Preparing the handbook for diligence in a fundraise or M&A event
You probably don’t need help if you’re under 10 employees in a single low-complexity state with a clean template and no pending issues. You likely want operator support if you’re scaling into multiple states, integrating with a new payroll stack, or preparing for any kind of due diligence.
Pegacorn Group works with venture-backed Series A and B startups on HR infrastructure that holds up under stress. If your handbook hasn’t been touched in a year, or you’re not sure whether what you have actually protects you, let’s talk.
This post pairs with: How to administer payroll and 401(k) plans at a startup, When to hire your first HR person, Multi-state employment compliance, and the 25-employee threshold.