Food Safety Document Control NZ: Remove Obsolete Procedures

Food safety document control in New Zealand is a practical question: can the person doing the work find and follow the right instruction today? A corrected file on a manager’s laptop does not achieve that if an older printout is still beside the packing line.

This guide explains a manageable replacement-and-check process for cafés, manufacturers, importers and other food businesses. The register and issue log below are recommended working tools, not a compulsory national form or a requirement for every business to operate an ISO-style document system.

Start with your actual food safety plan and responsibilities

Separate a document, which explains what to do, from a record, which shows what happened. A blank cleaning check is a controlled form; its completed entries are records. Replacing the blank form does not justify rewriting or discarding completed evidence.

The FAO’s HACCP documentation and record-keeping guidance supports proportionate systems suited to the operation, using paper or electronic records. The aim is usable information and evidence, not a large manual that nobody can navigate.

For operators using MPI’s Simply Safe & Suitable template Food Control Plan, its Instructions card allows an electronic plan and calls for easy staff access. Follow the applicable plan’s Do and Show sections. Do not treat this article as permission to alter prescribed procedures, add activities outside your scope or bypass an approval or evaluation requirement.

Check your registered plan, programme and any applicable customer or certification requirements before deciding what needs control. For broader context, see our New Zealand food safety compliance guide.

Build a document register that identifies the working copy

Start with documents that direct important work: production instructions, allergen information, cleaning instructions, supplier requirements and monitoring forms. Give each document an owner and an unambiguous identifier. A small business can begin with a short spreadsheet or written list.

On a small screen, swipe sideways to view all columns.

The register should point to the authoritative copy. It should not become another conflicting version. Avoid using a filename such as “final-new-final” as the only control. Test whether another person can identify the same current issue without asking the author.

Replace obsolete procedures at the point of use

1. Confirm what has changed before releasing the instruction

Have an appropriate person check that the proposed wording matches the actual process and relevant food safety controls. A change to a limit, ingredient, allergen control or process may need a wider technical review. Formatting a file or adding a version number does not validate its contents.

2. Find every place people rely on the instruction

Walk through the work area and ask staff to show what they use. Include wall sleeves, folders, drawers, shared drives, downloaded files, tablets and links in staff messages. Check other shifts and off-site teams where relevant. A distribution list built only from the office folder may miss the most important copy.

3. Issue the current copy and withdraw the old working copy

Replace controlled printouts and update the approved digital link. Mark the superseded master clearly as obsolete and move it out of the active area. Where historical copies need retention, restrict them to the archive and keep their identity. Do not leave a visibly obsolete instruction beside production as an informal reference.

4. Explain the operational difference

Tell affected staff what changed, when it takes effect and which action they now perform differently. Ask them to demonstrate or explain the revised task. Record relevant instruction or training, rather than relying on a broadcast email alone. Our food safety training guide explains how to connect learning with practical competence.

5. Check implementation and close the issue

An authorised person should confirm that the correct copy is accessible at each identified location and that staff understand it. Choose follow-up checks appropriate to the risk, shift pattern and nature of the change. A release date is not evidence that implementation occurred.

On a small screen, swipe sideways to view all columns.

What if an obsolete copy is found during production?

First prevent further reliance on the wrong instruction and provide the correct authorised direction. Then establish which issue was used, by whom, during which period and for which work. Compare the meaningful differences; do not assume an old version is harmless because its title is unchanged.

If the difference could affect food safety or suitability, use your applicable deviation and affected-product procedures. Identify potentially affected product, retain relevant records and obtain the technical assessment needed before deciding disposition. Simply replacing the page does not answer whether earlier work was acceptable.

Record why the obsolete copy remained available and correct that route: an overlooked folder, outdated shortcut, poor handover or uncontrolled downloads. Check for the same problem elsewhere. Avoid retrospectively completing records as though the current procedure had always been followed.

Keep digital convenience without losing version control

Use a clear current-documents location with controlled editing access. Let users view the approved issue while limiting who can alter it. Review whether shortcuts, synchronised folders and offline copies update as expected. Decide how staff obtain instructions if a device or connection fails.

Archive superseded issues separately with their dates and change history. Apply the retention requirements relevant to the system: for example, the cited Simply Safe & Suitable plan requires copies of required documents and records for at least four years. Do not turn that scoped example into a retention rule for every food business or every type of information.

The UK Food Standards Agency’s technical guidance on HACCP documentation also raises ownership, access, storage, update and issue controls. It is a useful implementation reference, not New Zealand law. Your own applicable plan and requirements remain the starting point.

A hypothetical replacement exercise and mistakes to avoid

Hypothetical example: a business changes a cleaning work instruction after reviewing a product-specific chemical instruction. The owner approves the revision, replaces the copy at the cleaning station and briefs the evening team. A point-of-use check finds an older copy in a relief-staff folder. That location is added to the distribution list and checked again before the issue is closed. This is an implementation example, not a prescribed chemical method or an AFVA client case.

• Changing the master without checking where staff work.
• Giving a new issue number to technically unreviewed instructions.
• Leaving obsolete files in the ordinary current-documents search results.
• Deleting history before checking retention requirements.
• Recording “staff informed” without checking who was affected and what they understood.

How AFVA can help organise the work

AFVA’s food safety and quality consulting service includes reviewing procedures and records, checking whether they match actual practice and recommending practical improvements. A defined project could review your register, a sample of point-of-use copies and the release process. Consulting supports implementation; it does not itself provide registration, certification or independent verification of the same work.

Frequently asked questions

Choose your next practical step

Choose one important instruction, identify every working copy and trace a revision from approval to point-of-use confirmation. Use that exercise to improve the release process before extending it across the document set.

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 classification, timeframe or record list.