RMP Significant Changes NZ: What to Review Before Implementation

An RMP significant-change review starts with a comparison: what does the registered programme cover now, and what would be different after the change? A new process, altered site arrangement or revised operating method can affect more than the paragraph being edited.

This guide is for operators and quality teams changing an existing Risk Management Programme under the Animal Products Act. It helps you organise the facts, identify the amendment question and commission a focused review. It does not classify a particular project or provide a universal approval timetable. The broader RMP consultant guide covers initial pathway and programme-development questions.

RMP significant changes: assess the effect, not the project label

MPI’s guidance on updating an RMP distinguishes minor and significant amendments. Its risk-based indication of significance is a change introducing new risk factors or potentially adversely affecting existing ones. A project called a “small upgrade” or “like-for-like replacement” still needs to be examined against the actual programme and operation.

Start with the registered scope and current controlled RMP, including relevant conditions and earlier amendments. Describe the change in ordinary operational terms before deciding which form to use. Identify the products, processes, premises and market arrangements affected, and who has information needed to assess them.

The result may be a clear route, a request for further evidence or a question for MPI or an appropriately recognised evaluator. Record the reasoning and advice received. A name chosen for the project is not a substitute for explaining how it affects the programme.

Prepare a clear before-and-after description

A useful change description allows someone outside the project team to understand what will happen. Do not send only a marked-up procedure if the physical operation, materials or responsibilities are also changing. Include the current arrangement so the reviewer can identify what remains the same.

These are review prompts, not a list declaring every equipment, layout or staffing change significant. A change can affect several areas at once. State what is known, what is proposed and what is not yet decided; uncertainty about a design should not disappear when it is copied into an application.

Review the controls and evidence affected by the proposal

Connect the proposed work to the existing programme. Identify the parts of the hazard analysis, supporting systems, procedures, monitoring and records that rely on the old arrangement. Consider how a change in one step could affect earlier or later steps rather than reviewing that step in isolation.

• Scope and product description: identify the existing products and activities covered and the proposed difference.
• Process and premises: provide current and proposed flow information, equipment details and site information relevant to the question.
• Hazards and controls: explain the assumptions behind existing controls and what the new arrangement could change.
• Supporting evidence: identify relevant validation or other technical evidence, its scope and any gap needing specialist assessment.
• Implementation: list affected procedures, monitoring forms, responsibilities and staff instructions.
• Verification history: include relevant findings or earlier advice that affects the proposed change.

This recommended evidence index is not a mandatory list for every amendment. Ask the reviewer which information is needed for the specific decision. Existing evidence may remain relevant, need a documented explanation of its applicability or leave a gap. Do not assume that a result for the old process demonstrates the performance of a materially different one.

Where products are intended for export, discuss proposed amendments with your verifier as MPI recommends, so market-access questions can be identified. This does not establish that an RMP amendment alone resolves every export eligibility or customer requirement.

Keep minor changes, evaluation, registration and verification distinct

A minor classification is not an instruction to ignore document control or notification. MPI lists specific administrative changes and their forms, including registration-detail and day-to-day-manager changes. Use its current guidance to confirm the route for the actual change rather than assuming all minor amendments require the same external step.

For significant amendments, MPI describes evaluation and registration, using the current AP6 application and clearly identified changes with the relevant evaluation report. The assessment needs to consider the affected parts of the RMP. Confirm the requirements applying to your particular programme, including any formally applicable exception or condition, with the appropriate parties.

• Operator and adviser: organise the facts, assess gaps and develop the proposed documents and evidence. Advisory work does not make MPI’s registration decision.
• Recognised evaluator: undertakes the formal evaluation required for the amendment within the applicable recognised scope.
• MPI: handles the amendment registration decision and any relevant conditions or effective date.
• Verifying agency: has a separate role concerning the operation of the programme. Agree how the change will be communicated and reflected in verification arrangements.

Confirm suitable recognition, scope and independence before commissioning a formal service. A routine verification booking does not demonstrate that a proposed amendment has been evaluated or registered. Similarly, a consultant’s completed draft is not an evaluator’s report.

Resolve the implementation point before the project runs ahead

Section 25 of the Animal Products Act 1999 requires the operator to amend and apply for registration before an event known in advance that brings the programme within that section. It also provides for MPI to specify when an amendment relating to a future event takes effect. Keep the planned operational change and the actual regulatory status distinguishable.

Build the required advice, evidence, evaluation, application and decision steps into the project plan. Confirm with the appropriate parties what can proceed, what remains conditional and what must be resolved before the changed operation is used. Do not describe “application submitted” as “amendment registered”, or invent a standard approval period to fit an equipment delivery date.

When the route and conditions are clear, control the final version used by the business. Identify the approved documents and instructions, the person authorising implementation, staff guidance and the checks needed after the change. Preserve the record of the actual decision and date rather than backdating a change log.

Example: moving a packing step within an existing operation

Suppose a registered animal-product operation proposes moving a packing step to another area. This is a hypothetical review example, not a classification or an AFVA case. A useful brief compares the existing and proposed flows, products, area boundaries, separation arrangements and relevant controls.

The reviewer can then identify the evidence and amendment question. The description “same site” cannot answer every question about premises scope or hazard control, while a layout change alone should not be presented here as automatically significant. Record the actual assessment and required route for that proposal.

Ask AFVA about a bounded change-review engagement

AFVA’s RMP support includes documentation and gap review, procedures, records and readiness support. Explain that you need help assessing and organising a proposed change. Agree the specific work and any need for an external recognised evaluator, verifier or technical specialist; do not assume AFVA is providing every formal function.

• Current registration and controlled RMP, relevant conditions and earlier amendment records.
• A short before-and-after description, with the process or premises information needed to understand it.
• Affected documents, existing technical evidence and the questions or gaps already identified.
• Current verifier/evaluator contacts where relevant, advice received and the actual project target date.
• The output needed: a documented gap review, an evidence plan, assistance revising documents or coordination of the next review step.

A focused first stage can identify what is ready and what remains unresolved. Confirm deliverables, exclusions and responsibilities before commissioning further work. Advice supports the operator’s decisions; it does not guarantee registration, a particular verification outcome or an implementation date.

Avoid shortcuts that obscure the amendment decision

• Calling a proposal minor because it is inexpensive or stays within the same building.
• Reviewing a new machine while overlooking changed flow, procedures or control assumptions.
• Reusing old evidence without checking whether its conditions still apply.
• Treating a submitted application, evaluation report and registration decision as interchangeable.
• Training staff from a draft while the final route, conditions or instructions remain unclear.

Frequently asked questions about RMP change reviews

Make the proposed change easy to assess

Bring the current programme, the proposed difference and the unresolved question together. That gives the initial review a practical purpose and helps keep project commitments aligned with the actual amendment route.

General information only: RMP amendment requirements depend on the complete operation, products, processes, premises, programme and intended markets. Confirm the current requirements and any conditions with MPI and appropriately recognised providers. This article does not classify a particular amendment, grant approval or authorise changed processing.