Validating Stakeholder Support Before a Major Regulatory Filing
When internal teams and external advisors disagree on stakeholder support for a regulatory filing, the cost of acting on the wrong read is severe. This guide sets out how to test both views quickly, identify which is closer to reality, and reach a defensible position before you file.
Start by understanding why the views diverge
Before you try to work out who is right, work out why they disagree. Internal teams and external advisors are usually looking at different evidence, weighted differently, and filtered through different incentives.
Internal teams often rely on direct relationships: what the regulator's case officer said in the last supervisory meeting, what a senior policy lead implied at an industry roundtable, what peers in the sector are quietly saying. This is high-signal but narrow, and it is shaped by the relationship itself. Regulators tell incumbents what they want incumbents to hear.
External advisors, particularly former regulators or specialist counsel, are reading institutional signals: speeches, consultation responses, enforcement patterns, internal politics at the regulator. This is broader but more interpretive, and advisors have a commercial incentive to flag risk.
Neither view is automatically correct. The disagreement itself is the data point. Treat it as a sign that the stakeholder picture is genuinely uncertain, not that one side is wrong.
Separate the question into three parts
Most stakeholder disagreements collapse three different questions into one. Pull them apart:
- Will the regulator approve the filing on its merits? This is a technical question about rules and precedent.
- Will the regulator be politically comfortable approving it now? This is about timing, sector context, and what else is in their inflow.
- Will other stakeholders, consumer groups, MPs, trade press, peer firms, react in a way that creates pressure to refuse or delay? This is about the wider field.
Your internal team is usually strongest on question one. Advisors are usually strongest on questions two and three. If you do not separate them, you will keep arguing past each other.
Run a structured validation in seven to ten days
You do not have time for a full stakeholder review. You need a fast triangulation.
Test the regulator read directly
Request a pre-application meeting or an informal call with the supervisor. Do not ask whether they will approve. Ask about their current concerns in the relevant area, what they have seen go wrong recently, and what evidence they would expect to see in a strong submission. The texture of the answer, what they probe, what they skim, tells you more than any direct question.
Commission two independent reads
Brief one specialist who has not worked on your filing, ideally a former regulator from the relevant team, and one specialist policy or public affairs adviser. Give them the same brief: a one-page summary of the filing and the two opposing views. Ask each to assess probability of approval, key risks, and what would change their view. If both independents land closer to one of your existing camps, that is meaningful. If they land somewhere new, that is more meaningful.
Map the adjacent stakeholders
Identify the five to eight stakeholders outside the regulator whose response will shape the regulator's comfort: relevant consumer bodies, the lead trade body, two or three peer firms, the Treasury Select Committee secretariat where relevant, key journalists. Have a senior person sound out three or four of these informally. You are testing for surprise, not consensus.
What most teams get wrong
The most common error is treating this as a debate to be won internally rather than a hypothesis to be tested externally. Boards spend two weeks in meetings reconciling internal and advisor views, when six well-placed conversations would have settled it.
The second error is over-weighting the most recent regulator interaction. One warm meeting does not mean support. One cool meeting does not mean opposition. Look at the pattern across the last three to four touchpoints.
The third error is asking advisors to validate rather than challenge. If you brief them on which view you prefer, you will get that view back.
What good looks like
A clear, written stakeholder position you can put in front of the board within ten working days, distinguishing what you know, what you have tested, and what remains assumption. Specific names against specific positions. A defined trigger, what would have to change for you to delay or restructure the filing.
Your next decision
Before your next steering meeting, decide one thing: who owns the validation, and what is the deadline. If the answer is the same team that produced one of the two original views, you have not solved the problem. Give it to someone who can be wrong without losing face.
Related guides
Testing Regulator and Decision-Maker Support Before You Build
This guide sets out how to validate whether regulators and industry decision-makers will back your compliance approach before you commit development budget. You will finish with a practical sequence for pressure-testing support, spotting soft opposition, and deciding whether to proceed, adjust, or pause.
Testing Compliance Readiness Against Regulator Reality: A Validation Guide
This guide shows senior leaders how to reconcile a confident compliance assessment with sales leadership's concern about regulator pushback. After reading, you will know how to test both views against external evidence and decide which risks warrant action before go-live.
Checking Your Compliance Strategy Against What Regulators Actually Expect
This guide explains how to test whether your compliance strategy matches the real expectations of regulators and connected stakeholders, rather than the version written in guidance documents. After reading, you will know how to structure that validation work and where the judgement calls sit.
When the Board and Compliance Disagree on Regulator Sentiment
This guide sets out how to resolve conflicting internal signals about regulator support before a product launch in a regulated market. After reading, you will know how to structure a validation exercise that produces a defensible answer, not just a louder opinion.
Validating Regulatory Assumptions Before Committing Compliance Capital
This guide shows senior leaders how to test their reading of regulator priorities before authorising major compliance spend. You will learn where assumptions typically break, which validation methods actually work, and how to sequence testing so you can commit capital with confidence.
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