Staff Training & Kitchen SOPs
Most kitchens train by apprenticeship: stand at the elbow of someone who knows, watch them, do it, get yelled at, do it better. It works, but it's slow, inconsistent, and hard to scale. The chefs who pull ahead are the ones who write down their kitchen's standards — and AI just made writing those standards 10x faster.
This lesson shows you how to turn a kitchen's tacit knowledge into clean, printable, station-ready SOPs and training documents.
What You'll Learn
- How to write a one-page kitchen SOP in 10 minutes
- How to build station training checklists for new hires
- How to draft staff communication in two languages (English/Spanish)
- How to create monthly skill-builder one-pagers for your team
- A framework for using AI without it sounding "corporate"
The One-Page SOP
Every recurring kitchen task — opening a station, cleaning the combi, breaking down the grill, tempering chocolate, opening shellfish — deserves a one-page SOP that anyone can follow. AI writes the first draft in 90 seconds.
Act as my chef de cuisine writing a one-page kitchen SOP.
Task: End-of-night close of the hot line, 80-seat full-service restaurant.
Context:
- Two cooks closing
- Service ends at 10pm, kitchen must be ready for 1pm next-day open
- Equipment: 6-burner range, flat-top, char-grill, salamander, two
convection ovens, two combi ovens, two induction tops
Write a one-page SOP with:
1. The end state we're aiming for (what "done" looks like)
2. A numbered procedure in the order it should be done (40-60 minutes total)
3. A two-column checklist a closer initials as each step is complete
4. A "if you only have 20 minutes, do these 8 things" priority subset
5. A sign-off line at the bottom (closer initials, date, time)
Tone: direct, no fluff. Written by a chef, for a cook, in plain English.
The output is a real SOP. Print it, laminate it, post it at the station. Update once a quarter as your team finds the steps that are wrong.
Build one for every recurring task. After a year you'll have a 30-SOP kitchen library that survives staff turnover.
Station Training Checklists for New Hires
When a new hire starts on a station, what do they need to be able to do, and in what order? Most kitchens have a vague answer. AI turns it into a clean four-week ramp.
Write a 4-week training plan for a new line cook starting on hot apps
station at a 100-seat modern American restaurant.
Week 1 goal: shadow and assist, learn mise en place, knife work check-in
Week 2 goal: run station with a senior cook over the shoulder
Week 3 goal: run station independently on Tuesday/Wednesday (slower nights)
Week 4 goal: run station Friday/Saturday at full volume
For each week, give me:
1. Specific skills to demonstrate (e.g., "executes the gnudi pickup within
the 4-minute target")
2. A short knowledge check the chef de cuisine signs off (e.g., "names the
3 allergens in the duck dish")
3. The 3 mistakes most likely to happen at this stage and how to coach
them
4. A 1-line check-in question for the daily pre-shift
Format as a markdown table per week.
Print it. Give a copy to the new hire on day one. This document does more for retention than any pay bump under $1/hour. New cooks who know what success looks like stay.
Bilingual Staff Communication
Many US and international kitchens run in both English and Spanish. AI translates well — but you should treat it as a draft, not as authoritative.
Translate the following kitchen SOP into restaurant-Spanish (mixed
English/Spanish kitchen vernacular -- not formal academic Spanish):
[paste SOP]
Keep technique words in their original language if that's how a working
Mexican/Central American kitchen would actually say them. Example:
"mise en place" stays in French; "saute" can stay or become "saltear."
Use "ustedes" (plural informal) for instructions to the team.
Output both versions side by side, English | Spanish, in a markdown table.
The side-by-side format makes it easy for a bilingual sous chef to spot-check the translation. Always have a native Spanish-speaking team member review before printing for service.
Monthly Skill-Builder One-Pagers
Most teams plateau because nobody is teaching anything new. A monthly one-page skill builder — focused on one technique — keeps your team learning.
Write a one-page skill builder for our kitchen team for May.
Topic: Browning meat for stocks and sauces (Maillard reaction, fond
development, deglazing).
Audience: line cooks and prep cooks of varying experience levels (1-7
years).
Structure:
1. The technique in one paragraph (what we're doing and why it matters)
2. The science in three sentences (what Maillard actually is, no jargon)
3. Three common mistakes (and how to spot them in your own pan)
4. A 15-minute drill any cook can do during prep with a small saute pan
5. The way this technique shows up in three of our current menu items
[we make stocks for the soup, braising for the short rib, fond for the
pan jus on the steak]
Tone: chef-to-cook, generous, never condescending. End with one sentence
that makes the cook want to try it tonight.
Print 10 copies. Leave them by the timecard. The cooks who pick them up are your future leads.
Why It Doesn't Sound "Corporate"
A reasonable worry: if you let AI write your kitchen docs, will they sound like an HR PDF?
Yes, by default. The fix is the same as everywhere else in this course: voice and specificity.
Always include in the prompt:
- The audience (specific roles, experience levels)
- The voice ("chef-to-cook, direct, generous, no fluff, no HR language")
- Banned words ("teammates," "synergy," "leverage," "stakeholder," "going forward")
- A real example from your kitchen ("we already use this technique in the duck-fat potato — reference it")
With those four ingredients, AI writes in your voice, not in McKinsey's.
Key Takeaways
- One-page SOPs are the right unit — short enough to read in 60 seconds, dense enough to actually do
- Build 4-week ramp training plans for every station and give them to new hires on day one
- Translate to kitchen-Spanish in side-by-side format and have a native speaker verify
- Monthly skill-builders keep teams learning and identify your future leads
- Voice + audience + banned words + a real example keeps AI from sounding corporate
- After a year of consistent SOP writing, you'll have a kitchen library that survives turnover