How to Build a Kitchen Training Manual With AI

Capture how your kitchen actually works first: voice notes or phone videos of each station, your recipe specs and your food-safety plan. Then have AI turn each capture into a consistent one-page station card, while the head chef checks every temperature, allergen and quantity before anything goes on the wall. A small kitchen should allow 15 to 25 hours.

The common mistake is asking an AI to "write a kitchen training manual" from nothing. You get a polished document describing an average kitchen, complete with times and temperatures that may not match your equipment or the rules that apply to you. The method below keeps the AI on formatting and structure, and keeps the knowledge, and the numbers, with your chefs.

Follow me on Instagram@sagnikteaches

What goes in, and what stays in the food-safety plan

Decide the sections before capturing anything. For most small kitchens:

Connect on LinkedInSagnik Bhattacharya

The last two rows matter most. Your food-safety plan is the controlled document, set up to meet whatever rules and inspections apply to you. The training manual should repeat its critical figures word for word, or point to it, but never generate its own.

Subscribe on YouTube@codingliquids

Capturing the chef's knowledge without a week of writing

Chefs rarely have time to write, but most will talk through a station while they prep. Three capture methods, in order of usefulness:

• Voice notes during quiet prep. The head chef talks through a station as if training a new cook standing next to them. Ten to fifteen minutes per station.
• Phone video of plating and set-up. Thirty seconds per dish, filmed from above. The video is the reference; the AI can't watch it for you, but the chef can describe it while filming.
• A short interview. Someone else asks the questions below and records the answers.

Transcription is simple: many phones transcribe voice notes, and most chat assistants accept audio. If you want a dedicated tool, Otter.ai Pro is $8.33 a user a month on annual billing, or $16.99 monthly.

Station interview questions (ask each, record the answers)
1. What has to be ready on this station before service starts?
2. What do you check first when you arrive?
3. Walk me through a typical ticket from call to pass.
4. What do new cooks get wrong here in their first week?
5. What should they never do on this station?
6. When should they call you over, no matter how busy it is?
7. What does "good" look like on the plate? What makes you send it back?
8. What needs doing before they leave the station at close?

Question 4 produces the most useful material. Every chef knows the mistakes new starters make; almost no manual records them. Here's a pastry chef's answer, recorded while rolling out tart cases (illustrative):

"They open the oven every two minutes to look at the tarts, and the cases drop. They use caster sugar from the wrong tub, the one that's for the bar. They don't write the time on the crème pât when they make it, so nobody knows if it's this morning's. And they pipe straight from the fridge, when it needs a beat first or it goes lumpy."

That becomes four lines on the card, each a mistake with its fix: "Opening the oven to check tarts: use the oven light and the timer; open only when the timer goes." "Using the bar's sugar: pastry sugar is the tub labelled P on the shelf above the mixer." "Unlabelled crème pât: label with the time and your initials as soon as it's made." "Piping it cold from the fridge: beat it smooth first." Nothing in those lines came from the AI except the layout, which is the point.

Turning a ramble into a station card

Paste the transcript into an assistant with a fixed format, so every card in the manual looks the same:

Turn this transcript into a one-page station card for a restaurant
kitchen. Use exactly these headings:
  Purpose of the station (one line)
  Before service (checklist)
  During service (numbered steps)
  Quality check before the pass
  Mistakes new cooks make (and the fix)
  Call the chef if...
  Closing down (checklist)
Rules:
- Use only what's in the transcript. Do not add temperatures, times,
  quantities or safety steps that aren't there.
- If something seems missing (e.g. a temperature is mentioned but
  not given), write [CHECK: ...] in its place.
- Short plain sentences. A new cook reads this mid-service.

Transcript: [paste]

The [CHECK] markers become the head chef's review list. On a typical first draft there are five to ten per card, and each one is a gap in knowledge that previously lived only in someone's head.

Worked example: the grill station

Say the head chef of a 50-cover restaurant (an illustration) records this while setting up:

"First thing, grill on, get it properly hot, clean the bars. Steaks out of the fridge to temper, but not the chicken, that stays in till it's called. Burgers come off at... well, the probe's there, use it every time, no guessing. New starters always press the burgers down, never press them, you lose all the juice. And if a steak comes back, you don't argue, you call me."

The AI's card, before review, includes:

• Before service: turn grill on; clean bars; take steaks out to temper; keep chicken refrigerated until called.
• During service: probe every burger before it leaves the grill. [CHECK: target core temperature for burgers]
• Mistakes new cooks make: pressing burgers on the grill. Fix: leave them; turn once.
• Call the chef if: any steak comes back from a table.

The chef replaces the [CHECK] with the figure from the kitchen's food-safety plan, adds how long steaks temper, and cuts "turn once" because that isn't actually the kitchen's method. That last correction is the reason the review exists: the AI added a plausible detail that nobody said.

The same thing happens with checklists, and there it's easier to miss. In one illustrative case the closing walk-through recording said, "fridge temps get written on the sheet before you go". The AI's tick-list turned that into "Check all fridges are between 0 and 5°C and record on the sheet." It looked more helpful than the original, and it was a range nobody had said, which didn't match the figure in the kitchen's own food-safety plan. It sat on a laminated card for three weeks until the head chef noticed during an internal check. The fix was the one this whole method depends on: the line now reads "Record every fridge temperature on the sheet. Target: see food-safety plan, section on chilled storage", and the prompt gained a line saying "never write a number the transcript didn't contain, even if it seems obvious".

Numbers the AI must never supply

Make this a written rule for whoever builds the manual. Every one of these comes from a named source, and the source goes in a column on the master copy:

• Temperatures and times for cooking, cooling, reheating and holding: from your food-safety plan.
• Allergen information: from your allergen records and recipe specs, never from what a dish "usually" contains.
• Cleaning chemical dilutions and contact times: from the supplier's product and safety data sheets.
• Portion weights and yields: from your recipe specs.
• Equipment settings and safety steps (slicers, fryers, combi ovens): from the manufacturer's manual.

If the head chef isn't sure of a figure, that's a finding, not a problem: check it with your food-safety adviser or the relevant authority before it goes into print.

A few rows of a filled-in source column on the master copy (illustrative). Food-safety figures are deliberately shown as references, because that's how the card should hold them:

Making it usable at 7pm on a Friday

• One page per station, laminated or in a wipeable sleeve, at the station.
• Version and date on every page, with a QR code linking to the current digital copy, so outdated cards are easy to spot.
• Photos taken by your own team of your own plates. Stock images of someone else's dish teach nothing.
• Plain words. Ask the AI to rewrite any sentence over 20 words. A cook glancing at a card mid-service reads the first few words of each line.
• Translations checked by a person, if your team works in more than one language; see the FAQ below.

If parts of your process happen on screens, such as the ordering system or the stock app, creating SOPs from screen recordings is a faster way to document those than voice notes.

Quizzes, sign-off and keeping it current

Once a card is approved, ask the AI to write eight to ten questions from that card only, with answers, for new starters. Short, practical questions work best: "What do you do if a steak comes back?" rather than trivia. The quiz checks reading; a senior chef still signs off each station after watching the new cook work it.

Part of a first quiz for the grill card (sample output, illustrative):

1. What must happen to the chicken before service?
   Answer: It stays in the fridge until it's called.
2. What should you never do to a burger on the grill?
   Answer: Press it down.
3. What temperature should the grill bars reach before service?
   Answer: Around 250-300°C.
4. A steak comes back from a table. What do you do?
   Answer: Call the chef.

Questions 1, 2 and 4 are good: each comes straight from the card and tests something a new cook will actually face. Question 3 has to go. The card says "get it properly hot" and gives no figure, so the AI has supplied one, and a new starter who learns it from the quiz will treat it as the kitchen's rule. Delete any question whose answer you can't point to on the card.

Record sign-offs in a simple training record: name, station, date, who signed off. Building a staff training matrix with AI shows how to turn that into a grid of who can cover what, which also helps when you're building the rota.

Review each card when the menu changes and at least every six months. Because each card came from a transcript plus a fixed prompt, updating is quick: record what's changed, re-run the prompt on the new section, review, reprint. The recipe facts you collect here can also feed your menu wording; writing menu descriptions with AI uses a similar facts-first sheet.

One master copy, and who may change it

Manuals decay when several versions exist: the laminated card from last spring, a newer PDF on someone's phone, the chef's own notes. Set three rules from the start:

• One master copy in a shared folder or document that the owner controls, with the source column for every number.
• One editor. The head chef, or a named deputy, approves every change. Anyone can suggest one; only the editor changes the master.
• A change log at the back: date, card, what changed, why. When an inspector or a new head chef asks why the fryer oil is changed when it is, the answer is there.

If staff use a chat assistant to look things up from the manual, give it the master copy only, and tell it to answer from that document and to say "not in the manual" rather than guess. An assistant that fills gaps from general cooking knowledge undoes the work of keeping numbers sourced. Test it with one question the manual answers and one it doesn't. Asked "How long do the steaks temper?", a well-set-up assistant replies "30 minutes, according to the grill card (version 3, 14 Oct)." Asked "How long can cooked rice be kept?", when rice isn't in the manual, it should reply "That isn't in the manual. Ask the head chef." If it gives a figure for the rice instead, it's drawing on general knowledge, and the instruction needs tightening before anyone relies on it.

Using the manual for a new cook's first week

The cards are only useful if induction is built around them. A simple pattern for a new cook:

1. Before the first shift: read the kitchen basics and allergen procedure; do those two quizzes.
2. Days 1-2: shadow one station with its card in hand; the senior cook points to the card, not just to the pan.
3. Days 3-4: work that station with the senior cook watching; sign-off when they're ready, not on a fixed day.
4. Day 5: ask the new cook what was missing or confusing on the card. Their answer is the best edit you'll get all year.

A typical day-5 comment, and the edit it produced (illustrative). The new cook said: "The card says call the chef if a steak comes back, but not what to do with the steak while I wait. I binned the first one." The line changed from "Call the chef if: any steak comes back from a table" to "Call the chef if: any steak comes back from a table. Put it on a plate at the pass, don't bin it or re-fire it; the chef needs to see it first." Nobody experienced would have spotted the gap, because experienced cooks already know. That's why the question goes to the newest person in the kitchen.

A realistic timetable for a small kitchen

1. Week 1 (3-4 hours): agree the sections; record voice notes and videos for each station during quiet prep.
2. Week 2 (4-6 hours): transcribe and draft every card with the prompt; collect the [CHECK] list.
3. Week 3 (5-8 hours): head chef reviews every card, fills every [CHECK] from a named source, cuts invented details.
4. Week 4 (3-5 hours): print, laminate, write quizzes; trial the cards with the next new starter and note where they got stuck.

That's roughly 15 to 25 hours in total. The general method for turning rough notes into procedures, outside the kitchen, is in writing SOPs with AI, and your front-of-house team will need a matching approach: training front-of-house staff to work alongside AI covers them.

Kitchen manual questions

Can I just ask AI to write a complete kitchen manual for me?

You'll get something that looks complete and describes an average kitchen, not yours. It will include times, temperatures and procedures that may not match your equipment, your menu or the food-safety rules that apply to you. Use AI to structure and tidy what your team already does, and treat anything it adds on its own as a question to check, not content to keep.

How do I train staff who read another language more easily?

Have the AI translate each finished card, then ask a bilingual member of staff to read the translation against the original, because kitchen terms and cooking methods are where machine translation slips. Keep the numbers, allergen names and warning symbols identical across versions, and put the version date on both so nobody works from an outdated translation.

Should the manual be on paper or on a screen?

Both, for different jobs. Laminated one-page cards at each station get used during service, when nobody has clean hands for a tablet. The full manual, with background and quizzes, lives in a shared folder or document that new starters read before their first shift. A QR code on each card linking to the current digital version helps catch outdated copies.

Further reads

• How Much Time and Money Does AI Staff Training Take? — Budgeting the hours that training on anything new takes.
• How to Onboard New Hires Onto Your AI Tools and Rules — Getting new starters onto the tools and rules you use.
• How to Set Up Human Review for AI Work Without Slowing Down — Setting up sign-off so AI drafts never skip a check.
• Writing Pharmacy SOPs With AI: A Step-by-Step Workflow — Another regulated setting where AI drafts need strict checks.
• Your First 30 Days of AI in a Restaurant, Week by Week — Where the manual fits in a restaurant's first month of AI.
• Where AI Actually Saves Time in a Small Restaurant — A task-by-task look at a small restaurant's admin week: where AI cuts real minutes, where it only moves them, and where it adds work.
• Should an AI Chatbot Answer Allergen Questions for Your Restaurant? — Which allergen questions a restaurant chatbot may answer, which must go to a person, and how to stop it guessing from general knowledge.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Otter.ai pricing page; general HACCP principles as used in food-safety management. Worked example is illustrative. Checked September 2026.