How to Map the Stakeholders Shaping a Regulatory Approval Decision

If you are pursuing a regulatory approval, whether a Part VII transfer, a Change in Control, a variation of permission, a new authorisation, or a product-level clearance, the decision is rarely made by one person reading one file. It is shaped by a network of case officers, technical specialists, senior decision-makers, internal committees, and often external consultees. Mapping that network properly is what separates applicants who engage credibly from those who are surprised by the questions they receive.

Key Executive Takeaways

• A regulatory approval is shaped by a defined set of internal reviewers, technical specialists, and sometimes external consultees, not a single decision-maker, and each has distinct concerns you must understand and address on the record.
• The purpose of stakeholder mapping is to strengthen the quality and completeness of your submission, not to lobby individuals or route around process; good mapping surfaces the questions you should be answering before they are asked.
• Most applicants underestimate the influence of secondary stakeholders such as consumer bodies, other regulators, and internal risk committees, and they discover this too late in the review cycle.

Start with the formal decision architecture

Before you name individuals, document how the decision is actually made. For most FCA and PRA approvals this means identifying the case officer, the head of department, the relevant authorisations or supervision committee, and any statutory decision-maker such as the Regulatory Decisions Committee where relevant. For competition or market-level decisions, add the panels or boards that issue the final view. Write down the sequence: who receives the file first, who challenges it, who signs it off, and at what point external consultation is triggered.

If you cannot describe the decision path in one page, you do not yet understand it well enough to prepare a credible submission.

Identify the technical specialists who will actually read the file

Case officers coordinate, but specialists form the substantive view. Depending on the matter, this could include prudential experts, conduct risk specialists, financial crime teams, operational resilience reviewers, actuarial staff, or data and technology assessors. Each brings a specific lens and a specific set of expectations about evidence.

What good looks like: you can list, for each specialist function likely to review your file, the two or three questions they will ask first and the evidence that answers them. What bad looks like: a submission written for a generalist reader that leaves every specialist wanting more.

Map external consultees and adjacent regulators

Many approvals trigger consultation beyond the lead regulator. A Part VII transfer involves the Independent Expert, policyholder representations, and often overseas regulators. A Change in Control may require coordination with home-state supervisors. Product approvals can involve the Financial Ombudsman Service perspective, consumer panels, or industry bodies. List every party with a formal or informal right to be heard, and note what each has said publicly about similar matters in the past twelve months.

This is where applicants most often get caught out. A consultee raises a concern the applicant had not anticipated, the timetable slips, and the file has to be reopened.

Understand internal governance on your own side

Your board, risk committee, and control functions are stakeholders too. Regulators expect to see genuine internal challenge in the record. Map who has signed what, when, and on what evidence. If your CRO or NEDs have reservations, those need to be resolved and documented before submission, not managed around it.

Capture what each stakeholder actually cares about

For each named stakeholder or function, record three things: their statutory or organisational remit, their known concerns based on published speeches, decisions, and consultation responses, and the specific evidence in your file that speaks to those concerns. If a box is empty, you have a gap to close.

Use the map to improve the submission, not to work individuals

The map is a preparation tool. It tells you which sections of your submission need more depth, which risks need explicit acknowledgement, and which supporting evidence needs to be in the pack rather than available on request. It is not a call sheet for informal lobbying. Regulators expect engagement to run through proper channels, and applicants who try otherwise damage their credibility.

Next action

Before your next pre-application meeting, produce a single-page stakeholder map covering the decision path, the specialist reviewers, the external consultees, and your own internal approvers. Then test your draft submission against it. Every stakeholder should be able to find the answer to their first question within the first ten pages.

Frequently Asked Questions

How early should stakeholder mapping begin?

Before the first pre-application meeting. The map shapes what you ask the regulator and what you bring to the table. Starting after submission is too late.

Should we name individual regulators in our internal map?

Yes, where they are publicly identified as case officers or heads of relevant departments. The point is not to target them personally but to understand the technical perspective they bring based on their published work and prior decisions.

How do we handle stakeholders whose concerns we cannot fully resolve?

Address them directly in the submission. Acknowledge the issue, explain the mitigation, and set out the residual risk and how it will be monitored. Regulators respond better to honest treatment of hard issues than to submissions that appear to gloss over them.

What is the biggest mistake applicants make?

Treating the regulator as a single entity. The file is read by multiple people with different remits, and a submission that satisfies one function while ignoring another will stall.

How often should the map be updated?

At every material milestone: after pre-application feedback, after any change in the transaction or product, and whenever the regulator publishes new guidance or a relevant decision. A stale map is worse than none.