Multi-Site Food Verification NZ: Who Holds Records and Owns Actions?

Multi-site food verification is easier to prepare for when the central team and each site can explain who does the work, where its evidence is kept and who follows up a finding. Shared branding, a common procedure or one contract does not answer those practical questions.

This guide focuses on responsibility and evidence handovers for New Zealand food businesses operating under the Food Act. It does not determine whether your sites qualify for one registration, a sampling arrangement, fewer visits or lower fees.

Start multi-site food verification preparation with the actual sites and scope

Build a current list of locations, legal operators, food activities and registrations. Include the functions performed centrally as well as what happens at each site. Identify differences in products, processes, customers or operating arrangements instead of assuming all branches are identical.

MPI’s food business registration guidance explains that the registration authority depends on the plan or programme, business type and location. For National Programme businesses based in more than one council area, its guidance describes separate council registrations or registration together with MPI. Confirm the applicable arrangement for your actual operation; a shared name does not establish it.

Keep copies of the current registration information and any relevant scope correspondence with the site list. Ask the registration authority and verifier to resolve discrepancies before relying on an old group chart.

Assign the central role and the site role separately

Use the following cards as examples to adapt. They are a planning aid, not a prescribed legal division of responsibilities. Put actual names and deputies against the work and identify who can authorise resources or resolve a disagreement.

MPI’s practice note explains why central arrangements need to work in practice at individual sites. A head office procedure or contract should connect to what local staff can show and explain. Confirm the assessment of central functions with the verifier rather than assuming head office is automatically included or excluded.

Map evidence to the site, activity and owner

Create a short index showing the topic, relevant sites, responsible person, evidence location and access route. This is AFVA’s organisational recommendation. The applicable programme or plan determines what records are actually required.

• Site or shared scope: can someone tell whether a document applies to one address, several sites or the whole business?
• Activity or asset: does the record identify the work, delivery, product, equipment or decision it supports?
• Current instruction and genuine record: distinguish the approved procedure, unused template and completed evidence.
• Access and cover: can the site manager and authorised deputy retrieve the relevant information when the usual coordinator is away?
• Report and follow-up: can the action owner find the original finding, submission and assessor’s response?

A central file location can be useful without being the only working location. What matters for preparation is a clear route to the correct evidence and an explanation of its limits. Avoid copying the same record into several folders without identifying which is the controlled or original version.

For sites confirmed as NP2, our National Programme 2 records guide addresses the separate question of which evidence may apply. Do not impose one programme’s record list on every location merely to make the group spreadsheet consistent.

Test the index with one shared item and one local item. Ask someone other than the usual file owner to retrieve them. Record the genuine access or evidence gaps and assign the next step; do not recreate a missed check to complete the folder.

Give findings an owner and keep their status clear

For each finding, keep its reference, affected site or function, required response, actual date, owner and evidence location together. Identify whether the next task is local work, a central decision, evidence submission or a response from the assessor.

1. Receive and clarify: retain the original finding and confirm what response or evidence is expected.
2. Assign: name the person doing the work and the person coordinating any central dependency.
3. Complete and check: retain genuine evidence of the action and any applicable follow-up check.
4. Communicate: send the agreed response through the agreed channel and keep the submission history.
5. Confirm status: record the assessor’s response, remaining conditions and next task.

A site can finish its assigned task while the wider response remains open. Equally, a central document update does not show that every affected site has implemented it. Where the same issue may involve other sites, arrange a proportionate review of the shared cause and local implications.

Use the dates in the actual report and applicable requirements. If work may miss a date, contact the relevant provider promptly and clarify the permitted next step. A change of coordinator or an unanswered email is not confirmation that the required date has changed.

Example: a shared contract and a report for only one site

Consider a hypothetical business with two sites and a centrally arranged equipment-service contract. Head office receives a service report for Site A and marks the group task complete. Site B cannot find a report for its own equipment.

The coordination question is whether the report supports the work claimed at each site. The central owner checks the contractor’s records and the agreed scope. Each local manager confirms the relevant address and equipment references, and the unresolved Site B task stays visible until its actual status is established.

This example illustrates evidence ownership, not a finding from an AFVA client or a decision that equipment or food is safe. A contract, invoice or another site’s report does not by itself demonstrate that the local work occurred.

Send the verifier a brief that exposes differences

Before requesting a proposal or coordinating the next assessment, prepare:

• The site list, legal operator details, current registrations and contact at each location.
• Food activities at each site, including meaningful differences and any changes.
• Central functions such as document control, purchasing, training or contracted services, where applicable.
• The current provider arrangements, relevant previous reports and open findings.
• Known required dates, practical availability and who can explain local and central work.
• The coordination question: scope, evidence access, communication, handover between agencies or another specific issue.

Ask the provider to confirm the appropriate recognised scope, responsibilities, evidence access, reporting route and proposed arrangements. If more than one agency is involved, clarify who coordinates which parts and how information will be shared through appropriate channels.

Our guide to choosing a Food Act verifier covers provider-selection questions. Ask for a quote for the actual work; central coordination alone does not establish lower fees or reduced assessment time.

MPI’s National Programme guidance says significant changes to the person running the business, scope, verification agency or site address details need to be notified to the registration authority. Keep a named owner for checking and communicating relevant changes, using the requirements for your actual registration.

Common coordination mistakes to avoid

• Using the brand as the scope: confirm the actual operator, sites and activities.
• Assuming one system means identical work: identify local differences and their implications.
• Equating a shared contract with completed service: connect the evidence to the actual site and work.
• Closing a group task too early: distinguish local completion, implementation elsewhere and assessor acceptance.
• Leaving access with one person: test cover and retrieval before the assessment.
• Promising the assessment arrangement internally: confirm it with the provider and relevant authority first.

Confirm the appropriate AFVA service before booking

AFVA provides National Programme verification and preparation support within recognised scope. Send the site list, activities, current registration arrangements and the coordination issue you need resolved.

The appropriate engagement depends on the actual operation, scope and independence requirements. Advisory preparation and formal verification need clear roles. A review of your responsibility map does not approve a registration arrangement, determine the assessment outcome or replace the verifier’s decisions.

Frequently asked questions about multi-site responsibilities

Start with one handover you can test

Choose one shared service or open finding and follow it from the central owner to the relevant site evidence and next decision. Any missing connection gives the team a specific task to resolve before agreeing the assessment arrangements.

General information only: Requirements depend on the actual operators, food activities, sites, plan or programme and registration arrangements. This organisational guide does not determine registration, sampling, verification frequency or outcome. Confirm the applicable requirements with the relevant authority and verifier.