Skip to main content

Pressure-Testing Regulator Support Before You Commit Capital

This guide sets out how to stress-test leadership's assumption that regulators and policy stakeholders back your approach, and how to surface objections that rarely make it into formal meetings. After reading, you will have a practical method for separating polite acknowledgement from genuine support before you spend serious money.

Start by naming the assumption precisely

Most regulatory misreads begin with imprecise language. "The PRA is comfortable with our approach" can mean anything from "a supervisor nodded in a meeting" to "we have written confirmation of no objection." Before you test anything, force your team to write down exactly what is being assumed, by whom, based on what evidence, and at what date.

A useful discipline: for each key assumption, record the source (named individual, not institution), the forum (formal submission, sidebar, industry roundtable), the specificity of the signal (general encouragement versus reaction to a concrete proposal), and how recent it is. Assumptions that fail on any of these four dimensions are candidates for retesting.

Separate the three types of regulator signal

Senior teams routinely conflate three very different things:

  1. Acknowledgement: the regulator has heard your position.
  2. Tolerance: they will not actively oppose it.
  3. Support: they will defend it internally or externally if challenged.

Most strategic bets require the third. Most feedback you receive is the first. Ask, of every supportive signal: would this person argue for our approach in a room where we are not present? If you cannot answer yes with evidence, treat it as acknowledgement only.

Map the decision-makers behind the decision-maker

The named supervisor or policy lead is rarely acting alone. Behind them sit technical specialists, legal advisers, cross-authority working groups, and international counterparts whose views shape the official position. Your assumption of support may rest on one relationship while the actual decision runs through five people you have never spoken to.

Build a chart of who influences the position, who signs off, and who can veto. Then ask which of those people you have direct evidence from, and which you are inferring about. The inferred ones are where hidden objections live.

Run structured challenge, not just internal debate

Internal red-teaming has limits. Your own people share your priors. Three techniques work better:

  • Former regulators on retainer, briefed to argue the case against your approach as if they were still inside the authority. Pay them to be uncomfortable, not agreeable.
  • Anonymous soundings through trade bodies or law firms who can ask the awkward question without attaching your name to it. What comes back is often sharper than what you hear directly.
  • Adjacent firm intelligence: quiet conversations with peers who have raised similar issues. If three competitors received cool responses on a related question, your warm reception deserves scrutiny.

Test with a smaller, reversible move first

Before committing the full compliance budget, find a lower-stakes action that would only make sense if your assumption holds: a technical consultation response, a pilot request, a specific data submission, a formal meeting request with a defined agenda. The response you get, in tone, speed, and specificity, tells you more than months of general engagement.

What good looks like: the regulator engages with the substance and pushes back on specifics. What tells you the assumption is wrong: vague encouragement, delays, or redirection to a different team.

Watch for the four warning signs

Hidden objections usually announce themselves before they detonate. Look for:

  • Supervisors asking the same clarifying question in successive meetings (they are not satisfied with your answer).
  • Written follow-ups that soften what was said verbally.
  • A shift from named individuals to "the authority" in correspondence.
  • Requests for information that seem tangential (often the real concern lives there).

Most teams explain these away. Treat each one as a signal to reopen the assumption.

What most leadership teams get wrong

They confirm rather than test. Meetings are scheduled with friendly contacts, briefings emphasise progress, and dissenting internal voices get labelled as unhelpful. By the time an objection surfaces formally, capital is committed and the political cost of reversing is high.

The fix is cultural as much as procedural: reward the person who finds the objection, not the person who reports smooth engagement.

Your next step

Pick the single largest regulatory assumption underpinning your current strategy. Write it down in one sentence, with source, date, and specificity. Then ask: if this assumption is wrong, when will we find out, and how much will we have spent by then? If the answer to the second question is uncomfortable, you have a testing programme to design this quarter, not next.

Polar Insight helps senior leaders in financial services understand what their key stakeholders actually think before significant decisions are made.

Book a conversation