Testing Your Regulator Map Before a Compliance Overhaul

Start by writing down what you're assuming

Before you test anything, force the assumptions into the open. Most compliance overhauls carry three unstated beliefs: which regulator will drive the approval outcome, what that regulator cares about most, and how they'll weigh trade-offs when your design creates tension between competing priorities. Programme leaders rarely articulate these. They just build.

Write a single page. Name the regulator you think holds the pen. Name the specific team or division within that regulator. State what you believe their top three priorities are for a firm like yours right now. State what you believe they'll accept as a trade-off. This is your hypothesis. Everything that follows tests it.

Separate the formal approver from the decisive voice

The regulator whose sign-off you formally need is often not the one whose view will shape the outcome. On a major overhaul, you may have a lead supervisor, a specialist function (financial crime, prudential, conduct, operational resilience), and a policy team all with a stake. The formal approval sits with one. The decisive input frequently comes from another.

Map the actual influence flow. Who briefs whom internally at the regulator? Which specialist teams have a track record of blocking or reshaping submissions in your area? Ask your regulatory counsel and your former-regulator advisers for a candid read, and press them when their answers converge too neatly. Convergence often reflects shared assumptions rather than shared evidence.

Test priorities against current supervisory behaviour, not published priorities

Published business plans and Dear CEO letters tell you what regulators say they care about. Supervisory behaviour tells you what they actually push on. These diverge more than firms admit.

Gather three inputs:

• Recent enforcement actions and public censures in your sub-sector from the last 18 months. What themes recur?
• Section 166 or equivalent skilled person reviews commissioned recently. The scope tells you what supervisors are worried about but can't yet prove.
• Feedback peers have received on similar submissions or thematic reviews. Your industry association and your Big Four advisers see patterns you can't.

Compare this evidence against your assumption page. Where does it confirm? Where does it contradict? Contradictions are the point.

Have the conversation before you build the case

Request a pre-submission meeting with your supervisor. Frame it as scoping, not selling. Present the problem you're solving and the two or three design directions you're weighing. Do not present a preferred solution. You want their reaction to the trade-offs, not their sign-off on your answer.

What good looks like: you leave the meeting knowing which of your assumptions were wrong, which specialist teams the supervisor will consult, and what evidence they'll expect. What most people get wrong: they arrive with a polished pitch, get polite nods, and mistake the absence of objection for endorsement. Supervisors rarely object to what they haven't yet been asked to approve.

Triangulate through indirect channels

Direct conversation is necessary but insufficient. Supervisors are careful about what they signal in bilateral meetings. Priorities show up more honestly in speeches by senior regulators, in the questions asked at industry roundtables, and in the framing of consultation responses.

Read the last six months of speeches from the specific division you're dealing with. Note the shifts in language. If operational resilience language is being folded into third-party risk framing, that tells you something about how a future submission will be read.

Re-run your assumption page

After this work, rewrite the page. What changed? If nothing changed, you probably didn't test hard enough. Typical corrections: the decisive team is a specialist function you'd underweighted; the priority you assumed was central has been overtaken by a newer concern; the trade-off you thought was acceptable will actually trigger escalation.

Now you can design the overhaul against a validated view rather than an inherited one.

The decision point

Before you approve the programme budget, ask your executive sponsor one question: can we name the specific individuals at the regulator whose view will decide this, and can we point to evidence, not inference, for what they want? If the answer is no, delay the budget approval by four weeks and do this work. It's the cheapest four weeks you'll spend on the programme.