ISO 22000 clause 8.5.1: build a reliable basis for hazard analysis

What clause 8.5.1 requires in practice

Clause 8.5.1 covers the preparation work that must exist before a hazard analysis can be trusted. The food safety team collects, maintains and updates the preliminary information in a documented form. The standard divides it into five areas: general information, raw materials, ingredients and product contact materials, end products, intended use, and flow diagrams with descriptions of processes and the process environment.

General information includes the applicable statutory, regulatory and customer requirements, the organisation's products, processes and equipment, and the food safety hazards relevant to the system. The material and product areas require applicable food safety requirements to be identified and characteristics recorded to the extent needed for analysis.

Intended use includes reasonably expected handling and reasonably expected misuse, and calls for consumer groups, especially vulnerable ones, to be identified. Flow diagrams are prepared, confirmed on site and updated, and processes are described including layout, equipment, existing controls, external requirements and seasonal or shift variation.

Connect materials with the end product

Material characteristics cover raw materials, ingredients and product-contact materials. Information should be sufficient for hazard analysis, including relevant composition, origin, processing, handling and food safety acceptance needs. Product-contact materials should not disappear from the review simply because they are not ingredients.

End-product characteristics describe what the organisation intends to produce, including relevant composition, safety characteristics, shelf life, storage, packaging, information and distribution. These details need to be consistent with the actual product and the assumptions used in its control.

Look for gaps between the two. A material specification may be accurate but insufficient to explain a hazard relevant to the finished product. The team needs to connect information rather than merely collect supplier documents.

Understand use and the real process

Intended use includes reasonably expected handling and reasonably foreseeable mishandling or misuse. Identify relevant users and especially vulnerable groups. Hazard-analysis assumptions should not rely on an ideal use pattern that ignores the product's realistic destination.

Flow diagrams and process descriptions explain the sequence, interactions and operating environment. Include relevant inputs, outsourced stages, rework, outputs and waste. Confirm diagrams on site rather than assuming a design drawing represents current work.

Describe relevant equipment, process parameters, existing PRPs, controls and external requirements. Include appropriate seasonal or shift variation. A single description of the easiest operating condition can conceal a significant difference.

Manage the information as a connected set

Use the general preparation requirements to establish responsibility for collecting and maintaining the information. Record uncertainties that need resolution before a conclusion can be relied on. A blank field should not quietly become an assumption that no hazard exists.

Make changes visible across the set. A different distribution arrangement can affect intended use assumptions, product information and the process description. Later hazard-control decisions may also require the preliminary information to be updated under clause 8.6.

Why the basis for hazard analysis matters to the business

A hazard analysis can only be as good as the information that goes into it. If the process diagram omits a rework loop, the analysis will not consider the hazard it creates. If intended use ignores a vulnerable consumer group, controls may be set too leniently. Errors at this stage flow invisibly through every later decision.

Careful preparation pays back in several ways. It reveals gaps in supplier information while there is still time to obtain it. It gives new team members a clear picture of what is being assessed. And it makes later reviews far quicker, because the team can see which assumption a change affects. For customer audits, an accurate information base shows genuine understanding of the operation.

How to implement clause 8.5.1

Gather and confirm information in a structured way, and keep it as a connected set rather than separate files. The following steps are a practical approach.

1. Identify what information each area needs, and assign owners from purchasing, production, technical and quality.
2. Collect material and ingredient information, including product contact materials, and applicable legal requirements for each.
3. Describe each end product with its characteristics, shelf life, storage, packaging, labelling and distribution.
4. Define intended use realistically, including expected handling, foreseeable mishandling and consumer groups needing particular care.
5. Draw flow diagrams for each product or category, then walk the line to check them against what really happens, including rework and outsourced steps.
6. Describe the premises, equipment, existing controls and relevant external requirements, noting seasonal and shift variation that could alter how hazards arise.
7. Keep a list of open questions, update the set when anything changes, and tell the whole team what has changed so everyone works from the same picture.

Illustrative food-manufacturing example

Illustrative catering example

A caterer expands from preparation and immediate service to supplying meals at a separate worksite. The team maps transport and service stages, clarifies responsibilities and records the realistic use conditions. It also considers the relevant consumer group.

The resulting hazard analysis can address the complete arrangement. A kitchen-only diagram would have omitted stages on which food safety decisions depend.

Evidence and common mistakes

Explore each numbered part