What Regulators Look For in a Submission: A Practical Guide

Regulators are not reading your submission for prose. They are reading it to answer a small set of questions: do you understand the risk, can you evidence what you claim, and will your firm behave the way this document says it will. Everything else is noise. This guide sets out what supervisors at the FCA, PRA, and equivalent bodies are actually looking for, and how to write a submission that earns their confidence rather than their follow-up questions.

Key Executive Takeaways

• Regulators assess submissions on three axes: clarity of self-assessment, quality of evidence, and credibility of the people accountable. Weakness in any one triggers scrutiny across all three.
• The most common failure is not omission but tone: submissions that read as advocacy rather than honest diagnosis lose credibility fast and are difficult to recover from.
• Good submissions answer the questions the regulator has not yet asked. That means anticipating the supervisor's next three follow-ups and addressing them inside the document.

What They Are Actually Assessing

Every submission, whether an authorisation application, a Section 166 response, a variation of permission, a change in control, or a reg return narrative, is read against the same underlying test: does this firm know itself, and can it be trusted to run itself.

Supervisors form a judgement on four things:

1. Self-awareness. Does the firm identify its own weaknesses before the regulator has to? A submission that presents a flawless picture is almost always a red flag. Supervisors expect to see risks named, quantified, and matched to mitigations.
2. Evidence discipline. Every material claim needs a source: a policy reference, a board minute, a MI pack, a testing result. Assertions without artefacts are treated as aspiration.
3. Accountability clarity. Who owns what, by name and SMF where relevant. Vague ownership signals weak governance regardless of how good the underlying controls are.
4. Consistency with what the regulator already knows. Supervisors cross-check submissions against prior returns, past correspondence, complaints data, and peer benchmarks. Inconsistencies without explanation are the fastest route to a deep review.

Structuring the Submission

Lead with the answer. Regulators read the first two pages with attention and skim the rest. If your executive summary does not state the position clearly, name the risks, and set out mitigations, the rest of the document will be read defensively.

Use the regulator's own language. If the handbook or the information request uses specific terms, mirror them. Recasting questions in your own framing looks evasive, even when it is not intended to be.

Separate fact from judgement. Where you are asserting a fact, evidence it. Where you are making a judgement, say so and set out the reasoning. Blurring the two is the single most common drafting error.

What Good Evidence Looks Like

Supervisors want to see the working, not just the conclusion. That means:

• Board and committee minutes showing the issue was actually discussed, with challenge visible.
• MI that predates the submission, not artefacts created for it.
• Testing results with sample sizes, methodology, and failure rates, not just headline pass figures.
• Third-party validation where the topic is contested or technical.

Manufactured evidence is obvious. If a policy is dated three weeks before submission and has no prior version history, supervisors notice.

What Most Firms Get Wrong

The recurring failures are predictable. Over-claiming capability that MI does not support. Burying material weaknesses in appendices. Using consultants to write in a voice the executive team cannot defend under questioning. Treating the submission as a one-off document rather than part of a continuing supervisory record.

The firms that do this well treat submissions as an extension of their governance, not a marketing exercise. The document reads the same as their internal board papers, because it is drawn from them.

The Next Step

Before sign-off, put the draft in front of someone who has not worked on it and ask them to list the three questions a supervisor would ask next. If those questions are not answered in the document, you are not finished.

Frequently Asked Questions

How much detail is too much?

If a section does not either answer a question the regulator asked or pre-empt one they will ask, cut it. Length is not a proxy for rigour, and padding dilutes the material points.

Should we acknowledge weaknesses openly?

Yes. Regulators discover weaknesses eventually. Naming them first, with a credible remediation plan and timeline, is treated as evidence of competent management. Concealment, once found, changes the supervisor's view of the whole firm.

Who should sign off internally before submission?

The accountable SMF, the general counsel or head of compliance, and at least one non-executive with relevant expertise. If the document cannot survive challenge from those three, it will not survive the regulator.

How do regulators treat inconsistencies with previous submissions?

As a signal. Small inconsistencies invite clarification requests. Material ones invite thematic reviews. Always reconcile against prior filings before submitting, and explain any changes in position explicitly.

Does presentation matter?

Only to the extent that poor presentation slows comprehension. Clear structure, accurate cross-references, and consistent terminology help. Design flourishes do not.