Embedding ISO 31000 risk management into your other ISO systems

Walk into a mid-sized exporter that holds ISO 9001, ISO 14001 and ISO 27001, and ask how the company manages risk. You will usually be shown three separate things: a quality risk spreadsheet built around process failure, an environmental register organised by aspects and impacts, and an information-security risk assessment scored on a scale of its own. Three owners, three review cycles, three vocabularies. A single sole-supplier dependency can surface as a quality risk in one file, an availability risk in another, and go unrecorded in the third. None of the three reaches the people who actually set strategy.
This is the gap ISO 31000 exists to close. It is not another certificate for the lobby wall. It is a guidance standard that gives you one defensible way to reason about risk, and that single approach can sit underneath every management system you already operate. Treating it as the connective tissue between your standards, rather than as a stand-alone project, is where the return lives. If you want that single approach laid out on its own, our overview of ISO 31000 risk management covers it; the more useful question here is how one framework can serve every standard you already hold, and the answer starts with how much those standards already have in common.
Why every modern ISO standard already speaks risk
Since 2012 the ISO management system standards have shared a common backbone, the harmonised structure once known as Annex SL. The clause that matters most here is 6.1, actions to address risks and opportunities, and it appears in near-identical wording across the family. The certifiable standard for quality, ISO 9001, asks you to determine the risks and opportunities that affect conformity and customer confidence. The ISO 14001 environmental management system frames them around aspects, impacts and compliance obligations. ISO 27001 goes furthest, requiring a formal information-security risk assessment and a documented treatment plan mapped to its Annex A controls. The objects differ; the underlying verbs do not: identify, analyse, evaluate, treat, monitor.
When each system invents its own method to satisfy that clause, you pay for the duplication every year. When a single ISO 31000 framework satisfies all of them, clause 6.1 stops being several separate chores and becomes one discipline applied in several contexts. The table below shows where risk already lives in each standard, and what a shared framework adds on top.

One process, repeated wherever risk appears
ISO 31000 describes a process that any of your systems can adopt without modification: establish the scope, context and criteria; assess the risk through identification, analysis and evaluation; treat it; then monitor, review, record and report, with communication and consultation running throughout. Practitioners of ISO 27001 recognise this at once, because information-security risk management already works this way and has long leaned on the companion guidance in ISO 27005. The insight that unlocks integration is that the security team is not doing anything exotic. It is running the ISO 31000 process on one category of risk. Extend the same process to quality and environmental risk and you remove three different procedures, replacing them with one that is described once and trained once.
Build one framework, not four registers
The practical work of integration is mostly about agreeing things a single time. ISO 31000 separates into a framework, meaning how risk management is governed, resourced and improved, and the process above. Both map cleanly onto the systems you already run.
Agree the context and risk criteria once
Before any register makes sense, decide what counts as a significant risk and how you will rate likelihood and consequence. Set those scales once, at organisation level, and let each discipline read them through its own lens. A high-consequence event for information security might be a data breach carrying regulatory exposure; for environment it might be a reportable spill; for quality, a product recall. The scoring logic is shared even when the examples differ. This is also where you set risk appetite, the amount of risk leadership will accept in pursuit of an objective, so that decisions stop depending on whoever happens to own a particular file.
Run one register, read through domain lenses
A single risk register with consistent fields, source, event, existing controls, owner, rating, treatment and review date, removes the contradiction of the same threat scored three ways. Tag each entry by domain so the quality, environmental, security and safety teams can filter to their slice without losing the shared picture. The sole-supplier dependency from the opening now appears once, with its quality, continuity and security consequences visible together, owned by one person and reviewed on one cycle. The same logic absorbs occupational health and safety risk under ISO 45001 and continuity risk under ISO 22301 when those systems join later.
Tie it to leadership and management review
ISO 31000 is explicit that risk management has to be led from the top and built into governance, not bolted on afterwards. That maps directly onto the leadership and management-review clauses your certified systems already contain. Bring one integrated risk picture to a single management review rather than three disconnected ones, and the conversation rises from housekeeping to real decision-making. This is the point at which the case for running the systems as one, rather than as three, becomes hard to argue against.
The opportunity half most companies skip
Clause 6.1 covers risks and opportunities, and ISO 31000 treats the creation and protection of value as the entire purpose of managing risk. Most registers quietly drop the second word. That is a missed return. The same framework that flags a single point of failure can flag a second-source supplier that opens a new market, or an energy project that lowers both cost and emissions at once. Reading opportunity through the same criteria as threat keeps your risk work from becoming a register of fears, and it gives leadership a reason to keep reading it.
Where integration usually goes wrong
Three failure patterns recur. The first is the audit-week spreadsheet, a register built to satisfy a certificate, then left untouched until the next visit and owned by no one. The second is confusing the risk-based thinking that ISO 9001 expects with the formal risk management that ISO 31000 describes: the first is a mindset woven through the system, the second is a structured process, and a mature organisation needs both. The third is over-engineering, a methodology so heavy that no one keeps it current, which is worse than a lighter process people actually use. Integration should reduce the total weight of risk work, not add a fourth layer on top of the three you already carry.
Done well, embedding ISO 31000 turns risk from a clause you satisfy into the thread that ties quality, environment, security and safety into one coherent system. If you are weighing how a single risk framework would map onto the standards you already hold, planning an integrated management systems certification is a sensible next step, scoped honestly rather than oversold.
Picked for You
Related Articles

Supply-chain security with ISO 28000: managing risk across the chain
Read More →
Getting ready for an ISO 14001 environmental audit: common pitfalls
Read More →
