How to Prepare a Change in Control Application That Avoids Regulatory Delay
A practical guide to assembling a Change in Control (Section 178) application that regulators can assess efficiently and approve on first pass. Readers will learn how to sequence pre-notification engagement, build an evidenced controller case, and anticipate the questions that typically stall decisions.
Most Change in Control applications stall for predictable reasons: thin source of funds evidence, vague forward business plans, unclear ultimate beneficial ownership, or regulators discovering material facts late. The statutory assessment period only starts when the application is complete, and the FCA or PRA can stop the clock whenever they need more information. The real work is making the submission genuinely assessable on day one.
Key Executive Takeaways
- The 60 working day clock only runs when the regulator deems the application complete, so completeness on first submission is the single biggest driver of timing certainty.
- Pre-notification engagement, done properly, surfaces the hard questions early and lets you address them in the submission rather than under time pressure during assessment.
- Source of funds, controller fitness, and the post-acquisition business plan are where applications most often fall down, and each requires evidenced, documented substantiation rather than assertion.
Start with the controller map, not the forms
Before drafting anything, build a precise ownership and control chart showing every direct and indirect controller at the 10%, 20%, 30% and 50% thresholds, plus anyone exercising significant influence. Include trusts, nominee arrangements, and shareholder agreements that create voting blocs. Regulators will reconstruct this independently, and discrepancies between your chart and public filings or beneficial ownership registers are a reliable way to trigger extended review.
For each proposed controller, identify who signs the controller forms, what jurisdiction they sit in, and what regulatory history they carry. If any controller has prior regulatory interactions, enforcement history, or politically exposed person status, flag it internally now. These issues do not prevent approval, but concealment or late disclosure will.
Use pre-notification seriously
Request a pre-notification meeting with the relevant supervisor well before you intend to submit. Come with a clear transaction summary, the controller map, the funding structure, and your preliminary view on the key assessment criteria: reputation, financial soundness, influence on sound and prudent management, and financial crime risk.
The purpose is not to secure informal approval. It is to understand what the supervisor will want evidenced, where they see sensitivity, and what format they expect. Firms that treat pre-notification as a tick-box exercise lose the chance to shape the submission around genuine supervisory concerns.
Build the source of funds trail properly
This is where applications most frequently fail. Trace every pound of acquisition funding to its origin. For private equity acquirers, this means fund structure, LP composition where relevant, and evidence of committed capital. For individual controllers, bank statements, tax records, and documentation of liquidity events. For debt-funded elements, signed term sheets and lender diligence.
If funds move through multiple jurisdictions or vehicles before reaching the target, document each step. Gaps here attract financial crime scrutiny and will stop the clock.
The business plan is a regulatory document, not a pitch
The post-acquisition business plan should show how the firm will operate under new ownership: governance changes, board composition, SMF appointments, capital and liquidity position, operational model, and any changes to risk appetite or strategy. Three-year financial projections should reconcile to the firm's regulatory returns and show the firm remains viable under stress.
Where the acquirer intends material change (new products, geographic expansion, outsourcing shifts), say so plainly and explain the controls. Discovering undisclosed strategic intent during assessment is corrosive to trust and almost guarantees delay.
What good looks like on submission
A strong submission arrives with: the Section 178 notification forms fully completed, controller forms for every notifiable party with supporting ID and regulatory references, the ownership chart, source of funds evidence pack, the business plan with financial projections, draft revised governance documents, and a covering letter that maps the submission to the statutory assessment criteria. The regulator should not have to hunt for anything.
What typically goes wrong
Late disclosure of a controller, inconsistency between the application and Companies House filings, source of funds evidence that stops at an intermediate vehicle, business plans that contradict the target's existing ICAAP or ILAAP, and SMF candidates who have not yet begun their own approval process. Each of these is avoidable with disciplined preparation.
Next step
Before you draft anything, convene the deal team, legal counsel, and the target's compliance function and build the controller map and funding trace. If either cannot be evidenced cleanly today, fix that before you approach the regulator.
Frequently Asked Questions
How early should we engage the regulator?
As soon as the transaction structure is stable enough to describe accurately, typically eight to twelve weeks before intended submission. Earlier engagement on complex structures is welcomed.
Can the 60 working day clock really be paused?
Yes. The regulator can issue information requests that interrupt the assessment period. A single significant request can add weeks. Completeness on submission is the only reliable protection.
What if a controller has adverse regulatory history?
Disclose it fully, explain the circumstances, and evidence what has changed. Regulators assess fitness in the round. Non-disclosure discovered during assessment is far more damaging than the underlying issue.
Do we need SMF applications ready at the same time?
Ideally yes. Running controller approval and SMF approvals in parallel avoids a gap between completion and the new governance taking effect, which regulators dislike.
What about overseas acquirers?
Expect additional diligence on home state regulatory status, information sharing arrangements, and group supervision. Build in time for home state regulator liaison.
Frequently asked questions
How early should we engage the regulator?
As soon as the transaction structure is stable enough to describe accurately, typically eight to twelve weeks before intended submission. Earlier engagement on complex structures is welcomed.
Can the 60 working day clock really be paused?
Yes. The regulator can issue information requests that interrupt the assessment period. A single significant request can add weeks. Completeness on submission is the only reliable protection.
What if a controller has adverse regulatory history?
Disclose it fully, explain the circumstances, and evidence what has changed. Regulators assess fitness in the round. Non-disclosure discovered during assessment is far more damaging than the underlying issue.
Do we need SMF applications ready at the same time?
Ideally yes. Running controller approval and SMF approvals in parallel avoids a gap between completion and the new governance taking effect, which regulators dislike.
What about overseas acquirers?
Expect additional diligence on home state regulatory status, information sharing arrangements, and group supervision. Build in time for home state regulator liaison.
Related guides
How to Structure a Section 178 Change in Control Notification That Avoids Mid-Transaction Information Requests
This guide sets out how to prepare a Section 178 notification that the FCA and PRA can approve within the statutory 60 working day assessment period without pausing the clock. It shows senior deal principals what regulators actually want to see, where notifications typically stall, and how to sequence the filing to protect transaction timelines.
Structuring a Section 178 Notification That Withstands PRA Group Structure Review
This guide sets out how to prepare a Change in Control notification that presents the acquirer's group with the clarity, completeness, and supervisory logic the PRA expects. After reading, you will know how to sequence disclosures, frame group complexity honestly, and engage the regulator in a way that supports timely approval on the merits.
How to Prepare a Change in Control Application That Avoids Regulator Information Requests
This guide sets out how to prepare a Section 178 Change in Control application that clears the FCA and PRA assessment window without triggering supplementary information requests. Readers will finish with a clear view of what to pre-empt, what to disclose proactively, and where most applications lose time.
How to Build a Regulatory Narrative for a Change in Control Application at a UK Bank or Insurer
This guide sets out how to construct a coherent regulatory narrative for a Section 178 change in control application to the PRA and FCA. After reading it, you will understand how to frame the acquirer story, sequence supervisory engagement, and pre-empt the objections that stall or block approval.
How to Build a Credible ICAAP Narrative That Withstands Supervisory Scrutiny
This guide explains how to construct an ICAAP document that reads as a genuine articulation of risk, capital adequacy and board ownership rather than a compliance artefact. After reading, you will know what supervisors actually test for, where most narratives fall apart, and how to sequence the work so the story holds together under challenge.
Where a specific question needs an outside answer, quickly
Polar Insight's Expert Network connects leadership teams with practitioners who can speak to a precise regulatory, commercial, or stakeholder question before a decision is finalised.
Explore Expert Network