DLD Initial Registration and Project 360: What Dubai Buyers and Developers Should Verify

1. What was announced, and when?

DLD announced Initial Registration on 3 September 2026. It connects project and transaction registration with escrow management, uses AI document extraction and supports eligible standard transactions. Project 360 combines unit, escrow, financial and project records with early indicators. Developer access uses defined permissions and separate submission and review roles.

WAM corroborates the launch date. At this article’s 16 September review, the announcement is 13 days old: this is practical analysis, not breaking news. DLD’s 11 September report on its London participation on 9–10 September provides broader context about connecting regulation, data and digital services.

References: DLD — Initial Registration announcement, 3 September 2026 · WAM — launch corroboration · DLD — London report, 11 September 2026

2. Separate public enquiries from developer access

DLD’s public Project Status Enquiry provides project details and completion information using a project number, land number or project name. Its listed channels include the website, Dubai REST and WhatsApp. Use that official service for enquiries across Dubai; this article has not checked an individual project.

Our reading of the launch announcement is limited: it does not establish public access to all Project 360 balances, universal instant approval, changed legal rights or guaranteed delivery. This operational announcement alone is not evidence of a legal change.

For a decision on 16 September, compare the date of each underlying record with that decision date. A recent download can contain an older inspection. Record both dates, and ask what period the information covers. A missing field should remain an open question.

References: DLD — Project Status Enquiry · DLD — scope of the launch announcement

3. Compare six kinds of evidence

The following is DR’s proposed reconciliation checklist, not a DLD approval test. Read each row separately: agreement in one category does not resolve a difference in another. Keep an unresolved-items column in your own working copy.

References: DLD — scope of public project information · Law No. 8 of 2007 — escrow framework · Decree No. 33 of 2020 — authority processes

4. Ask for the record that fits the property’s stage

For Dubai off-plan registration checks, DR recommends retaining the applicable registration evidence alongside the signed sale and purchase agreement, amendments and assignment documents. Ask which document records the completed transaction, which merely acknowledges an application, and how its reference can be checked through the appropriate official channel.

DLD’s Verify Title Deed service verifies a title certificate or deed issued by DLD. That service should not be treated as evidence that every off-plan purchaser already has a final title deed.

Keep the original-language record when comparing spellings or translations. Note a name difference separately; do not silently standardise a purchaser’s name in a document. Ask the record issuer to explain the difference and identify the appropriate correction procedure.

References: DLD — Verify Title Deed

5. Trace your payment without assuming access to everyone’s accounts

Article 9 of Dubai Law No. 8 of 2007 requires project-specific escrow, with separate accounts for separate projects. Article 12 allows depositors or their representatives to inspect and obtain their own accounting records. It does not grant general access to other buyers’ private data.

DR’s practical recommendation is to build a payment chain: your transfer confirmation, the recipient’s acknowledgement and the entry allocating the payment to your unit. Compare dates, amounts, currency, reference and beneficiary details. Record any unexplained difference without assigning blame.

Ask the developer and, where appropriate, the escrow agent for clarification through their verified channels. Identify the particular payment and request confirmation of its allocation. An account name or a receipt should not be used to estimate available construction funding. A missing acknowledgement remains unresolved evidence; it is not, by itself, proof of misconduct.

References: Law No. 8 of 2007 — Articles 9 and 12

6. Request a correction while preserving the originals

DR recommends a short discrepancy schedule rather than an edited certificate. Give each issue a reference, identify the two conflicting records, quote the relevant field accurately and state the clarification requested. Distinguish a suspected error from a change supported by a later document.

Send the request to the organisation responsible for that record. Ask it to confirm whether an amendment, replacement extract or another formal step is appropriate. Keep the acknowledgement, request number, response date and any revised document. Do not assume a developer’s explanation has also corrected an authority or bank record.

• Preserve original files and emails; annotate separate working copies.
• Share only the records needed through a verified, appropriate channel.
• Ask what changed, who issued the correction and its effective date.
• Keep earlier and corrected versions together with the explanation.
• Recheck dependent records and mark the issue resolved only to the extent confirmed.

7. A hypothetical unit-reference mismatch

Hypothetical example only: a buyer’s SPA identifies Unit A-1204, while a payment acknowledgement identifies Unit B-1204. The payment amount and purchaser name agree. No actual project, buyer or developer is described.

The sensible next step is to compare the transfer reference and registration evidence, then ask the issuer whether the building letter reflects a documented renumbering or an entry error. Preserve both documents. Request written confirmation of the intended unit and a corrected acknowledgement if appropriate.

Until clarified, label the allocation unresolved. Do not change the receipt yourself, infer that another buyer received the credit, or describe the mismatch as fraud. If corrected, check whether the same error appears in the purchaser ledger or later statements.

8. What each participant should do differently

DR’s recommendations differ by role because each participant controls different documents and decisions. A shared checklist helps, but the person who can explain a sales reference may not be the person authorised to correct registration or accounting records.

• Buyers: request a dated evidence pack for the exact unit. Separate what you have verified from what the seller or developer has stated, and identify the next document needed.
• Sellers and brokers: check the seller’s identity and authority, describe the registration stage accurately and carry unresolved discrepancies into the transaction discussion. Preserve the source behind each material representation.
• Developers: compare extracted fields with source documents, nominate a reviewer for exceptions and reconcile sales, registration and finance records. Record who approved a correction and check its effect across connected records.
• Existing owners: preserve historical assignments, amendments and payment acknowledgements. A newly issued summary should be reconciled with that history before an earlier discrepancy is treated as resolved.

9. Keep authority decisions separate from platform records

For unfinished or cancelled projects, Decree No. 33 of 2020 assigns functions to the Special Tribunal and RERA, including processes concerning completion and liquidation. A platform entry does not replace the applicable authority decision. DR’s separate committee guide explains that framework; this article provides general information, not individual legal advice.

References: Decree No. 33 of 2020 — Articles 6 and 9

10. Turn the comparison into a dated working file

Create a one-page index listing each record, its issuer, document date, retrieval date and the question it answers. Add a separate list of unresolved differences, the responsible contact and the next requested evidence. This gives the next reviewer a clear starting point.

Refresh material official information when the decision date changes. The aim is a traceable account of what is known and what remains open, not a claim that the project is risk-free. If you need help organising a fragmented owner file, request a confidential assessment from Development Resolution.