Mapping the Stakeholders Behind a Regulatory Approval Decision

If you are preparing for a regulatory approval, whether a change in control, a new permission, a product authorisation or a licence variation, the written submission is only part of what determines the outcome. The decision is shaped by a wider set of people: case officers, policy specialists, supervisors, external advisers, counterparty regulators, and internal governance bodies at the regulator itself. Mapping those stakeholders properly is how you make sure your case is understood on its merits, by the people who actually weigh it.

Key Executive Takeaways

• A regulatory approval is decided by a network of named and unnamed participants, not a single reviewer, and your preparation should reflect that reality.
• The purpose of mapping is to make your case easier to assess accurately, not to lobby, pressure or route around the formal process.
• The most common failure is treating the regulator as a monolith and missing the internal committees, adjacent authorities and third parties whose views carry weight.

Start with the decision, not the people

Before listing names, write down the specific decision you are seeking, the statutory or rulebook basis for it, and the tests the regulator must apply. A change in control approval under FSMA turns on different questions than a Part 4A permission variation or an SMF approval. Each test implies a different set of specialists inside the regulator: prudential, conduct, financial crime, operational resilience, data, or sector policy.

Once you know the tests, you can identify which teams inside the regulator will be asked to opine. That is the real map.

Build the map in four layers

Layer one: the formal decision chain

Identify the case officer, their supervisor, the relevant head of department, and the committee or executive that formally takes the decision. For significant matters this often includes a regulatory decisions committee or an authorisations committee. Understand how the case escalates and at what thresholds.

Layer two: internal consultees

Most approvals involve input from specialist teams the applicant never speaks to directly: financial crime, prudential policy, resolution, data protection liaison, or thematic supervision teams. Your submission has to answer their questions even though they will not ask them of you. If you do not know which specialists will be consulted, assume the full range and address each explicitly.

Layer three: external authorities

For dual-regulated firms, both the PRA and FCA will coordinate. For cross-border matters, home and host regulators, the Bank of England, HMRC, the ICO, or overseas authorities may be consulted. Market infrastructure approvals can draw in the Payment Systems Regulator or the CMA. Map the coordination points and the likely sequencing of their views.

Layer four: your own ecosystem of signals

Auditors, skilled persons, legal counsel, outgoing shareholders, counterparties, and sometimes customers will be referenced or contacted. Their files, past correspondence and public statements form part of the evidence base the regulator weighs. Know what the regulator will see when it looks at them.

Assess each stakeholder on three dimensions

For every person or body on the map, record: what question they are answering, what evidence they will rely on, and what their likely starting position is based on prior interactions, published priorities or known concerns. This is where honest internal challenge matters. If your financial crime controls have been questioned before, the financial crime consultee will arrive with that history. Pretending otherwise wastes everyone's time.

What good preparation looks like

Good preparation means your submission anticipates the questions each stakeholder will ask and provides the evidence in the form they expect. It means your executive sponsors can speak credibly to any part of the case, not just their own function. It means you have raised known weaknesses yourself, with a remediation plan, rather than waiting to be asked.

It does not mean back-channel contact, selective disclosure, or framing designed to obscure. Those approaches damage credibility that takes years to rebuild and often surface during the review itself.

What most people get wrong

The three recurring failures: treating the case officer as the whole audience, underestimating how much weight internal specialist consultees carry, and failing to update the map as the review progresses. Stakeholder maps built at kick-off and never revisited miss the people who join the review at month three.

Your next step

Before your next pre-application meeting, produce a one-page stakeholder map covering all four layers, with each entry showing the question they will ask and the evidence you have prepared. If you cannot complete it, you are not ready to file.

Frequently Asked Questions

How early should stakeholder mapping start?

Before the pre-application meeting. The map shapes what you ask the regulator in that meeting and what you commit to providing.

Should we contact internal regulator specialists directly?

No. Route all contact through the case officer or the formal pre-application channel. Mapping is about anticipating their questions, not approaching them.

How do we handle a stakeholder with a known negative prior view?

Address their concern directly in the submission, with evidence of what has changed. Ignoring a known concern is read as either poor preparation or avoidance.

Who owns the stakeholder map internally?

The accountable executive for the application, usually an SMF holder, with support from regulatory affairs and legal. It should not sit solely with external advisers.

How often should the map be updated?

At every material event: new information requests, personnel changes at the regulator, policy publications relevant to your case, or shifts in your own position.