ISO 22000 clause 8.5.1.1: prepare the information the food safety team needs
ISO 22000 clause 8.5.1.1 requires the food safety team to collect, maintain and update preliminary documented information for hazard analysis. This includes applicable statutory, regulatory and customer requirements, the organisation's products, processes and equipment, and relevant food safety hazards. These categories are a starting point, not a limit on information that may be necessary.
What clause 8.5.1.1 requires in practice
Clause 8.5.1.1 is the general opening to the preparatory work for hazard analysis. It places a duty on the food safety team to collect, maintain and update preliminary documented information. The standard lists three categories that the information includes, and adds that the list is not exhaustive: applicable statutory, regulatory and customer requirements, the organisation's products, processes and equipment, and the food safety hazards relevant to the management system.
The words about maintaining and updating are important. The information is not a one-off pack assembled for an initial study. It must remain current as products, equipment and requirements change.
This clause works as the umbrella for the detailed subclauses that follow on materials, end products, intended use and process description. The output is a body of information, held by the team, that is adequate to support a reliable hazard analysis and that can be traced to sources.
Give each information item a purpose
Ask which hazard-analysis decision the information will support. Product composition may help identify a hazard; equipment details may explain where it can be introduced or controlled; an applicable requirement may establish an acceptance expectation. This makes collection more purposeful than requesting every available document.
Identify suitable sources and responsible people. Purchasing can obtain supplier information, operations can explain the actual sequence and technical personnel can evaluate relevant hazard knowledge. The food safety team needs to bring the information together and judge whether it is sufficient.
Separate current facts from historical references and unconfirmed assumptions. An old product specification may still be useful background, but it should not silently represent a changed product. Keep the information's status clear enough that team members do not rely on different versions during the same discussion.
Why preparing information for the food safety team matters to the business
Teams often rush to the hazard analysis workshop because it feels like the real work. Without good preparation, the discussion relies on memory and assumption, and conclusions vary depending on who attends. Preparation turns a debate into a decision based on facts.
The commercial benefit is repeatability and speed. When information is organised and current, a new product can be assessed in a fraction of the time, and the same answer emerges whoever leads the team. Gaps are found early, such as an unclear supplier specification or an unknown customer requirement, avoiding delays when a product is introduced. It also makes handover easier when team members leave and gives auditors confidence that decisions have a reliable foundation.
How to implement clause 8.5.1.1
Link each piece of information to a decision it will support, and make the team accountable for keeping it current. A practical order is as follows.
- Write down the decisions the hazard analysis must support, then list the information each requires.
- Gather the applicable legal and customer requirements and note which products and processes they affect.
- Collect descriptions of products, processes and equipment from the people who operate them, not only from design documents.
- Compile relevant hazard knowledge from experience, supplier information and reliable external sources, and note where it came from.
- Mark each item as confirmed, assumed or missing, and decide how every gap will be closed before it influences a conclusion.
- Set how changes reach the team, using the internal communication arrangements, and who updates the information.
- Keep the information in a form the team can easily find and read, and review it at planned points and after incidents.
Resolve important gaps
When information is missing, identify what decision cannot yet be supported and how the gap will be addressed. The appropriate action may be obtaining clarification, examining the process, consulting competent expertise or reviewing relevant reliable data.
Do not fill a gap with a convenient generic value or a conclusion copied from another operation. The question is whether the information applies to the actual product, process and environment. External material needs appropriate evaluation under the requirements for externally developed elements.
A simple information-status review can help the team distinguish items ready for use from matters requiring further work. This is an optional method, not an additional mandatory register.
Maintain a basis that can be revisited
Preliminary information must remain maintained and updated. Establish how relevant changes reach the food safety team and who revises affected information. The internal communication arrangements should support this process.
Keep enough context to understand why the information was considered applicable. Later reviewers should be able to connect a changed fact with the hazard-analysis decisions that may need reconsideration. This is particularly useful when personnel or external experts change.
Illustrative ingredient-production example
A producer receives a broad supplier declaration for a formulated ingredient. The team finds that it does not provide enough detail to evaluate a relevant food safety question. Purchasing obtains clarification, and technical personnel assess its relevance before the ingredient information is treated as complete.
The gap remains visible during the review. The absence of a stated concern in the original declaration is not interpreted as proof that no relevant hazard exists.
Illustrative food-logistics example
A logistics business takes on a product category unfamiliar to its current team. It obtains relevant product and handling information and examines the actual storage and transport arrangements. The team identifies where additional competence is needed to interpret the information.
Its scope remains the food-chain services it performs. The review does not assume that a generic logistics procedure answers every product-specific food safety question.
Evidence and common mistakes
The required evidence is the maintained preliminary documented information. An index, dossier or structured workspace can make it easier to use. Whatever method is chosen, confirm that the information supports the hazard analysis.
Common weaknesses are collecting material without evaluating it, leaving unresolved questions invisible and using outdated equipment or product information. Another is treating the team's first analysis meeting as the last opportunity to update its evidence base.
Frequently asked questions
Who owns preliminary information?
The food safety team has the specific responsibility to collect, maintain and update it, with contributions from relevant functions and sources.
Must every source be scientific research?
No. The information set includes operational facts and applicable requirements as well as relevant hazard knowledge. Its suitability matters.
Can hazard analysis start while some information is missing?
Work can progress where the basis is adequate, but unsupported conclusions should not be treated as settled. Resolve gaps that affect the decision.
Build an information set your team can explain
Ask Sterling to help scope the preliminary information needed for your operation. Documentation, learning and suitable Effivity ISO & GRC automation software support can make responsibilities clearer. Explore HACCP Awareness, alongside the preliminary-steps guide and hub.