Food Consultant Project Changes NZ: Agree Extra Work Before It Starts

Food consultant project changes can begin with a small request: another product, a different site, an extra training session or new information that changes the review. The useful question is what that request does to the agreed work, price, evidence and completion date.

This guide helps New Zealand food businesses manage changes during an assignment. It focuses on recording and agreeing the next piece of work. For the initial buying decision, use our guides to choosing a food safety consultant and food safety consultant costs and quote comparisons.

Spot food consultant project changes against the agreed scope

Keep the current proposal, accepted scope and agreed revisions together. Identify the products, processes, sites, documents, review rounds and outputs they cover. Compare a new request with that baseline before deciding it is included or additional.

A correction to an agreed deliverable, a clarification and a new assignment can look similar in an email. Ask the consultant to explain the distinction against the actual agreement. This article does not determine whether a particular correction attracts a fee or what either party is contractually entitled to.

These are management prompts, not rules assigning charges. If the scope is unclear, resolve that uncertainty in writing. Avoid allowing a string of brief messages to become the only description of what has been commissioned.

Agree the response before extra work starts

AFVA recommends a short sequence proportionate to the change. Use the actual agreement for approval and payment arrangements; there is no universal change fee or standard review period stated here.

1. Describe the request. State what has changed, why and which part of the assignment it affects. Attach the current evidence rather than only summarising it.
2. Ask for the impact. Identify additional review, revised outputs, missing information, site access, specialist input and work that would be deferred or removed.
3. Confirm cost and timing. Ask whether the price is fixed, estimated or time-based; clarify GST, travel, external charges and how any further increase is agreed. Separate requested dates from confirmed commitments.
4. Record the decision. Name who may approve work for the business and the consultant, what they approved and any conditions. An acknowledgement of an email need not be an approval.
5. Update the working plan. Link the approved change to the current scope, deliverables and task list. Tell affected staff which versions and dates now apply.

A request can be declined, deferred or narrowed. For example, agree an initial review to define the evidence gap before deciding on a larger project. If an item remains undecided, keep its status visible rather than treating silence as consent.

Use a short project change record

The following fields are AFVA’s recommended project-management aid. They are not a mandatory MPI form, a food-safety validation record or a replacement for your contract. One indexed email or shared record may be enough if the relevant people can retrieve the decision.

• Reference and date: a change identifier, requester and link to the existing assignment.
• Current baseline: the scope or proposal version and the affected deliverable references.
• Requested change: the specific addition, removal or revision and its reason.
• Evidence and assumptions: source documents, versions, information still missing and who supplies it.
• Impact: revised outputs, work limits, responsibilities, review steps and dependencies.
• Commercial details: agreed price basis, inclusions, exclusions and authority for further work.
• Dates: proposed and agreed dates, plus any external deadline or appointment still unconfirmed.
• Decision: approved, declined, deferred or awaiting information; decision-makers, date and conditions.
• Follow-through: working documents updated, people informed and remaining actions assigned.

Retain the reason and decision when a request is withdrawn or superseded. Correct the working record openly if the situation changes again. Do not alter an earlier decision date to make the approval appear to have preceded work that had already started.

Apply the record to a practical example

Hypothetical example: A one-site food manufacturer commissions a review of the receiving procedure and a revised receiving form. During the assignment, the business asks the consultant to include dispatch checks as well. This is an illustration, not an AFVA client account or a quote.

After the information arrives, the parties can record an accepted proposal or another decision. The business reviewer can then track the revised outputs against CR01. A request marked “sent” or information marked “received” should not automatically become “approved” or “completed”.

At completion, carry accepted changes into the final deliverable list. Use the food consultant project handover checklist to separate delivery, business review, open actions and implementation.

Check whether the food business is changing too

A change to the consulting assignment and a change to the food operation are separate questions. Adding a document review may only alter the project. Introducing a process, product or site may also need a review of the applicable food-safety and registration arrangements.

MPI’s guidance on changing or growing a food business says people planning business changes need to inform their registration authority. Check the route applying to your operation with that authority; the project record should identify who will obtain the answer and retain it. Do not use this article to decide whether a particular amendment requires evaluation or approval.

Keep advisory and formal assessment roles clear. MPI’s guidance on hiring a food consultant explains that consultancy is optional, does not guarantee registration or a successful verification, and a consultant who writes a plan or programme cannot evaluate or verify what they created. An expanded consulting scope does not remove those boundaries.

Avoid common change-control mistakes

• “Just add it” without a revised scope. Ask what the request changes and retain the answer before commissioning it.
• Only the total price is updated. Also identify outputs, exclusions, review responsibilities and dependencies.
• A preferred launch date becomes a promise. Confirm the work and external decisions that need to happen first.
• New evidence is filed without review. Assign someone to decide which earlier advice or documents it affects.
• Project approval is treated as approval to operate. Confirm any separate food-safety, registration or assessment steps through the correct route.
• Staff use competing versions. Identify the current working instructions and control superseded copies under the business’s arrangements.

Discuss the changed scope with AFVA

AFVA’s published consulting service includes document and record review, practical recommendations, corrective-action support, staff guidance and follow-up. Send the existing scope, the specific new request and the evidence that prompted it. Explain who can make decisions for your business and any confirmed deadline.

AFVA can discuss the support appropriate to the situation and the next step. Any formal evaluation or verification needs its own applicable recognition, scope and independence arrangements. No particular fee, availability or completion date is promised in this guide.

Bring the scope, request and decision together

Start with the current assignment and one specific request. Record what changes, who decides and what remains unresolved. Update the working plan after agreement so everyone can identify the same outputs, responsibilities and next step.

General information only: This recommended workflow does not determine contractual rights or establish food safety, compliance or a formal assessment outcome. Requirements depend on the complete food activities and applicable system. Confirm the arrangements for your business and obtain legal advice for contract disputes.