HACCP Validation Evidence NZ: Build a Control Evidence File

A HACCP validation evidence file connects one control in your existing plan to its technical support, the conditions that support covers, and the records showing how the control is operated and checked. It gives a reviewer a route through the evidence, including the questions that remain open.

This guide is for New Zealand food manufacturers and quality teams organising that file. You do not need a proposed process change to use it. The worksheet below is a suggested administrative tool; it does not supply a hazard analysis, critical limits or a validation conclusion for your food.

HACCP validation evidence: start with one existing control

Choose a control that is already identified in the current HACCP study. Record its identifier, process step, relevant product or product group, hazard reference, intended outcome and the plan version. Use the actual study’s classification; do not turn every production check into a critical control point (CCP) merely to complete this file.

Write one review question, such as: “Does the technical information held for control C-01 cover our current product and operating arrangement?” Also state what the file will not decide. A folder review may identify a need for specialist work without establishing that the control is effective.

For the wider development sequence, use the guide to developing a HACCP plan. Where a proposed change affects the evidence, use the HACCP change-review guide for that separate assessment. This article concentrates on making the support for an existing control traceable.

Keep three kinds of evidence identifiable

• Validation support: the technical basis for the control’s capability to achieve the specified outcome.
• Monitoring records: observations or measurements of the control during operation.
• Verification records: additional checks of implementation and whether the system works as intended.

These distinctions follow Codex’s General Principles of Food Hygiene. Codex is international technical guidance; use it alongside the requirements applying to your New Zealand operation. The internal checks discussed here do not replace a separate regulatory or scheme assessment that may apply.

Build an index that explains why each record is held

We recommend a short index with stable evidence references. The supporting documents can stay in their controlled locations; the index should let another reviewer find the correct version and understand what question it answers. Avoid maintaining several uncontrolled copies of the same report.

FAO’s HACCP record-keeping guidance says documentation should suit the operation and support checks that controls are maintained. Records can be electronic or paper-based. A useful file therefore needs clear connections, rather than an unnecessarily complicated format.

1. Control record: link the current hazard analysis, relevant control decision and approved operating procedure.
2. Technical basis: identify the complete report, authoritative guidance or other source relied on, with its date, version and relevant section.
3. Applicability assessment: explain which actual product and operating conditions were compared and retain the information used.
4. Operational evidence: link genuine monitoring, instrument checks and relevant deviation or corrective-action records.
5. Review and decisions: record who assessed the evidence, what was concluded, qualifications, open actions and the evidence used to close them.

For each item, add a brief “supports” statement and a “does not establish” statement where needed. For example, a calibration record concerns instrument performance; it does not, by itself, provide the scientific basis for a food treatment. Keep original qualifications attached to the source instead of copying only its favourable conclusion.

Record why the technical evidence applies to this control

FAO’s validation and verification guidance describes evidence such as scientific literature, suitable models, studies and authoritative guidance, and stresses applicability to the operation and product. Its guidance on validated critical limits also recognises that credible existing information may be usable. A new study is not automatically the answer to every filing gap.

Ask the technical reviewer to identify the conditions that matter for the particular evidence. They may concern the food, hazard, equipment, loading or other operating conditions. Do not assume this short list covers every parameter. Record the relevant conditions in the source, the corresponding actual information, the comparison and any limitation.

A similar product name or equipment model is only a starting point. If the report does not describe a condition needed for the comparison, record the uncertainty and obtain the missing information or appropriate technical assessment. The person assembling the file should not extend a study’s scope by assumption.

Preserve the difference between a source being available and its applicability being assessed. Identify the reviewer and the basis for the decision. A signed index or a recently renamed folder does not supply missing technical evidence.

Worked example: one existing control evidence register

Hypothetical administrative example: a manufacturer is organising evidence for an existing cooking control, C-01, for Product A on line L-01. No process change is proposed. It holds a technical report, but the file does not yet explain whether the current loading arrangement is covered. The identifiers below are invented for the worksheet; they are not an AFVA case or a safe processing specification.

The example records a genuine unresolved question in its fictional scenario. It deliberately supplies no operating values, treatment target, test result or production-release decision. Replace the structure with your actual controlled references and competent assessment.

On a small screen, swipe sideways to view all columns. Keyboard users can focus the table region to scroll horizontally.

Assign technical review, operation and verification clearly

File administration, technical assessment and operational responsibility are separate jobs, even when a small team combines some roles. We recommend naming the document owner, the person who can assess the relevant technical evidence, the person responsible for implementing decisions, and the verification reviewer. Obtain suitable specialist expertise where the team cannot resolve the technical question.

FAO’s monitoring guidance explains the need for appropriate methods, trained personnel and review by someone with authority to act on deviations. Link those arrangements from the file to the actual procedure; the register should not create a second, inconsistent set of operating instructions.

Codex section 19.11.2 recommends verification by someone other than the person responsible for monitoring and corrective actions. It also addresses external expertise where an activity cannot be performed in-house. Record the review arrangement and its scope. Do not label an internal evidence-file review a recognised regulatory verification or assume it fulfils a separate certification requirement.

When an evidence gap is found, specify the unanswered question, responsible person, agreed review date and evidence needed for closure. If a food safety concern or loss of control is identified, follow the applicable operating and corrective-action arrangements promptly. Assembling the file must not delay that response.

Checklist before closing an evidence-file action

1. The control, product scope and current document versions are identifiable.
2. The full relevant technical source can be retrieved, including qualifications and necessary appendices.
3. Applicability conclusions identify the actual information compared and the competent reviewer.
4. Monitoring, instrument and verification references lead to the relevant real records.
5. Missing evidence and unresolved assumptions are visible, with owners and agreed next steps.
6. Closure records show what was obtained, what was assessed and who made the decision.
7. Any operating-document changes are handled through the business’s document-control process.

These are recommended filing and review checks, not an official MPI form or a universal audit checklist. Keep the detail proportionate to the control and applicable requirements. Retain earlier conclusions and their context so a later reviewer can understand why the current decision was made.

Common evidence-file mistakes

• A bibliography without an applicability assessment: explain what each relevant source supports for the actual operation.
• Blank forms offered as operating evidence: distinguish the instruction from records of work actually performed.
• A green status without a reason: link the assessment and closure evidence behind the decision.
• Missing records filled retrospectively: preserve the gap and the genuine information available.
• Unclear scope of sign-off: state whether the person checked filing, technical applicability, implementation or a separate formal requirement.

Ask AFVA to review a defined evidence gap

AFVA’s published HACCP consulting service includes identifying validation evidence needs, reviewing existing validation information, monitoring and corrective-action records, internal HACCP checks, and records or documentation support. Send the control reference, current plan section, evidence index and precise unresolved question.

Agree the scope of document review, site information, technical assessment and any further specialist work. Where analysis is needed, it is performed by an appropriate external laboratory. Consulting support does not supply certification, formal approval or a guaranteed assessment outcome. The HACCP consultant scope guide helps with that separate commissioning decision.

Frequently asked questions

Start with the control and the unanswered question

Select one existing control, gather its current references and identify the conclusion that needs support. Contact AFVA about a focused HACCP evidence review with that question and the information already available.

General information only. This suggested evidence-file structure does not validate a process, prescribe critical limits, approve a plan or authorise production or product release. Technical and formal assessment requirements depend on the actual food, hazards, controls and applicable New Zealand programme or scheme. Confirm the appropriate requirements and specialist responsibilities for your operation.