The stainless steel is shining. The benches are clear. The fridge handles have been wiped and every container has a lid. From the doorway, your kitchen looks exactly as it should.
Then someone asks a different question: can you show that yesterday’s chicken was cooked safely, that the soup cooled quickly enough, that the morning fridge check actually happened, and what your team did when a result was outside the limit?
That is the difference between a kitchen that looks clean and a food safety system you can prove is working.
Clean is important. It is not the whole test.
Cleaning and sanitising are essential. They help prevent harmful bugs and allergens spreading through food, equipment and surfaces. MPI includes cleaning, handwashing, separation, cooking and chilling among its core food safety factors.
But appearance alone cannot tell you whether chilled food stayed under control overnight, whether a cook used a reliable method, whether a staff member returned too soon after vomiting or diarrhoea, or whether an allergen order was protected from cross-contact. A spotless bench cannot answer any of those questions.
New Zealand food businesses operating under a Food Control Plan or National Programme are independently verified. MPI says a verifier checks that a business is following good food safety practices and keeping the records that apply to it. In other words, the test is not only what the kitchen looks like at one moment. It is whether the day-to-day system can be trusted.
Proof is a story, not a pile of completed forms
Good evidence connects four things: what was checked, what the result was, who completed it and what happened next. A temperature of “4°C” written on a sheet is only one part of that story. Which fridge was checked? When was it checked? Was the thermometer reliable? If the result was 9°C instead, what happened to the food and the equipment?
The records needed by each business depend on its registered plan, menu and processes. They may cover refrigeration, cooking, cooling, reheating, hot holding, deliveries, cleaning, maintenance, staff illness, pests, allergens, training, complaints and specialised processes. The current version of your own Food Control Plan or National Programme should determine what you keep.
Believable records matter
Real kitchens are not perfect. Fridges warm up, probes fail, deliveries arrive outside specification and checks occasionally get missed. A record system in which every reading is identical and nothing ever goes wrong can raise more questions than it answers.
Do not invent a missing entry or rewrite an inconvenient result. Record the problem honestly, protect any affected food, investigate the cause and note the action taken. Evidence that your team recognised and controlled a failure is far more useful than a perfect-looking form that does not reflect reality.
The moment something goes wrong is when your system is tested
Imagine the first fridge check of the day is too warm. A weak record shows a high number with no explanation or the number is quietly changed. A strong record shows which unit was affected, how the food itself was assessed, where stock was moved, what was discarded, who arranged the repair and how safe temperatures were confirmed afterwards.
The same principle applies when food cools too slowly, a pest is sighted, a staff member reports illness, a delivery arrives damaged, an allergen mistake is caught or a customer complains. The immediate risk comes first. Then the underlying cause needs to be addressed so the same failure is less likely to happen again.
This is corrective action in practical terms: what went wrong, what food may have been affected, what you did immediately, what caused it and what you changed. Keep the supporting evidence too, such as a photograph, repair invoice, supplier message, disposal note, retraining record or follow-up temperature checks.
Your staff are part of the evidence
A folder can say the right thing while the shift does something completely different. That is why staff should understand the safe method for the tasks they perform, not simply know where to sign.
Ask practical questions during a normal shift. How does the cook know this batch is safe? What happens if a fridge is too warm? How is an allergy request communicated from the customer to the person plating the meal? When must an unwell food handler stay away from food? Where is a failed check recorded?
The answers do not need to sound rehearsed. They do need to match your written system and what happens in front of you. If only one manager knows the process, the system is fragile. Training should be repeated when staff, equipment, menus or methods change, and the training itself should be recorded where your plan requires it.
Could you follow one ingredient through your kitchen?
Proof is not limited to temperatures and cleaning. If a supplier recalls a product or a customer reports illness, you may need to establish what arrived, when it arrived, where it was used and what remains on site. MPI’s recall guidance emphasises traceability, and a simulated recall is one way to test whether your procedure works before a real incident.
Choose one higher-risk ingredient and run a simple challenge. Can you find the supplier and delivery details? Can you identify the relevant batch or date? Can you work out which dishes used it and whether any stock remains? Could you do all of that during a busy afternoon without searching through several unlabelled folders?
If the answer is no, the problem is not that the kitchen looks untidy. The problem is that you may lose valuable time when speed and accurate information matter most.
Missing records can become an expensive problem
Record keeping is not paperwork for paperwork’s sake. In January 2025, MPI reported that an Auckland food producer and its manager were fined a combined $16,500 after repeated failures to keep required production records. MPI said those records were needed to support traceability and a recall if a food safety problem occurred.
That case involved a food producer rather than a restaurant, and every business must follow the requirements applying to its own operation. The lesson for hospitality is still direct: saying a check happened is not the same as being able to demonstrate it. When records are required, repeated gaps can have real regulatory and financial consequences.
Food safety officers also have a range of enforcement tools available under the Food Act 2014, including warnings, infringement notices, directions and other compliance orders. Good evidence will not excuse unsafe food, but poor evidence can make it much harder to show that your controls were operating as intended.
Six questions to ask before your next service
1. Does our plan match what we actually make? New menu items, catering, transport, cooling, reheating and specialised processes can change the risks your system needs to cover.
2. Are checks completed when the work happens? A result entered from memory at the end of the week is weaker than a contemporaneous record.
3. Do we record the action, not just the failure? An unsafe result without a response leaves the most important part of the story missing.
4. Can staff explain their own tasks? Knowledge needs to exist on the shift, not only in the manager’s office.
5. Can we retrieve evidence quickly? Paper or digital can work, provided records are protected, readable and easy to find.
6. Do we review patterns? Repeated warm readings, missed checks or recurring pest sightings are warning signs, even if each individual entry was filed away.
Build proof into the way the kitchen works
The goal is not to create more administration. It is to make the important work visible. Give each check a clear owner and sensible frequency. Keep the form short enough to complete during service. Make unsafe results prompt an action. Review gaps regularly instead of waiting for verification week.
A digital system such as Jiko can make this easier by keeping checks and corrective actions in one place, helping managers see missing work and making older evidence faster to retrieve. The tool should support the system, not replace staff training, sound procedures or the requirements of your registered plan.
For official information, use MPI’s food business guidance, the food safety toolkit, the verification guidance and the documents applying to your own registration. If you are uncertain about a requirement, check with your local council, recognised verifier or MPI.
A clean kitchen creates confidence for a moment. A working food safety system earns it every day. The real question is not whether your kitchen looks safe when someone walks in. It is whether your team can show what happened when nobody was watching.
If your team needs a simpler way to turn daily checks into organised evidence, see how the Jiko food safety app for NZ kitchens helps small hospitality businesses complete checks, keep searchable digital records and retrieve information when it is needed.