When Board Assumptions About Regulators Diverge From Approval Reality

The gap that kills approvals

Boards form views about regulator priorities from speeches, published strategies, prior interactions, and adviser briefings. Decision-makers inside the regulator operate from supervisory concerns, case precedent, internal escalation thresholds, and the political weather of the month. These two pictures overlap, but they are not the same. When the board assumes alignment that does not exist, the consequences show up late: in a Section 165 request, a deferred decision, a conditional approval with terms that break the business case, or a quiet signal that withdrawal would be wise.

The risk is not that boards misunderstand regulation. It is that they misjudge which concerns are live, which are dormant, and which decision-maker actually holds the pen.

Where the mismatch usually comes from

Three sources account for most failures.

Stale intelligence. The board's mental model was built 18 months ago, when the previous director was in post, before the latest enforcement action, before the policy team reorganised. Priorities shift faster than board papers refresh.

Adviser optimism. External counsel and consultants are incentivised to confirm feasibility. They report what regulators have said publicly, not what case teams are pushing back on privately. The signal that matters, what is being asked of comparable firms in week six of their approval, rarely reaches the boardroom.

Confusing principals with agents. The Chair of the regulator gave a speech about innovation. The case officer reviewing your application is worried about operational resilience and the wind-down plan. Both views are real. Only one decides your approval.

The risks that actually materialise

Conditions that gut the economics

Approvals come with capital add-ons, growth caps, governance undertakings, or customer segment restrictions that were not modelled. The board signed off on a plan that no longer exists by the time the licence is issued.

Sequencing failure

The board pushes for submission to hit a commercial deadline. The regulator was signalling, through choice of questions and pace of engagement, that it was not ready. The application lands, stalls, and the firm burns credibility it will need later.

Loss of optionality

Once a position is taken in writing with a regulator, it is hard to walk back. Boards that assume flexibility on, say, outsourcing arrangements or board composition often find the first written response has already closed doors.

Reputational drag inside the regulator

Firms that misread priorities get categorised. The label, ambitious but not listening, or technically strong but governance-light, persists across teams and survives personnel changes.

What to do about it

Separate the public position from the operating position. Commission, internally or externally, a written view of what the relevant case team is actually focused on this quarter. Not the strategy document. The live concerns. If no one can produce this, that is the finding.

Identify the actual decision-maker and their constraints. Not the named senior responsible officer, the person whose recommendation will be accepted. Understand what would cause them to escalate, defer, or attach conditions. Their risk appetite is the one that matters.

Stress-test the board's assumptions before submission, not after. Run a structured challenge session: list the five things the board believes the regulator will accept, and the evidence for each. Where the evidence is a speech, a prior conversation, or adviser assurance, treat it as untested.

Build a private early-warning channel. Pre-application meetings, technical sessions, and informal soundings are the cheapest intelligence you will get. Boards that rely solely on formal correspondence are reading the regulator with a six-week lag.

Re-paper the board when the picture changes. If priorities shift mid-process, say so explicitly in board papers. The instinct to reassure is the instinct that produces approval failures.

What good looks like

A board that can articulate, in one page, the difference between the regulator's published priorities and the case team's operating concerns, and has adjusted the application accordingly. A CEO who has tested the firm's assumptions with someone outside the deal team in the last 30 days. A submission timeline driven by regulator readiness, not internal pressure.

The next decision

Before your next board meeting on a regulated approval, ask one question: what is our evidence that the case team agrees with our reading of their priorities? If the answer relies on public statements or adviser confidence, you have work to do before submission, not after.