Food safety culture is what your people do about food safety when no one is checking: whether the newest hire stops the line when something looks wrong, whether someone with a stomach bug calls in instead of coming to work, whether a dropped scoop goes in the wash or back in the tub. FDA's plan for the next decade calls a strong food safety culture a prerequisite to effective food safety management, says it will support tools for companies to assess their culture, and is considering how a positive culture could count toward inspection frequency. The rules underneath are concrete: everyone handling food has to be trained in food hygiene and food safety, including employee health, with training records kept, and in a retail kitchen staff have to report symptoms like vomiting, diarrhea or a sore throat with fever to the person in charge. For a small business, measuring culture can be a ten-question anonymous survey twice a year, plus watching what happens on a busy Saturday. In the example below, an ice cream maker's eight-person survey shows the scoopers wouldn't stop production. Below are the signs, the rules, the example, and a free survey.
The short version
- Food safety culture is what people do about food safety when no one is watching.
- FDA calls a strong culture a prerequisite to effective food safety management.
- Everyone handling food is trained in food hygiene and safety, with records kept.
- Staff report vomiting, diarrhea, jaundice, sore throat with fever and infected wounds.
- Measure it: a short anonymous survey, and what you see on a busy day.
- Fix the lowest scores first, tell people what changed, and ask again in a few months.
- TaroStack records who did each step and why every change was made. More below.
What it looks like
| Sign | Strong | Weak |
|---|---|---|
| Speaking up | Anyone stops the line and is thanked for it | Problems wait for the owner |
| When busy | Cleaning and temperatures still happen | Steps skipped on Saturdays |
| Sick days | People call in with symptoms | People come in sick to keep their hours |
| Mistakes | Reported, fixed, and the fix explained | Hidden, or blamed |
| The owner | Washes hands like everyone else | Rules for staff, not for the owner |
| Records | Filled in when it happens | Filled in at the end of the week |
How training gets recorded is in employee training log template.
The rules
| Rule | Where |
|---|---|
| FDA's view | A strong food safety culture a prerequisite to effective food safety management; tools to assess it; a positive culture considered in inspection frequency (FDA blueprint, Core Element 4) |
| Training | Everyone handling food qualified and trained in food hygiene and food safety, including employee health and personal hygiene (21 CFR 117.4) |
| Supervisors | Responsibility for following the rules assigned to qualified supervisors (117.4) |
| Records | Training records kept (117.4) |
| Reporting illness | Vomiting, diarrhea, jaundice, sore throat with fever, infected wounds and diagnosed illnesses like norovirus reported to the person in charge (Food Code 2022, 2-201.11) |
What an auditor walks through is in food safety audit checklist. This is general information, not legal advice.
An example: a Birmingham ice cream maker
Ironwood Pint Co., the made-up ice cream maker in Birmingham, Alabama, I use in these examples, makes pints from a pasteurized base and runs a weekend scoop window. Its eight people answered ten statements anonymously, from 1, disagree, to 5, agree:
| Statement | Average | Lowest |
|---|---|---|
| The owner follows the same food safety rules we do | 4.6 | 4 |
| I know why the base stays cold from delivery to the freezer | 4.1 | 3 |
| I have what I need: gloves, sanitizer, thermometers, time to clean | 4.1 | 4 |
| I was trained on the food safety parts of my job | 3.9 | 3 |
| I can report a mistake without getting in trouble | 3.5 | 3 |
| When we're busy, food safety still comes before speed | 3.4 | 2 |
| I can afford to stay home when I'm sick | 3.3 | 3 |
| I know I have to report vomiting, diarrhea or a sore throat with fever | 3.1 | 2 |
| When something goes wrong, we hear what changed because of it | 3.1 | 3 |
| I would stop production if I saw a food safety problem | 2.6 | 2 |
The owner scores well as an example; the gaps are about permission. The weekend scoopers, hired in the spring, didn't think stopping was their call, and two didn't know which symptoms to report. Ironwood wrote the stop rule on the wall by the window, added the reportable symptoms to the first-day training and the training log, told everyone that a sick call keeps its shift's pay, and now ends each Monday meeting with what changed and why. The same ten statements go out again in January. The base's own controls are in ice cream HACCP plan.
Get the template
Download the food safety culture survey. One sheet: ten statements by category with a column for each person's answer from 1 to 5; the average and lowest answer for each statement, a flag on low averages, and an average for each category fill in. Change the statements to fit your kitchen. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A survey tells you how people feel twice a year. The everyday evidence is in the records: whether checks get done when they're due, by whom, and whether problems get written down or quietly fixed.
How TaroStack does it
TaroStack makes every change a record of who, when and why, which is what a culture leaves behind.
Every change has a reason. Every movement of stock is a permanent record of who, when and why; a write-off carries its reason, spoiled, damaged or expired, so problems show up in reports instead of disappearing.
Batch records with your own fields. A batch record can carry fields of your own, such as the base temperature at receiving and who checked it, with sign-off.
Corrections, not erasures. A mistake is recorded as a correction and can be undone, so the record shows what happened rather than a clean page.
| The job | Paper | In TaroStack |
|---|---|---|
| Who checked the base | Initials, sometimes | A field on the batch record |
| Why a tub was thrown out | Not written | An adjustment, with its reason |
| A mistake on a count | Crossed out | A correction, on record |
| Problems by kind | Memory | Write-offs reported by reason |
Batch records, your own fields and adjustments with reasons are on every plan, from $49 a month. The first 30 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.