Yes, AI can draft a restaurant staff handbook covering conduct, shifts, tips, hygiene and leave in an afternoon. An employment adviser must check everything that depends on local law before it is issued: pay and tips, breaks and hours, leave and sick pay, discipline, and whether the handbook becomes part of staff contracts.
Template downloads and AI drafts share a weakness: they read as finished while quietly assuming rules that may not apply where you employ people. A handbook written for one place should not be used in another, and a wrong sentence about breaks or tips does more harm than a missing one. This is a drafting guide, not legal advice.
Sort every section green, amber or red before drafting
Decide who is allowed to write each section before anything is generated. The three colours: green sections have no legal content, so AI drafts them and you check the facts. Amber sections mix your practice with outside rules, so AI drafts from your facts and the adviser skims. Red sections state a legal minimum or a legal consequence, so AI builds a skeleton with markers and the adviser writes or confirms the wording.
Here is the sort for an illustrative restaurant with 14 staff: six in the kitchen, eight front of house, one of them under 18 and working weekends.
| Section | Colour | Why |
|---|---|---|
| Welcome and values | Green | No legal content |
| Opening and closing routines, station duties | Green | Describes your own operation |
| Uniform and appearance | Amber | May need adjustments for religion or health |
| Phones and social media | Amber | Links to discipline and monitoring |
| Shifts, rota notice, swaps, lateness | Amber | Notice and pay rules vary |
| Hygiene, allergens, illness reporting | Amber | Must mirror your food-safety plan and local rules |
| Tips and service charge | Red | Who may share, deductions and records |
| Pay, hours, breaks, overtime, young workers | Red | Legal minimums vary |
| Leave, sick pay, family leave | Red | Entitlements are set by law and contract |
| Conduct, discipline, grievance, harassment | Red | Procedure and fairness rules |
| Contract status and changes to the handbook | Red | Legal effect depends on wording and place |
Five of the eleven sections are red, and those are the ones where the adviser reads every line. The colour code also shapes the brief you send: red first, amber as a skim, green not at all. The general method for an employee handbook is covered in the tutorial on writing an employee handbook with AI; the sort above is what makes it work for a kitchen and a dining room.
A prompt that stops the model stating law as fact
Left alone, an assistant writes "all employees are entitled to..." with great confidence and borrowed numbers. The prompt has to forbid that and give it somewhere to put the questions:
You are drafting sections of a staff handbook for a 14-person restaurant (6 kitchen, 8 front of house, one employee under 18 on weekends). Use plain language, short sentences, second person.
Facts: [paste opening hours, shift lengths, how the rota is published, swap rule, tip pooling points, uniform, hygiene procedure name and version, leave rule]
Rules:
- Describe what we do. Never state what the law requires, allows or forbids.
- For any topic involving pay, breaks, hours, young workers, tips, leave, sick pay, discipline, harassment, monitoring or the handbook's legal status, write [ADVISER TO CONFIRM: topic] and list what you need to know.
- Do not invent numbers, notice periods or disciplinary steps. If I have not given one, write [OWNER TO DECIDE].
- End each section with a checklist of its markers.Compare what an unguarded draft does with a breaks paragraph (illustrative):
All employees are entitled to a 30-minute unpaid break for every shift longer than six hours and a paid 10-minute rest break every four hours.
Every number there is the model's guess. It reads as a legal entitlement, and in some places adults are owed no set break while in others breaks are mandatory, longer or paid. The guarded version says what you do and routes the law to the adviser:
Breaks. On shifts over six hours you take a 20-minute meal break at a time your shift lead agrees. [ADVISER TO CONFIRM: minimum breaks and rest periods, whether breaks are paid, rules for employees under 18.]
Every marker becomes one line in your adviser's brief, which is the efficient way to buy their time.
Conduct and discipline: you set standards, the adviser sets process
The standards are yours: be on time, wash hands, no phones on the line, no drinking on shift, treat colleagues and guests with respect. AI writes these well. What it should not write is the consequence, because process is where handbooks create trouble. A first draft will often say (illustrative): "Any lateness will result in immediate dismissal." It sounds firm, but it promises something you may not want to or be allowed to do, and the next time you give someone a second chance, the handbook says you broke your own rule.
A workable version states the expectation and points to a procedure written by the adviser:
Being on time matters in a kitchen. If you will be late, phone the shift lead before your start time. Repeated lateness is handled under the disciplinary procedure in section 9.
Three things for the adviser here. The disciplinary and grievance procedure itself, including steps, who decides and any right to be accompanied or to appeal. The list of gross misconduct, such as theft, serious safety breaches or working while impaired, and how it differs from ordinary misconduct. And the harassment, discrimination and whistleblowing statements, which must be accurate for where you operate. AI will happily invent a three-warning ladder. Treat any ladder it writes as a question, not a policy.
Shifts and breaks: promises that need a rule behind them
Your rota practice goes in the handbook, so the handbook needs the right rule behind each promise. The pattern is the same each time: you supply the practice, the adviser supplies the rule.
| Your practice | Rule the adviser confirms |
|---|---|
| Rota published seven days ahead | Whether any notice period or pay for late changes applies where you operate |
| Swaps agreed between staff, approved by the shift lead | Whether swaps change pay, hours or overtime |
| Call the shift lead one hour before a missed shift | What counts as reasonable notice and what you can do about no-shows |
| Closing shifts end by 11.30pm | Limits on hours, night work and breaks for employees under 18 |
| Split shifts with a gap of up to three hours | Whether the gap is paid or counts as working time |
The under-18 row is the one a general-purpose model is most likely to miss, because an 11.30pm finish raises no question for the adults on the rota. The tutorial on rota rules that keep the schedule legal shows how to enter the same limits into the rota itself once the handbook has stated them.
One employee under 18: what changes across the handbook
The example restaurant has one 16-year-old on weekends, and that single person touches more sections than any adult on the team. Hours and night work: the closing time the rota assumes may be too late for them. Breaks: young workers often have different minimums. Tasks: in some places there are limits on what under-18s may operate, such as slicers and fryers, or serve, such as alcohol, and on what they may lift. Paperwork: some places expect a permit, a parent's consent or a notification. Pay: minimum rates can differ by age. Supervision: who closes with them, and whether they can be alone with cash or stock.
None of that appears in a general-purpose draft, and it should not be hidden in a footnote either. The clean solution is a short section headed "If you are under 18", written by the adviser from your facts: shift lengths, the tasks and equipment the young person will use, and who supervises. Give the AI the facts and keep the wording of the rules in the adviser's hands.
Tips: write the policy from your real till and card flow
Staff tend to read the tip section closely, so it has to match what actually happens. Take an illustrative week with $2,400 in tips pooled and shared by hours worked multiplied by a role weight that the owner chooses:
| Role | Hours | Weight | Points | Share of $2,400 |
|---|---|---|---|---|
| Servers | 120 | 1.0 | 120.0 | $1,371.43 |
| Bartenders | 60 | 0.8 | 48.0 | $548.57 |
| Runners and bussers | 50 | 0.6 | 30.0 | $342.86 |
| Hosts | 30 | 0.4 | 12.0 | $137.14 |
That is 210 points, so each point is worth $2,400 divided by 210, or about $11.43. The weights are a business decision, not a legal one, and AI can happily draft the maths and the staff-facing explanation. The adviser's questions are different: who is allowed in the pool at all (kitchen staff, managers, owners), whether the business may deduct card-processing costs before sharing, how a compulsory service charge is treated compared with a voluntary tip, when and how the money is paid, and what records you must keep. The tutorial on drafting a fair tip pooling policy goes deeper on those questions.
Hygiene and sick pay must say the same thing
Two sections written separately can undo each other. Suppose the hygiene section says "report any vomiting or diarrhoea and do not work until cleared", while the leave section says "no sick pay for the first three days". A cook reading both concludes that reporting an illness costs three days' pay, and some people will respond by saying nothing and working. AI wrote both sections in isolation and each looks fine on its own.
Fix the clash in the facts you supply, not in the wording. State the exclusion period and who clears someone to return, copying it from your food-safety authority's guidance, not from AI. Then ask the adviser what sick pay applies during that period and write one cross-reference in each section. The hygiene section should also name your food-safety plan and the current version of your allergen procedure, rather than offering generic reminders; a handbook sentence is not training, so keep dates of staff training in a separate record. The kitchen training manual tutorial covers the how-to side that the handbook should point to.
The allergen paragraph is the other place where AI goes vague. Its usual line (illustrative) is "Staff must be knowledgeable about allergens at all times." That is a wish, not an instruction. Replace it with what a server actually does:
If a guest mentions an allergy, stop and note it on the ticket in capitals. Do not guess. Check the allergen matrix at the pass; if the dish is not listed, tell the guest you need to check with the kitchen, then ask the shift lead. Never offer a substitute you have not confirmed. [ADVISER OR FOOD-SAFETY CHECK: training and record-keeping duties.]
Everything before the bracket is your procedure, and the AI's job is to make it short enough to be read at the pass. The bracket is for whoever knows the rules where you operate.
Leave: write the accrual rule so a part-timer can check it
Leave is where models import another place's entitlements, so the handbook's leave section stays red. Your facts supply the rule you use; the adviser confirms it meets the legal minimum and handles part-timers and irregular hours. Here is why a worked example belongs in the handbook. Say the rule is one hour of paid leave for every 20 hours worked. A server working 24 hours a week accrues 1.2 hours a week, which is 62.4 hours over 52 weeks, or 7.8 days of eight hours. A part-timer who can run that sum trusts the rule. One who cannot asks the manager every month. These figures are illustrative, and the legal minimum where you operate may be higher, which is exactly what the adviser's check is for.
The same section covers public holidays, sick pay, family leave, unpaid leave and how to request time off, and each is a marker for the adviser. The related employment contracts tutorial explains how the handbook and the contract should agree on these terms.
Version control: the part most handbooks skip
You will change the handbook, and the day someone disputes a rule you need to show which version they had. Set up four habits. Keep one master file and issue it only as a PDF. Put a footer on every page with the version, the effective date and the owner. Keep a change log. And record each person's acknowledgement against a version. For the example restaurant:
| Version | Effective | What changed | Adviser sign-off | Acknowledged |
|---|---|---|---|---|
| v1.0 | 3 Mar 2026 | First issue | 24 Feb 2026 | 12 of 12 |
| v1.1 | 15 Jun 2026 | Tips rewritten for the points system | 9 Jun 2026 | 13 of 13 |
| v1.2 | 1 Oct 2026 | Leave rule and sick-pay wording | 24 Sep 2026 | 11 of 14 so far (79%) |
The last row is the one to act on: three people have not acknowledged v1.2 four weeks in, and the register tells you who. Keep day-to-day material out of the handbook so it does not need reissuing for every change. The allergen matrix, closing checklist and rota are live documents with their own owners. When one policy changes mid-year, issue a dated addendum rather than a new handbook. Software that collects e-signatures and tracks completion can keep the register for you, but check what a tool really offers before you rely on it. Ask your adviser too whether staff must be told or consulted before certain changes take effect.
Contract status and the sentence everyone copies
Almost every template carries a line saying the handbook is not a contract. Whether it works depends on the wording and on where you operate. In many places vague boilerplate does not reliably protect the employer, clear and specific wording does better, and an individual policy can still create rights even when the rest of the handbook does not. So this is a red section: you tell the adviser how you want the handbook to be treated, and they write the sentence. Do not let AI choose.
Related lines get invented too: the length of the probation period, notice periods, what counts as full-time. Those come from contracts, not the handbook. If the handbook repeats them, the numbers must match every signed contract, and a model that wrote "three months" without being told has just created a mismatch. Either leave them out and point to the contract, or copy them from the contract and let the adviser check.
A short rule for staff who use AI tools
Staff are already pasting things into chatbots: guest allergy notes, reservation details, rota data, a complaint email. A handbook written this year should say what is allowed. Keep it short: use only the tools the restaurant has approved; never enter guests' names, contact details, allergy or health information, or colleagues' personal details; and check anything AI produces before it reaches a guest. Personal accounts usually have a model-training or chat-history setting in their privacy options, and business plans do not train on content by default, but neither makes guest data safe to paste, so the rule is simpler than the settings. Because it links to monitoring and discipline, this is an amber section. The tutorial on an AI-use clause for staff handbooks covers the wording, and the adviser confirms how it connects to your disciplinary process.
What to hand the adviser, and in what order
Send a short pack: the draft with its markers, your staff structure (headcount, ages, full-time and part-time, any under-18s), your tip arrangement, the current contracts or offer letters, and your existing disciplinary procedure if you have one. Ask for a fixed fee for the red sections first, then a skim of the amber ones. Eight questions cover most of what they will need to settle:
- What are the minimum breaks, rest periods and weekly limits for adults and for under-18s?
- Which staff may share in tips, may we deduct card costs, and how must tips be recorded and paid?
- What are the legal minimums for leave, sick pay and family leave, and how do they apply to part-timers?
- Does our disciplinary and grievance procedure meet the rules, and how should it be described?
- What should the handbook say about its own legal status?
- Which harassment, discrimination and whistleblowing statements must appear?
- What must we tell or consult staff about before changing the handbook?
- How long should we keep old versions and signed acknowledgements?
When the adviser returns the draft, issue it with a 20-minute staff meeting rather than an email, then test it: ask three people to find, within a minute, how tips are shared, how to swap a shift and what to do when they are ill. If they cannot, the structure is the problem, and a quick reshuffle will fix it. Keep a running log of the questions staff ask in the first month. AI can turn that log into a short FAQ page to pin beside the rota, which is the best use of it once the legal work is done.
Handbook questions owners ask after the first draft
How often should a restaurant handbook be reviewed?
At least once a year, and whenever your practice changes (a new tip system, a new rota app) or the law does. Put a review date in the footer and ask your adviser to flag changes that affect you. A handbook that describes last year's rules is worse than none.
Can AI translate the handbook for staff with other first languages?
AI translation is a useful first draft, but have a fluent speaker check it, especially the pay, discipline, safety and allergen sections. Keep one version as the reference text, record which language version each person received, and ask your adviser whether the translation needs to be treated as part of the official handbook.
Do temporary and agency staff need the handbook?
They should see at least the safety, hygiene, allergen and conduct sections before their first shift. Who is responsible for their pay and terms depends on the arrangement, so ask your adviser and the agency. Give them a short extract rather than the full handbook if some sections do not apply.
Further reads
- AI Scheduling App for Restaurants: Split Shifts, Tips and Swap Rules — Split shifts, tips and swap rules inside a rota app.
- AI Shift Scheduling vs a Rota Spreadsheet for Small Teams — Compare AI scheduling with a spreadsheet for small teams.
- How to Build a Restaurant Staff Rota With AI Demand Forecasts — Build the rota that the handbook's shift rules describe.
- AI for Hospitality: Which Jobs to Delegate and Which Stay With Staff — Which hospitality jobs to hand to AI and which to keep.
- Restaurant Labour Cost Percentage: Test Rota Changes With AI First — Test how rota and tip changes affect labour cost.
- Restaurant SOP Template: Opening and Closing Checklists With AI — A one-page SOP template, a closing routine corrected line by line, filled-in opening and closing checklists, and a version log with manager sign-off.
- Restaurant Job Descriptions: Can AI Write a Server or Line Cook Ad? — ChatGPT can draft a server or line cook ad in a minute. Here is what a hiring owner must check on shifts, pay, tips and wording before posting.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: general legal commentary on employee handbooks (legal effect depends on wording and place; disclaimers; signed acknowledgements; legal review); the owner's staffing figures supplied as illustrative examples.