Sharing a Commercial Kitchen: Who Keeps the Food Safety Records?

A shared commercial kitchen can give several food businesses access to suitable premises and equipment. The difficulty often appears between bookings: one team leaves, another arrives, and nobody is sure who checked the chiller, cleaned the mixer or kept the evidence.

This guide explains how to organise cleaning responsibilities, temperature records and handovers in a New Zealand shared kitchen. It focuses on food businesses operating under the Food Act, with specific examples from MPI’s Simply Safe & Suitable template Food Control Plan.

Confirm who operates each food business

Start by identifying the food business operator, the activities being carried out and the plan or programme covering them. Owning the kitchen, holding the lease and operating a food business can be different roles. A booking agreement or another tenant’s registration does not, by itself, establish that your business activities are covered.

Use MPI’s My Food Rules tool for your products and processes. Confirm uncertain shared-site arrangements with the registration authority before starting or changing the operation. Do not assume that every tenant needs the same type of Food Control Plan, or that the site has one arrangement suitable for all users.

For the premises and fit-out questions, see our commercial kitchen setup checklist. Here, the practical question is narrower: can each operator show how its food remained safe while other people used the same facilities?

For FCP businesses, the Food Regulations requirements for the physical boundaries of a food business include identifying activities within the site and managing relevant risks from other activities. A useful shared-kitchen arrangement therefore describes work areas, storage, timing and the controls at the point where users change over.

Agree who does, checks and keeps each record

Separate three questions: who carries out the task, who checks the result, and who retains access to the record? Writing “all tenants” in a cleaning schedule does not answer any of them clearly.

MPI’s Simply Safe & Suitable “Taking Responsibility” card requires someone to be responsible for making sure the plan is followed. It also explains that a verifier may ask how you know delegated food safety tasks are being done properly. An agreement with the kitchen manager should help you answer that question.

Practical example, not a prescribed MPI form: Adapt this responsibility matrix to the registered arrangements and the controls each business actually needs.

On a small screen, swipe sideways to view all columns.

Name a backup for absences and agree what happens outside staffed hours. Payment for a service is not evidence that the service was completed. A contractor’s report can support your records, but someone still needs to review its food safety implications.

Make cleaning responsibilities specific

Describe the actual clean rather than relying on “leave the kitchen tidy”. List food-contact equipment, benches, utensils, sinks, floors, waste areas and any less frequent tasks relevant to the site. Identify which jobs belong to the departing user and which belong to the kitchen manager.

Under Simply Safe & Suitable’s cleaning and closing requirements, cleaning comes before sanitising. Follow the chemical manufacturer’s instructions and the applicable plan. A surface looking tidy does not demonstrate that the cleaning and sanitising steps were completed.

• Specify the method: identify the equipment parts, cleaning product and required sanitising steps, including any instructions for dilution, contact time and rinsing.
• Define the changeover: agree when the clean must be completed and what the next user checks before starting.
• Address different foods: manage raw and ready-to-eat work and relevant allergens across users. Use the applicable separation and cleaning controls; a signature alone does not establish that contamination has been prevented.
• Record exceptions: identify anything not completed, the restriction placed on its use, and the person responsible for fixing it.

A signed changeover checklist is a useful practical control. Do not describe a particular cleaning-log format as compulsory for every business: the applicable plan determines what must be done and shown. The record should provide meaningful evidence, rather than a row of unexplained ticks.

Keep temperature checks connected to the food

A shared refrigerator belongs to the site, but the food inside it belongs to identifiable operators. Agree which checks are required, who takes them, when they occur and how results reach businesses that are not on site at that time.

For businesses using the Simply Safe & Suitable “Keeping food cold” card, check daily that food requiring refrigeration for safety is at 5°C or lower, use the monitoring method selected in the plan and keep temperature-check records. The card says not to rely on the chiller display alone. These are examples from that template, not a universal monitoring schedule for every food activity.

Distinguish a unit display, an air reading and a food or other-substance measurement. Record the method you used. A generic “fridge OK” entry may not show that the relevant food and storage conditions were checked. Use the plan’s requirements for accurate monitoring equipment.

Keep business-specific cooking, cooling, hot-holding or transport records where required. Putting a cooked batch into a shared chiller does not demonstrate that it cooled safely. Identify the food and the responsible business so a reading can be connected to the activity it supports.

Use a short, useful kitchen handover

The handover should give the arriving team enough information to start safely and identify unfinished work. It can be a paper form or a reliable electronic record. These suggested fields are an operational aid; they do not replace the plan’s required records.

On a small screen, swipe sideways to view all columns.

Keep the handover concise and link it to the detailed records. For example, refer to the chiller log and a maintenance report rather than rewriting them in every booking sheet. If there is a problem, use an active message or call to the responsible person as well as the record. A note nobody has seen is a weak handover.

A shared-kitchen handover example

Illustrative scenario: A morning food producer and an afternoon caterer operate as separate businesses in the same kitchen. Their registration arrangements have already been confirmed. They share a mixer, bench and chiller, while keeping identifiable stock and their own production records.

The morning team records completion of the agreed clean, identifies the equipment used and leaves a handover referring to the day’s chiller check. The afternoon team checks that the bench and mixer are ready for its work and reviews any relevant storage issues before bringing in food.

During that check, the caterer finds food residue on a mixer attachment. It keeps the attachment out of use, arranges the required clean and records the finding and action. The site manager and morning operator review why the original completion check missed it. The afternoon team does not simply sign “clean” to avoid delaying the booking.

The handover identifies the interface problem. Each operator retains evidence relevant to its responsibilities, while the kitchen manager keeps the site action record. The useful result is a corrected control and an understandable record trail.

Keep records accessible and retain them

Agree where shared records are stored and who can retrieve them during a booking, an incident or verification. Access should not depend on one person’s phone or a folder that disappears when a tenant leaves.

For FCP businesses, regulation 37 on the quality and availability of records requires records to be readable, accurate, complete and appropriately dated or versioned. Activity records identify the date, time where appropriate, result and the person doing the work. Relevant people must be able to access them.

Required records for FCP businesses must be kept for at least four years after creation under regulation 36. Regulation 81 also sets at least four years for required records of National Programme businesses. Apply these rules to the relevant required records; do not assume every casual booking message is automatically a statutory food record.

• Before leaving the site: arrange copies or reliable continuing access to shared evidence your business needs.
• For electronic records: define access permissions, backups and how records can be retrieved if a staff member leaves.
• For corrections: keep changes understandable and truthful. Never invent a missing historical temperature or cleaning check.

MPI’s Food Safety Toolkit record blanks can help organise evidence. Simply Safe & Suitable also allows suitable records in other formats. Choose a system staff can complete correctly and retrieve when needed.

Common shared-kitchen record mistakes

• “The kitchen owner keeps everything.” Identify the records your operator needs and verify you can actually obtain them.
• “Everyone cleans.” Assign the task, completion check and backup person.
• “The fridge display was fine.” Use the monitoring method required by the applicable plan and identify what was measured.
• “The next user will fix it.” State the immediate control and confirm a named person has accepted follow-up.
• “We filled the missing checks in later.” Record the gap honestly and assess its effect on food safety.
• “The site induction covers every business.” Train people for their actual tasks, food processes and responsibilities.

Our guide to food safety training for staff explains why competence matters alongside records. Check the training requirements in the applicable plan, including any distinction for sole operators.

Before your next kitchen booking

• Confirm the operator, activities, premises and registered scope for your business.
• Read the plan or programme requirements applying to your actual work.
• Agree named responsibilities for cleaning, shared equipment checks and site services.
• Identify storage areas and controls for raw, ready-to-eat and allergen-containing food.
• Set up the required records and a practical changeover process.
• Test that you can retrieve shared records and receive urgent issue notifications.
• Brief the team, including relief staff, and check they understand the arrangements.

Frequently asked questions

Does the kitchen owner’s registration cover my business?

Do not assume it does. Confirm the operator, activities and registration scope with the relevant registration authority. The fact that the premises are already used by another food business does not settle your arrangements.

Can several businesses use the same chiller log?

A shared log can support the record system where it provides the information required for each operator’s activities and is accessible to the relevant people. Check its method and scope against the applicable plan. It does not replace separate batch or process records that are also required.

Who cleans between kitchen bookings?

Agree who completes the clean and who checks readiness before the next operation. Each operator must ensure the controls relevant to its food are followed. A useful handover identifies areas, equipment, completion and exceptions.

Is a signed handover sheet an MPI requirement?

This article recommends a handover sheet as a practical control. It does not claim that MPI prescribes this exact form for every shared kitchen. Required controls and records come from the law and the applicable plan or programme.

Do I need special record-keeping software?

No particular software is required by the Simply Safe & Suitable examples discussed here. Paper or suitable electronic records can work. Accuracy, completeness, accessibility and retention matter more than the product used.

What happens to shared records when I stop renting the kitchen?

Arrange to retain copies or reliable access to required evidence for the applicable retention period. Make this part of the agreement before the booking relationship ends, rather than waiting until a verifier asks for it.

Get help with workable records and procedures

AFVA’s food safety and quality consulting can help you review procedures, records and staff responsibilities. Our food safety audit preparation support can also help organise evidence and identify gaps before a review.

Agree the service scope and any independence requirements before engagement. Consulting support does not transfer the operator’s responsibility or guarantee a verification outcome.

General information only. Requirements depend on your complete activities, products, processes and registered arrangements. The template examples above apply to relevant Simply Safe & Suitable businesses; use the requirements that apply to your own operation and confirm uncertain arrangements with the registration authority or verifier.