hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Clause 8.5.1.5.3ISO 22000:2018 · Describe the process that actually handles the food

ISO 22000 clause 8.5.1.5.3: explain the conditions behind the process flow

ISO 22000 clause 8.5.1.5.3 requires the food safety team to describe the processes and process environment to the extent needed for hazard analysis. A flow diagram shows the sequence; the description explains relevant conditions within that sequence. It must remain documented and updated, including appropriate variation arising from seasonal changes or shift patterns.

What clause 8.5.1.5.3 requires in practice

Where the flow diagram shows the order of steps, this clause requires the food safety team to describe the conditions around them, to the extent the hazard analysis needs. The description covers the layout of premises including areas where food is and is not handled, the equipment, contact materials, processing aids and movement of materials, and the controls already in place: prerequisite programmes, process parameters, existing control measures and how strictly they are applied, and procedures that could influence safety. It also covers outside requirements, from authorities or customers, that affect which controls are chosen and how strict they must be. Expected seasonal changes and shift patterns are included where relevant. The result is a maintained written description the team can use alongside the diagrams.

Describe the physical and process context

Include relevant premises layout, with food and non-food handling areas. Explain the equipment, product-contact materials, processing aids and material flows that matter to the analysis. The aim is to make significant interfaces understandable, not to reproduce every engineering drawing.

Connect descriptions to the process stages they explain. If a shared area or transfer arrangement affects several stages, show that relationship clearly. Otherwise, the team may assess each stage in isolation and overlook an interaction.

Use information from people who understand actual work. A facility design specification may not show later modifications or routine operating arrangements. Align the description with on-site flow confirmation.

ISO 22000 consulting & certification support

Get clause 8.5.1.5.3 right the first time — with a global leader in ISO 22000 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Explain existing controls and their application

Describe relevant PRPs, process parameters, existing control measures and procedures that can influence food safety. Include the degree of control actually applied where it matters. A statement that cleaning or inspection occurs may be insufficient if its relevant conditions are unknown.

Do not confuse documenting an existing measure with establishing that it is adequate. The hazard analysis and subsequent validation and planning requirements determine the necessary control decisions.

Include external requirements that may affect the choice or strictness of control measures. These can arise from authorities or customers. Keep the applicable basis visible instead of treating an inherited process parameter as self-justifying.

Account for meaningful variation

Consider whether seasonal conditions or shift patterns change the environment, resources or way the process operates. Include relevant differences rather than describing only a typical daytime condition. Not every variation is significant, but the team needs a reasoned view.

Maintain the description when conditions change. A change to layout, equipment, cleaning, material movement or an external requirement may affect more than one part of the analysis. Use the internal communication arrangements to bring such information to the team.

Why clause 8.5.1.5.3 matters to the business

Two steps that look identical on a diagram can behave very differently depending on layout, equipment, staffing or season. If the team assumes a single typical day, hazards that appear only on the evening shift or in a busy season stay invisible. Describing real conditions also exposes controls that exist in name only, for example a cleaning routine whose actual conditions nobody has written down. Customers and regulators ask these questions when they trust a supplier less, so being able to answer from a current description is reassuring. It also makes later decisions on controls quicker, because the facts are already gathered.

How to implement clause 8.5.1.5.3

Treat the description as a working companion to the diagram, built by walking the premises and talking to the people who use them. Aim for description that answers real questions a hazard analyst will ask, and resist collecting engineering detail that nobody will read or keep up to date afterwards.

  1. Mark food and non-food areas on a layout and note shared spaces, transfer points and any area serving more than one stage.
  2. List equipment and product-contact materials for each step and note how materials move between them.
  3. Record the prerequisite programmes and control measures that already apply, and how rigorously each is actually carried out.
  4. Add outside requirements from authorities and customers that influence which controls are needed.
  5. Ask each shift and each season-affected area how work differs, and describe the differences that could change a hazard.
  6. Link every item to the diagram step it explains so the team can find it without searching.
  7. Update the description when layout, equipment, cleaning or material routes change, and review it with the diagram.

Illustrative food-manufacturing example

Illustrative example 1

A manufacturer has the same nominal process sequence on two shifts, but one shift uses a different material-staging arrangement. The food safety team describes the difference and examines whether it affects hazard identification or the application of existing controls.

Illustrative example 2

The team does not automatically declare the difference unsafe. It establishes the facts so the analysis can reach a justified conclusion rather than assuming both shifts are identical.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 8.5.1.5.3 alive in Effivity

Record what you decided under clause 8.5.1.5.3, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO 22000 programme.

Illustrative catering example

A catering operation uses a temporary service arrangement during a seasonal increase in demand. The team records the relevant layout, material flow and supporting controls, then evaluates the implications for the existing analysis.

The description distinguishes the temporary arrangement from normal service. It also identifies the conditions under which the arrangement is used so it can be reviewed when the operation changes again.

Evidence and common weaknesses

What counts as evidence

Maintain the description in a form the food safety team can use. Linked diagrams, photographs, equipment information and written explanations may help, but the standard does not prescribe a single format. Keep technical context accurate and appropriately controlled.

Common weaknesses

Common weaknesses include generic descriptions of hygiene, missing details about shared areas and assumptions that a control is applied identically across shifts. Another is recording desired operating conditions while personnel follow different actual arrangements.

Read the description alongside the flow-diagram overview. The combined information should allow the team to explain why a particular hazard question arises at a particular stage.

Frequently asked questions

Does this require every equipment setting to be listed?

No. Include the detail needed for hazard analysis and the relevant controls and requirements. Avoid both missing significant information and unnecessary data collection.

Should seasonal differences always be documented?

Include them as appropriate where they affect the process description needed for hazard analysis.

Does describing a PRP prove it works?

No. Description provides an input. Implementation, monitoring where applicable and verification need their own evidence.

Describe the conditions your current plan assumes

Ask Sterling to review process-environment information with your team. Documentation, learning and suitable Effivity ISO & GRC automation software support can help connect changes with their evidence. Review Prerequisite Programmes for Food Safety, which covers the 2025 common requirements and food-manufacturing application, and return to the ISO 22000 hub.

Source basis and reading note. This is original practical guidance for ISO 22000. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide management-system certification outcomes. Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO 22000 in your organisation.