Skip to main content

Structuring a PRA NBSU Mobilisation Exit Application That Demonstrates Readiness

A practical guide to preparing a mobilisation exit submission that gives the PRA and FCA confidence the bank is genuinely ready to operate without restrictions. Covers evidence structure, sequencing with supervisors, and the areas where applicants most often fall short.

Exiting mobilisation is not a paperwork exercise. It is the moment the PRA and FCA decide whether your bank can operate as a fully authorised deposit-taker without the safety rails of restricted deposit limits. Applicants who treat the exit as a status update rather than a fresh evidential case tend to receive extended timelines, further information requests, or conditions carried into full authorisation. The bar is genuine operational readiness, evidenced at a level a supervisor can test.

Start with the supervisory question, not your internal narrative

The PRA is answering one question: can this bank be released from restrictions without material risk to depositors, financial stability, or its own viability? Structure the application around that question. Every section should let a reader confirm, with primary evidence, that a specific readiness criterion is met. Internal milestones, board journeys, and mobilisation history are context, not the substance.

The strongest applications open with a concise readiness statement from the CEO and Chair that maps directly to the conditions imposed at authorisation and the commitments in the Regulatory Business Plan. Each commitment gets a status, evidence reference, and a named accountable SMF.

Build the evidence pack before you draft the narrative

Most weak submissions are written first and evidenced second. Reverse that. Assemble the artefacts, then write to them.

The pack should include: signed policies with version control, operating procedures with live process owners, ICAAP and ILAAP with board approval dates and reverse stress tests that actually bite, recovery plan with tested playbooks, outsourcing register with executed contracts and exit plans, financial crime framework with completed customer risk assessments and tested transaction monitoring rules, SMCR documentation including Statements of Responsibilities and a current responsibilities map, and audited or reviewed opening financials.

Where something is not yet live because it depends on lifting restrictions, say so plainly and describe the parallel-run or dress-rehearsal evidence that substitutes for it.

Address the four areas supervisors probe hardest

Capital and liquidity credibility

The ICAAP and ILAAP must reflect the post-mobilisation business, not the mobilisation shell. Show the capital plan under base, stress, and reverse stress with clear management actions and trigger points. If you are relying on further capital injections post-exit, evidence committed funding, not indicative support.

Third-party and technology resilience

Core banking, payments, and cloud arrangements should be contracted, tested, and covered by exit plans that are more than templates. Include penetration test results, incident response rehearsal outcomes, and evidence of your ability to meet operational resilience impact tolerances for important business services.

Financial crime controls

Demonstrate the framework works in practice: sample customer files across risk tiers, tuning evidence for monitoring thresholds, SAR process walk-throughs, and MLRO reporting to the board. Model-based claims without transaction evidence are a common weakness.

Business plan realism

Pipeline, unit economics, and funding assumptions should reconcile to the plan submitted at authorisation. Material divergence is not fatal, but it must be explained with revised projections and, if needed, a refreshed capital view.

Sequence engagement with the case officer

Book a pre-submission meeting before you finalise. Walk through your readiness self-assessment, flag known gaps, and agree what evidence format works. This is where credibility is built or lost. Submitting cold, with unresolved issues buried in appendices, is the fastest route to extended restrictions or conditions.

After submission, expect follow-up questions within weeks. Prepare a small, senior response team with authority to sign off answers quickly. Slow, inconsistent responses signal governance weakness.

What good looks like

A good exit application reads as though the bank is already operating at full scale. Policies are used, not filed. Committees meet with real papers and real decisions. The three lines of defence show independent challenge with documented outcomes. Residual risks are named, owned, and mitigated with dates.

The decision point for the executive team is straightforward: if you cannot evidence readiness to the standard above today, delay submission and close the gaps. A short delay is materially cheaper than conditions carried into full permissions.

Frequently Asked Questions

How long does the exit process typically take once submitted?

Plan for three to six months from submission to decision, longer if material gaps emerge. Front-loading engagement with the case officer usually compresses this.

Can we exit mobilisation with some conditions still in place?

Yes, but conditions carried into full authorisation constrain commercial activity and signal residual supervisory concern. Where possible, close issues before exit rather than accept conditions as the price of speed.

What role should Internal Audit play in the exit submission?

An independent readiness review by Internal Audit or a qualified third party, covering the same criteria the PRA will test, materially strengthens the application and surfaces gaps before supervisors do.

How much should the business plan be updated from authorisation?

Update it to reflect current reality. Supervisors expect divergence over the mobilisation period. What they do not accept is a plan that quietly ignores changed assumptions on funding, pricing, or customer acquisition.

Who should sign the submission?

The CEO and Chair, with the SMF2 (CFO) and SMF4 (Chief Risk Officer) explicitly attesting to the financial and risk evidence respectively. Named accountability throughout the pack matters more than a single cover signature.

Frequently asked questions

How long does the exit process typically take once submitted?

Plan for three to six months from submission to decision, longer if material gaps emerge. Front-loading engagement with the case officer usually compresses this.

Can we exit mobilisation with some conditions still in place?

Yes, but conditions carried into full authorisation constrain commercial activity and signal residual supervisory concern. Where possible, close issues before exit rather than accept conditions as the price of speed.

What role should Internal Audit play in the exit submission?

An independent readiness review by Internal Audit or a qualified third party, covering the same criteria the PRA will test, materially strengthens the application and surfaces gaps before supervisors do.

How much should the business plan be updated from authorisation?

Update it to reflect current reality. Supervisors expect divergence over the mobilisation period. What they do not accept is a plan that quietly ignores changed assumptions on funding, pricing, or customer acquisition.

Who should sign the submission?

The CEO and Chair, with the SMF2 (CFO) and SMF4 (Chief Risk Officer) explicitly attesting to the financial and risk evidence respectively. Named accountability throughout the pack matters more than a single cover signature.

Related guides

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 →
Regulation & Regulatory Change

How to Structure a Section 178 Change in Control Notification That Holds Up

A practical guide to assembling a Section 178 notification that the PRA and FCA can assess on first pass, without multiple rounds of clarification. Covers sequencing, evidence quality, and the judgement calls that determine whether the 60 working day clock runs clean.

Regulatory submissionAcquisitionRegulators
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Dear CEO Letter Response That Lands Credibly

This guide sets out how to construct a Dear CEO letter response that answers the FCA's concerns with evidence, candour, and proportionate commitments. After reading it, you will know how to sequence the response, calibrate tone, and close the loop in a way that builds supervisory trust rather than prompting further questions.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Section 167/168 Investigation Response Strategy

A practical guide to building an investigation response that protects the firm's legal and commercial interests while demonstrating genuine cooperation with the FCA. Readers will finish with a clear framework for governance, document handling, witness preparation, and stakeholder sequencing in the first critical weeks of an investigation.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Boards, Governance & Defensibility

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.

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