ISO 22000 clause 8.5.1.5.2: confirm flow diagrams against actual work
ISO 22000 clause 8.5.1.5.2 requires the food safety team to confirm the accuracy of flow diagrams on site, update them where appropriate and retain documented information. This is the reality check between a prepared diagram and the process it represents. A signature obtained without examining the operation cannot provide the same basis.
What clause 8.5.1.5.2 requires in practice
After the diagrams are drawn, the food safety team has to go and check them where the work happens. This clause requires on-site confirmation that each flow diagram is accurate, updating of the diagram wherever the check shows a difference, and retention of the result as documented information. It is a verification of the drawing against reality, carried out by the team itself rather than delegated to whoever drew the first version. The point is simple: a diagram that nobody has compared with the shop floor is only an opinion about the process. The outputs are a confirmed, current diagram and a trace of the confirmation, for example which version was checked, what was observed, who took part and what changed as a result.
Follow the flow where the work happens
Take the current diagram into the relevant operating areas and compare it with the actual sequence. Speak with personnel who perform the tasks and examine how materials enter, move, return and leave. Look beyond the main production route.
Pay attention to temporary storage, rework, rejected material, outsourced interfaces and other routes that can be overlooked during drafting. Ask how the process differs for relevant products or circumstances. The purpose is to establish accuracy, not to prove the first drawing was correct.
Plan the confirmation so it can reveal meaningful variation. Depending on the operation, a different shift, seasonal condition or product route may need examination. The standard does not prescribe an identical observation programme for every business.
Investigate differences rather than editing blindly
When the diagram and operation differ, establish which description is accurate and whether the actual arrangement is authorised and suitable. An observed workaround should not automatically become an approved process merely because it is added to the diagram.
Involve the relevant process owner and technical personnel. A difference may need correction in operation, revision of the diagram or a broader review. Keep the decision connected with operational change control.
Consider the implications for hazard analysis. A previously missing step can introduce a new point of exposure or change how an existing hazard behaves. Updating the diagram alone may leave the analysis incomplete.
Retain a useful confirmation record
Preserve the confirmed diagram and appropriate evidence of the confirmation. A practical record can identify the version, scope of the check, participants, differences and resulting actions. These details are a useful method, not a mandatory form specified word for word by the standard.
Make sure open issues remain visible. If a process could not be observed under a relevant condition, record the limitation and arrange an appropriate follow-up rather than presenting the confirmation as more complete than it was.
Why clause 8.5.1.5.2 matters to the business
Processes drift. Capacity is added, a temporary hold becomes routine, a night shift develops its own habits. A diagram that was right when it was drawn can quietly become wrong, and the hazard analysis built on it inherits the error. Confirming on site is the cheapest way to catch this before a customer, an inspector or an incident does. It also builds ownership, because operators see their knowledge used to correct the record. Organisations that check regularly tend to find that change communication gaps surface early, which protects product and reduces the cost of rework to the analysis later.
How to implement clause 8.5.1.5.2
Plan the confirmation as a short, structured walk rather than a signature on a drawing. Keep the effort proportionate: a focused walk on a representative day, repeated when something changes, will tell the team far more than a long annual exercise that nobody feels ownership of.
- Print or display the current version and decide in advance which products, shifts and routes the walk must cover.
- Include the food safety team lead, an operator who knows the area, and technical staff who can judge what is observed.
- Follow the material from receipt to dispatch, looking for temporary storage, rework paths, rejected material and outsourced hand-offs.
- Note every difference between drawing and practice, then decide whether the practice or the drawing needs to change.
- Update the diagram, and ask whether the hazard analysis is affected by what was found.
- Keep the confirmed version with a short record of scope, participants, differences and follow-up actions.
- Set a trigger for repeating the walk, such as a process change, a new line or a complaint pointing to an unexpected route.
Evidence an auditor expects for clause 8.5.1.5.2
An auditor will usually start by asking to see the confirmed diagram and then ask how the team knows it is right. Expect to be asked for the record of the on-site check, showing the version examined, who took part and what was found. The auditor may then walk part of the process with you, comparing it with the drawing, and may talk to operators about whether they have been consulted. Evidence of updated diagrams after changes, minutes showing hazard analysis was reconsidered when differences appeared, and examples where the check revealed a real discrepancy are all convincing. A diagram signed without any trace of observation is weak evidence.
Illustrative food-manufacturing example
A team walks a process diagram and observes a routine intermediate holding stage that is absent from the drawing. Operators explain that the stage was introduced after a capacity change. The team records the actual arrangement and evaluates the associated operating and hazard-analysis implications.
The review also establishes why the earlier change did not reach the food safety team. This addresses the communication weakness that allowed the diagram to become outdated.
Illustrative catering example
A catering team confirms a diagram during normal preparation, then checks a service route used for remote sites. It finds that meals pass through a handover point not shown in the original diagram. The team adds the stage and describes the relevant conditions and responsibility.
The retained record distinguishes the routes examined. It does not imply that observing the kitchen alone confirmed the entire supply arrangement.
Common mistakes and useful checks
Common failures include confirming the diagram only in a meeting, checking one convenient product while ignoring significant variations and signing an old version after changes have occurred. Another is treating operator explanations as sufficient where direct observation could resolve an important uncertainty.
Use the confirmed flow with the process and environment description. Together they should support a realistic analysis. Maintain the connection through relevant change notifications and FSMS updates.
Frequently asked questions
Who must confirm the diagram?
The food safety team has this responsibility. Relevant operating personnel and specialists can contribute the knowledge needed for an accurate check.
Is a signed diagram enough evidence?
A signature can record approval, but the underlying on-site confirmation must actually occur. Retain information sufficient to support what was checked.
What if the diagram reveals an unauthorised workaround?
Evaluate the operating issue and its consequences. Do not legitimise the workaround simply by redrawing the flow.
Use a process walk to challenge assumptions
Discuss a facilitated flow-confirmation review with Sterling. The scope can connect observations, actions, learning and suitable evidence management through Effivity ISO & GRC automation software. Explore HACCP Awareness; see the parent guide and requirements hub.