Stress-Testing Research Coverage Before a Regulatory Submission

The problem with late-breaking objections

The objections that derail regulatory submissions rarely come from the stakeholders you briefed. They come from the second-tier policy adviser who was on leave during your consultation, the consumer body that only engages once a draft is public, or the desk officer whose concerns your sponsor never flagged. By the time these surface, you are negotiating from a weaker position, often with your board watching a slipping timeline.

So the question is not whether research is useful. It is whether the research you have commissioned will find the objections that matter before they find you.

What good coverage actually looks like

Good stakeholder research for a regulatory submission does three things that most research does not.

First, it maps beyond the named decision-makers. A submission goes through case officers, technical specialists, legal counsel, policy leads, and sometimes cross-authority reviewers. Each has a different threshold for concern. Research that only speaks to the senior sponsor tells you what will be said in the room, not what will be written in the internal note.

Second, it covers the adjacent voices that regulators listen to when a submission gets contested: consumer groups, trade bodies, competitor responses to consultations, academic critics, and the financial press. Regulators rarely reject a proposal on their own analysis alone. They reject it because someone external gave them a reason to.

Third, it tests specific objections, not general sentiment. "Broadly supportive" is worthless. "Supportive, but will raise concerns about client asset segregation if the SPV structure isn't clarified" is actionable.

How to interrogate a research design

Before you sign off on any research programme, ask the following of whoever is running it.

Who is on the interview list, and who isn't?

Ask for the full list. Then ask which names were considered and dropped, and why. The interesting answers are usually in the dropped list: the former regulator now advising a consumer body, the technical specialist at a peer authority, the policy lead who has moved on but shaped the current thinking.

What are the specific objections being tested?

A credible research design should name the objections in advance: capital treatment, conduct implications, competition effects, precedent risk, operational resilience. If the design cannot list what it is testing for, it will report back what respondents happen to say, which is not the same as what they think when they read your submission.

How is dissent being surfaced?

Stakeholders rarely volunteer objections to a well-briefed interviewer representing a large firm. Ask how the research protocol invites disagreement. Techniques that work: presenting the strongest counter-argument and asking the interviewee to improve it; asking who would object and why; asking what the interviewee would write in an internal note if asked to critique the proposal.

What is the plan for the voices you cannot access directly?

Some stakeholders will not speak to research. Regulators in live cases, for example. A serious research design says how it will triangulate: consultation response analysis, speeches, enforcement patterns, adjacent conversations with former officials, submissions on comparable cases.

What most people get wrong

The most common failure is confusing access with insight. A research programme that lands twenty interviews with senior figures can still miss the objections that matter, because senior figures are diplomatic and the objections come from the layer below them.

The second failure is treating the research as a one-off. Objections evolve. The concern that did not exist in month one appears in month four because a peer firm's case has shifted the reference points. Good programmes build in a checkpoint before submission, specifically to test whether the field has moved.

The third failure is not pressure-testing the findings internally. If your submission team reads the research and says "that all sounds right," the research has probably told you what you already believed. The value is in the findings that make your team uncomfortable.

The decision point

Before you commission or accept a research programme, ask for one thing in writing: a list of the specific objections the research will test, the stakeholders whose views on each will be surfaced, and the method for accessing those views. If that list is thin, the research will be thin. Fix it before the fieldwork starts, not after the submission is filed.