HACCP Flow Diagrams NZ: Recording Factory-Floor Findings

When a process-flow review produces handwritten notes, operator explanations and proposed diagram changes, put them into a record that another person can follow. This article offers a practical administrative log for those findings.

The focus is deliberately narrow: identifying the diagram examined, preserving the evidence behind each finding and keeping follow-up visible. It does not explain how to construct or formally confirm a HACCP flow diagram, determine the required coverage of that work, or decide when technical confirmation is complete.

Keep the record's purpose clear

Use the log to organise findings generated through your business's process-flow review. Keep the technical procedure, its coverage requirements and the decision about completion separate from this administrative worksheet.

FSANZ's guidance on shaping food safety culture identifies two-way communication, staff contributions and systems for recording and assessing information as useful practices. That supports clear information handling; it does not establish a HACCP flow-confirmation method or prescribe this log.

For the broader subject, see AFVA's guide to developing a HACCP plan for a New Zealand food business. Here, the reader's task is narrower: making existing findings understandable and traceable.

Identify the HACCP flow diagram and source information

We recommend a short header so a reviewer can identify the documents behind the log. Adapt these fields to your business's record system:

• Review reference: the identifier used for the relevant review or set of findings.
• Diagram reference: its title, identifier, version and date, where available.
• Named subject: the product, line or operation identified in the source record. Do not expand that description beyond what the record supports.
• People and dates: who supplied the finding, who entered it and the relevant dates.
• Evidence reference: the original note, document or other record supporting the entry.
• Record limitations: information that is missing, unclear or still awaiting a response.

Keep the original note identifiable. If someone later clarifies it, record the clarification and its source rather than silently rewriting an uncertain statement as an established fact.

Separate observations, reports and questions

As a recording convention, label what the contributor says they directly observed, what someone reported, and what remains a question. If the source does not make that distinction, ask for clarification rather than choosing the strongest description.

FSANZ's food safety culture overview recognises contributions across a business, including cleaning, maintenance and purchasing. Invite relevant staff contributions without treating every contribution as a direct observation or a technical conclusion.

An illustrative process-flow discrepancy log

The following examples show how to organise incomplete finding records. They are hypothetical administrative examples, not observations from a factory or an AFVA client. They do not identify the checks needed to confirm a flow diagram.

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

Link responses and amendments

We recommend keeping a short trail from the original finding to its response. Before filing the updated record, check that:

• Each finding has a unique reference.
• The original information and its contributor remain identifiable.
• Open actions have a named owner and a follow-up date.
• Responses identify their supporting information rather than only saying “done”.
• Any diagram amendment identifies the replacement version.
• The record identifies who made the relevant decision and what that decision covers.
• Outstanding questions remain visible after administrative updates.

This is a suggested filing approach, not a statutory retention schedule or a technical acceptance test. Closing an administrative action in this log does not declare a process safe or establish that HACCP confirmation is complete.

Recording mistakes to avoid

• Upgrading the evidence: do not change “reported by the operator” to “observed” without supporting information.
• Losing the examined version: keep the finding linked to the diagram used at the time, even after a replacement is issued.
• Replacing a question with a tick: record the answer and its source.
• Copying the example as completed work: use your own findings and references.
• Confusing an amendment with a technical decision: distinguish the person updating the record from the person making the relevant technical decision.

Frequently asked questions

Can this log confirm a HACCP flow diagram?

No. It is a suggested structure for organising findings. It does not set the technical method, required coverage or completion criteria for flow confirmation. Use the requirements and procedures applying to your business for that work.

What if a finding does not say whether something was observed?

We recommend retaining the original wording and asking its contributor to clarify the evidence. Until then, label the uncertainty rather than presenting the entry as a direct observation.

Is the table an official record form?

No. It is an authored administrative example. Adapt its fields to your existing system without treating it as a complete list of required records.

Does recording a proposed diagram change approve that change?

No approval is supplied by this worksheet. Record the proposal and the relevant decision separately; do not use the example log as permission to change production.

What should we send with a request for help?

For an organised enquiry, we recommend the diagram version, the relevant findings, their source references and a short list of questions. Clearly identify any information that has not yet been checked.

Prepare an AFVA consulting enquiry

AFVA's HACCP consulting service includes process-flow development and confirmation, together with review of relevant documents. To discuss support, prepare the current diagram, existing findings and the questions you want help resolving.

This invitation concerns consulting support only. No combined consulting and recognised verification or evaluation engagement is offered here.

General information only: Requirements depend on the complete food activities, products, processes, locations and sales model. Use current official guidance and confirm the requirements applying to the specific business before relying on a record list. This administrative worksheet does not establish technical flow-confirmation requirements, validate controls or approve production changes.