How to Structure a Change in Control Application That Holds Its Timeline

Change in Control applications fail timelines for one reason more than any other: the regulator cannot complete its assessment from what was filed and has to ask. Each formal information request stops the 60-working-day clock, and in practice resets stakeholder confidence as well. The fix is not to file less, or to file artfully. It is to file an application that answers the questions a supervisor will actually ask, in the order they will ask them, with evidence attached.

Key Executive Takeaways

• The statutory clock pauses every time the FCA or PRA issues a formal information request, so the quality of the initial filing determines completion certainty more than any other single factor.
• Supervisors assess five things in substance: who the controller is, where the money comes from, whether the acquirer is financially sound, whether governance and management will remain fit, and what the target firm will look like post-acquisition. Each needs its own evidenced section.
• Pre-notification engagement, done properly, is the single highest-return activity available to the acquirer and is routinely under-used.

Start with pre-notification, and treat it as substantive

For any transaction of scale, complexity, or novelty, request a pre-notification meeting at least six to eight weeks before intended filing. Bring a draft structure chart, a funding summary, and a short note on strategic rationale and post-completion plans. The purpose is not to seek approval in principle. It is to surface the issues the case officer will care about: indirect controllers, PEP exposure, source of funds, regulatory history of the acquirer group, and any proposed changes to the target's business model, capital, or senior management.

What goes wrong here is treating pre-notification as a formality. Teams send a holding note, get a generic response, and lose the chance to calibrate the filing. Good looks like a focused agenda, named attendees from the acquirer, and a written follow-up capturing what the regulator flagged.

Build the controller map before you build anything else

Most delays trace back to the controller analysis. The regulator needs a complete picture of every direct and indirect controller at 10%, 20%, 30% and 50% thresholds, including the natural persons at the top of the chain. For fund structures, GP/LP arrangements, carried interest vehicles, and nominee holdings all need to be mapped and explained, not just drawn.

For each controller requiring a Form A or equivalent, confirm early whether individual forms will be needed, what identity and probity evidence is required, and whether any controller sits in a jurisdiction that will trigger additional diligence. Begin collecting certified documents, regulatory references, and criminal record checks the moment the structure is settled. These take weeks, not days.

Evidence source of funds in a form the regulator can test

A statement that funds come from an institutional investor is not source of funds evidence. The regulator needs to see the chain: ultimate origin, intermediate vehicles, and the mechanics of how funds will reach the target. For debt-funded elements, provide the facility agreement, covenants, and repayment assumptions. For equity, provide investor commitments and drawdown mechanics. If funds pass through multiple jurisdictions, explain why, and anticipate the AML question before it is asked.

Address the post-acquisition firm head-on

Supervisors are assessing the target's safety and soundness after the deal, not just the acquirer's suitability. The application should include a clear statement of intent: business model changes, capital and liquidity post-completion, board and senior management changes, booking model implications, and any planned restructuring. If the answer to any of these is "no change," say so explicitly and evidence it with a board resolution or shareholder undertaking.

Where SMF changes are contemplated, align the Change in Control timetable with SMF application timing. Filing them in parallel, with cross-references, prevents the regulator from having to ask how the two fit together.

Anticipate the second-order questions

The strongest applications include a short section headed something like "matters the regulator may wish to consider," covering known sensitivities: prior enforcement history of any controller, litigation, tax investigations, concentration risk in the acquirer's existing holdings, or anything unusual about the deal structure. Raising these proactively, with context and mitigation, is treated very differently from having them surface mid-assessment.

The decision point before you file

Before submission, ask one question of the application pack: can a case officer who has never met the acquirer complete the assessment from this document alone? If the answer requires any assumption, fill the gap now. Every assumption left in the pack is a future information request, and every information request is a stopped clock.

Frequently Asked Questions

How long should we allow between pre-notification and filing?

Six to eight weeks is a reasonable minimum for straightforward cases. Complex structures, overseas controllers, or novel business model implications can push this to three or four months. Compressing it rarely saves time overall.

What triggers the clock stopping most often?

Incomplete controller information, inadequate source of funds evidence, and unclear post-completion plans for the target. Form A deficiencies for individual controllers are also common, particularly around regulatory references and overseas probity evidence.

Should we file Form A documents for controllers in draft first?

Yes, where the regulator will engage with that. Sharing draft Form As during pre-notification lets the case team flag gaps before the formal clock starts. Not all case officers will do this, but it is worth asking.

How do we handle a controller with a prior regulatory issue?

Address it in the application, with the facts, the outcome, and what has changed since. Attempting to minimise it, or hoping it will not be found, is the single fastest way to lose supervisory confidence and extend the assessment.

Can we start integration planning before approval?

Planning, yes. Execution of anything that assumes control, no. The regulator will ask about pre-completion conduct, and any evidence of de facto control before approval is a serious issue in its own right.