Processing Timelines
Timelines depend on scope, completeness, and the number of clarification cycles. This page provides a stage-gate view so applicants can plan drafting, evidence packaging and launch milestones.
Main driver of speed
Evidence pack quality. One clean pack beats “fast drafting” every time.
Clarification cycles
Each cycle adds time. Plan for rapid responses and version-controlled resubmissions.
Operator vs Supplier
Supplier validations often focus on security, logs and testing evidence; operators on AML/RG and funds flow.
Stage-gate flow
High-level view of what happens, in order.
Pre-submission alignment
Scope selection, evidence inventory, and pack structure setup (ideally with a Registered Agent).
Submission + fee confirmation
Submission pack is lodged, fee references verified, file created, and initial acknowledgement issued.
Completeness checks
Mandatory artefacts and identity/corporate basics are checked. Missing items trigger quick clarification.
Substantive review
Controls assessed by domain (AML/CFT, RG, security, integrity, outsourcing, disclosures).
Clarification cycles (if needed)
Questions are issued; applicants respond with updated artefacts. Each cycle should be versioned and indexed.
Decision + publication
Decision issued. Where applicable: issuance fee confirmation and public register publication step.
Indicative ranges (framework)
Use these as planning bands. Publish official numbers separately if needed.
| Stage | Typical band | What changes it |
|---|---|---|
| Pre-submission alignment | 1–4 weeks | Evidence inventory maturity, drafting capacity, agent availability. |
| Completeness checks | 1–2 weeks | Missing corporate docs, unclear scope, incorrect pack structure. |
| Substantive review | 4–10 weeks | Complexity, number of domains, technical validation depth. |
| Clarification cycles | +1–4 weeks each | Response speed, version discipline, evidence quality. |
| Decision → publication | 1–3 weeks | Issuance fee confirmation, final checks, register publication queue. |
Fastest way to cut time
Keep artefacts versioned, indexed, and mapped to requirements. Unstructured PDFs are timeline killers.
Planning ranges are illustrative and should not be treated as a guarantee. Complexity and clarification cycles vary by file.
What causes delays (top 6)
Common issues seen in intake and review phases.
Wrong scope selection
Operator vs supplier obligations mixed.
No artefact index
Reviewers can’t find evidence quickly.
Weak logs
Security / monitoring evidence missing.
AML gaps
KYC/monitoring not operationalised.
RG not measurable
No thresholds, triggers or interventions.
Slow clarifications
Untracked changes and late replies.
If you want a “minimum viable pack” approach, start with the Requirements Hub and build the evidence index first.