Risk-based thinking ISO 22000 asks food businesses to manage two different kinds of risk, and many teams only manage one of them. HACCP controls hazards to the product at each process step. Clause 6.1 of ISO 22000:2018 covers risks and opportunities to the management system itself. Mixing the two up is a common reason audits stall on planning questions.
This guide shows how the two levels fit together, what auditors look for and five steps to build both into one working food safety management system (FSMS).
What risk-based thinking ISO 22000 requires
ISO 22000:2018 treats risk at two levels. ISO’s announcement of the 2018 edition describes a new approach that separates risk at the operational level from risk at the business level of the management system. Risk-based thinking ISO 22000 expects you to manage both and to show how they connect.
Organisational level: Clause 6.1
Risk-based thinking ISO 22000 starts with Clause 6.1. When planning the FSMS, you consider the issues in Clause 4.1 and the requirements of interested parties in Clause 4.2. You then decide which risks and opportunities need action so the system can deliver its intended results. Actions must be proportionate to their effect on food safety requirements, on product conformity and on the needs of interested parties in the food chain. The ISO 22000 family page lists the current documents.
Operational level: hazard analysis and HACCP
At the operational level, risk-based thinking ISO 22000 shows up as hazard analysis and the hazard control plan in Clause 8, built on the Codex HACCP principles. This layer asks what could make a product unsafe and where you control it. If you need a refresher, read our guide on how to write a HACCP plan that passes an audit.
Risk-based thinking ISO 22000 vs HACCP: key differences
Both levels use risk logic, but they answer different questions and belong to different owners. The table shows how they differ in practice.
| Aspect | HACCP (operational level) | Clause 6.1 (organisational level) |
|---|---|---|
| Main question | What could make this product unsafe? | What could stop the FSMS achieving its results? |
| Typical examples | Pathogen survival, allergen cross-contact, metal fragments | Staff turnover, supplier failure, new regulation, plant expansion |
| Main tools | Hazard analysis, CCPs, OPRPs, monitoring records | Context analysis, risk and opportunity register, objectives |
| Usual owner | Food safety team and production | Top management and functional heads |
| Reviewed through | Validation and verification | Management review |
A practical example: staff turnover at a dairy plant
Imagine a dairy plant where three trained pasteuriser operators leave within six months. The HACCP plan has not changed, yet the monitoring records show late temperature checks. The hazard analysis cannot explain the drift, but the Clause 6.1 register can. A system risk, the loss of competent operators, is weakening a product-level control.
Sensible actions include a competency matrix, cross-training and automated data logging. The logging system is also an opportunity, so record it as one. This is risk-based thinking ISO 22000 at work: the two levels explain each other.
How to apply risk-based thinking ISO 22000 in 5 steps
Use these five steps to build a register that auditors can follow without creating a second management system. The same approach works for a small bakery or a multi-site manufacturer, because Clause 6.1 asks for proportionate action.

1. Define context and interested parties
List the internal and external issues from Clause 4.1 and the interested parties from Clause 4.2. Typical parties include customers, regulators, certification bodies, suppliers and employees. In the GCC, add the municipal food control authority and the requirements of your export markets.
2. Build a linked risk and opportunity register
Keep this register separate from the hazard analysis, but cross-reference the two where a system risk feeds a product hazard. For each entry, record the risk, its cause, the possible effect on food safety and the planned action. Add opportunities too, such as a supplier that offers better traceability data. This register is your main evidence of risk-based thinking ISO 22000 in practice.
3. Score and prioritise
Use a simple scale, for example 1 to 5 for likelihood and for impact, and set a score above which action is mandatory. A short, consistent method beats a complex model nobody uses. Proportionate is the key word in Clause 6.1.
4. Assign owners and actions
Name an owner and a due date for every action. HR typically owns turnover risk, procurement owns supplier risk and top management owns regulatory and strategic risk. Link actions to your objectives in Clause 6.2 and to resource decisions, so the register drives real budget and training choices.
5. Review and update
Review the register at management review, after incidents and when you plan changes. Feed internal audit findings back in. Use our ISO 22000 internal audit checklist as the base for your audit questions and add a check on the link between the HACCP plan and the register.
What auditors check on risk-based thinking ISO 22000
Auditors rarely ask for the register first. They start with a symptom, such as a drifting CCP or a supplier complaint, and trace it back. Expect them to look for:
- Evidence that top management helped identify risks, not only the quality manager.
- Consistency between the register, the objectives and the resources provided.
- Opportunities recorded alongside risks.
- Updates after incidents, recalls and planned changes.
Incident learning matters here. Our ISO 22000 crisis management plan guide shows how a response plan feeds back into the system. A mature register is also evidence for the food safety culture requirements in ISO 22000:2026, because it shows the system finds gaps before an audit does.
Common mistakes that weaken the risk register
Weak risk-based thinking ISO 22000 shows up in four errors that appear again and again.
- Copying the HACCP hazard list into the register. This duplicates work and misses system risks.
- Using a generic template. A register that ignores your context fails the Clause 4.1 link.
- Writing risks once. A static register shows that nobody reviews it.
- Skipping opportunities. Clause 6.1 covers both, and auditors notice the gap.
If you are still choosing a certification route, our FSSC 22000 vs ISO 22000 comparison explains how the schemes build on the same clauses.
Conclusion: one connected system
Risk-based thinking ISO 22000 works best when product hazards and system risks sit in separate registers that refer to each other. Keep HACCP for the process, use Clause 6.1 for the organisation and review both at management review. Start with the five steps above, test the link at your next internal audit, and your system will show auditors that it finds problems before they do. Explore more food safety guides on the Standards Unlimited blog.
