Reading Regulator Priorities Correctly Before a Major Approval

The problem with how leadership teams read regulators

Most executive teams walk into a major approval process believing they understand what the regulator wants. They have read the speeches, met the supervisors, and worked through the rulebook. What they usually miss is the gap between what regulators say publicly and what actually drives a decision inside the authority. That gap is where approvals are lost.

The blind spots below are the ones we see most often at board and ExCo level. They are not failures of intelligence. They are failures of perspective.

Blind spot 1: Confusing the published priorities with the operational ones

Regulators publish strategic priorities annually. These documents are accurate but incomplete. The operational priorities, what supervisors are actually being measured on this quarter, are rarely the same. A bank reading the FCA business plan and assuming it knows what the case officer cares about is making a category error.

What good looks like: a clear distinction in your internal briefing between the regulator's stated agenda, the supervisory team's current pressure points, and the personal priorities of the individuals who will write the recommendation. All three matter. They are not the same thing.

Blind spot 2: Underweighting the regulator's recent failures

Approval decisions are shaped heavily by what the regulator got wrong last. If a supervisor was burned by a firm that looked strong on capital but failed on governance, expect every subsequent applicant to face sharper governance scrutiny, regardless of what the formal criteria say. Leadership teams routinely miss this because they read the rulebook rather than the enforcement actions and Section 166 reviews.

Before filing, map the last 24 months of enforcement, public censures and dear CEO letters from your specific regulator. The themes you find there will tell you more about your reception than any policy document.

Blind spot 3: Assuming the regulator speaks with one voice

In most authorities, the prudential team, the conduct team, the authorisations team and the policy team have different views, different incentives, and sometimes different reads on the same firm. Treating the regulator as a single actor is the most common error we see. It produces submissions that satisfy one function and antagonise another.

The fix is to identify, by name where possible, who will be consulted internally on your application, and to test whether your proposition holds up against each of their priorities. If you cannot name them, you are not ready to file.

Blind spot 4: Misreading the political overlay

Regulators are not political actors, but they operate inside a political reality. Treasury pressure, parliamentary scrutiny, recent press coverage, and the government's growth agenda all shape risk appetite at the authorisation stage. A regulator that has just been criticised for being too permissive will not approve your transaction on its technical merits alone.

Good teams build a short, honest read of the current political pressure on their regulator into the approval strategy. Most teams skip this entirely and treat it as noise.

Blind spot 5: Believing your relationship will carry you

Senior executives consistently overestimate how much goodwill they have banked with the regulator. Relationships help at the margin. They do not survive a weak case, and they do not transfer when the supervisor changes, which happens often. If your strategy assumes the regulator trusts you, stress test it by assuming the person on the other side is new, sceptical, and reading your file cold.

What to do before you file

Run a structured pre mortem with three questions. First: if this application is rejected or delayed, what is the most likely reason the regulator will give, in their words, not ours? Second: which of the five blind spots above is most likely to be at work in our current thinking? Third: who inside the authority has not yet been considered, and what would they say if asked?

If you cannot answer those questions with specifics, you have more work to do before submission. The cost of doing that work now is small. The cost of discovering the answer through a Minded to Refuse letter is not.

The decision point

Before your next steering committee, ask your team to present the regulator's view of your application, not yours. If the answer sounds like your own pitch deck with the logos changed, you are not ready.