We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
Risk & Governance

What Documents You Need for ISO 31000 Implementation

What Documents You Need for ISO 31000 Implementation
In short

ISO 31000 implementation documents: the policy, framework, risk register, criteria and reports you need, and what is optional. A practical checklist.

In this article
  1. Start with how ISO 31000 is built
  2. Core documents for the framework
  3. Core documents for the risk process
  4. Records that prove it is working
  5. A quick reference table
  6. How to keep documentation proportionate
  7. Frequently asked questions

Most people who search for ISO 31000 documentation expect a checklist like the one for ISO 27001 or ISO 9001. ISO 31000 does not work that way. It gives guidance on risk management principles, a framework and a process. It does not list mandatory documents, and it is not a standard you certify against.

That does not mean you can skip documentation. Without written decisions, criteria and records, risk management turns into opinion and memory. This article explains which documents are worth creating, why, and how to keep them proportionate.

Start with how ISO 31000 is built#

The guidance has three parts, and your documents should map to them:

  • Principles: the ideas that make risk management effective, such as being integrated, structured, customised and responsive to change.
  • Framework: how risk management is embedded in the organisation. It covers leadership and commitment, integration, design, implementation, evaluation and improvement.
  • Process: the repeatable cycle of communication and consultation, defining scope, context and criteria, risk assessment, risk treatment, monitoring and review, and recording and reporting.

A useful test for any document is whether it supports one of these parts. If it does not, you probably do not need it.

Core documents for the framework#

These documents show that risk management is a managed activity, not a one-off exercise.

  1. Risk management policy. A short statement of management's intent and commitment. It should say why the organisation manages risk, who is accountable and how the policy links to objectives. One or two pages is usually enough.
  2. Risk management framework or plan. Describes how risk management is integrated into governance, planning and decision-making. It covers the approach, resources, timelines and how the framework will be reviewed.
  3. Roles and responsibilities. Who owns risks, who coordinates the process, who reviews results and who escalates. This can sit inside the framework or be a separate matrix.
  4. Risk appetite and tolerance statement. Describes how much risk the organisation will accept in pursuit of its objectives. Many organisations hold this in the criteria document instead.
  5. Communication and reporting arrangements. Who receives risk information, how often and in what form.

Core documents for the risk process#

These are the working documents that people use each time they assess and treat risk.

  • Risk management procedure. A step-by-step description of how to run the process: how risks are identified, analysed, evaluated and treated, and who signs off.
  • Scope, context and criteria. Defines what is being assessed, the internal and external context, and the criteria used to judge risk. Criteria include the likelihood scale, consequence scale and the level at which a risk needs action. Without agreed criteria, two teams will rate the same risk differently.
  • Risk register. The central record of identified risks. It normally holds a description, cause and consequence, owner, current controls, rating, treatment decision and review date.
  • Risk assessment records. Worksheets, workshop notes or outputs showing how ratings were reached.
  • Risk treatment plan. Actions chosen to modify, avoid, share or retain each risk, with owners, deadlines and resources. Record the residual risk once the action is complete.

Records that prove it is working#

ISO 31000 stresses monitoring, review, recording and reporting. These records show the framework is alive, not just written down.

  • Risk reports to senior management or the board, showing top risks, trends and treatment progress.
  • Review records: minutes or notes from risk reviews and meetings where risk was discussed.
  • Incident and near-miss links: evidence that events feed back into the register.
  • Framework evaluation and improvement log: periodic checks on whether the framework fits the organisation, and the changes you made as a result.
  • Training and awareness records, if staff have defined risk responsibilities.

A quick reference table#

DocumentSupportsPriority
Risk management policyFramework: leadership and commitmentEssential
Framework or planFramework: design and implementationEssential
Risk criteriaProcess: scope, context and criteriaEssential
Risk management procedureProcessEssential
Risk registerProcess: assessment and recordingEssential
Risk treatment planProcess: treatmentEssential
Risk reports and review recordsMonitoring, review and reportingEssential
Risk appetite statementFramework and criteriaRecommended
Framework evaluation logFramework: evaluation and improvementRecommended

How to keep documentation proportionate#

The most common mistake is writing too much. ISO 31000 asks for a framework that is customised to the organisation, so a small firm and a large group will not need the same volume of paper.

  • Write for the people who use it. If a procedure is too long to follow in a workshop, shorten it.
  • Reuse what you have. If you already run information security, quality or business continuity programmes, link to existing risk methods instead of creating a parallel one. Our guides on ISO 22301 documents and ISO 14001 documents show where risk records already appear in other management systems.
  • Control versions. Give each document an owner, a version number and a review date.
  • Keep one register. Scattered spreadsheets make reporting unreliable. Agree one format and one owner.
  • Get management sign-off. Policy and criteria carry weight only when leadership approves them.

Frequently asked questions#

Can an organisation be certified to ISO 31000?#

No. ISO 31000 provides guidelines, not requirements, so it is not designed for certification. Organisations use it to build and improve their own risk management and can ask a third party for an assessment or gap review, but that is different from a certificate.

Are there mandatory documents in ISO 31000?#

The guidance does not set out a list of mandatory documents. It does expect risk management to be recorded and reported, and it expects decisions and criteria to be traceable. In practice, that means the policy, framework, criteria, register, treatment plans and reports listed above.

Do we need a separate risk process if we already have ISO 27001 or ISO 22301?#

Usually not. Those standards have their own risk requirements, and many organisations use ISO 31000 as the enterprise-level umbrella. The key is to align criteria and terminology so that risks can be compared and rolled up in one view for management.

If you would rather start from a structured set of templates than a blank page, the ISO 31000 Toolkit is a ready-to-use documentation toolkit you can adapt to your organisation, or you can contact AdWiser to talk through your requirements.

Share this guide

Ready to put this into practice?

Start with the ISO 31000 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp