License application workflow for RAKEZ, Ajman Free Zone and ANC
Every application on a real free-zone process, with an owner at every step
Thirteen steps for RAKEZ, eleven for Ajman Free Zone and a full ANC path, each one the sequence the authority actually puts you through rather than a generic pipeline with the stages renamed. Every step has an owner, every hand-off is logged, and the client sees an ETA that stops counting while you're waiting on them.
Nobody can tell you what step an application is on
Ask three people about the same file and you get three answers. The coordinator thinks documents are complete, finance is waiting on a payment nobody chased, and the client was told 'next week' eight days ago.
- Missing documents surface halfway through instead of at the start.
- Files sit with someone who has been on leave since Tuesday.
- There is no record of who approved what, so mistakes turn into arguments.
- The client gets a status only when they chase for one.
- Application createdSales
- Quotation sentSales
- Client onboarding formClient
- Documents collectedCoordinator
- Payment approvedFinance
- Free-zone processingOperations
- Supervisor approvalSupervisor
The stepper: current step, the role that owns it, and an ETA marked paused because the ball is in the client's court.
What happens between a signed client and an issued license
Every step below is a hand-off. The system knows whose turn it is, and the audit log knows who had it last.
- 01
Application created
SalesConverted from a won lead in one click, or opened directly by sales.
- 02
Sales review and quotation
SalesPackage and pricing set, branded quotation PDF generated and emailed.
- 03
Client onboarding
ClientThe client fills in their own company details through a secure link. No login, no back-and-forth email.
- 04
Documents collected and verified
CoordinatorA checklist per application. Coordinators see what has landed and what is missing without opening a drive folder.
- 05
Payment recorded and approved
FinanceFinance signs off before processing starts, so nothing gets submitted against an unpaid file.
- 06
Free-zone processing
OperationsThe authority-specific steps: name reservation, initial approval, documentation, issuance. Your team works the real process.
- 07
Supervisor approval
SupervisorA final check before the license is marked issued and the client is activated.
If you want the RAKEZ version written out properly, with who owns each step and the two places nearly every file loses a week, read the RAKEZ trade license process, step by step.
The clock stops when you're waiting on them
Each application carries a milestone-based estimated completion date. The moment a step depends on the client, whether for a passport copy, a signature or a decision, the countdown pauses and the reason is written on their screen.
- Your ETA stays credible because it is not absorbing client-side delay.
- Clients see exactly what is blocking them and can act on it from the app.
- A public tracker covers clients who never install anything, with no login required.
- Milestones update as steps complete, so the date moves for real reasons only.
- Documents received
- Payment confirmed
- Name reservation
- License issued
Documents, checked once
Each application carries its own document checklist. Uploads land in encrypted cloud storage attached to the file, not in a shared drive folder someone renamed. Coordinators verify against the list rather than from memory.
A trail you can defend
Every action is logged with who did it, which role they were acting in, and when. When a client disputes a timeline or a colleague disputes an approval, the answer is in the record instead of in someone's recollection.
Activity finder
Describe what the client's business actually does and get back matching licensed activities from roughly 19,000 RAKEZ and AFZ entries. It turns a twenty-minute search through a PDF into a sentence.
Two things this doesn't do
Worth knowing before you talk to us rather than after the contract.
There is no workflow builder
Workflows are built and maintained by us, per free zone, to match each authority's real process. You don't drag steps around in an editor. If your process differs, tell us when you get in touch.
There is no direct authority integration
Nothing submits to RAKEZ or AFZ portals on your behalf. Free-zone data is reference data; your team still does the submission. What changes is that the tracking around it stops being manual.
Questions about the workflow
Which free zones have a workflow?
RAKEZ, Ajman Free Zone and ANC. RAKEZ and ANC run on thirteen steps and AFZ on eleven. You can still manage clients, service requests and finance for anywhere else, including mainland, but those don't get a step-by-step workflow.
Does it submit the application to the authority for us?
No. Nothing connects to RAKEZ, AFZ or any other authority's portal. Your team submits through the authority's own channels, and the platform tracks everything around that submission.
Can we change the steps?
Not yourselves. There is no workflow builder; we build and maintain each free zone's workflow. If your process differs from the standard path, tell us early and we'll tell you honestly whether it fits.
Can an application skip the payment checks?
No. An application can't move past the pre-approval stage until finance has approved the pre-approval payment, and it can't move past the full payment stage until that payment is approved too.
What does the client actually see?
Step names, a short description of each and which one they are on, in the app or on the no-login tracker. They never see roles, internal notes or who on your team is holding the file.
Run one of your live applications through it
Pick an application currently stuck somewhere. We'll show you where it would sit, who would own it, and what the client would be seeing.