What to Include in a Restaurant Employee Handbook (Free Cheat Sheet)

Most restaurant employee handbooks fail in the same way. Either they are a 60-page legal document copied from a template, signed once, and never opened again — or they are a flimsy 4-page Google Doc that misses every policy that would actually protect the operator in a dispute. There is a middle path, and it starts with knowing exactly what belongs inside.

This post walks through what to include in a restaurant employee handbook — grouped into the four sections every handbook needs, with notes on what belongs in each, what is operationally smart, and what to skip. At the bottom is a free printable cheat sheet you can use as a structural checklist before you write a word. It is one to two pages, prints on any browser, no email required.

The handbook sits inside a larger system. It only works if it lines up with the rest of how the operation runs — see the broader six pillars of tight restaurant operations for the full picture. The handbook is the policy layer; the execution layer (recipes, vendor lists, opening routines) is what protects you when a key employee leaves and takes all the knowledge with them. This post is about getting the policy layer right. On the execution side, the opening, closing, and prep routines are where restaurant checklist software earns its keep, turning those routines into a record instead of a binder no one opens.

Why Most Restaurant Handbooks Fail

A restaurant employee handbook is the document that sets out the rules, expectations, and policies every team member is expected to know — covering the legal basics, day-one essentials, operational standards, and the discipline and accommodation process. Walk into a hundred restaurants and ask to see the handbook. You will get one of three responses: a battered binder pulled from a back-office shelf, a PDF the GM has to email later, or a long pause followed by "I think we have one somewhere." None of those operations are protected, and none of those teams know the actual rules.

The two failure modes are predictable. The first is the legal-template handbook — bought from an HR vendor, full of language nobody reads, signed by every new hire and immediately forgotten. It checks a compliance box but does nothing operationally. The second is the homemade four-page version, which covers the obvious stuff (uniform, schedule) but leaves out the policies that matter when something goes wrong (anti-harassment, wage rules, discipline process, accommodation requests).

The handbook that works does both jobs at once: it satisfies the legal requirements, and it answers the questions a real team member has on a real shift. That requires structure — a clear set of sections, written in language people understand, kept short enough that the team will actually open it.

The 4 Sections Every Handbook Needs

Every section in your handbook should map cleanly into one of four buckets. If something does not fit any of these four, it probably belongs in a separate operational document — a training manual, a daily checklist, a recipe binder — not in the handbook.

• The Legal Basics — The policies your employment attorney will want documented, and the ones that protect the operation if something goes wrong.
• Day-One Essentials — What the new hire needs to understand before their first shift ends.
• Operations & Standards — The rules of the floor, the kitchen, the bar. The "how we do it here" policies.
• Culture & Conduct — The standards that shape how the team treats each other, the guests, and the work.

The next four sections walk through each bucket. The cheat sheet at the bottom of this post lists every individual item with a checkbox so you can audit your existing handbook against it.

Section 1 — The Legal Basics

This is the part of the handbook to build with an employment attorney, not from a blog post. What applies to you depends on your state, your county, and how many people you employ, and it changes. What follows is the list of topics to bring to that conversation so you walk in prepared instead of paying someone to tell you what a handbook is.

At-will employment statement. A clear paragraph on how employment can be ended, by either side. The wording matters and it varies by state, so have this one drafted for you.

Equal employment opportunity and non-discrimination. Your non-discrimination commitment and the protected classes it covers. Your attorney will tell you which ones apply where you operate; some states add to the federal list.

Anti-harassment and reporting procedure. Defines harassment, names the reporting chain, and states a no-retaliation rule. Of everything in this section, this is the one operators most often leave thin, and it's the one that hurts most when it's missing.

Wage, hour, and tip policies. Pay periods, how overtime is handled, and how tips are treated in your house. Tip rules in particular are a minefield and they differ sharply by state, so get yours confirmed rather than copied from another restaurant.

Meal and rest breaks. Whatever your state requires, plus whatever you offer beyond it. Write down what your team actually gets so nobody is guessing mid-shift.

Workplace safety and injury reporting. How to report an injury, where the first-aid kit lives, and the response protocol for slips, burns, and cuts. Practical regardless of what's required of you.

Accommodation requests. The process for requesting an accommodation and a no-retaliation commitment.

Sick leave and extended leave. Your sick-leave terms and how longer leaves are handled. Requirements here vary a lot by state and headcount, so confirm what applies to you.

Workers' compensation notice. State-specific. Usually required as both a posted notice and a handbook entry.

Employee acknowledgment and signature page. The last page of the handbook. Confirms the employee received and read it. Signed copies go in the personnel file. This is what protects you when a former employee disputes a policy in court.

Section 2 — Day-One Essentials

Section 1 is for the lawyer. Section 2 is for the new hire. The goal here is that by the end of the first shift, the new team member can answer five questions: where do I work, who do I report to, when do I get paid, when do I work, and what happens if I cannot make a shift.

Welcome and the restaurant's story. One page. Who founded it, why it exists, what it stands for. This sets the tone before the policies start. A handbook that opens with "the company reserves the right to..." reads like a warning. One that opens with the story reads like an invitation.

Org chart and chain of command. Who reports to whom. Who approves comps, time-off requests, schedule swaps, and uniform replacements. New hires waste their first two weeks asking "who do I ask about..." — a clear org chart removes that friction.

Schedule policy. When schedules drop (e.g. Thursday for the following Monday), how far out, how to request time off, swap rules, and any blackout dates around major holidays.

Attendance and punctuality. Expected arrival window before each shift, the call-out procedure (who to call, how, how far in advance), and the consequence of a no-call no-show. Be specific. Vague attendance policies create disputes.

Pay info. Pay period, payday, direct deposit setup, where to access paystubs, tip distribution timing, and the payroll contact.

Day-One Essentials is the section a new hire will reference 10 times in their first month. Make it the easiest part of the handbook to find. This is also where a strong 5-day onboarding framework matters — the handbook is the document, but onboarding is how the new hire actually internalizes it. The companion document at this stage is the new hire welcome packet — the shorter, warmer Day 1 read that pairs with the handbook and includes a free hybrid template.

Section 3 — Operations & Standards

Section 3 is where the handbook earns its keep on the floor. These are the rules that govern how service runs, how the kitchen runs, and how the team handles money, allergens, and the public. Enforcing this layer consistently is a core part of restaurant manager responsibilities — the pillar guide breaks down how the handbook fits with the other six duties every manager owns.

Dress code and grooming. Uniform pieces, who supplies them, hair, jewelry, slip-resistant shoe policy, visible tattoos, nail length and polish (kitchen-side), perfume and cologne. Specific beats vague.

Side work and opening / closing. Reference your daily checklists rather than duplicating them. The handbook is policy; the checklist is operational. Keep them separate so the checklist can be updated without re-issuing the handbook.

Allergen and food safety protocol. The allergens your kitchen tracks, your handwashing rule, glove policy, temperature checks, FIFO rotation, and expired-product disposal. Confirm the allergen list and the standards with your local health department, and reference your full food safety SOP here.

Tip handling and pooling formula. The exact pool, percentages, tip-out rules to bar, BOH, and runners, and when tips are paid. Spell it out — tip disputes destroy team morale faster than almost any other issue.

POS and cash handling. Voids, comps, who can ring discounts, the manager-approval threshold, and the cash drop procedure. Theft prevention starts with making the rules explicit.

Phones and personal devices. Where phones live during service, when they can be checked, exceptions for parents and emergencies. The cleaner the rule, the less it gets argued.

Social media policy. What can and cannot be posted from the restaurant. Off-limits items typically include guest photos without consent, internal financials, recipes, and behind-the-scenes content that violates a guest's expectation of privacy.

Comps, voids, and discounts. Manager-approval threshold, family and friends discount rules, and the owner-only override situations. Same logic as POS handling — clarity prevents disputes.

Section 4 — Culture & Conduct

The last section is where most handbooks get either too soft or too strict. Too soft and the rules are unenforceable. Too strict and the team feels surveilled. The right tone is direct: here is how we treat each other, here is what is not negotiable, here is how we handle it when something goes wrong.

Code of conduct. Plain-language rules for how the team treats guests, vendors, and each other. This is the readable version of the EEO and anti-harassment policies — the version someone actually reads on a break.

Conflict resolution. Where to take disagreements, who handles guest complaints, the escalation path. Most disputes are small until they are not — a clear path keeps them small.

Substance use policy. Drugs and alcohol on premises, shift-drink rules (if any exist), end-of-shift staff drinks, DUI prevention. Restaurants live close to alcohol; the policy should be explicit.

Theft and integrity. Family meal rules, taking food home, voids and comps, freebies for friends. The line between hospitality and theft. Most theft is unintentional drift — explicit rules prevent the drift.

Confidentiality. Recipes, vendor pricing, internal financials, guest information. What stays in the building.

Discipline and progressive correction. The process: verbal warning, written warning, final written, suspension, termination. Stating the steps makes the process feel fair and gives managers a framework to follow consistently — and each step should be documented on a consistent employee write up form so the record holds up if it ever escalates.

Termination and exit. Final paycheck timing (state-specific), property to return (uniform, keys, tablets, login credentials), reference policy.

How to suggest improvements. The legitimate channel for ideas, complaints, and feedback. Closes the loop on culture and signals that the team's input is wanted, not just tolerated.

How to Format It So People Actually Read It

Content alone is not enough. The format determines whether the handbook gets read or not. The pattern that works:

• Plain language, short paragraphs. Write the way a manager would explain it to a new hire on the floor — not the way a lawyer would write it for court. The legal version belongs in the legal review, not the handbook itself.
• 20 to 40 pages total. Under 20 and you are missing required policies. Over 40 and the team will not finish it. Cut anything that belongs in a separate operational doc.
• Mobile-first formatting. Most of your team will read it on a phone. Use short sections, generous spacing, and numbered headings so they can find a policy mid-shift in 10 seconds.
• Searchable. A printed binder cannot be searched. A PDF in Dropbox can. A handbook inside an operations app can be searched, bookmarked, and surfaced in context.
• Linked, not duplicated. Reference your daily checklists, recipes, and training materials — do not paste them inside the handbook. Operational docs change; the handbook should not.

This is also where consistent staff training connects. The handbook is policy; training is craft. Both should live in the same place if you want the team to actually use them.

How to Distribute It (And Keep It Current)

The best handbook in the world is worthless if it lives in a binder on a shelf. Three rules for distribution and maintenance.

Sign it once, store it forever. Every employee — full-time, part-time, seasonal — signs an acknowledgment confirming they received and read the handbook. Keep the signed copy in their personnel file. Re-collect signatures after any material revision.

Review annually. Once a year minimum, plus immediately when a relevant law changes. State sick-leave rules, minimum wage updates, and tip-pool law changes happen often enough that an annual review is the floor, not the goal. Date every revision so version disputes never happen.

Move it off paper. A handbook in a binder is updated once and forgotten. A handbook in a phone-accessible app stays current, gets searched mid-shift, and removes the excuse of "I never read that." This is the single biggest format upgrade an operator can make — and it is exactly the gap that a custom operations app closes. The handbook becomes part of the same tool your team already uses for the menu, the prep guides, and the closing checklist.

Free Cheat Sheet

One printable, four sections, 32 items. Use it as a structural audit against your existing handbook, or as a starting point if you are writing from scratch. Click Print to save as PDF or send to a printer — no email required.

If you want a handbook your team actually reads — not a binder that gets signed once and forgotten — Crewli builds custom restaurant operations apps that hold your policies, your training, and your daily standards in one place. Branded to your concept, current, mobile-first. Let's talk.

Frequently Asked Questions