Structuring an ICAAP Under SS31/15 That Evidences Robust Stress Testing
A practical guide to building an ICAAP document under PRA SS31/15 where stress testing is genuinely integrated, credible, and proportionate. Readers will understand how to structure the narrative, calibration, and board engagement so Pillar 2A outcomes reflect the firm's actual risk profile rather than supervisory concern about weak analysis.
The quickest way to attract Pillar 2A add-ons is to produce an ICAAP where stress testing reads as a bolt-on exercise rather than a live management tool. The PRA's concern, consistently signalled through SS31/15 and subsequent supervisory communication, is not the size of the capital number but the quality of the thinking behind it. If the stress testing section cannot be traced to real board decisions, calibrated to the firm's actual vulnerabilities, and reconciled to the capital stack, supervisors will fill the gap themselves.
Start With the Risk Identification Spine
The ICAAP should open with a risk identification section that is specific to the firm's business model, not a generic taxonomy. SS31/15 expects the firm to demonstrate that it has considered all material risks, including those not fully captured under Pillar 1. The common failure is listing risks without evidencing why each has been sized the way it has.
For each material risk, show three things: the exposure measurement, the historical and forward looking evidence base, and the link to a specific stress scenario or capital charge. If a risk is identified but not stressed or capitalised, explain why, with reference to mitigants that are themselves evidenced.
Design Scenarios That Reflect the Firm, Not the Benchmark
Scenarios borrowed wholesale from the annual cyclical scenario or anchored only to the PRA's published stresses will read as unimaginative. The PRA wants to see reverse stress testing that identifies the firm's actual breaking points, and idiosyncratic scenarios that reflect concentrations, business model dependencies, and management actions that would plausibly be taken.
Good practice: run at least one severe but plausible macro scenario calibrated to the firm's geography and portfolio, one idiosyncratic scenario targeting the largest concentration or dependency, and a combined scenario. Document the narrative logic, the transmission mechanisms into P&L, RWAs, and liquidity, and the time horizon over which each shock plays out.
Make Management Actions Credible
This is where ICAAPs most often lose supervisory confidence. Management actions that assume orderly deleveraging, dividend suspension on day one, or cost cuts that have never been executed at the stated scale will be challenged. Each action should carry an owner, a trigger, a quantified effect, and evidence of feasibility, ideally cross referenced to the recovery plan.
If management actions reduce the capital requirement materially, expect supervisors to probe the counterfactual. Show the capital path both with and without actions.
Connect Stress Outputs to the Capital Stack
The reconciliation from stress testing outputs to Pillar 2A sizing is where many documents fall apart. Set out, explicitly, which risks are covered by Pillar 1, where Pillar 2A is intended to top up for underestimation or uncovered risks, and how the stress results inform the Pillar 2B buffer. Avoid double counting, and be explicit where overlaps exist.
Where the firm's internal assessment differs from the PRA methodology for a given risk, do not obscure the difference. Set out the methodology, the quantitative result, and the rationale.
Evidence Genuine Board Ownership
SS31/15 is clear that the ICAAP is a board document. Minutes, challenge logs, and iterative drafts should show substantive engagement, not a single approval meeting. The board's risk appetite should be the anchor for scenario severity, and the ICAAP should show the board accepting, modifying, or rejecting specific assumptions.
A board that has genuinely engaged will have asked uncomfortable questions. Capture them.
What Good Looks Like
A strong ICAAP under SS31/15 reads as a coherent argument: here is our business model, here are the risks it generates, here is how we have stressed them, here is what we would do, and here is the capital we hold as a result. Each link in that chain is evidenced. Weaknesses are acknowledged and being addressed on a stated timeline.
The next action: before submission, have an independent reader, ideally someone with supervisory experience, trace the argument end to end and flag where it relies on assertion rather than evidence. That is where add-ons originate.
Frequently Asked Questions
How severe should idiosyncratic scenarios be?
Severe enough to challenge the firm's capital position meaningfully. If the scenario produces a comfortable surplus, either the scenario is too mild or the firm's analysis has not captured second order effects. Reverse stress testing should identify the point of non viability and work back from there.
How much weight should we give to management actions?
More weight is defensible when actions are pre agreed, quantified, operationally tested, and consistent with the recovery plan. Less weight when they rely on market access under stress, counterparty behaviour, or execution at a scale the firm has never achieved.
Should we disclose model limitations openly?
Yes. Supervisors already form a view of model weaknesses from peer comparison and thematic work. A firm that identifies its own limitations and sets out a remediation plan is treated more credibly than one that presents models as more robust than they are.
How often should the ICAAP be refreshed between annual cycles?
Whenever there is a material change in risk profile, strategy, or external environment. A document that has not been revisited after a significant acquisition, portfolio shift, or macro event will struggle under supervisory review, regardless of its annual cycle date.
Frequently asked questions
How severe should idiosyncratic scenarios be?
Severe enough to challenge the firm's capital position meaningfully. If the scenario produces a comfortable surplus, either the scenario is too mild or the firm's analysis has not captured second order effects. Reverse stress testing should identify the point of non viability and work back from there.
How much weight should we give to management actions?
More weight is defensible when actions are pre agreed, quantified, operationally tested, and consistent with the recovery plan. Less weight when they rely on market access under stress, counterparty behaviour, or execution at a scale the firm has never achieved.
Should we disclose model limitations openly?
Yes. Supervisors already form a view of model weaknesses from peer comparison and thematic work. A firm that identifies its own limitations and sets out a remediation plan is treated more credibly than one that presents models as more robust than they are.
How often should the ICAAP be refreshed between annual cycles?
Whenever there is a material change in risk profile, strategy, or external environment. A document that has not been revisited after a significant acquisition, portfolio shift, or macro event will struggle under supervisory review, regardless of its annual cycle date.
Related guides
How to Structure an MLRO Annual Report That Evidences Effective Financial Crime Controls
A practical guide to building an MLRO annual report that gives the board and the FCA genuine assurance on financial crime controls. After reading, you will know how to structure the document, what evidence to include, and where most reports fall short.
Structuring a PS21/3 Operational Resilience Self-Assessment That Evidences Impact Tolerance Testing
A practical guide to building an Operational Resilience self-assessment that credibly evidences impact tolerance testing to the FCA and PRA. After reading, you will know how to structure the document, sequence the evidence, and surface the vulnerabilities supervisors expect to see acknowledged.
How to Prepare a Credible FCA Threshold Conditions Attestation Under Supervisory Pressure
This guide sets out how to prepare an attestation on compliance with the FCA's Threshold Conditions when supervisors have raised concerns. It explains what credible looks like, where attestations commonly fall short, and how to sequence board, executive, and evidence work so the submission holds up.
How to Prepare a Credible Operational Resilience Self-Assessment
This guide sets out what a credible Operational Resilience self-assessment looks like under the PRA and FCA regimes, with particular focus on evidencing impact tolerance testing. After reading it, you will know how to structure the document, where boards usually fall short, and what supervisors expect to see when they challenge your mapping, scenarios and vulnerabilities.
How to Structure a Credible RAF Public Disclosure to the Bank of England
This guide sets out how major UK firms should structure their Resolvability Assessment Framework public disclosure so it demonstrates genuine capability rather than procedural compliance. After reading, you will know how to sequence the document, where Bank of England scrutiny concentrates, and how to handle shortcomings with credibility intact.
Where internal confidence may exceed external evidence
Polar Insight helps leadership teams test critical assumptions against stakeholder, market, regulatory, and operational reality before risk compounds.
Explore Stakeholder Proximity