Skip to main content

How to Structure an Operational Resilience Self-Assessment Under PRA SS1/21

A practical guide to building a self-assessment that evidences impact tolerances with intellectual honesty, including how to treat mapping gaps as findings rather than hide them. Readers will finish with a clear structure, a credible approach to residual weaknesses, and a sharper view of what the PRA actually expects boards to own.

The PRA reads self-assessments to test two things: whether the firm can remain within impact tolerances during severe but plausible disruption, and whether leadership genuinely understands where it cannot. A document that polishes over mapping weaknesses fails both tests. The firms that land well are those that treat mapping gaps as evidenced findings with owners and dates, not as embarrassments to obscure.

Start With the Logic the PRA Will Follow

Supervisors read in a specific order: important business services, impact tolerances, mapping, scenario testing, vulnerabilities, remediation, governance. Structure the document to mirror that order. If a reviewer has to jump between annexes to connect a tolerance to the mapping that supports it, you have already lost credibility.

For each important business service, the reader should be able to trace a single thread: why it is important, what harm the tolerance is calibrated to prevent, which resources support delivery, where the mapping is complete, where it is not, what testing has been done, what the test revealed, and what is being done about it.

Treat Impact Tolerances as Calibrated Judgements, Not Numbers

The common failure is presenting tolerances as outputs of a formula. The PRA expects to see the judgement: what harm to consumers, market integrity, or safety and soundness was considered, which metrics were chosen and why, what alternatives were rejected. Where tolerances are expressed in time, explain why time is the right unit for that service. Where they combine time with volume or value thresholds, show the harm logic behind the combination.

Good self-assessments include a short tolerance rationale per service, typically half a page, that a non-expert board member could defend under questioning.

Map What You Know, Flag What You Do Not

This is where most firms get into trouble. Mapping is almost never complete to the level SS1/21 implies, particularly for legacy technology estates, intra-group dependencies, and fourth-party concentrations. The instinct is to present mapping as more mature than it is. Do not.

Instead, use a maturity scale per resource category per service: for example, complete and tested, complete and untested, partial with known gaps, material gap under remediation. Then evidence it. A partial mapping that is clearly labelled, with a dated remediation plan and an accountable SMF, is a stronger position than a claim of completeness the supervisor will unpick in the first meeting.

The PRA has told firms repeatedly that honest gap disclosure is treated more favourably than defensive presentation. Act on that.

Make Scenario Testing Do Real Work

Scenarios should be severe but plausible, and they should stress the mapping, not confirm it. If every scenario concludes the firm remained within tolerance, the testing is too soft. Include at least one scenario per important service where tolerance was breached or would have been without compensating action, and explain what that revealed.

Tie each scenario to specific mapped resources. If a scenario cannot be run properly because mapping is incomplete, say so, and record it as a testing limitation with a remediation date.

Vulnerabilities and Remediation: The Section That Gets Read Twice

Supervisors spend disproportionate time here. Each vulnerability needs: the service affected, the resource or dependency involved, the tolerance implication, the remediation action, the SMF owner, the target date, and the interim mitigation. Vague remediation ("enhance monitoring", "review controls") will be challenged. Specificity signals grip.

Group vulnerabilities by theme where patterns exist: third-party concentration, legacy platform fragility, data lineage gaps. Themes show the board is thinking across services, not just within them.

Evidence Board Ownership Through Challenge, Not Sign-Off

Minutes showing the board tested tolerance calibrations, questioned mapping completeness, or pushed back on scenario severity carry more weight than a signed foreword. Reference specific board and committee discussions by date. Where the board accepted residual risk, record the rationale.

The Decision Point

Before submission, ask one question: if the PRA interviewed your Chief Operations SMF and your Chair separately, would their accounts of the firm's real vulnerabilities match what the document says? If not, rewrite the document, not the answer.

Frequently Asked Questions

How detailed should mapping be for shared services and intra-group dependencies?

Detailed enough to identify the specific resource, location, and substitutability. "Group IT provides hosting" is not mapping. Name the platform, the location, the recovery arrangement, and the contractual basis. Intra-group dependencies attract particular supervisory interest post-DORA.

What is the right posture on mapping gaps we cannot close before the next assessment?

Disclose, prioritise, and evidence interim mitigation. A credible multi-year remediation plan with board oversight is acceptable. An undisclosed gap discovered by the supervisor is not.

How many scenarios are enough?

There is no number. Enough to stress each important service against its most material vulnerability categories, including at least one cyber, one third-party, and one people or facilities scenario. Quality and honesty of testing matter more than count.

Should the self-assessment be written for the board or the PRA?

Both, which means plain language, traceable logic, and no hidden assumptions. If the board cannot follow it, the PRA will conclude the board did not own it.

Frequently asked questions

How detailed should mapping be for shared services and intra-group dependencies?

Detailed enough to identify the specific resource, location, and substitutability. "Group IT provides hosting" is not mapping. Name the platform, the location, the recovery arrangement, and the contractual basis. Intra-group dependencies attract particular supervisory interest post-DORA.

What is the right posture on mapping gaps we cannot close before the next assessment?

Disclose, prioritise, and evidence interim mitigation. A credible multi-year remediation plan with board oversight is acceptable. An undisclosed gap discovered by the supervisor is not.

How many scenarios are enough?

There is no number. Enough to stress each important service against its most material vulnerability categories, including at least one cyber, one third-party, and one people or facilities scenario. Quality and honesty of testing matter more than count.

Should the self-assessment be written for the board or the PRA?

Both, which means plain language, traceable logic, and no hidden assumptions. If the board cannot follow it, the PRA will conclude the board did not own it.

Related guides

Regulation & Regulatory Change

How to Structure a MIFIDPRU ICARA That Evidences Adequate Own Funds

A practical guide to building an ICARA submission under FCA IFPR that demonstrates genuine capital adequacy and sound risk judgement. Readers will understand how to sequence the assessment, calibrate own funds and liquid assets credibly, and engage supervisors in a way that stands up to challenge.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

How to Structure an FCA Business Model Assessment Response

This guide explains how to construct a Business Model Assessment (BMA) response that credibly evidences strategic viability and prudent risk ownership. Readers will learn how to sequence the narrative, align financial projections with stated strategy, and address weaknesses in a way that demonstrates genuine control rather than defensiveness.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

How to Structure a Pillar 3 Disclosure That Protects Competitive Position

A practical guide to building a CRR Pillar 3 disclosure that meets market transparency expectations in full while handling genuinely sensitive information through the mechanisms the framework provides. Readers will finish with a clearer view of how to sequence drafting, apply the proprietary and confidential carve-outs properly, and defend disclosure judgements to auditors, the PRA, and the board.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Recovery Plan Under SS9/17 Without Resolvability Drag

A practical guide to building a Recovery Plan submission that evidences credible, executable recovery options while avoiding content that undermines the firm's resolvability position. Covers the sequencing, stakeholder choreography, and judgement calls that separate a plan the PRA accepts from one that triggers follow-up.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Section 165 Response That Protects Privilege

A practical guide to responding to FCA Section 165 information requests in a way that meets the firm's statutory disclosure duties in full while preserving legal professional privilege. Readers will understand how to scope, sequence, and document a response that is both credible to the supervisor and defensible in later proceedings.

Regulatory submissionRegulatorsBoards
4 min readRead guide →

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