Checklist · Labor and Employment

Drafting an Employee Handbook That Holds Up: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2026-04-25
Topic
Labor and Employment

An employee handbook is the most widely read legal document in most workplaces, and a careless one quietly surrenders the at-will defense, breaks federal labor law, or becomes the plaintiff's best exhibit. This checklist walks a drafter through the whole job in sequence: scoping and architecture; the at-will disclaimer and the implied-contract traps from Toussaint and Woolley; the load-bearing policies built around the Faragher/Ellerth and Kolstad defenses, the ADA interactive process, FMLA and the stacked leave landscape, and an FLSA safe harbor; drafting facially neutral work rules narrowly enough to survive the NLRB's Stericycle standard; the acknowledgment form; why arbitration belongs in its own document; the multistate maze; and a governance cadence. Each phase pairs checkboxes with the reasoning and the traps, then closes with common mistakes, primary authority, and cross-references to deeper UpLaw resources. Treat it as a drafting companion, not a substitute for counsel licensed where you actually employ people.

Drafting an Employee Handbook That Holds Up: A Practical Checklist

Labor and Employment > HR Policies | Published 25 April 2026 - Updated 12 May 2026 | UpLaw - uplaw.us

A handbook is read by two audiences who want opposite things: new hires looking for a welcome, and lawyers looking for a binding promise or an unlawful rule. This checklist drafts for both — sequenced so the decisions that are hardest to unwind (entity, architecture, the at-will disclaimer) come first, and the policies that carry legal weight are built to do their job under Faragher/Ellerth, Kolstad, the ADA, the FLSA, and the NLRB's Stericycle standard.

Keywords: employee handbook, at-will disclaimer, implied contract, Toussaint, Woolley, Faragher/Ellerth defense, Kolstad good-faith defense, ADA interactive process, FMLA, FLSA safe harbor, PTO as wages, NLRA Section 7, Stericycle work rules, handbook acknowledgment, arbitration, multistate employer

The Document That Is Both a Shield and a Loaded Gun

Ask a founder what an employee handbook is for and you will hear something about culture, onboarding, and answering the same questions so a manager does not have to. All true. But the handbook has a second life that founders rarely picture at the drafting stage: it is a piece of evidence, manufactured by the employer, held in the employer's own files, and produced under subpoena the day a fired worker sues. Every sentence you write to reassure an employee is a sentence a plaintiff's lawyer can quote back to you. Draft the document as pure warmth and you may convert your at-will workforce into one you can fire only for "good cause." Draft it as pure liability shield and employees ignore it — which defeats the point, because a policy nobody reads is a policy you cannot enforce and cannot use to defend yourself.

The way through is to understand that a good handbook is doing four distinct jobs at once, and they pull in different directions. It communicates expectations, benefits, and culture in language a human will actually read. It standardizes policy so rules get applied the same way to everyone, which matters enormously in litigation because the single most reliable way to lose a discrimination case is to enforce a neutral rule unevenly. It delivers legally required notices — FMLA rights, harassment reporting procedures, wage-deduction complaint channels, trade-secret whistleblower immunity. And it generates evidence: a signed acknowledgment, a documented complaint procedure, a paper trail showing the company had reasonable rules and followed them. The friction between "readable" and "defensible" is not a flaw in the assignment. It is the assignment.

This checklist works that friction in order. The sequencing is deliberate. Foundational choices — which legal entity is on the hook, which states you actually operate in, and how the at-will disclaimer is worded — are the ones that are expensive or impossible to fix after the fact, so they come first. The load-bearing policies come next, then the facially neutral work rules that trip up even sophisticated employers, then the acknowledgment, arbitration, multistate wiring, and the governance discipline that keeps the whole thing from going stale. Everything below is general information; the law here is overwhelmingly state-specific and it changes every legislative session, so have counsel licensed in each state where you employ people review the result before it ships. For the narrative treatment that sits behind this checklist, see UpLaw's companion guide, Building a Legally Sound Employee Handbook.

Phase 1 — Scope, Entities, and Architecture (Decide Before You Draft)

  • [ ] Confirm which legal entity employs the covered workers, and name that entity consistently throughout the document
  • [ ] Inventory every state — and country — where you have employees, including remote hires the company never planned to "operate" in
  • [ ] Choose an architecture: one national handbook, a core handbook plus state-specific addenda, or fully separate state handbooks
  • [ ] Decide what lives in the handbook (readable summaries and required notices) versus a separate intranet or HRIS (granular benefits mechanics, IT configurations, expense minutiae that change often)
  • [ ] Map which coverage thresholds you cross today: Title VII and the ADA at 15 employees, the ADEA at 20, the FMLA at 50 within a 75-mile radius
  • [ ] Assign a named owner — a specific person or outside counsel — not "HR generally"
  • [ ] Choose a distribution method (paper or electronic) and a mechanism to capture verifiable, timestamped acknowledgment

The architecture decision is the one most drafters underrate, and it is the one that punishes multistate employers hardest. American employment law is federalized at the level of headline principles — Title VII, the ADA, the FMLA, the FLSA — but it is intensely local at the level of operational detail: overtime thresholds, meal and rest breaks, paid sick leave accrual, final-paycheck timing, whether accrued vacation is a vested wage, which categories are protected, and whether harassment training is mandatory. A single clause that is perfectly lawful in Texas can be flatly illegal in California. That is why the core-plus-addenda structure is usually the right answer above a handful of states: a clean, readable national core carries the culture and the federal baseline, and thin state addenda carry the divergences. It keeps the core from bloating into an unreadable fifty-state hedge, and it makes updates surgical — when Colorado changes its sick-leave accrual formula, you edit one addendum instead of re-proofreading the whole book.

The threshold map matters because coverage is a moving target that tracks headcount. An employer with twelve people is not yet subject to Title VII or the ADA; hire the sixteenth and both attach. Cross fifty employees within seventy-five miles and the FMLA's notice, eligibility, and job-restoration machinery switches on and must be reflected in the handbook. Growing companies routinely trip these wires without noticing, because nobody owns the calendar.

Worked example. Northwind Coffee Roasters starts as an eleven-person shop in Portland with a friendly two-page handbook. Over eighteen months it opens a warehouse in Nevada, hires a remote bookkeeper in New York, and lets a senior roaster relocate to Illinois. Nobody updates the handbook. The company now employs people in four states with wildly different sick-leave, final-pay, and pay-transparency rules; it has crossed fifteen employees (Title VII and ADA now apply) and is closing in on the ADEA's twenty; and its "friendly two-pager" contains none of the required notices for any of those states. Northwind has not done anything malicious. It has simply grown faster than its paperwork, which is exactly how most handbook liability is born. The fix is not a bigger single document — it is a governed core with a Nevada, New York, and Illinois addendum, and a named owner watching the headcount thresholds.

Remote hires deserve a special flag. The company that lets one engineer work from a state where it has no office often assumes it has not "entered" that state for employment-law purposes. Wrong. That employee generally sits inside the wage, leave, notice, and protected-category regime of the state where the work is physically performed, not the state of incorporation. Track where employees actually are, not where the org chart says the company is.

Phase 2 — The At-Will Disclaimer and the Implied-Contract Traps

  • [ ] Write a prominent, unambiguous at-will disclaimer stating that (1) employment is at-will, terminable by either party at any time, with or without cause or notice; (2) nothing in the handbook is a contract or a guarantee of continued employment; (3) the handbook is not exhaustive and may be changed or withdrawn at the company's sole discretion; and (4) only a designated officer can alter at-will status, and only in a signed writing
  • [ ] Make the disclaimer visually unmissable — bold, boxed, the operative sentence in capitals, or set apart on its own page near the front
  • [ ] Repeat the disclaimer in the acknowledgment form, and consider a separate initial line next to it
  • [ ] Scrub "we're a family," "long and rewarding career," "permanent employee," and "job security" language from the welcome letter and everywhere else
  • [ ] Convert any mandatory progressive-discipline sequence to discretionary language ("the company may, in its sole discretion, use any of these measures, in any order, or move straight to termination")
  • [ ] Avoid "for cause" or "for good reason" termination promises unless you genuinely intend to be legally bound by them
  • [ ] Reconsider the phrase "probationary period"; if you keep it for benefits eligibility, state expressly that completing it does not change at-will status
  • [ ] Confirm the disclaimer is analyzed against the law of every state where you employ workers

Here is the counterintuitive part that catches sophisticated employers: a handbook can become an enforceable contract even when the employer never intended to make one. The doctrine is unilateral contract — the idea that a promise of job security, broadcast to the workforce and reasonably relied upon, can bind the employer regardless of the "we didn't mean it that way" defense.

The two landmark cases are worth knowing by name because opposing counsel will cite them. In Toussaint v. Blue Cross & Blue Shield of Michigan, 408 Mich. 579 (1980), the Michigan Supreme Court held that an employer's personnel manual, which stated employees would be dismissed only "for just cause," created legitimate expectations the employer was contractually bound to honor — even without individualized bargaining. Five years later, in Woolley v. Hoffmann-La Roche, Inc., 99 N.J. 284 (1985), the New Jersey Supreme Court held that a handbook's job-security and progressive-discipline provisions could be enforced as a unilateral contract absent a clear and prominent disclaimer. Read those two holdings together and the drafting lesson writes itself: the disclaimer is not boilerplate you paste at the back. It is the load-bearing wall. Woolley practically tells you what it must look like — clear and prominent — which is why "bury it in nine-point type on page 47" is malpractice-adjacent.

The single most common trap is progressive discipline. A handbook proudly lays out a humane sequence — verbal warning, written warning, suspension, then termination — because it reads as fair. A terminated employee then argues the company promised that sequence, skipped the first three steps, and therefore breached. Sometimes that argument wins. The defense is not to abandon progressive discipline (it is good management and good optics with a jury) but to frame every step as discretionary and to reserve the right to terminate immediately for any reason or no reason. UpLaw's practice materials on structured discipline walk through how to keep a fair-looking process from hardening into a contractual entitlement.

Two limits keep the disclaimer honest, and you should understand both so you neither over- nor under-rely on it. First, at-will is the default in every state except one: Montana, whose Wrongful Discharge from Employment Act, Mont. Code Ann. § 39-2-901 et seq., requires good cause to discharge non-probationary employees. Everywhere else you start from at-will and merely have to avoid contracting it away. Second — and this is the limit employers forget — a disclaimer defeats contract claims and nothing else. It does absolutely no work against a statutory claim (discrimination, retaliation, FMLA interference, an FLSA violation) or against the public-policy wrongful-discharge tort that most states recognize (you cannot fire someone for refusing to break the law, for filing a workers' comp claim, or for whistleblowing, disclaimer or no disclaimer). A perfect at-will disclaimer stops a contract theory dead; it is invisible to a discrimination theory.

Worked example. Pinnacle Logistics fires Delia, a dispatcher, for chronic lateness. Its handbook promises that discipline "will proceed" through four escalating steps; Pinnacle skipped straight to termination. Delia sues for breach of an implied contract, pointing to the mandatory-sounding "will proceed" language and the absence of any prominent disclaimer. Under the logic of Toussaint and Woolley, she has a live claim — not because Pinnacle intended a contract, but because it wrote one by accident and never disclaimed it. Had the handbook said the company "may, in its sole discretion, use any of the following measures, in any order, or terminate immediately," and carried a boxed, capitalized at-will disclaimer up front and again in Delia's signed acknowledgment, the contract theory would collapse at summary judgment. Note what the disclaimer would not have done: if Delia's real claim were that younger dispatchers were kept on for identical tardiness, that is age discrimination under the ADEA, and no disclaimer touches it. See Age Discrimination Law: A Worker's and Employer's Overview.

Phase 3 — The Load-Bearing Policies

This is the substantive heart of the handbook, and each policy below is doing specific legal work — often defensive work you will not appreciate until a claim lands. Treat these as structural members, not decoration.

  • [ ] EEO statement naming every federal protected category — race, color, religion, sex (including pregnancy, sexual orientation, and gender identity after Bostock), national origin, age (40+), disability, genetic information, and military/veteran status — plus every category the states you operate in add
  • [ ] Anti-harassment policy with plain-language definitions and concrete examples, multiple reporting channels (never a single "tell your supervisor" route), a promise of prompt and impartial investigation, an explicit anti-retaliation guarantee, and confidentiality worded as "to the extent practicable," not absolute
  • [ ] ADA reasonable-accommodation policy that explains how to request an accommodation, commits to the interactive process, keeps medical information confidential and separately filed, and avoids rigid maximum-leave or automatic-termination rules that foreclose that process
  • [ ] FMLA policy (required in the handbook for covered employers) covering eligibility, how to request leave, certification, concurrent use of paid leave, and the job-restoration right
  • [ ] The wider leave landscape: state paid sick leave, state paid family and medical leave, bereavement, jury duty, voting leave, USERRA military leave, and PWFA and PUMP Act accommodations
  • [ ] Wage-and-hour policy with exemption classifications and, critically, an FLSA safe-harbor and complaint provision for improper deductions; a prohibition on off-the-clock work; and an instruction to report unpaid time
  • [ ] PTO / vacation drafted for the governing state, because accrued vacation is vested, non-forfeitable wages in California and several other states
  • [ ] Code of conduct: attendance, use of company property, conflicts of interest, gifts, drugs and alcohol (with attention to state marijuana and off-duty-conduct laws), safety and OSHA, and dress and grooming (with CROWN Act and religious-accommodation carve-outs)
  • [ ] Confidentiality and trade secrets, including the DTSA whistleblower-immunity notice under 18 U.S.C. § 1833(b), plus a BYOD / acceptable-use policy
  • [ ] Discretionary discipline paired with an open-door / complaint procedure offering more than one route and an anti-retaliation promise

The Anti-Harassment Policy Is a Litigation Instrument

Of all the policies, the anti-harassment policy is the one whose legal function is most misunderstood. It is not primarily a statement of values. It is the operative half of an affirmative defense.

Under the companion Supreme Court cases Faragher v. City of Boca Raton, 524 U.S. 775 (1998), and Burlington Industries, Inc. v. Ellerth, 524 U.S. 742 (1998), an employer facing a hostile-work-environment claim based on a supervisor's harassment — where the harassment did not culminate in a tangible employment action like firing or demotion — may raise an affirmative defense with two elements: (a) that the employer exercised reasonable care to prevent and promptly correct harassing behavior, and (b) that the employee unreasonably failed to take advantage of the preventive or corrective opportunities the employer provided. A real, publicized, multi-channel complaint procedure is the centerpiece of element (a); a signed acknowledgment that the employee received and understood it is the centerpiece of element (b). This is why the reporting mechanism must offer more than one route. If the only channel is "report to your supervisor," and the supervisor is the harasser, the procedure is worthless — and a court will say so. Give employees at least two independent paths (a designated HR contact plus a senior officer or hotline), so no single bad actor can bottleneck a complaint.

Two drafting details make or break the defense. First, do not promise absolute confidentiality; you cannot deliver it, because a genuine investigation requires talking to witnesses. Promise discretion "to the extent practicable" and mean it. Second, and this is the part that turns a shield into a sword: the policy only helps if you actually use it. Promise a "prompt, impartial investigation" and then ignore a complaint, and you have manufactured Exhibit A proving you breached your own written standard. The Faragher/Ellerth defense rewards employers who follow their procedures; it punishes employers who advertise procedures they treat as decorative.

There is a second, less-cited defense that the same policy powers, and it reaches all the way to the damages line. In Kolstad v. American Dental Association, 527 U.S. 526 (1999), the Supreme Court held that an employer can avoid vicarious liability for punitive damages under Title VII by showing it made good-faith efforts to comply with the anti-discrimination laws — and a genuine, enforced EEO and anti-harassment policy is the textbook proof of good-faith effort. In other words, the policy you draft in Phase 3 does not just help you win on liability under Faragher/Ellerth; if you lose on liability, it can still cap your exposure by defeating punitive damages under Kolstad. For how those numbers actually shake out — back pay, the Title VII statutory caps, and the Kolstad punitive standard — see Damages in Employment Litigation: Back Pay, Statutory Caps, and Punitive Awards.

State law can raise the floor. California's Fair Employment and Housing Act imposes an affirmative duty to take reasonable steps to prevent harassment, Cal. Gov't Code § 12940(k), and mandates supervisor and employee harassment-prevention training on a fixed schedule — obligations a national handbook must accommodate through a California addendum rather than a one-size national paragraph.

EEO and the Post-Bostock Category List

The EEO statement looks simple and is easy to get wrong by omission. It must name the full federal protected-category set, and after Bostock v. Clayton County, 590 U.S. 644 (2020), "sex" under Title VII unambiguously includes sexual orientation and gender identity — so a policy that lists "sex" but is silent on those two is both under-inclusive and a tell that the drafter has not updated the document since 2020. Then layer the state-added categories: marital status, political affiliation, arrest or conviction history, reproductive health decisions, hairstyle and texture (the CROWN Act), and more, all of which vary by state. The EEO statement and the anti-harassment policy should name the same categories, because a mismatch reads to a jury as carelessness about the very thing the policy is supposed to protect.

The ADA, the Interactive Process, and the Rigid-Rule Trap

The reasonable-accommodation policy has one job above all others: to commit the company to the interactive process and then get out of the way of it. The governing regulation, 29 C.F.R. § 1630.2(o)(3), frames accommodation as an interactive, individualized dialogue in which the employer and the employee together (1) pin down the precise limitations the disability creates and (2) explore accommodations that would let the employee perform the essential functions of the job, short of undue hardship. The policy should tell an employee exactly how to start that conversation, promise that the company will engage in it, and commit to keeping medical information confidential and filed separately from the personnel file.

The trap is the rigid rule that quietly forecloses the process. A "no-fault" attendance policy that fires anyone at a fixed number of absences, or a maximum-leave rule that automatically terminates after a set number of weeks, can violate the ADA precisely because it substitutes a bright line for the individualized analysis the statute requires — additional leave is itself a possible accommodation. The safest posture is a policy that expressly subjects any such attendance or leave ceiling to the accommodation process. And because pregnancy accommodation now has its own dedicated statute, coordinate the ADA policy with the Pregnant Workers Fairness Act; UpLaw's Pregnancy Discrimination and Accommodation After the PWFA maps how the PWFA, the PDA, the ADA floor, and the PUMP Act interlock.

FMLA and the Stacked Leave Landscape

For employers who cross the FMLA's coverage threshold, an FMLA policy in the handbook is not optional — it is part of how the statute expects covered employers to give notice. Cover eligibility (twelve months and 1,250 hours), the qualifying reasons, how to request leave, the certification process, whether paid leave runs concurrently, and the right to be restored to the same or an equivalent position.

Then confront the reality that FMLA is only one layer. A single leave event can implicate the FMLA, a state paid-family-and-medical-leave program, state paid sick leave, the ADA (leave as accommodation), the PWFA, and USERRA, all at once, and they stack and interact in state-specific ways. Bereavement, jury duty, voting, and organ-donation leaves each have their own statutory homes in many states. Trying to compress all of this into one national paragraph is how employers end up out of compliance in half their states simultaneously. Parental and maternity leave in particular reward careful, gender-neutral drafting; see Maternity and Parental Leave Policies: Five Things Employers Should Know Before Drafting.

Wage-and-Hour and the FLSA Safe Harbor

The wage-and-hour policy carries a piece of drafting that pays for the entire handbook the day an exempt employee's classification is challenged. Under the Fair Labor Standards Act, 29 U.S.C. § 201 et seq., an employee is exempt from overtime only if she satisfies both a duties test and the salary-basis test — and the salary-basis test can be destroyed by improper deductions from an exempt employee's salary. Deduct for a partial-day absence, or dock pay in a way inconsistent with salaried status, and you risk blowing the exemption not just for that person but for everyone in the same job classification, converting a whole class to overtime-eligible retroactively.

The regulatory rescue is the safe harbor at 29 C.F.R. § 541.603. An employer that (1) maintains a clearly communicated policy prohibiting improper deductions, (2) includes a complaint mechanism, (3) reimburses employees for any improper deductions, and (4) makes a good-faith commitment to comply in the future generally preserves the exemption even after an isolated improper deduction — unless it willfully keeps deducting after complaints. That policy language belongs in the handbook, verbatim in substance. It is cheap insurance against an expensive, class-wide misclassification finding. Pair it with an affirmative instruction that non-exempt employees must record and report all time worked and must never work off the clock, which cuts off the most common unpaid-overtime theory before it starts.

PTO and the Vacation-as-Wages Divergence

Paid time off looks like a benefits detail and is actually a state-law minefield. In several states, most prominently California, accrued vacation is treated as earned wages that vest as they accrue and cannot be forfeited — no "use it or lose it," and any unused balance must be paid out at termination. The California rule traces to Suastez v. Plastic Dress-Up Co., 31 Cal. 3d 774 (1982), and Cal. Lab. Code § 227.3. Other states permit "use it or lose it" and do not require payout. A single national PTO clause is therefore lawful in one state and illegal in another by definition. This is the cleanest possible illustration of why the core-plus-addenda architecture from Phase 1 is not bureaucratic overhead but structural necessity.

Code of Conduct: Where Federal Neutrality Meets State Idiosyncrasy

The code of conduct gathers attendance, company property, conflicts, gifts, safety, and the two provisions that most often collide with state law: drugs/alcohol and dress/grooming. A zero-tolerance drug policy that treats a positive marijuana test as automatic grounds for discharge runs headlong into a growing set of state statutes protecting off-duty lawful use and, in some states, barring adverse action based on a marijuana metabolite test alone. Dress and grooming standards must yield to religious accommodation and, under the CROWN Act, must not penalize natural hairstyles and textures associated with race. Draft these as national principles with state addenda carrying the carve-outs, not as a single rigid national rule.

Confidentiality, Trade Secrets, and the Whistleblower Notice You Must Include

A confidentiality policy protects the company's crown jewels, but it also carries a mandatory federal notice that employers routinely omit. The Defend Trade Secrets Act, 18 U.S.C. § 1836 et seq., grants whistleblower immunity for confidential disclosures made to the government or in a sealed court filing, and § 1833(b) requires employers to give notice of that immunity in any agreement governing trade secrets or confidential information. Skip the notice and you forfeit the ability to recover exemplary (double) damages and attorney's fees against an employee in a later DTSA suit. The handbook's confidentiality policy (and every NDA and invention-assignment agreement) should carry the § 1833(b) notice for that reason alone.

Confidentiality drafting also has to survive the NLRA, which is the subject of Phase 4 — a rule that broadly forbids discussing "company information" can be read to forbid discussing wages, and that reading is unlawful. And a modern confidentiality regime is only as strong as its device and access controls, which is where the BYOD and acceptable-use policy earns its keep. For the surrounding program, UpLaw's Trade Secret Law: How Secrecy Becomes Protectable Intellectual Property, the clause-level Building an Enforceable NDA Clause by Clause: A Practical Checklist, and Guarding Trade Secrets Without a Perimeter: Remote Work and the Cloud go far deeper than a handbook can. Clean IP title, meanwhile, comes from a properly drafted assignment agreement, not the handbook — see Employee Invention Assignment Agreements: Securing Clean Title Across Jurisdictions. If your BYOD policy touches biometric timeclocks or facial-recognition access, add the privacy overlay from Biometric Privacy Law and the AI Systems That Read Faces and Voices, and route device-data handling through the framework in Building a Privacy Compliance Program: Governance, Data Mapping, and the Legal Patchwork.

A note on non-competes, which drafters instinctively want to drop into the handbook: keep them out. Non-competes are separately negotiated, consideration-dependent, and governed by a volatile state-by-state patchwork that increasingly bans or narrows them. A non-compete stuffed into a non-contractual handbook is both unenforceable-looking and a magnet for challenge. Handle restrictive covenants in standalone agreements, informed by The Future of Non-Competes: FTC Rulemaking and the State-Law Patchwork.

Phase 4 — Facially Neutral Work Rules and the NLRA (Drafting to Survive Stericycle)

  • [ ] Inventory every facially neutral work rule: confidentiality, civility and conduct, social media, media/press contact, non-disparagement, and no-recording rules
  • [ ] Rewrite confidentiality rules to name the categories you actually mean (trade secrets, customer lists, financials, proprietary technical data) and add a carve-out preserving the right to discuss wages, hours, benefits, and terms of employment
  • [ ] Rewrite civility and conduct rules so they attach to legitimate interests (harassment, threats, operational disruption) rather than to "negative" or "disparaging" speech as such
  • [ ] Rewrite social media rules to prohibit specific harms — disclosing trade secrets, harassing coworkers, speaking for the company without authority, posting unlawful content — instead of vague "criticism of the company"
  • [ ] Limit media/press rules to speaking on behalf of the company, never employees speaking about their own working conditions
  • [ ] Include an NLRA savings clause, but do not treat it as a cure for an otherwise unlawful rule
  • [ ] State the legitimate business reason behind each rule — a rule tied to an articulated interest is far easier to defend

Here is the single most expensive misconception in handbook drafting: "The National Labor Relations Act is about unions, and we are not a union shop, so it does not apply to us." It applies to you. Section 7 of the NLRA, 29 U.S.C. § 157, protects employees across nearly all private-sector workplaces — union and non-union alike — when they act together to improve wages, hours, and working conditions ("protected concerted activity"). Section 8(a)(1), 29 U.S.C. § 158(a)(1), makes it an unfair labor practice to maintain a rule that would tend to chill that activity. The trap has a vicious feature: a rule can violate the Act by its mere maintenance, even if the employer never once enforced it against protected activity. The unlawful act is having the rule on the books, because employees reading it might reasonably decide to stay quiet.

The governing standard is Stericycle, Inc., 372 NLRB No. 113 (2023). It evaluates a challenged rule from the perspective of an economically dependent employee — someone inclined to read a rule cautiously and avoid risking their job — and it deems the rule presumptively unlawful if that employee could reasonably interpret it to restrict Section 7 activity, even if other, lawful readings also exist. The burden then shifts to the employer to prove the rule advances a legitimate and substantial business interest that cannot be achieved with a more narrowly tailored rule. This is a demanding, pro-employee test, and it is the one to draft against.

It is also politically volatile, which is the practical reason to draft conservatively. The Board's work-rule standard has swung three times in eight years: Lutheran Heritage Village-Livonia, 343 NLRB 646 (2004), asked whether employees would "reasonably construe" a rule to prohibit protected activity; The Boeing Co., 365 NLRB No. 154 (2017), replaced it with an employer-friendly balancing of business justifications against the rule's impact; and Stericycle swung back to a stringent, employee-protective posture. A rule drafted to satisfy Stericycle — the strictest of the three — will satisfy the others, so you insulate yourself from the next swing by drafting to the toughest standard now. The reverse is not true: a rule that passed muster under Boeing may be unlawful under Stericycle.

The translation from doctrine to drafting is concrete, and it comes down to specificity plus stated purpose:

  • Confidentiality. "Do not disclose company information" is fatal, because an employee could reasonably read it to forbid telling a coworker what she earns — squarely protected activity. Name the categories (trade secrets, customer data, financial and technical proprietary information) and add an express carve-out preserving discussion of wages, hours, and terms of employment.
  • Civility and non-disparagement. A rule against "negative," "disparaging," or "disloyal" statements about the company is presumptively unlawful, because complaining publicly about working conditions is exactly what Section 7 protects. Tie the rule instead to genuine harms — harassment, threats, defamation, disclosure of confidential data, disruption of operations.
  • Social media. Do not prohibit "criticizing the company." Prohibit the specific misconduct: leaking trade secrets, harassing coworkers, impersonating the company, posting unlawful content. The interaction between these labor-law limits, Section 230, and the FTC's endorsement rules is mapped in Social Media Law: A Field Guide to the Legal Stack.
  • Media contact. Limit the rule to who may speak for the company to the press. You may not stop an employee from telling a reporter about her own pay or working conditions.
  • No-recording rules. A blanket ban on recording in the workplace can chill protected activity (employees sometimes record to document unsafe or unlawful conditions), so tie any recording restriction to specific, legitimate interests and be aware of the separate state wiretap and consent regime, which the handbook should not contradict; see Cameras, Consent, and the Law of Recording People.

The savings clause — a paragraph stating that "nothing in these policies is intended to restrict rights under the National Labor Relations Act" — is worth including but must not be leaned on. The Board has repeatedly refused to let a generic disclaimer rehabilitate a rule that an employee could not reasonably reconcile with the disclaimer. The clause is a backstop, not a cure. Fix the rule; then add the clause.

Worked example. Harborline Freight, a non-union trucking company, publishes a handbook forbidding employees from "posting negative comments about the company or its management on social media" and from "discussing confidential company matters, including compensation." A dispatcher posts on Facebook that Harborline underpays its night shift and organizes coworkers to raise it with management. Harborline never disciplines her — but a coworker files an unfair labor practice charge over the rules themselves. Under Stericycle, both rules are presumptively unlawful on their face: an economically dependent employee could plainly read "negative comments" and "discussing compensation" to bar protected concerted activity, and Harborline cannot show a legitimate interest that a narrower rule could not serve. The company loses on maintenance alone, having never enforced either rule. The lesson is that the drafting error, not the enforcement, was the violation.

Phase 5 — The Acknowledgment Form

  • [ ] Draft an acknowledgment that confirms receipt, states the employee's duty to read the handbook, restates the at-will disclaimer, reserves the company's right to amend unilaterally, and reinforces the policy-knowledge element of the Faragher/Ellerth defense
  • [ ] Capture a verifiable signed — or timestamped, authenticated electronic — acknowledgment at onboarding
  • [ ] Re-collect the acknowledgment whenever you issue a material update
  • [ ] Confirm the acknowledgment does not contradict the body (no mandatory-discipline language sitting next to "this is not a contract")

The acknowledgment is a small form doing outsized evidentiary work. It is where the at-will disclaimer gets a second, individually signed appearance; it is the document that proves an employee received the anti-harassment procedure (element two of Faragher/Ellerth); and it is the vehicle for the company's reserved right to change policies unilaterally. Collect it at onboarding, store it, and — this is the step everyone skips — collect it again every time you make a material change. An employer that revised its arbitration or leave language two years ago but can only produce the original 2019 acknowledgment has no proof the employee ever saw the update. Electronic acknowledgment is fine and often better, provided the system authenticates the signer and timestamps the event so the record is admissible.

Watch for internal contradiction, which is a surprisingly common self-inflicted wound. If the body still contains mandatory "the company will" discipline steps while the acknowledgment says "this handbook is not a contract," a plaintiff will argue the contradiction creates ambiguity to be resolved against the drafter. The acknowledgment and the body must tell the same story.

Phase 6 — Arbitration Belongs in Its Own Document, Not the Handbook

  • [ ] Keep any arbitration agreement in a standalone, separately signed document with its own recited consideration — never embedded in a handbook that elsewhere disclaims all contractual effect
  • [ ] Account for the Ending Forced Arbitration of Sexual Assault and Sexual Harassment Act, 9 U.S.C. §§ 401-402, and for state limits on mandatory employment arbitration
  • [ ] Confirm the arbitration document does not depend on the handbook for its terms or its enforceability

There is a structural irony at the center of handbook arbitration clauses. A well-drafted handbook says, loudly and repeatedly, "this is not a contract, and we can change any of it at any time in our sole discretion." An arbitration clause, by contrast, is a contract — one of the most consequential the employee will ever sign. Bury the arbitration clause inside a document that disclaims contractual effect and reserves the right to rewrite everything, and you hand the employee two potent arguments: that the clause is illusory (the employer promised nothing it could not unilaterally revoke) and that it was never a real, mutually assented-to agreement. Courts have refused to enforce handbook-embedded arbitration clauses for exactly these reasons.

The Federal Arbitration Act, 9 U.S.C. § 1 et seq., strongly favors arbitration, and Epic Systems Corp. v. Lewis, 584 U.S. 497 (2018), confirms that class- and collective-action waivers in employment arbitration agreements are enforceable and do not violate the NLRA. But Epic Systems protects a real contract — a separately presented, separately signed agreement supported by consideration — not a paragraph smuggled into a non-contractual handbook. Two further limits shape the drafting. The EFAA, 9 U.S.C. §§ 401-402, lets a person asserting a sexual-assault or sexual-harassment claim void a pre-dispute arbitration agreement as to that claim, so a blanket "all disputes" clause cannot capture those cases. And a number of states restrict or condition mandatory employment arbitration. Treat arbitration as its own project — the right way to structure it, and whether to use it at all, is covered in Choosing a Dispute-Resolution Forum: Litigation, Arbitration, and Mediation Compared, the practical Arbitration and ADR: A Toolkit for Choosing a Forum, Drafting Clauses, and Running a Case, and the deeper Arbitration in Practice: A Comprehensive Guide to Alternative Dispute Resolution.

Phase 7 — The Multistate Maze: State-Specific Addenda

  • [ ] Build a state addendum wherever local law diverges from the national core, covering at minimum: vacation-as-wages and payout rules, daily overtime, meal and rest breaks, final-paycheck timing, paid sick and family leave, pay-transparency and salary-range disclosure, harassment-training mandates, marijuana and off-duty-conduct protections, and state-added protected categories
  • [ ] Confirm each addendum names the employees it covers and states that it controls over the national core where the two conflict
  • [ ] Re-run the addendum inventory every time you hire in a new state

The addendum system is the operational payoff of the architecture decision made in Phase 1. It lets the core handbook stay readable and national while the state-specific rules — which are where most day-to-day compliance actually lives — travel in modular attachments. Final-paycheck timing alone illustrates the stakes: some states require the final check on the day of termination, with penalty wages accruing for each day of delay, while others allow payment on the next regular payday. A national "we pay final wages promptly" clause is not compliance; it is a placeholder that happens to be wrong in several states. Pay-transparency laws, harassment-training mandates, and daily-overtime rules follow the same pattern. Each addendum should state plainly that it governs over the national core for the employees it covers, so there is never a question about which rule applies.

Phase 8 — Keep It Alive: Governance and Review Cadence

  • [ ] Schedule a full review at least annually, plus interim reviews triggered by expansion into a new state, crossing a coverage threshold, or a significant appellate or Board decision
  • [ ] Re-collect acknowledgments after every material change
  • [ ] Train managers on the handbook, because the company is bound by what supervisors say and do
  • [ ] Keep documentation discipline: personnel files should show policies communicated, complaints investigated, discipline applied consistently, and accommodations and leave handled through the interactive process

A handbook is perishable in a way most legal documents are not. Federal standards shift under your feet — the Board rewrote its work-rule test three times in eight years — states add leave entitlements and protected categories nearly every session, and the company itself keeps crossing coverage thresholds as it grows. A handbook that nobody owns goes stale, and a stale handbook is worse than none: it makes affirmative but outdated representations, which is how a compliance document becomes a plaintiff's exhibit. The named owner from Phase 1 exists precisely to prevent that drift.

Manager training deserves emphasis because it is the leak most companies never plug. The finest anti-harassment policy in the world is undone by a supervisor who, told of harassment, says "just try to get along with him" and does nothing — because the company is charged with what its supervisors know and do. The handbook creates the standard; training is what makes the standard real on the floor. And the documentation discipline in the last checkbox is what converts good practices into admissible proof: a clean file showing the policy was communicated, the complaint was investigated, the discipline was even-handed, and the accommodation was worked through the interactive process is, in the end, the evidence that wins the case the handbook was drafted to help you win.

Common Mistakes That Turn a Shield Into a Sword

  • Promising job security by accident. "We're a family," "a long and rewarding career," mandatory "the company will" discipline steps, and stray "for cause" language each hand a terminated employee an implied-contract theory under Toussaint and Woolley.
  • Assuming the NLRA does not reach a non-union workplace. It reaches nearly every private employer. Broad confidentiality, civility, and social-media rules fail the Stericycle standard by their mere maintenance, enforcement or not.
  • Burying arbitration in the handbook. A clause inside a document that disclaims all contractual effect risks being held illusory and unenforceable.
  • Advertising procedures you then ignore. Promise a prompt, impartial investigation and then sit on a complaint, and you have created proof you breached your own written standard — the opposite of the Faragher/Ellerth shield.
  • Running one national clause where the states diverge. A single PTO, final-pay, or drug-testing clause is lawful in one state and illegal in another; only the addendum architecture fixes it.
  • Collecting the acknowledgment once and never again. Issue material updates without a fresh signed acknowledgment and you have no admissible proof the employee ever saw them.
  • Omitting the DTSA § 1833(b) whistleblower notice. Leaving it out forfeits exemplary damages and fees in a later trade-secret suit against a departing employee.
  • Forgetting that the disclaimer only stops contract claims. It does nothing against discrimination, retaliation, FMLA, or public-policy tort theories.

Primary Authority at a Glance

Related UpLaw Resources

Related Guides

Related Articles

Related Checklists

Related Toolkits

This checklist is general information, not legal advice. Employment law varies significantly by state and changes frequently; consult qualified counsel licensed in each jurisdiction where you employ workers before drafting, distributing, or relying on an employee handbook.