A food safety verification visit can feel stressful, especially when you are also managing staff, suppliers and a busy service. The best preparation is not a frantic clean the night before. It is making sure your Food Control Plan or National Programme matches what your kitchen actually does, and that your team can show it.
A verifier is there to check that your business is making safe and suitable food, following the food safety system it is registered under and keeping the records that apply to its operation. They may inspect the premises, review records, watch a task and ask staff to explain how they manage a risk. Preparing well means bringing those parts together before the visit.
Start with the food safety system you are registered under
Before checking the kitchen, confirm whether your business operates under a Food Control Plan, a National Programme or another risk-based measure. Open the current version and check that it describes the food you make, the processes you use and the places where you operate. MPI’s My Food Rules guidance can help businesses identify which requirements apply.
Pay particular attention to anything that has changed since the last visit. A new menu may introduce cooling, reheating, sous vide, sushi rice, fermentation or allergen risks that were not previously part of the operation. New equipment, online sales, catering, transport or a change of premises can also affect what your system needs to cover. If your registered scope no longer reflects the business, contact your registration authority or verifier rather than waiting for the visit.
Review the last verification report
Find the previous report and read every corrective action, recommendation and agreed close-out date. Gather the evidence showing that each issue was resolved. A repair invoice, photograph, updated procedure, staff training record or several weeks of completed checks may all help demonstrate that the change has lasted. Do not assume a problem is closed simply because it has not happened again.
Check your records before the verifier does
Your records should form a clear story: the required checks happened, the results were realistic and action was taken when something went wrong. Review the records relevant to your kitchen, which may include fridge and food temperatures, cooking and cooling, hot holding, reheating, deliveries, cleaning, maintenance, staff illness, training, water, pests, complaints and specialised processes.
Look for unexplained gaps, identical readings repeated day after day, missing names, results outside safe limits with no follow-up, or records that cannot be linked to a food or batch. Do not backfill missing entries or change an inconvenient result. Record the gap honestly, investigate why it occurred and show what you have done to prevent it happening again.
Make records easy to retrieve
Paper and digital records can both work. The practical test is whether the manager can find the requested information without a long search. Organise records by type and date, make sure digital logins work, and have backups or export options available. If part of your system is kept off-site, confirm it will be accessible during the visit.
Walk through the kitchen as if you were the verifier
Begin at delivery and follow the route food takes through storage, preparation, cooking, cooling, reheating, service and disposal. At each stage, ask what could make food unsafe or unsuitable and how your team controls that risk. The answers should be visible in the condition of the kitchen, the way staff work and the records they complete.
Check that food is protected from contamination, raw and ready-to-eat foods are separated, allergen cross-contact is controlled, date labels are clear and stock rotation is working. Inspect handwashing facilities, cleaning chemicals, rubbish areas, pest controls and staff amenities. Look beneath and behind equipment, but also watch the everyday details: wiping cloths, utensils, storage containers, ice machines and anything staff touch repeatedly.
A spotless kitchen can still have unsafe processes, and a good procedure on paper does not help if nobody follows it. Verification brings both sides together.
Test the equipment that supports food safety
Check that fridges, freezers, hot-holding units, dishwashers and other critical equipment are operating as intended. Make sure a suitable probe thermometer is available, clean and giving a reliable reading. Staff should know where it is kept, how to use it without contaminating food, and what to do if a result is unsafe.
Do not hide a fault until after the visit. If a fridge is struggling, protect the food, arrange the repair and keep evidence of both actions. A documented problem that was managed properly shows far better control than an unexplained warm unit or a freshly altered record.
Brief your team without giving them a script
The person responsible for day-to-day food safety should be available for the visit. Other staff may also be asked simple questions about the work they perform. They do not need to recite the Food Control Plan. They should be able to explain, in their own words, how they complete a task safely and what they would do if something went wrong.
Before the visit, talk through practical scenarios. Ask a cook how they know chicken is safely cooked, a prep worker how they prevent allergen cross-contact, or a duty manager what happens if a fridge is too warm. Check that staff understand illness reporting, handwashing, cleaning and the records assigned to them. If an answer is uncertain, retrain the person and record it.
Encourage staff to answer honestly and demonstrate the real process. “I’m not sure, I’ll check with the manager” is safer than guessing. A rehearsed answer that conflicts with what the verifier observes can create more concern than a genuine request for clarification.
Know what to expect on the day
Verification is usually arranged with your council or chosen verification agency. The scope and length of the visit depend on the complexity of the business and how well food safety is being managed. MPI explains that verification frequency can range from every three months to every 18 months, depending on factors such as the food processes, the food sold and the business’s performance.
At the opening discussion, tell the verifier about significant changes, recent incidents and any work still in progress. Give them space to observe normal operations and make the plan, records and responsible people available. They may select only some topics or records for closer review, so do not prepare a special “verification folder” that ignores the rest of the system.
Remote verification may sometimes be possible
MPI notes that some verifications can be completed remotely using technology. If your visit will be remote, test the connection, camera and sound, and make sure records can be shared clearly. You may need to move through the premises on video, so plan for safe access without disrupting food handling.
Respond properly to findings
After considering the topics checked, the verifier will give the verification an acceptable or unacceptable outcome. Individual findings may identify good performance, areas for improvement or non-compliance. If corrective action is required, agree on what evidence is needed and the date by which it must be supplied.
Fix the food safety risk first, then address the reason it happened. For example, replacing spoiled food deals with the immediate problem; repairing the fridge, changing the checking routine and confirming stable temperatures deal with the cause. Submit clear close-out evidence by the agreed deadline and keep a copy with the report.
An unacceptable outcome can lead to more frequent verification and further regulatory attention, particularly when serious or repeated problems are involved. On the other hand, strong performance can support longer intervals between visits. That makes preparation part of everyday cost control as well as food safety.
A practical seven-day preparation plan
Seven days before: confirm the appointment, registered scope and current plan. Read the previous report and list anything that still needs evidence.
Five days before: audit the required records. Investigate gaps and repeated failures. Check that digital systems, passwords and backups work.
Three days before: walk through the premises from delivery to service. Arrange urgent repairs, remove damaged equipment and check pest, waste and chemical controls.
Two days before: test thermometers and critical equipment. Review allergen information, labels, traceability details and the way food is cooled, reheated and transported.
One day before: brief staff on the visit and the tasks they perform. Make sure the day-to-day manager will be present and can access every part of the system.
On the day: operate normally, be open about problems and have the plan, records and previous close-out evidence ready. Take notes during the final discussion so responsibilities and deadlines are clear.
Make verification readiness part of normal service
The easiest verification to prepare for is the one your kitchen is already ready to pass. Complete checks when they happen, record honest results, deal with problems promptly and review the system whenever the menu, equipment or team changes. A short internal check each month is more useful than a major clean-up once a year.
Official guidance is available from MPI’s food business verification page, the template Food Control Plan guidance and your local council or recognised verifier. Always follow the documents and conditions that apply to your particular registration.
Good preparation is not about creating a perfect-looking kitchen for one appointment. It is about being able to show that safe food practices continue through busy shifts, staff changes and the occasional problem. When the evidence is already part of the way your kitchen works, verification becomes a review of the system rather than a scramble to rebuild it.
If paper folders make that evidence difficult to maintain or retrieve, see how the Jiko food safety app for NZ kitchens helps teams complete everyday checks, keep searchable digital records and export selected information when it is requested.