How to check a Dubai off-plan project status
To check a Dubai off-plan project status, do four things in order: identify the exact project, search it in the official status tool, save what you saw with the date, and compare that record with the developer’s latest update and the document that sets your next payment. The key discipline is simple: observed project status, promised handover, and your payment obligation are related, but they are not the same record.
If you need the full buying sequence rather than this single verification task, start with our guide to buying property in Dubai.
Start with one exact identity sheet
A status check is only useful if you are checking the correct project. In off-plan sales, the marketing name, community name, tower name, and phase name can appear in different combinations across brochures, emails, forms, and portal updates. Before you open any search tool, prepare one short identity sheet from your own documents.
Record these items exactly as written:
- project name
- project number, if you have it
- developer name
- tower, building, or phase name
- unit number
- source document and date: brochure, email, booking form, draft SPA, signed SPA, or portal update
If two names look similar but do not match exactly, treat that as unresolved. Do not assume that the tower name and the wider master project name refer to the same searchable record.
Check the project in DLD or Dubai REST
DLD supports search by project name or number and shows project, developer, and escrow details; Dubai REST includes Mashrooi; the result is not a completion guarantee (DLD Project Status Enquiry).
Search the exact project name first. If you also have the project number, run that search too. Your aim is not only to find a result page. Your aim is to confirm that the result clearly matches the identity sheet you prepared.
As soon as you find a likely match, save evidence immediately:
- screenshot or PDF of the result
- date and time of the check
- whether you searched by name or by number
- the exact search term used
- which details matched: project name, developer, phase, or another identifier
Keep every check as a separate record. Do not replace an older screenshot with a newer one. A dated sequence is more useful than a single image because it lets you compare what was visible on different days.
If the search result cannot be matched confidently to your project, pause and ask for written clarification before you rely on it.
Keep three tracks separate
A project status page answers one narrow question: what you observed in that system on that date. It does not automatically answer what handover date was promised or whether your next payment has changed.
1) Observed project status
Write only what the status tool showed and the date you checked it. This is your evidence log.
2) Promised handover
Write the handover timing from the exact source that made the claim: brochure, email, portal notice, sales message, or contract document. Add the source date.
3) Your payment obligation
Write the document that currently sets the next payment item: booking form, SPA draft, signed SPA, payment plan line, invoice, or reminder. Record the document name and date instead of relying on memory.
This separation helps you avoid a common mistake: treating a general impression of progress as if it automatically changes the payment record. If these three tracks point in different directions, ask the developer representative, your property adviser, or your legal adviser to explain the link in writing.
Use this verification log
Create one row every time you check the project.
| Date checked | Search route | Identity used | What the status result confirmed | Handover source compared | Payment document reviewed | Mismatch to resolve | Next action |
|---|---|---|---|---|---|---|---|
| DLD name / DLD number / Dubai REST | Project name, number, tower or phase, developer | Exact match, partial match, or unresolved | Brochure, email, portal update, SPA, with date | Booking form, SPA, invoice, reminder, with date | Name, phase, timing, or payment trigger | Proceed / ask for written clarification / pause |
How to use it well:
- In What the status result confirmed, write facts, not conclusions.
- In Handover source compared, identify the separate promise you are testing.
- In Payment document reviewed, note the document that controls your next step.
- In Mismatch to resolve, name the precise gap: wrong phase, unclear tower, undated update, or a payment trigger that does not tie cleanly to the same record.
- In Next action, force one clear decision after each check.
What to ask when the records do not line up
When the status result, developer update, and payment paperwork do not align, send one focused written query instead of several scattered messages. A simple list works well:
- Is this the exact same project name and project number shown in my booking or SPA documents?
- Does this update refer to the whole project, or to my specific tower or phase?
- What is the date of the developer update being relied on?
- Which document currently sets my next payment item?
- What written explanation connects the present project status to the handover timing being quoted?
- If two records differ, which document should I rely on for this decision now?
This gives you a clean paper trail: one project identity, one dated status observation, one source for handover, and one source for payment.
Turn the log into a decision worksheet
After each check, classify the project into one of three working outcomes.
Match confirmed — the identity sheet, status result, handover source, and payment document all point to the same project and there is no material mismatch to clear.
Needs clarification — the project is probably identified correctly, but one important point still needs a written answer, such as phase, tower, timing, or which document controls the next payment.
Re-check before proceeding — the result cannot yet be tied cleanly enough to the project you are considering.
That small classification helps you act on evidence rather than on a vague sense of progress. If you are still comparing launches before creating a separate log for each one, browse current off-plan properties, compare developers, or narrow the shortlist with the property quiz.