Responding to supervisory questions: what the decision maker looks at
When a supervisory authority sends a request for further information on an authorisation file, the reviewer reads the reply for consistency with what is already on file, not for style. The reviewer checks whether every sub-question got a direct answer, whether the documents referenced actually arrived, and whether the evidence chain has gaps. A late or partial reply slows the file and invites a second, narrower round of questions.
Why the reply matters
A request for information is rarely random. It usually flags a point where the file is thin, contradictory, or missing a document that the reviewer expected to see. Treating the request as a formality and answering in general terms tends to backfire: the reviewer notes the gap again, asks more precisely, and the file loses time it cannot easily recover.
The opposite mistake is over-supplying material that was not asked for. Extra documents do not speed up review; they add volume the reviewer has to sort through before reaching the actual answer. The reply that moves a file forward is narrow, complete, and traceable to the specific question asked.
What to do
- Read the request line by line and list every sub-question separately before drafting anything.
- Assign one person to own the reply so the wording and evidence stay consistent across sections.
- Match each answer to a named document or a specific paragraph in an existing filing, rather than a general reference.
- Where a gap in evidence is found during this check, run a structured review before replying — see Gap review and remediation plan step by step for how that review is typically organised.
- Send the reply through the same channel the request arrived on, and keep a dated copy of what was sent.
- Flag internally any question the team cannot answer without external input, and start that work immediately rather than waiting for the deadline.
Who decides
The reviewing authority stays the same body that opened the file. It does not hand the question to a separate panel unless the file escalates. The authority sets its own response window in the request itself, and that window is the operative deadline — there is no standard default that applies across all cases.
| Stage | Who acts | What is expected |
|---|---|---|
| Initial request | Supervisory authority | Specific list of missing or unclear points |
| Applicant's reply | Applicant, through the named contact on file | Direct answers plus supporting documents |
| Follow-up questions | Supervisory authority | Narrower queries on the same points, if the first reply left gaps |
| Decision or further request | Supervisory authority | Approval, refusal, or another round of questions |
The reviewer does not usually explain why a point is unclear beyond the wording of the request. If the request itself is ambiguous, the safer course is to answer the literal wording and note the ambiguity in the covering letter, rather than guess at intent.
If your situation differs
If the supervisory request lands while an existing authorisation is also due for renewal, the two tracks do not automatically merge. Handle each on its own timeline — see Renewal and restoration step by step for how the renewal clock runs separately.
If the question concerns the origin of a data set used to support the application, the reply needs a documented provenance trail rather than a description in prose. The requirements for that trail are set out separately — Provenance requirements for data sets in ownership of results covers what counts as sufficient evidence.
If the file already went through a governance or fit-and-proper check earlier in the process, the current request may simply be testing whether that earlier answer still holds. Re-reading the original submission before drafting the reply avoids contradicting an earlier statement.
Related steps
The governance and fit-and-proper stage is often reviewed by the same team that later sends supervisory questions, so a mismatch between the two stages is one of the more common reasons for delay. See Governance and fit and proper review step by step for what that earlier stage checks.
What this page does not cover
This page describes the mechanics of replying to a supervisory request. It does not tell you what a particular authority will accept as sufficient in a specific case, and it does not predict the outcome of the review. It also does not cover the separate question of what services, licences, or thresholds require authorisation in the first place — that belongs to a different part of the site.
Sources and limits
Reviewed: June 2025. The description above reflects how supervisory dialogue is typically structured under the applicable authorisation framework for digital asset service providers, based on publicly available guidance from the relevant authorities. It does not quote specific legal provisions, because the point of this page is the procedure, not the statutory reference.
Where a client's file also involves a completed transaction that needs to be checked against what a given jurisdiction can actually establish, a separate transaction report is the relevant tool — see Transaction report estonia for the Estonian scope.
The same type of check exists for the Dutch market, with its own limits on what can be confirmed — Transaction in Netherlands.
Next steps
If the supervisory questions touch a token that is marketed as already carrying a licence, treat that claim separately before replying — see When a token claims to carry a licence for the first checks to run.
If the file is expanding into another member state while the questions are being answered, the scope of supervision can change mid-process — Cross-border services are added authorisation sets out what to check first.
FAQ
How long does responding to supervisory questions take in practice?
The authority sets its own window in the request, and that window varies by case and by how many points are raised. A reply prepared against a clear checklist of sub-questions is usually faster to finalise than one drafted from scratch after the deadline is already close.
Which documents are needed to start?
Start with the original request, the file as it currently stands with the authority, and any internal notes on why each disputed point was answered the way it was. Without the original submission in hand, it is easy to contradict an earlier statement without noticing.
What happens if the applicant does not respond in time?
A missed deadline does not usually close the file outright, but it removes goodwill and often triggers a stricter follow-up request. Some authorities treat a missed deadline as grounds to pause the review clock until a reply arrives, which extends the overall timeline rather than shortening it.