What Regulators Actually Read For When They Open Your Submission
This guide explains what UK and international financial regulators are genuinely assessing when they review a submission, from authorisation packs to thematic responses. After reading it, you will know how to prepare a submission that demonstrates real control, judgement and self-awareness, rather than one that merely covers the required fields.
If you want to know what regulators look for in a submission, start with this: they are reading for evidence that the firm understands itself. Technical accuracy is assumed. What supervisors are actually testing is whether the people running the firm can see their own risks clearly, have made deliberate choices about them, and can be trusted to tell the regulator the truth when something goes wrong. Everything else in the review flows from that judgement.
Key Executive Takeaways
- Regulators assess submissions on three things above all: internal coherence, evidence of genuine ownership, and honesty about weaknesses and remediation.
- The most common failure is not poor drafting but a mismatch between the narrative in the submission and what the regulator already knows about the firm from other sources.
- A credible submission reads as if the senior accountable individuals wrote it themselves, with clear judgement, specific evidence, and a realistic account of what is not yet fixed.
What supervisors are actually testing
Supervisors read submissions against a mental model of your firm they have already built from supervisory meetings, returns data, peer comparisons, complaints information, and prior correspondence. The submission is tested against that model. If what you file looks materially different from what they already believe, the question becomes why, and whether the firm or the regulator has the clearer picture.
That means the single biggest determinant of how a submission lands is not the quality of the writing. It is the degree of alignment between the document, the firm's actual operating reality, and the supervisor's existing view.
The four tests a submission has to pass
Internal coherence
Does the risk appetite match the capital position? Does the strategy match the risk appetite? Does the control environment match the risk profile described? Reviewers routinely cross-check sections against each other. A recovery plan that assumes rapid asset sales but a liquidity policy that treats the same assets as core HQLA will be flagged within minutes. Before submission, someone senior and independent of the drafting team should read the whole document for internal contradictions.
Evidence of ownership
Supervisors can tell when a submission has been written by consultants, lightly reviewed, and signed. The tells are generic language, consistent tone across sections that should reflect different functional voices, absence of firm-specific examples, and board minutes that record approval without recording challenge. Good submissions show fingerprints: specific decisions, dated board discussions, named committees, numbers that reconcile to the firm's own MI.
Honesty about weakness
This is where most firms underperform. A submission that claims full compliance with everything, no material issues, and all controls operating effectively is read as either naive or evasive. Regulators expect mature firms to identify their own gaps, explain the root cause, set out the remediation plan with owners and dates, and show progress against earlier commitments. A candid self-assessment with a credible plan is almost always received better than a polished claim of completeness.
Traceability
Every material assertion should be traceable to a source: a policy, a committee minute, a dataset, a test result, a management action. When supervisors ask follow-up questions, and they will, the firm needs to produce the underlying evidence quickly and without reconstruction. If evidence has to be built after the question is asked, the submission has already lost credibility.
What good preparation looks like
Start from the supervisor's likely questions, not from the template. Map what the regulator already knows, what they will expect to see, and where your firm's position has changed since the last touchpoint. Write the hard sections first: the ones covering known weaknesses, open remediation, or recent incidents. Get those right and the rest follows.
Have the submission read end to end by someone who was not involved in drafting any section, ideally a non-executive or an independent reviewer. Their job is to find the contradictions, the unsupported assertions, and the places where the tone slips from accountable to defensive.
The decision point
Before you submit, ask one question: if the regulator walked into the firm tomorrow and tested every claim in this document against the operating reality, would it hold? If the honest answer is no, the fix is not editing the document. It is addressing the gap, or being explicit in the submission about what is not yet in place and when it will be.
Frequently Asked Questions
How much detail is too much?
Detail that supports a material judgement is useful. Detail that pads length without adding evidence dilutes the document and signals a lack of editorial discipline. If a paragraph does not help the reader understand a decision, a risk, or a control, cut it.
Should we flag issues the regulator has not yet raised?
Yes, where they are material and the firm has a credible plan. Self-identification is one of the strongest signals of a mature control environment. Burying an issue the regulator later finds independently is the fastest way to lose trust.
Who should sign the submission off internally?
The accountable senior manager under SM&CR, with documented board or committee review proportionate to materiality. The sign-off process should be evidenced in minutes, including specific challenge, not just approval.
What is the single most common failure?
A mismatch between the confident tone of the submission and the known reality of the firm's control environment. Supervisors notice immediately, and it reframes how they read everything else in the document.
Frequently asked questions
How much detail is too much?
Detail that supports a material judgement is useful. Detail that pads length without adding evidence dilutes the document and signals a lack of editorial discipline. If a paragraph does not help the reader understand a decision, a risk, or a control, cut it.
Should we flag issues the regulator has not yet raised?
Yes, where they are material and the firm has a credible plan. Self-identification is one of the strongest signals of a mature control environment. Burying an issue the regulator later finds independently is the fastest way to lose trust.
Who should sign the submission off internally?
The accountable senior manager under SM&CR, with documented board or committee review proportionate to materiality. The sign-off process should be evidenced in minutes, including specific challenge, not just approval.
What is the single most common failure?
A mismatch between the confident tone of the submission and the known reality of the firm's control environment. Supervisors notice immediately, and it reframes how they read everything else in the document.
Related guides
How to Write an ICAAP Narrative That Shows Real Capital Judgement
This guide sets out how to construct an ICAAP document that evidences genuine board-level thinking about capital adequacy, not formulaic compliance. After reading, you will know how to sequence the narrative, where to place judgement, and how to make the document defensible under supervisory challenge.
How to Prepare a Credible Response to a Section 165 Request
This guide explains how to respond to an FCA or PRA Section 165 information request with the rigour, accuracy and timeliness regulators expect. After reading it, you will know how to mobilise the right people, control the production process, and engage credibly with the supervisor throughout.
How to Structure a Section 166 Skilled Person Review Response That Preserves Firm Credibility
This guide explains how to engage a Section 166 Skilled Person review in a way that evidences genuine control, candour, and remediation capability. After reading, senior leaders will know how to structure their response, govern the interaction, and position the firm to emerge with regulatory trust intact.
How to Prepare a Credible ILAAP Submission That Reflects Genuine Liquidity Risk Thinking
This guide sets out how to produce an ILAAP that demonstrates real liquidity risk understanding rather than template compliance. Readers will finish with a clearer view of what supervisors actually test, where submissions typically fall short, and how to build a document the board can defend.
How to Build a Credible ICAAP Narrative That Withstands Supervisory Scrutiny
This guide explains how to construct an ICAAP document that reads as a genuine articulation of risk, capital adequacy and board ownership rather than a compliance artefact. After reading, you will know what supervisors actually test for, where most narratives fall apart, and how to sequence the work so the story holds together under challenge.
Where a specific question needs an outside answer, quickly
Polar Insight's Expert Network connects leadership teams with practitioners who can speak to a precise regulatory, commercial, or stakeholder question before a decision is finalised.
Explore Expert Network