A handbook nobody follows is worse than no handbook
Most of the handbooks I am handed have the same three problems. They were bought as a template. They describe a company that doesn’t exist. And nobody’s read past page four, including the person who gave them to me.
That’s not a neutral situation. A handbook that says one thing while your managers do another isn’t an empty gesture — it’s a written record of the policy you failed to follow. You’d be better off with nothing.
What a handbook is actually for
Three things, in this order.
It tells employees how this place works, so they’re not guessing. It gives managers a consistent answer, so the same question doesn’t get three different responses at three different locations. And it establishes that you communicated a rule before you enforced it, which is the entire ballgame when somebody challenges a termination.
Notice that all three depend on people reading it. Everything else in this post follows from that.
The template problem
I’ve opened handbooks at Georgia restaurants that contained California meal-break rules, references to a corporate ethics hotline that doesn’t exist, and a remote work policy at a business where every single job requires you to be standing in the building.
Each of those is a promise. If your handbook describes a hotline, an employee who complains and gets nowhere has a document saying you told them there was a hotline. If it describes a progressive discipline sequence you skipped, you’ve handed somebody the argument that you didn’t follow your own process.
The test for every paragraph is the same: do we actually do this? If the answer is no, either start doing it or take it out. There’s no third option.
What has to be in it
For a small operator in Georgia, the load-bearing sections are:
- At-will employment, stated clearly and not contradicted anywhere else in the document. This is the clause most often undermined by a friendly sentence somewhere on page thirty.
- Equal employment opportunity, harassment, and how to complain — with more than one person to complain to, because the default reporting path always runs through somebody’s direct supervisor and that’s frequently the problem.
- Timekeeping and pay. Pay periods, overtime, how to record hours, and an explicit instruction that off-the-clock work is prohibited and that pay errors will be corrected. In an hourly business this section does more wage-and-hour protective work than anything else in the book.
- Attendance, scheduling, and time off, written to match how your schedule is actually built.
- Safety and injury reporting. Report every injury immediately, to whom, and what happens next.
- Conduct and discipline, including the specific things that will get somebody terminated on the spot in your business.
- Technology, social media, and customer privacy, written for people carrying phones on the floor.
- Acknowledgement page, signed and filed.
Federal obligations layer on by headcount, and the thresholds matter — FMLA at fifty employees, and various others at fifteen and twenty. If you’re near a threshold, or you’ve got multiple entities that might be counted together, get that checked. Employers cross those lines without noticing all the time.
What should come out
Anything that reads as a contract. Language promising job security, guaranteed steps before termination, or annual raises turns a policy statement into something an employee can hold you to.
Anything that discourages employees from discussing pay or working conditions with each other. Those clauses are still floating around in old templates and they shouldn’t be in yours.
And detailed benefit plan terms. Summarize, then point to the actual plan documents. Plans change every year and your handbook won’t keep up, and a handbook that misstates a benefit is a problem you didn’t need to have.
Write it for ten o’clock on a Saturday night
This is the part people skip, and it’s the part that decides whether any of the above works.
Your reader isn’t a compliance officer. It’s a twenty-two-year-old shift lead in the middle of a rush who needs to know whether he can send somebody home. If your policy requires him to parse a sentence with three subordinate clauses in it, he’s going to guess, and his guess is now your practice.
So: short sentences. Real words. “Tell your manager the same day” instead of “employees shall provide notification to their immediate supervisor within the operative reporting period.” Second person. Headings someone can scan. And where a rule has a bright line, say the number.
If more than half your workforce speaks Spanish, the handbook exists in Spanish. Not a summary. Not a translated acknowledgement page stapled to an English book. The whole thing, professionally translated, and both versions distributed. An employee who can’t read the policy hasn’t been given notice of it, and everybody in the room knows that.
Distribution isn’t an afterthought
A signed acknowledgement in every personnel file, for every employee, current ones included. If you can’t produce it two years later, functionally it doesn’t exist.
Walk the high-consequence sections in orientation rather than handing over a book and a pen. Ten minutes on injury reporting and timekeeping pays for itself many times over.
And when you change a policy, redistribute and re-acknowledge. A revision nobody was told about isn’t a policy.
How often
A light legal review every year. A real rewrite every two to three years, or immediately when you cross a headcount threshold, open in a new state, acquire another entity, or change how you schedule or pay people.
If yours is more than three years old, don’t read it looking for typos. Read it asking the only question that matters: is this what we actually do? Mark every place the answer is no. That list is your rewrite, and it’s usually longer than anybody expects.
Employment law changes and headcount thresholds have real consequences. This is how I approach the work, not legal advice — on anything close to a line, involve counsel.