Surfacing the Objections That Only Appear During Regulatory Review

Why the worst objections arrive late

Objections that surface during formal regulatory review are rarely new. They existed before you filed. What changes is the incentive to voice them. Once a review opens, competitors, consumer bodies, adjacent regulators, and internal supervisory teams have both a formal channel and political cover to raise concerns they previously kept private. By then, your filing is fixed, your public position is set, and every concession looks like a retreat.

The work, therefore, is to construct the review conditions before the review begins. That means finding the people who will speak up later and getting them to speak up now, when you can still adjust.

Where hidden objections actually live

Most teams look in the wrong places. They test with the obvious counterparties: the lead regulator, a few trade associations, one or two industry peers. The objections that ambush filings tend to come from four less obvious sources:

• Secondary supervisors inside the same regulator whose sign-off is required but who are not the primary contact. Conduct teams, prudential teams, financial crime teams, and data protection teams often see the file differently from the relationship supervisor.
• Adjacent regulators whose remit touches yours only at the edges. They rarely object publicly, but they brief the lead regulator privately.
• Consumer and market integrity bodies who read consultations carefully and coordinate responses. Their positions harden months before they are published.
• Competitors who benefit from delay rather than outright refusal. Their objections are technical, procedural, and designed to extend timelines.

If you have not mapped these four groups specifically, your pre-filing testing is incomplete.

How Polar Insight structures the work

Our approach rests on three principles: talk to the right people, ask questions that reveal true position rather than public position, and interpret silence correctly.

Reaching the people who will actually speak during review

We identify the specific individuals inside secondary supervisory teams, adjacent authorities, and stakeholder bodies who will be consulted once the review opens. Not the head of the organisation. The person whose desk the file will land on. This is where institutional knowledge matters: the reviewer at a conduct regulator who consistently raises operational resilience questions on cross-border filings is a known quantity, and their likely objection can be anticipated.

Structured, attributable, off-the-record conversations

We conduct interviews under Chatham House terms with named stakeholders who will not speak candidly to the filer directly. The value is not in aggregated opinion. It is in specific, sourced positions: what this named body will say, on what grounds, and how firmly. Sentiment surveys and desk research will not produce this.

Interpreting silence and soft support

The most common error is treating a lack of stated objection as endorsement. In our experience, roughly a third of stakeholders who offer no view pre-filing raise substantive concerns once formally consulted. We test for this by asking counterfactual questions: what would cause you to object, what have you objected to in comparable filings, who inside your organisation would need to sign off.

What good looks like

A well-run pre-filing exercise produces a written register of probable objections, attributed to specific bodies or individuals, ranked by likelihood and impact, with the technical grounds each is likely to cite. It also identifies which objections can be pre-empted by filing design, which require direct engagement before submission, and which you should simply prepare responses for.

You should end up with fewer than a dozen genuine risks, each with a named owner on your side and a planned response. If your risk register runs to fifty items, you have not done the analytical work.

What most teams get wrong

Three recurring mistakes:

1. Testing the concept rather than the filing. Stakeholders respond differently to a general idea than to a specific submission with specific commitments.
2. Confusing access with insight. Meeting the chair of a body tells you less than a candid conversation with the technical lead.
3. Running the exercise too late. If you begin six weeks before filing, you cannot redesign in response to what you learn.

Your next decision

Before your next major filing, ask one question: can you name the five stakeholders most likely to object during formal review, and cite the specific grounds each will use? If not, the objection mapping work has not been done, and you are filing on hope. Start that work at least three months before submission.