Assess the route
AKIUConfirm purpose, category, nationality, role, dependants and the entities involved.
Understand what happens, who is involved and what moves the process forward. Choose a journey to view its flowchart and reference timings.
AKIU preparation and authority decisions are separate stages.
Open service or workspace →Case-specific process category, nationality, role, entity and checklist confirmed.
Confirm purpose, category, nationality, role, dependants and the entities involved.
Check received documents, translations, validity and requirements. Obtaining missing documents is a separate dependency.
Use the permitted channel and available appointment; retain the submission reference.
Follow additional requests and communicate changes. Timing depends on the category, authority and case.
Check the issued document and applicable conditions before confirming travel.
Journey outcomeRecorded authority outcome and, where authorised, a confirmed mobilisation plan.
| Stage | Owner | Timing / lead time |
|---|---|---|
| 01 · Assess the route | AKIU | 1–3 business daysIndicative reference |
| 02 · Review the file | AKIU | 2–5 business daysIndicative reference |
| 03 · Submit / attend | AKIU + client | Schedule / window to be confirmed |
| 04 · Await the decision | Responsible authority | Authority / provider timing — confirm for the case |
| 05 · Verify and mobilise | AKIU + client | 1–2 business daysIndicative reference |
The case owner identifies what is missing, who needs to act and its effect on timing. “Action required”, “Awaiting external authority” and “Scheduled” distinguish a required reply, an external dependency and a confirmed window. Available statuses depend on the request type.
If the delivered outcome needs correction, record the reason through the case channel. Closure should reflect the outcome actually delivered.
Track my requests →