How to Identify What Will Give a Regulator Confidence in a Proposed Change

Regulators do not grant confidence because a change is well-argued. They grant it because the firm has demonstrated it understands the risks, has tested its own thinking, and can be trusted to run the change safely once it goes live. If you want to know what will give a regulator confidence in a proposed change, start by understanding what they are actually assessing: not the change itself, but your capability and honesty in making it.

Key Executive Takeaways

• Regulator confidence rests on three things: evidence the risks are understood, governance that shows the firm challenged itself, and credible controls for what happens after go-live.
• The single biggest failure mode is presenting a polished case without visible evidence of the counter-arguments that were considered and resolved.
• Confidence is built through the pattern of engagement over months, not the quality of a single submission.

Start with the supervisor's job, not yours

A supervisor's role is to protect defined outcomes: consumer protection, market integrity, prudential soundness, operational resilience. When you propose a change, they are asking a narrower question than you are. Not "is this a good idea?" but "can this firm execute this change without harming the outcomes I am responsible for?"

That reframing matters. It tells you the case you need to make is about your firm's capability and self-awareness, as much as the merits of the change itself.

The four things regulators look for

1. Evidence you understand what could go wrong

A proposal that only sets out benefits reads as naive. Confidence comes from showing the failure modes you have identified, the ones you have ruled out and why, and the ones that remain as residual risks with mitigations attached. Name the harms in the regulator's language: customer detriment, market disruption, operational failure, financial loss.

What good looks like: a risk section that a sceptical supervisor could not meaningfully add to.

2. Evidence the firm has challenged itself

Supervisors read board and committee minutes to see whether the change was tested internally or waved through. If the papers show unanimous support with no dissent recorded, that is a red flag, not a green one. Show the questions that were asked, the alternatives considered, the second-line challenge, and how disagreements were resolved.

What most people get wrong: sanitising governance records to look consensual. Regulators read this as weak challenge, not strong alignment.

3. Proportionate, testable controls

Controls should match the risk. Over-engineered controls suggest you do not understand the risk; under-engineered ones suggest you do not take it seriously. Be specific: who owns each control, how it is monitored, what the trigger points are for escalation, and what you will do if it fails.

4. A credible post-implementation plan

Many firms treat go-live as the finish line. Regulators treat it as the start. What metrics will you track? What thresholds will trigger a pause or rollback? Who reviews the change three, six, twelve months out? A clear answer here often does more for confidence than the pre-launch analysis.

Sequence the engagement

Confidence is cumulative. If the first time a supervisor hears about a material change is when the formal submission lands, you have already reduced your chances. Signal early, share thinking in draft, invite challenge before positions harden. This is not lobbying; it is giving the supervisor time to form a view without pressure.

When you engage early, listen for what they push on. The questions they ask reveal the concerns you must address in the formal case. If they raise a point twice, treat it as decisive.

What undermines confidence, quickly

• Inconsistencies between what the submission says and what internal documents show.
• Claims of customer benefit without customer evidence.
• Optimistic timelines that leave no room for issues.
• Silence on the obvious downside case.
• Changes to the proposal that appear only after regulator pushback, suggesting the firm did not spot the issue itself.

The test to apply before submission

Ask: if a supervisor read our internal papers, our risk assessments, and our submission side by side, would they tell the same story? If not, fix the gap before it becomes the question you cannot answer.

The next action is straightforward. Take your current proposal and stress-test it against the four areas above. Where the evidence is thin, strengthen it before the regulator has to ask.

Frequently Asked Questions

How early should we engage with the regulator on a material change?

As soon as the direction is firm enough to describe honestly, even if the detail is not settled. Early engagement is about signalling intent and inviting concerns, not seeking approval.

What if our internal governance records show real disagreement?

Show them. Documented challenge that was worked through is a strength. Attempting to smooth it over creates a bigger problem if the regulator sees the underlying papers.

How much detail should a formal submission contain?

Enough that a supervisor can independently assess the risks and controls without needing to ask basic questions. If the first response is a long list of clarifications, the submission was not ready.

What is the most common reason regulators lose confidence mid-process?

The firm's position shifts in ways that appear reactive rather than considered. Each change without a clear rationale erodes trust in the original analysis.

Should we use external advisers to support the case?

Only where they add genuine expertise or independent challenge. A submission that reads as written by advisers rather than owned by the firm reduces confidence, not increases it.