The Employee Handbook That Helps You in a Dispute

Why this matters

Two cards in this library already cover what goes in a handbook and how to write it in plain language. This one covers the only thing that matters once there is a dispute: the handbook is a document that will be read back to you, sentence by sentence, by somebody looking for the gap between what you wrote and what you did. A shop that has a handbook and did not follow it is in a materially worse position than a shop with no handbook at all, because it has handed over the standard and the departure from it in one exhibit.

Orientation, not legal advice about your situation. Two genuine forks are marked below.

The document cuts both ways, and that is the whole idea

A handbook does one useful evidentiary job: it proves you communicated a standard. When a tech is fired for something, the first question is whether he knew it was a rule, and a signed acknowledgment of a handbook that states the rule answers it cleanly. That is worth real money in a dispute, and it is why shops write them.

The same document proves the second thing at exactly the same moment: that you had a procedure. If the procedure says four steps and the file shows one, the handbook has just supplied the plaintiff with both the standard you claim to run on and the evidence you did not run on it. Without the handbook, he would have had to prove the standard existed some other way. With it, he proves the standard and the breach from the same page.

Everything below follows from that. The clauses worth getting right are the ones that do evidentiary work in both directions, and the maintenance problem matters because an out-of-date handbook is a set of promises about a shop that no longer exists.

The at-will statement and the section that contradicts it

The at-will doctrine and its exceptions belong to the at-will card, so take this as given: a written or implied promise of continued employment can convert an at-will job into something else, and a handbook is one of the commonest places that promise gets made by accident.

The accident is always the same. Near the front sits a clean at-will disclaimer. In the middle sits a progressive discipline section reading: employees will receive a verbal warning, followed by a written warning, followed by a final written warning, before termination. Both cannot be true. Which governs is a question your state's courts answer, and several answer it against the employer where the discipline language is specific and mandatory.

The drafting fix is one sentence. Write the section in discretionary terms - the shop may use any, all or none of these steps, in any order, and may end employment at any time with or without prior warning - and mean it, because reserved discretion sitting on top of an invariable four-step practice is a weaker position than it looks.

Two traps in the same family, both promises nobody meant to make:

• A probationary period phrased so it implies security afterwards. "After ninety days you become a permanent employee" is a sentence with a meaning, and it is not the one intended.
• A deadline you will not meet. "All complaints will be investigated within 48 hours" is a standard you set for yourself and will be measured against. Write what you will actually do: promptly, and then do it promptly.

The complaint procedure that has to name more than one person

This is the single clause in the book that can win a case, and it works only if it is drafted for the small-shop reality.

Under Faragher v. City of Boca Raton and Burlington Industries v. Ellerth, both decided in 1998, an employer facing a supervisor-harassment claim where no tangible employment action was taken (no firing, demotion or undesirable reassignment) may raise an affirmative defense with two elements: that it exercised reasonable care to prevent and promptly correct harassing behaviour, and that the employee unreasonably failed to take advantage of the preventive or corrective opportunities the employer provided.

Your handbook is the evidence for the first element and the precondition for the second. Note the gate: where the harassment culminated in a tangible employment action, the defense is not available at all, so this clause protects you in one category of case, not every case.

Now look at how a nine-person shop usually writes it: report any concern to your supervisor. Where one of three supervisors is the person being complained about, an employee who says nothing has not acted unreasonably - he had nowhere to go. The second element collapses, and with it the defense the first element was paying for.

So the procedure names at least two channels, and at least one must bypass the ordinary chain of command: a named owner, a specific email address, a phone number. It allows reports verbally or in writing, states that retaliation for making one is prohibited, and does not make a written complaint a condition of being acted on. Whether the clause performs in a real dispute turns on facts and on your state, which is a question for your own attorney; what you can bank operationally is that a single-channel procedure running through the chain of command reliably does nothing.

The acknowledgment page, and what makes one worth anything

A signed acknowledgment is how the handbook gets into evidence as something the employee actually received. A weak one is a loose undated sheet saying "I have received the handbook."

A useful one carries four things: the date, the specific version or revision date received, a statement that the employee had the opportunity to read it and ask questions, and a restatement of the at-will language so the acknowledgment itself carries it. An electronic acknowledgment with a server timestamp is usually better evidence than paper, because it dates itself and cannot be produced later. It files in the personnel file (the personnel-file card covers the structure and why the separation matters).

What an acknowledgment does not do is worth stating, because shops over-read it. It is not a contract and it does not waive statutory rights. And an arbitration agreement, a jury waiver or a class-action waiver tucked into a handbook is a different legal instrument from the handbook it sits in, with its own formation and enforceability questions that vary sharply by state. That is the first fork: if you want one, it is a standalone document drafted by an employment lawyer, not a page 34 anybody can point at.

The change mechanism

The handbook has to change without becoming a contract you cannot amend, which means reserving the right to modify it and then documenting that you did.

Practically: a version number and revision date in the footer of every page, so an exhibit dates itself. A change log at the back. And for any material change, a one-page memo describing what changed, distributed and acknowledged separately rather than buried in a reissue nobody read. A shop that reissues the whole book annually and collects one signature has proved receipt of a document; a change memo proves the employee was told about the specific rule in dispute.

One area to date deliberately. The National Labor Relations Board's test for when a facially neutral work rule unlawfully chills protected activity has changed at least twice since 2017 (Boeing in 2017, Stericycle in 2023), and Section 7 of the National Labor Relations Act reaches shops with no union near them. Confidentiality, civility, social media and recording rules are the clauses affected, so know which year yours was written in.

Worked: four prescribed steps, one document in the file

An eleven-employee residential service shop. The handbook prescribes four disciplinary steps: a documented verbal warning, a written warning, a final written warning with a performance plan, then termination. A tech is fired for repeat callbacks.

The facts are good. Across six techs over twelve months the callback counts were 9, 8, 4, 3, 2 and 1, totalling 27, so the shop average is 4.5 per tech. The fired tech's 9 is exactly twice that average. Nobody would call the decision unreasonable.

Now the file. It contains one written warning, dated fourteen months before the termination, about a missed appointment. Nothing about callbacks at all. Against a handbook prescribing four steps, the file shows one, on a different subject, outside the period in question.

And the comparison. The tech at 8 callbacks - one fewer than the man who was fired - was never written up and still works there. The honest reason is probably not the callback count: the second man is the shop's best installer, or the first argued with a customer, or the owner had simply had enough. Any of those may be a lawful reason to fire somebody. None is written down anywhere.

So at a hearing the shop's stated reason is the callback count, because that is the only reason with a record behind it, and the callback count does not separate 9 from 8. The plaintiff's exhibit list is short and it is all the shop's own paper: the handbook that promised four steps, the file that holds one, and the service records showing a comparable employee who kept his job. The shop was right and cannot show it, which is the position the record-standard card exists to prevent.

What would have changed it. Not a better outcome - the same termination, with three documents in the file naming the callbacks, the dates, the standard and what was said, and one document explaining why the tech at 8 was handled differently. Two hours of writing spread over four months.

What you must not do once you are here. Do not add to the file now and do not amend the handbook now. A document created after a termination and filed as though it were contemporaneous is the worst exhibit available, and it converts a defensible case into an indefensible one. That is the second fork: take the handbook, the file and the service records to an employment lawyer exactly as they are.

The handbook describing a shop you stopped being

The commonest failure is not a bad clause, it is an accurate description of four years ago. A policy referencing the paper timesheet you stopped using. A PTO accrual that does not match what payroll actually does. A complaint procedure naming a manager who left. A safety section for equipment you sold.

Each is a small discrepancy between what you wrote and what you do, and in a case that turns on whether your stated reason is your real reason, each costs a little credibility. Collectively they invite the argument that the handbook is decoration, which is fatal when your whole defense depends on it being the opposite.

The other drift is jurisdictional. A shop that opened across a state line and never revisited the book is operating under a document that omits whatever that state requires, and state-specific policies are the ones an agency looks for first.

The review that keeps it true

Once a year, on a fixed date, and then off-cycle within about thirty days of any of these:

• Crossing a headcount threshold. Fifteen employees brings Title VII and the ADA; twenty brings the ADEA and federal COBRA; fifty brings the FMLA. Each carries policies that were optional the week before.
• Opening in a new state or city.
• Changing your own practice - a new timekeeping system, a new pay basis, a new on-call rotation.
• Any incident that revealed a gap, including one that resolved fine.

And the audit worth running once, because it takes an afternoon and finds the problem before anyone else does: take your last three terminations, read the handbook beside each personnel file, and mark every place the handbook describes something the file does not show. That list is the exhibit list. You now get to decide whether to fix the practice or fix the document, which is a choice you only have while nobody is asking.

References

• Faragher v. City of Boca Raton, 524 U.S. 775 (1998); Burlington Industries, Inc. v. Ellerth, 524 U.S. 742 (1998)
• National Labor Relations Act Section 7; NLRB work-rule standards in Boeing (2017) and Stericycle (2023)
• Coverage thresholds: Title VII and the ADA at 15 employees; ADEA and federal COBRA at 20; FMLA at 50
• See related: Employee Handbook Essentials; Writing an Employee Handbook in Plain English; At-Will Employment and the Exceptions That Actually Bite; Documenting Performance Before You Ever Need To; The Personnel File: What Goes In and Who Can See It