Staff training record
A plan in a binder controls nothing
The document does not keep anybody safe. The person on the line knowing the number, the method, and what to do when it fails — that is the control. A training record is how you show the gap between those two things has been closed.
Free to build. You see the whole thing before anything is asked of you.
01The idea
Certificates are not training.
A food handler card proves somebody passed a general exam. It says nothing about whether they know how your kitchen cools a batch, where yourthermometer is kept, or what your plan says to do when the walk-in reads 46°F.
The worker on the line has to know the number, the method, and what to do when it fails.
Why this record exists
Which means training is against your own procedures — the SOPs your plan produced — not against food safety in the abstract.
02What one looks like
Your procedures, by name.
| Employee | Position | Topic / SOP | Trained by | Date | Method | Signed | Cert expiry |
|---|---|---|---|---|---|---|---|
| A. Okafor | Line cook | Cooling SOP — shallow pan method | J. Reyes | 3 Sep | Demonstration + did it | AO | Handler: 11 Mar 2028 |
| A. Okafor | Line cook | Cooking temps — poultry 165°F | J. Reyes | 3 Sep | Demonstration | AO | — |
| M. Silva | Kitchen manager | Corrective action SOP | Owner | 28 Aug | Read + discussed | MS | CFPM: 2 Feb 2029 |
03Two things worth tracking
Expiry dates, and language.
Expiry. Certifications lapse, usually quietly and usually on the week you need them. A manager certification and a handler card renew on different clocks. Keeping the dates in the same place as the training means you see them coming.
Language. If someone reads Spanish more comfortably than English, training them in English produces a signature and not much else. Train in the language the person actually reads, and note which one you used. A record of training nobody understood protects nobody.
04The loop nobody closes
A deviation should create a training entry.
Here is the connection most kitchens never make, and it is the one that turns paperwork into a system.
- 1
Something goes wrong and lands on the corrective action log
A batch cooled too slowly. A cooler reading missed. A cleaning task skipped.
- 2
You record the cause — honestly
Often the cause is that somebody did not know, or knew and forgot, or was never actually shown.
- 3
That produces a retraining entry here, naming the people involved
Same SOP, fresh date, and a method that is likely to stick this time.
- 4
Which is why the same line does not appear next month
The deviation gets fixed and so does the reason for it. Without step three you just keep writing the incident down.
05Being straight with you
Why there is no blank one here.
Why there’s no blank one to download
The column that matters is “Topic / SOP”, and on a blank sheet it is empty for a reason no template can fix — it is supposed to name your procedures, and a downloaded grid does not know what they are.
Filled in from a finished plan, the topics are your actual SOPs, so training a new starter becomes working down a list rather than inventing one.
And something we are not offering yet: turning each of those SOPs into a short course a new hire completes before their first shift is planned, not built. When it exists it will be part of a subscription. We are not going to imply otherwise on the way to asking you to sign up.
06Getting it wrong
What an inspector notices.
Certificates on file and no training records
Shows general knowledge and nothing about your own procedures, which is what the plan actually relies on.
Topics like 'food safety' or 'hygiene'
Too vague to check. An SOP has a name; the record should use it.
Trainer signed, employee did not
The employee's signature is the part that says they were there and understood.
Deviations with no matching retraining
The corrective action log says something went wrong; nothing shows the reason being addressed.
07Questions
The things people ask.
Isn't a food handler card enough?
It proves general knowledge. It does not prove the person knows how your kitchen cools a batch of chilli, where your thermometer lives, or what to do when the walk-in reads 46°F. Those are your procedures, and training on them is a separate thing from a certificate.
What's the difference between a CFPM and a food handler card?
The Certified Food Protection Manager is the supervisory certification — longer exam, longer validity, and most jurisdictions want at least one person who holds it. A food handler card is the entry-level one most staff need. Different exams, different renewal periods, and both worth tracking by expiry date.
Why does the record ask how someone was trained?
Because 'read the SOP and signed it' and 'watched someone do it then did it themselves' are very different levels of confidence. If a deviation happens later, the method column is what tells you whether the training was ever likely to stick.
What about staff who don't read English well?
Then training in English is a record rather than a control. Train in the language the person actually reads, and note which one. A signature on a page somebody could not read protects nobody, least of all them.
Someone made a mistake. Does that mean retraining?
Yes, and this is the link most kitchens never make. Any deviation on your corrective action log should produce a retraining entry for the people involved. It closes the loop — the problem gets fixed and the reason it happened gets addressed.
Someone is doing a job they were never trained on.
Pair them with a trained worker until they are trained. Not 'they'll pick it up' — alongside somebody who knows, until the record can be signed honestly.
Your plan produces the SOPs. The training record lists them, so signing somebody off is working down a list instead of writing one.
The loop closes through the corrective action log, which is free to print.