How to build a restaurant training program that survives a busy month

They rarely fail loudly. What happens is that the program was defined as a document, the document was finished, and then the actual training carried on happening informally the way it always did. Six weeks later the binder is a historical artifact and nobody can answer whether the new hire can run the grill.

The programs that stick are defined as a set of repeated actions with a record attached, not as a document. The six steps below are those actions.

1. Step 1

   List the stations, not the job titles

   Write down every position somebody can physically stand at during a shift: fryer, grill, expo, register, drive-thru window, dish, bar, prep, opening, closing. Job titles are a payroll concept and they hide the thing you actually need to staff. 'Line cook' is not a station; grill and fry are two different skills and one person is usually better at one of them.

2. Step 2

   Write each station's checklist as observable actions

   For each station, list what a competent person visibly does. 'Understands food safety' is not checkable. 'Checks and logs the fryer temperature before first drop' is. Aim for 10 to 25 items per station: fewer and it proves nothing, more and no trainer will finish it during a shift. Mark the handful that are non-negotiable as critical.

3. Step 3

   Set the bar for signed off

   Decide, before you train anyone, what 'can run this station' means. A workable default: no critical items missed, an overall score above a line you set, and observed on at least two separate shifts, one of which was busy. Write the bar down. An unwritten bar means every manager applies their own, and the record becomes uncomparable.

4. Step 4

   Name who can sign off

   Certification is worthless if anybody can grant it. Pick your trainers deliberately, and make signing someone off a specific act by a specific person on a specific date. This is also the single biggest driver of whether the record stays trustworthy a year from now.

5. Step 5

   Schedule the training into shifts that can absorb it

   Training during a Friday rush does not happen, it just gets recorded as happening. Put learners on a station during a block with slack, pair one trainee with one coach, and prioritise whoever currently knows the fewest stations. Two deliberate training blocks a week beats a full-day session nobody can staff.

6. Step 6

   Re-check on a cycle, and treat old sign-offs as expired

   Skills decay, menus change, and a sign-off from fourteen months ago is a rumour. Pick a re-check interval per station (90 days on anything safety-critical is common, 6 to 12 months elsewhere) and treat anything past it as unconfirmed rather than as a pass.

Step three is where nearly every program is won or lost, and it is the one most likely to be waved through. If "signed off on fry" is not defined, then it means something slightly different to each of your four managers, and a year of records becomes uncomparable because they were never measuring the same thing.

A bar that works in practice

• Zero critical items missed. One missed critical item is a fail regardless of the total.
• An overall score above a line you set per station, not one global number: expo and dish do not deserve the same bar.
• Observed on at least two shifts by a named trainer, at least one of them busy.
• Dated, so it can expire.

Write those four lines on the wall of the office. That is more program than most independent restaurants have.

Three numbers tell you whether any of this is working. Coverage per station: how many people are currently signed off, and which station is thinnest. Trend: whether average scores on a station are going up over months. Most-missed items: the specific checklist lines your crew fails most.

That third one is the highest-value report in the whole category and almost nobody computes it. When one item is missed by most of your crew, the problem is nearly always the training material or the station setup, not the people. It is the cheapest fix available to you and it is invisible without a structured record.