What Regulators Look For in a Submission: A Practical Guide

Regulators do not read submissions the way boards read papers. They read them looking for evidence that the firm understands its own risks, has thought through the consequences of its decisions, and can be trusted to do what it says it will do. If your submission does not make that visible on the first read, you have a problem, regardless of how technically correct the content is.

Key Executive Takeaways

• Regulators judge submissions on evidence, coherence, and candour: they want to see that the firm understands its risks, has tested its own thinking, and is telling the whole story.
• Weak submissions usually fail on the same things: unclear accountability, unsupported assertions, gaps between narrative and data, and silence on known issues.
• Strong submissions read as if the senior accountable person wrote them, not as a legal document assembled to satisfy a checklist.

What Regulators Are Actually Assessing

Whatever the specific process, whether a Part 4A authorisation, a variation of permission, a Senior Manager application, a change in control, a s.166 response, or a thematic data return, the underlying assessment is broadly the same. Reviewers are testing four things.

Substance. Does the firm meet the threshold conditions or the specific requirement in question? Is the business model viable, the capital adequate, the controls proportionate to the risks, the individuals fit and proper?

Self-awareness. Does the firm understand where its risks sit and where it is weaker? A submission that claims everything is fine when the regulator already has supervisory intelligence suggesting otherwise damages credibility for years.

Governance. Who decided what, on what basis, and with what challenge? Reviewers look for board minutes, committee terms of reference, and evidence that senior managers actually engaged rather than rubber-stamped.

Consistency. Does the narrative match the numbers? Does this submission align with previous returns, the ICAAP, the ILAAP, the Recovery Plan, the Consumer Duty board report? Contradictions across documents are treated as either sloppiness or concealment. Both are damaging.

What Good Looks Like

A strong submission has a clear thread from the strategic decision or risk being addressed, through the analysis, to the controls and monitoring. It states what the firm is doing, why, what could go wrong, and what would trigger a change. It uses the regulator's own language where relevant, not to flatter, but to demonstrate that the firm understands how the requirement is being interpreted.

It is also honest about weaknesses. Naming a known issue, explaining the remediation plan, and setting out timelines is far more credible than hoping the reviewer will not notice. Regulators almost always notice, and the file note that results is worse than the original problem.

What Most Firms Get Wrong

The most common failures are not technical. They are:

• Assertion without evidence. Statements like "the board provides robust challenge" with no minutes, attendance records, or examples of decisions changed as a result.
• Legal polish over substance. Submissions that read as if drafted to withstand litigation rather than to inform a supervisor. This raises suspicion, not confidence.
• Misaligned documents. The cover letter says one thing, the appendix says another, and the underlying MI says a third.
• Senior manager distance. Applications and attestations that the accountable individual clearly has not read carefully. Reviewers can tell.
• Silence on prior issues. Not referencing previous supervisory correspondence, past breaches, or known thematic concerns in the firm's sector.

How to Prepare a Submission That Holds Up

Start with the reviewer's question, not your answer. What is the regulator trying to decide, and what evidence would a reasonable supervisor need to decide it? Build the submission backwards from that.

Have the accountable senior manager read the full pack, not just the summary, and be able to defend every material claim in an interview. Run a red team review internally, ideally involving someone who was not part of drafting, whose job is to find the weakest paragraph and the biggest gap between claim and evidence.

Check cross-document consistency systematically. Align this submission with your last three board packs, your most recent regulatory returns, and any live supervisory correspondence.

The Decision Point

Before you submit, ask one question: if the regulator called the accountable senior manager tomorrow and asked them to talk through this document unaided, would they be credible? If the answer is uncertain, the submission is not ready.

Frequently Asked Questions

How much detail is too much?

Enough to answer the question and evidence the claim, no more. Padding signals that the firm is trying to bury something. If a point needs an appendix, put it in an appendix and reference it clearly.

Should we pre-engage with the supervisor before submitting?

For anything material or novel, yes. A short call to confirm scope, format expectations, and any specific supervisory concerns almost always improves the quality of the submission and reduces follow-up requests.

How do we handle a known weakness we have not yet fixed?

Name it, explain the root cause, set out the remediation plan with dates and owners, and describe the interim controls. Concealment is treated far more seriously than the underlying issue in almost every case.

Who should actually write it?

Subject matter experts draft, the accountable senior manager owns and edits, legal and compliance review for accuracy and consistency. If legal is drafting the substance, the submission will read that way, and reviewers will notice.

What happens if we get it wrong?

Depending on the process, outcomes range from extended information requests and delayed decisions, to formal findings, to attestation and personal accountability consequences under the Senior Managers Regime. The cost of a weak submission is almost always higher than the cost of doing it properly the first time.