Responding to supervisory questions: costs drivers
A written enquiry from a supervisor during an authorisation or ongoing-supervision file triggers a fixed sequence: read, map, draft, submit, wait. What drives the cost of that sequence is not the enquiry's length but its shape — how many registers it touches, how many jurisdictions the entity operates in, and whether a clock is already running. This page sets out the stages, the documents typically requested, the usual timing and the point past which a partial answer stops being useful.
What changes once the enquiry lands
Once a supervisory question arrives, the file moves from passive to active. Every subsequent submission is read against the earlier one, so inconsistencies that were harmless in a first-round application become material at this stage. The practical effect is that the answer has to be assembled once, checked internally, and sent as a single coherent package rather than in instalments.
A second effect concerns timing. Supervisors typically set an indicative reply window rather than a fixed statutory deadline at this procedural step. Missing that window rarely ends the file, but it does reset the supervisor's own internal queue, so the practical cost of delay is a longer wait for the next substantive reply, not a formal penalty.
What drives the cost
| Factor | Effect on effort |
|---|---|
| Number of registers or systems referenced in the question | Each additional register means a separate extraction and a separate internal sign-off |
| Number of jurisdictions the entity operates in | Cross-border answers need a consistency check against each local file |
| Whether a supervisory clock is already running | Running clocks compress drafting time and raise the priority of the file |
| Whether the question follows an earlier, incomplete answer | A second round is read against the first; contradictions cost more to fix than to avoid |
| Whether a third party (auditor, custodian, data processor) must contribute | External input adds a coordination step outside the entity's direct control |
What to do
- The compliance officer reads the enquiry line by line and lists every discrete question separately, even if the supervisor grouped several under one heading.
- The compliance officer or an instructed adviser maps each question to the internal record that answers it — policy, register entry, transaction log, or governance minute.
- Where the enquiry touches personal data held across systems, the team that extracts the underlying records should follow the same logic used to demonstrate a lawful data transfer; see Transfer mechanism data protection how it is proved explained for how that evidencing is usually structured.
- The entity drafts one consolidated response document, numbered to mirror the supervisor's own numbering, and attaches supporting records as annexes rather than embedding them in the narrative.
- A senior signatory reviews the draft against the entity's earlier submissions in the same file before it goes out, to catch contradictions before the supervisor does.
- The response is submitted through the same channel the original enquiry arrived on, with a short covering note confirming which questions are answered and which require a follow-up extension.
Who decides
The competent supervisory authority decides whether the response is sufficient. There is no independent adjudicator at this stage; the same case officer or team that raised the question reviews the answer. If the response is accepted, the file either closes the open point or moves to the next stage of the review. If it is not accepted, the supervisor issues a further, usually narrower, enquiry rather than a refusal — refusal is reserved for cases where the gap in the answer is treated as a substantive gap in the application itself.
Branches
If the enquiry concerns a governance or fit-and-proper point rather than a documentation gap, the drafting logic differs; the step-by-step sequence for that scenario is set out separately in Governance and fit and proper review step by step.
If the question concerns a licence that has already lapsed but a linked token instrument remains in circulation, the ordinary response sequence does not apply cleanly, because the underlying authorisation no longer exists; see When a licence terminates but the token remains for how that situation is usually approached.
If the entity is also mid-way through renewing an unrelated registration — for example a trade mark tied to its brand — the same discipline of assembling documents against a fixed window applies, and the comparable sequence is described in Renewal and restoration step by step.
Limits
This page does not set out what a supervisor is permitted to ask, nor how a specific register or authorisation regime is structured — those are separate procedural and reference questions handled elsewhere on this site. It also does not estimate how long a full authorisation review takes overall; it addresses only the response step once a written enquiry has already been raised. Numerical deadlines vary by authority and by the nature of the question, and are not stated here because they are set procedurally rather than fixed in this file.
Verified
Verified: 4 March 2025, against current procedural practice observed in authorisation and supervision files handled by this office. No statutory citations are included on this page, consistent with its procedural nature; readers seeking the underlying legal basis for a specific supervisory power should raise that separately.
Related publications
Readers assembling a response file often need to close a separate governance question at the same time; see Governance and fit and proper review step by step for that adjacent procedure.
If the file is stuck before you even reach this stage
Some files never reach the response stage cleanly because the underlying application was incomplete from the start. If the gap concerns AML documentation specifically, the first steps are set out in The file is incomplete on AML authorisation.
A related but distinct gap arises when a contractor rather than the entity itself is the source of the missing material — for instance, disputed code ownership underlying a token issuance. That situation is addressed in When a contractor claims ownership of the code.
FAQ
How long does responding to supervisory questions take in practice?
There is no fixed statutory period at this step. In practice, a single-register, single-jurisdiction answer can be drafted within days once the underlying records are located; a multi-jurisdiction answer touching several registers, or one following an earlier incomplete reply, typically takes longer because each addition requires its own internal sign-off.
Which documents are needed to start?
Start with the original enquiry itself, the entity's most recent prior submission in the same file, and the internal register or log that the question refers to. Where a third party holds part of the record — an auditor, custodian or data processor — their confirmation should be requested at the outset, not once drafting is already under way.
What happens if the entity does not respond in time?
A missed indicative window does not usually close the file on its own. The more common consequence is that the supervisor's own review slows down, and a further, often more pointed, enquiry follows. Repeated non-response across several rounds is treated differently and can be read as a sign that the underlying application itself is incomplete.