ISO 22000 clause 8.5.4.5: show that the hazard-control plan is implemented
ISO 22000 clause 8.5.4.5 requires the organisation to implement and maintain the hazard-control plan and retain documented evidence of implementation. This is the bridge from a technically prepared plan to actual work. The question is whether the measures, monitoring and response arrangements operate as intended, including when normal conditions are challenged.
What clause 8.5.4.5 requires in practice
The last part of clause 8.5.4 is short and demanding. The organisation implements and maintains the hazard control plan, and keeps evidence of implementation as documented information. It is not enough for the plan to be approved, filed and technically sound. People must be carrying out the monitoring, interpreting results, taking the specified actions and keeping the records, and the organisation must be able to show that. The evidence is typically the stream of monitoring results and related actions, together with the signs that competent people evaluated them. The clause also expects maintenance: when conditions change, the plan in use must change with them. Put simply, the clause requires proof that the plan is lived, not just approved, which an auditor will test by observation as well as by records.
Prepare the operating system around the plan
Ensure that personnel have current instructions, suitable equipment and appropriate competence. Responsibilities and authorities should be clear before routine use. A plan can be technically correct while implementation fails because nobody has assigned evaluation of its results.
Check that the necessary forms or systems can capture the information the plan requires. A record should connect a result with the relevant activity and product sufficiently to support later decisions. Do not let the limitations of an old form determine what evidence is collected.
Confirm that the validation and monitoring arrangements supporting the plan are ready. Implementation should not be used as an informal experiment to find out whether an unvalidated measure might work.
Look at work under representative conditions
Observe how the plan is used across relevant products, shifts and operating arrangements. Ask personnel to explain the criterion and response. Compare their actions with the current plan and the evidence retained.
A sample can include an ordinary acceptable result and an event where monitoring was missed, uncertain or outside criteria. The second sample often reveals whether escalation, product identification and authority are actually understood.
Use findings to improve the arrangement. If personnel cannot follow the plan reliably, investigate whether the issue concerns instructions, resources, competence or the plan itself rather than assuming the answer is always more signatures.
Maintain implementation through change
Keep the plan aligned with changes in product, process, equipment and responsibility. Review related instructions and records together. An updated technical plan that has not reached the workstation is not fully implemented.
Connect implementation evidence with verification. Monitoring records show particular operating results; verification examines whether the plan is implemented and effective through the planned activities.
Why clause 8.5.4.5 matters to the business
Many failures in food safety happen not because the plan was wrong but because it was never fully put into practice. A form filled in for the sake of the record, a procedure that never reached the night shift, or an instrument nobody reads can all make a good plan worthless. Customers who audit a site test exactly this: they ask operators to explain what they do. Strong implementation therefore protects reputation and supplies the proof that the investment in analysis and validation is actually paying off.
How to implement clause 8.5.4.5
Treat implementation as a managed rollout followed by regular checks that the plan still reflects real work. Be ready to simplify the plan if the review shows people cannot follow it, because a smaller workable arrangement is better than a complete one that is quietly ignored.
- Put current instructions, forms and equipment at each point of use, and remove old versions.
- Confirm that operators and evaluators understand the limit or criterion, the monitoring and the response, and that they have the authority they need.
- Observe real production on different shifts and products, asking people to explain what they would do if a result were unacceptable.
- Check a sample of records for completeness, timing, evaluation and follow-up, including at least one case where something went wrong.
- Fix causes when practice differs from the plan, which may mean changing instructions, resources or the plan itself.
- Retain records under document control and protect them from alteration.
- Use verification results to decide where implementation needs another look.
Illustrative food-manufacturing example
A manufacturer introduces a revised CCP monitoring arrangement. A start-up review confirms that the operator uses the correct method, records the result against the relevant production interval and knows the escalation route. The evaluator can explain how an unacceptable result would trigger product control.
A later night-shift sample finds that the revised instruction was not available there. The organisation addresses distribution and checks whether earlier work needs evaluation, rather than declaring implementation complete from the daytime trial.
Illustrative catering example
A caterer implements an OPRP with an observable criterion. Supervisors compare actual observations with the supporting instruction and examine how failed criteria were handled. One completed form contains ticks entered after service without a reliable basis.
The organisation investigates the practice and changes the arrangement so monitoring occurs at the required time. The record is evidence only when it represents the activity it claims to document.
Evidence and common weaknesses
Retain documented evidence of implementation, including relevant monitoring and action records. Keep it usable and protected under documented-information control. Evidence should allow a reviewer to follow what was done, when and with what result.
Common weaknesses include blank forms presented as records, backfilled entries, implementation checked on only one shift and old plans remaining at workstations. Another is failing to act when implementation evidence reveals that the operating arrangement is impractical.
The plan overview explains the content that must become practice. Implementation is sustained work, not a one-time launch event.
Frequently asked questions
Does an approved plan meet this clause?
No. It must be applied and maintained, with retained evidence showing implementation.
Are training records implementation evidence?
They can support readiness and competence, but they do not replace evidence that the control plan actually operates.
Should every shift be considered?
Consider relevant operating variation when evaluating implementation. Do not assume one observed shift represents materially different arrangements.
Check whether the plan survives normal working conditions
Discuss a practical hazard-control implementation review with Sterling. The scope can connect observations, competence and suitable evidence support through Effivity ISO & GRC automation software. Explore HACCP Awareness and the ISO 22000 hub to support the team's next step.