How to Structure an RRP Data Submission That Meets Bank of England Expectations

The quality of an RRP data submission is judged less on volume than on coherence. The Bank of England's Resolution Directorate reads submissions to test whether a firm genuinely understands its own structure, dependencies and resolvability, not whether it can populate a template. A submission that reconciles cleanly across legal entity, financial and operational views signals a firm that could actually be resolved. One that does not signals the opposite, regardless of how polished the narrative appears.

Start With the Resolution Entity Perimeter

Before any template is populated, fix the resolution group perimeter and the preferred resolution strategy you are supporting. A single point of entry bail-in strategy demands different data cuts from a multiple point of entry or modified insolvency approach. Firms that begin with templates and work backwards to strategy produce submissions that look internally inconsistent because they are. Confirm the strategy with the Bank's account manager before you commit engineering effort.

Build the Data Spine in This Order

Sequencing matters. The following order avoids the most common rework cycles:

1. Legal entity hierarchy and booking model, including branches, SPVs and service companies.
2. Critical functions and critical shared services mapped to the entities that house them.
3. Financial MI at solo and consolidated level, aligned to the same entity perimeter.
4. Contractual data: financial contracts, operational contracts, intragroup arrangements, and the resolution-resilience clauses within them.
5. Operational continuity data: staff, systems, properties, third parties, and the service catalogue connecting them.
6. FMI dependencies and the contingency arrangements that support continued access.

Each layer should reconcile to the one above it. If your critical functions sit in entities that do not appear consistently in your financial MI, the submission will fail its first integrity check.

Treat Data Lineage as a First-Order Deliverable

For every material data point, document the source system, the extraction logic, the transformation steps, the owner, and the control that evidences accuracy. The Bank increasingly asks firms to walk through how a specific number was produced. Firms that cannot answer within the meeting lose credibility that takes years to rebuild. A short lineage appendix for the twenty or thirty most sensitive data points is worth more than a hundred pages of methodology prose.

Reconcile Recovery and Resolution Views Explicitly

Recovery indicators, early warning thresholds and resolution data should be visibly consistent. If your recovery plan assumes a capital action is executable in a stress, the resolution submission should show the legal, operational and contractual conditions that make it so. Divergences between the two documents are among the most frequently cited supervisory findings. Build a single reconciliation schedule that maps each recovery option to the resolution-relevant entities, instruments and dependencies it touches.

What Good Looks Like

A credible submission reads as one document produced by one firm. Entity names, function definitions, service taxonomies and financial figures match across every annex. Assumptions are stated once and referenced thereafter. Known weaknesses are disclosed, scoped and accompanied by a remediation plan with dates and owners. The tone is factual rather than defensive. Where the firm has made judgements, those judgements are visible and justified.

What Most Firms Get Wrong

Three failure patterns recur. First, templates are populated by workstream silos that never reconcile, producing a submission that contradicts itself. Second, the Resolvability Assessment Framework barriers are treated as narrative rather than evidenced with data. Third, the Board is shown a summary that is materially more confident than the underlying data supports, which surfaces awkwardly in the Bank's follow-up questions.

The Next Decision

Before the next submission cycle, commission an independent internal review of the reconciliation layer between your legal entity data, financial MI, critical services register and contractual inventories. If that review cannot be completed cleanly in four weeks, you have a data integrity issue that will surface in supervisory dialogue. Fix it before the Bank finds it.

Frequently Asked Questions

How much narrative should accompany the data templates?

Enough to explain methodology, assumptions and known limitations, no more. The Bank reads the data first and the narrative as context. Over-long narrative often signals that the data cannot stand on its own.

Who should own the submission internally?

A single accountable executive, typically the CFO or a dedicated Resolution SMF, with Board-level visibility. Distributed ownership across Finance, Risk, Legal and Operations without a single integrator is the most common structural cause of inconsistent submissions.

How should we handle known data gaps?

Disclose them, scope them, and commit to a remediation plan with dates. Attempting to mask gaps almost always surfaces during Bank testing and damages credibility more than the gap itself.

How far in advance should we engage the Bank on methodology changes?

At least one full cycle ahead for anything material. Surprising the Resolution Directorate with a methodology shift at submission is a reliable way to invite extended challenge.

What role should internal audit play?

Independent assurance over data lineage and reconciliation, not over strategic judgements. Audit involvement strengthens supervisory confidence that the numbers can be relied on.