Where Leadership Teams Misread Regulator Intent on New Rules

The interpretation gap is where supervisory problems start

Most compliance failures on new rules do not stem from wilful breach or weak controls. They come from a quiet mismatch: the firm's reading of the rule, refined through internal debate and legal opinion, diverges from how supervisors actually apply it in practice. By the time that divergence surfaces, usually in a Section 166, a thematic review, or a quiet phone call, the cost of correction has multiplied.

Leadership teams consistently underestimate this gap. Here are the blind spots that matter most, and what to do about each.

Blind spot 1: Treating the rulebook text as the interpretation

Internal teams read the final rules, the policy statement, and perhaps the consultation response. They build the control framework from that text. Regulators, by contrast, interpret rules through a wider lens: speeches, Dear CEO letters, enforcement notices on adjacent rules, and the supervisory priorities for the year.

The rule says what it says. The interpretation is shaped by what the regulator has been worrying about for the last eighteen months. If your reading does not account for that context, you are reading a different document.

What good looks like: A structured review of every relevant regulator communication from the prior two years before finalising your interpretation. Map themes, not just rule references.

Blind spot 2: Confusing legal defensibility with supervisory acceptance

In-house counsel and external firms are trained to produce defensible positions. Supervisors are not running a legal contest. They are forming a judgement about whether your firm understood the spirit of the rule and acted accordingly.

A legally sound position that ignores supervisory expectation will still attract criticism, and often a requirement to remediate. "We took advice" is not a defence against a supervisor who thinks you missed the point.

What good looks like: Test interpretations against likely supervisory framing, not just legal risk. Ask: if a supervisor walked in tomorrow, would they recognise our reading as reasonable, or argue we engineered around the intent?

Blind spot 3: Assuming consistency across the regulator

Firms often assume the regulator speaks with one voice. In reality, supervision teams, policy teams, and enforcement teams can hold different views on the same rule. The policy team that wrote the rule may have had a narrower intent than the supervision team now applying it.

The view that counts is the one held by the people who will assess your firm. That is usually supervision, not policy.

What good looks like: Identify the specific team that will supervise this rule for your firm and test your interpretation against their recent positions and questions, not against the policy team's drafting intent.

Blind spot 4: Over-weighting peer behaviour

"The industry is reading it this way" is reassuring and dangerous. Peer consensus often forms around the most permissive defensible reading, because that is what each firm's commercial teams pushed for. Regulators know this, and thematic reviews are frequently designed to challenge exactly that consensus.

If your interpretation aligns with the industry mainstream, that is information, not validation.

What good looks like: Treat peer alignment as a data point, then stress-test against the opposite case. If the regulator decided the industry consensus was wrong, what evidence would they cite, and do you have a response?

Blind spot 5: Missing the signal in regulator silence

When firms ask supervisors for interpretation comfort and receive a non-committal answer, internal teams often record this as tacit acceptance. It almost never is. Supervisors are trained not to give individual firms an interpretive green light, because doing so transfers risk to them.

Silence is not endorsement. It is preserved optionality, theirs.

What good looks like: Document supervisor responses precisely. If they did not endorse your reading, your file should reflect that, not paraphrase it into comfort.

How to close the gap before it costs you

Build a structured interpretation challenge before implementation locks in. Three practical moves:

1. Run a red team. Assign someone, internal or external, to argue the supervisor's likely position against your proposed interpretation. Make them use real supervisory language from recent communications.

1. Pressure-test with former supervisors. People who have sat on the other side will tell you within twenty minutes whether your reading will hold. Use them before you commit, not after.

1. Sequence implementation so interpretation can be revised. Avoid building controls that are expensive to unwind. Where the rule is ambiguous, design for adjustment.

The decision point

Before the next significant rule lands, ask one question at the executive table: how do we know our interpretation matches the supervisor's, and what evidence would change our view? If the answer is a legal opinion and peer benchmarking, you have not tested it. You have documented it.