Testing Compliance Readiness Against Regulator Reality: A Validation Guide

The disagreement is a signal, not a problem

When compliance says you are ready and sales says regulators will push back, both are usually partly right. Compliance is measuring the wrong thing (technical conformance with rule text) while sales is sensing the right thing (supervisory posture, peer treatment, and how regulators actually behave when the rule bites) without being able to prove it.

Your job is not to pick a winner. It is to work out which parts of each view are grounded in evidence and which parts are grounded in assumption. That requires structured validation, not more internal debate.

Separate the two questions

Compliance is answering: does our documented approach meet the letter of the regulation?

Sales is answering: will the regulator, in practice, accept our interpretation, our timing, our customer communications, and our commercial model?

These are different questions. Firms get into trouble when they treat a green light on the first as a green light on the second. The rulebook tells you what is required. Supervisory behaviour tells you what is tolerated, expected, and quietly disapproved of. The gap between the two is where enforcement action lives.

Build the evidence base before the meeting

Before convening the two sides again, gather three specific inputs.

Peer behaviour

What have comparable firms filed, published, or been sanctioned for on this regulation? Look at Dear CEO letters, s166 outcomes, published enforcement notices, and industry association submissions. If three peers have adjusted their approach in the last six months, that is data. If your interpretation is materially more aggressive than peers, sales is probably right to be nervous.

Regulator signalling

Read the speeches, not just the policy statements. Supervisors telegraph priorities months before they act on them. Pay attention to which specific behaviours are being called out, which firms are being named, and which phrases are being repeated. If your compliance readiness document does not address the themes senior supervisors are speaking about publicly, you have a gap.

Supervisory relationship history

What has your firm's supervisor said in the last four quarterly meetings? What follow-up requests are still open? A firm with unresolved thematic findings on adjacent topics will be treated differently to one with a clean history, even under the same rule.

Run a structured challenge session

Bring compliance, sales, risk, and a senior independent voice (a non-executive, external counsel, or a specialist advisor) into one room. Structure it deliberately.

First, compliance presents the readiness assessment with the specific evidence supporting each conclusion. Not the policy, the evidence.

Second, sales presents the specific pushback scenarios they anticipate, tied to specific customer interactions, product features, or commercial practices. Vague concern is not useful. "When we explain the new fee structure to advised clients, we expect complaints that will draw supervisory attention" is useful.

Third, the independent voice tests both. Where is compliance relying on interpretation rather than confirmed regulator view? Where is sales relying on instinct rather than pattern?

What good validation looks like

You finish this process with a written view that identifies: the areas where compliance and external evidence align (proceed), the areas where sales concerns are supported by peer or supervisory signals (mitigate before go-live), and the areas where neither side has enough evidence (test directly, through trade body channels, supervisory dialogue, or targeted external research).

The third category is where most firms fail. They treat absence of evidence as evidence of absence, and discover post-launch that the regulator had a settled view they never asked about.

What most firms get wrong

They resolve the disagreement by hierarchy. The CRO or CEO picks a side, usually compliance, because compliance owns the formal accountability. Sales concerns get logged and ignored. Six months later, the pushback sales predicted arrives, and the post-mortem concludes that the warning signs were there.

The fix is procedural: no major regulated launch proceeds without a documented reconciliation of the compliance view and the commercial view, tested against external evidence, with named owners for any unresolved items.

Your next decision

Before your next steering committee, ask for one document: a side-by-side of what compliance is confident about, what sales is worried about, and the specific external evidence supporting each. If that document cannot be produced in a week, you do not yet know whether you are ready. That is the answer you need.