Enterprise risk leadership: appetite, ownership and assurance
A premium course for executives on running enterprise risk management as a leadership tool, not a register exercise: ISO 31000 and COSO ERM, setting risk appetite, owning principal risks, key risk indicators, and assurance. The documented BP Texas City disaster (2005) shows what happens when the wrong indicators reassure leaders. Not an accredited qualification.
What you will learn
- Explain the purpose of enterprise risk management and compare ISO 31000:2018 with COSO ERM (2017).
- Write a usable risk appetite statement with measurable tolerances.
- Assign ownership of principal risks and integrate risk into strategy and budget decisions.
- Choose leading key risk indicators and avoid false reassurance, using the BP Texas City findings.
- Organise risk assurance and executive reporting using the Three Lines Model.
Modules
- Why enterprise risk management: ISO 31000 and COSO ERM
- Risk appetite and tolerance
- Ownership and integration into decisions
- Key risk indicators and the danger of false reassurance
- Assurance and executive risk reporting
Course facts
- Estimated study time
- about 1.5 hours
- Final assessment
- 10 questions · Pass mark 80%
- Available in
- English, Français, العربية
- Price
- Free. Optional verifiable certificate: $12
- Last updated
- Published by
- AMAADOR ACADEMY
Who this course is for
Executive committee members, directors, risk owners, heads of risk, audit and compliance, and managers preparing for executive roles.
Prerequisites
No formal prerequisite. Familiarity with business planning or budgeting helps.
Course content
1. Why enterprise risk management: ISO 31000 and COSO ERM
ISO 31000:2018 defines risk as the effect of uncertainty on objectives, and states that the purpose of risk management is the creation and protection of value. It is organised in three parts: principles (for example integrated, structured and comprehensive, customised, inclusive, dynamic, based on the best available information, attentive to human and cultural factors, and continually improved), a framework led by top management, and a process of communication, context, assessment, treatment, monitoring and reporting.
COSO’s Enterprise Risk Management — Integrating with Strategy and Performance (2017) is written for executives and boards. It groups 20 principles into five components: governance and culture; strategy and objective-setting; performance; review and revision; and information, communication and reporting. Its main message is that risk belongs in strategy selection, not after it.
The two are compatible. Many organisations use ISO 31000 for the common language and process, COSO for the link to strategy and performance, and sector rules for specifics. Public bodies in the UK use HM Treasury’s Orange Book, which sets out principles for risk management in government.
- Executive test: can each member of the executive team name the organisation’s five principal risks, their owners and the current trend?
Key point: A risk register that never changes a decision is documentation, not risk management.
2. Risk appetite and tolerance
Risk appetite is the amount and type of risk an organisation is willing to pursue or retain in pursuit of its objectives. Tolerances (or limits) translate it into measurable boundaries. An appetite statement that says “we have a low appetite for risk” helps no one; a useful statement differs by category and can be measured.
A practical structure, used by the HM Treasury Orange Book guidance and many firms, rates each category on a scale such as averse, minimal, cautious, open and eager. Safety and legal compliance usually sit at averse or minimal; innovation or market entry may be open. Each rating then gets two or three metrics with amber and red thresholds and an escalation rule.
Appetite must be approved by the board and used by management: in investment cases, in project gates, in supplier choices. If no decision ever refers to it, it is not working.
Key point: Write appetite by category, attach numbers, and say who acts when a number turns red.
3. Ownership and integration into decisions
A risk owner is the person with the authority and resources to manage the risk — usually a member of the executive team, not the risk manager. The risk function designs the method, challenges assessments and reports; it does not own the business’s risks.
Integration means risk appears where decisions are made: in the strategic plan (what could stop us?), in the budget (are critical controls funded?), in investment and project gates (what is the downside case?), in mergers (what risks are we buying?) and in incentive design (could targets push people to take risks outside appetite?).
Watch for interdependencies. A cyber incident becomes an operational outage, a regulatory breach and a reputational crisis at once. Executive risk reviews should look at clusters and scenarios, not isolated lines.
Key point: The risk team owns the method; executives own the risks.
4. Key risk indicators and the danger of false reassurance
Key risk indicators (KRIs) give early warning that a risk is moving outside appetite. Lagging indicators count what already happened (losses, injuries, fines); leading indicators show the condition of controls before something goes wrong (overdue critical maintenance, open audit findings, alarm overrides, staff in critical roles without training).
The most dangerous indicator is a good-looking one that measures the wrong risk. Low personal-injury rates say little about the likelihood of a major explosion; low complaint numbers may mean customers have given up complaining.
Good KRIs are tied to a specific risk and control, have thresholds linked to appetite, come from reliable data, and trigger a defined action. Review them yearly: if one has never moved, ask whether it can.
Key point: Ask of every green indicator: green for which risk?
Case study: BP Texas City refinery explosion (2005). On 23 March 2005, during the startup of an isomerisation unit at BP’s Texas City refinery, a distillation tower was overfilled and hydrocarbons released from a blowdown stack ignited. Fifteen workers were killed and 180 injured. The U.S. Chemical Safety Board’s final report (2007) found that BP had relied on low personal-injury rates as a measure of safety performance while process safety deteriorated, and that cost-cutting and failures to invest had left the refinery vulnerable. The independent Baker Panel (January 2007) reached similar conclusions on BP’s US refineries. The lesson for executives: the KRI must match the catastrophic risk.
5. Assurance and executive risk reporting
The IIA’s Three Lines Model (2020) helps executives organise who does what: management (first line) owns and manages risk; specialist functions such as risk, compliance and safety (second line) provide expertise, support and challenge; internal audit (third line) provides independent assurance to the governing body.
An executive risk report should fit on two pages: the principal risks with owner, trend and position against appetite; KRIs in breach and actions; emerging risks; and assurance results, including overdue actions. Use the same format every time so trends are visible.
Finally, test the system with scenarios. Once a year, take one severe but plausible scenario through the executive team: what would we see first, who would decide, what would it cost, and are we inside appetite?
Key point: Same two-page format, every quarter: owner, trend, appetite, KRIs, assurance.
The full lesson, case studies, scenarios and templates continue in the interactive course on this page.
Sources and references
- ISO 31000:2018 Risk management — Guidelines (catalogue)
- Enterprise Risk Management — Integrating with Strategy and Performance (2017)
- The Orange Book: Management of Risk — Principles and Concepts
- The IIA’s Three Lines Model (2020)
- BP America (Texas City) Refinery Explosion — investigation page and final report (2007)
- IRM — risk appetite and tolerance guidance and resources
Executive education only, not an accredited qualification. ISO and COSO content is paraphrased from public pages without reproducing paid text; check the ISO catalogue for the current status of any revision. Case facts are taken from the public investigation reports cited.