Embedding ERM in decision-making
What the exam tests
Embedding ERM: making risk information change decisions in strategy, pricing, products, capital and operations.
Core rules
- Embedding means risk is considered before decisions, not documented afterwards. It requires clear roles, appetite-linked delegation, and risk input into business planning.
- Use gates: strategy approval, product launch, M&A, outsourcing, pricing and capital allocation each require a risk assessment and appetite check.
- Performance metrics and incentives should include risk-adjusted returns and conduct measures.
- The use test asks whether models and risk information are actually used in management decisions.
- Feedback loops: post-decision reviews, loss events and near misses update the register and models.
Worked example
A new product promises high growth but has uncertain claims experience. The gate review requires: risk identification, appetite fit, capital impact, stress scenarios, pricing loadings and monitoring plan. The decision is to launch with volume limits, a review trigger and a capital allocation. Reasoning: embedding converts the ERM framework into a decision with conditions and accountability. Without the gate, risk assessment would be a parallel paper exercise; with it, appetite and capital directly shape the launch.
Traps
ERM as a separate function; risk assessment after the decision; no appetite linkage; incentives rewarding volume only; no post-decision review.