← Insights

Real Estate Development Law in Dubai: Developer Obligations

Every requirement traces back to one thing — the off-plan buyer's instalment sitting in escrow.

The obligations a Dubai developer meets in the order a project meets them: DLD and RERA licensing, project registration, the escrow account, construction milestones and reporting, handover, and defect liability.

Reviewed by Mohamed Noureldin, Founder, Managing Partner & Senior Legal Consultant

Follow a single payment. A buyer signs for an apartment that does not exist yet and transfers the first instalment. That money does not reach the developer’s working account; it goes into a project escrow account, and it comes out only against construction actually completed. Almost every obligation Dubai imposes on developers can be traced back to protecting that payment, and most of the enforcement action taken against developers is about what happened to it.

Read the rules that way and they stop looking like an administrative burden and start looking like a sequence. Get licensed. Register the project. Open the escrow. Build to the approved drawings and the approved programme. Report. Hand over what was sold, with the paperwork. Fix what turns out to be defective. Each step has its own regulator-facing requirement and its own private-law consequence if it is missed.

What follows sets out those obligations in the order a project meets them, together with the contractual arrangements that decide whether a developer meets them comfortably or in a scramble.

Related: our real estate advisory practice acts for developers on licensing, project documentation and disputes.

The developer licence

Development in Dubai starts with registration and licensing through the Dubai Land Department and the Real Estate Regulatory Agency. The licence is not a formality collected alongside a trade licence; it is the permission to hold yourself out as a developer and to sell.

What the vetting looks at

The review covers financial standing and technical capability. On the financial side, the question is whether the applicant can fund the project through to completion rather than fund the start of it: capital, liquidity, the funding structure behind the land, and the track record of any related companies. On the technical side, it is whether the applicant has the people, the consultants and the delivery history that the proposed project requires. Applicants tend to underestimate how much of this is document-driven. Audited accounts, ownership evidence for the land, consultant appointments and organisation charts are checked as submitted, and inconsistency between them delays the file more often than any substantive weakness does.

Keeping the licence

Licensing is a continuing status, not a one-off clearance. It carries conditions: building in accordance with approved plans, submitting progress information, meeting safety and environmental requirements, and keeping the regulator informed of material changes. Where those conditions are not met, the exposure runs from directions and fines through to suspension or withdrawal, and a developer without a valid licence cannot lawfully continue to sell. That is a commercial event, not merely a regulatory one, because sales revenue funds construction and construction unlocks escrow releases.

Project registration and what it puts on the record

Each project is registered separately with RERA before it is marketed or sold. Registration puts the project on the public record and fixes the version of the project against which everything later is measured.

The submission covers ownership of the land, the approved designs, the construction programme, the specification and the financial arrangements including the escrow account. Once registered, the project has a defined scope, and changes to it are a regulatory matter as well as a contractual one. Developers who alter unit layouts, amenities or common areas after sales have begun should treat the change as requiring both approval and disclosure, not as an internal design decision.

The escrow account

The escrow account is the central control in the off-plan model. Buyer payments go into an account held with an approved bank, dedicated to the project, and money is released against construction progress certified in the manner the escrow arrangements require. The account is not a source of general working capital, and using it as one is the single most damaging thing a developer can do to its regulatory position.

Practical consequences follow for the finance function. Receipts have to be traceable to units and buyers. Requests for release have to be supported by the certification the bank and the regulator expect, which means the consultant’s certification cycle has to be fast enough to keep pace with the contractor’s payment cycle. Where those two cycles are out of step, the developer ends up funding the gap from its own resources, which is a cash flow problem created entirely by administration.

Disclosure to buyers

Buyers are entitled to accurate information: title to the land, the approved plans and specification, the programme, the payment schedule, and an honest description of what is being sold, including amenities and common facilities. Marketing material is part of this, not separate from it. Renderings and brochures shown to buyers are read back against what is delivered, and the distance between them is the single most common source of complaints.

The workable discipline is a review step before anything reaches a buyer: sales presentations, brochures, floor plans and website content checked against the registered project documents by someone who has both in front of them.

Related: our real estate lawyers in Dubai review sale documentation and marketing material before launch.

Construction: building to the approved programme

Construction obligations run to the approved milestones and to the approved drawings. Progress has to be reported, and the reported position has to match the site. Where the programme slips, the developer’s position is far better if the slippage has been reported and explained as it happened than if it emerges at an inspection.

Reporting as a system, not a task

The reporting obligation is continuous and is best handled by making the project’s existing progress reporting produce the regulator’s format as a by-product, rather than by re-assembling information every reporting cycle. Where certification, escrow release and regulatory reporting all draw on the same measured progress, the three stay consistent. Where they are prepared separately, they diverge, and the divergence is what an inspection finds.

The contracting chain

A developer’s obligations are owed to the regulator and to buyers, but performance depends on the main contractor, the consultants and a long chain of subcontractors. The contracts have to carry the developer’s obligations down that chain rather than leaving them at the top of it.

That means completion dates in subcontracts that support the main programme rather than merely referring to it, specification and materials obligations that match what was registered and sold, liquidated damages for delay set at a level that reflects the developer’s own exposure, retention and defect obligations that run at least as long as the developer’s own liability to buyers, and access, testing and information rights so the developer can see problems before they become delays. Variations deserve particular attention: a specification change agreed on site with a contractor can put the delivered unit out of line with the registered project and the sale contract at the same time.

A delay worked through

A subcontractor falls behind on electrical installation and the handover date is at risk. A developer whose subcontract sets a firm date, provides for liquidated damages, and gives a right to engage others at the defaulting party’s cost has real options: press the contractor, recover the loss, or bring in additional resource. A developer whose subcontract simply requires work “in a timely manner” has a negotiation. In both cases the buyers’ contractual position is identical, which is why the developer’s remedies against its own supply chain matter so much.

Handover

Handover is where the project is finally measured against what was sold. Units must be complete, compliant with the approved designs and specification, and delivered within the agreed timeframe.

Inspection before the buyer inspects

Run the developer’s own inspection and rectification round before inviting buyers to theirs. Defects found and fixed internally cost a fraction of defects logged by a buyer, which have to be recorded, scheduled, re-inspected and signed off, all while the buyer forms a view about the building. Record the inspection: photographs, checklists, dated sign-offs.

What goes with the keys

Handover is a transfer of documents as well as possession: title documentation, warranties and guarantees for installed systems and equipment, operation and maintenance manuals, and details of the defect reporting process with the contacts and timescales that apply to it. Buyers who are told clearly how to report a defect and what happens next report defects instead of complaints.

Late handover

Where handover is late, buyers have remedies. Depending on the contract and the circumstances they may claim compensation, seek to terminate, or complain to RERA, which can act against the developer. Delay that is being managed openly – notified, explained, with a revised date and, where appropriate, an agreed accommodation – produces fewer claims than delay that buyers discover for themselves.

After handover: defect liability

Responsibility does not end at the door. Developers remain liable for defects arising within the defect liability period, which is typically a minimum of one year and may run longer depending on the contract and the nature of the works.

Running the process

Defect liability is administered rather than argued. What is needed is a single channel for reports, a log that records every report with its date, an assessment of whether the item falls within the liability, a repair schedule, and closure confirmed by the owner. The equivalent obligations must be live down the contracting chain, so that a defect in a system installed by a subcontractor is rectified by that subcontractor rather than by the developer at its own cost.

Take water ingress reported by several owners some months after handover. A developer with a functioning process identifies the affected units, gets the responsible contractor to site under its subcontract obligations, tells the owners what is happening and by when, and closes each report with a record. The alternative is the same repair carried out later, at the developer’s cost, after complaints have been made to the regulator.

Where defect claims go

Contracts should say how disputed defect claims are resolved and provide for something before litigation: a defined escalation, then mediation or expert examination by an agreed specialist, then arbitration or court proceedings. Technical questions about causation are usually resolved faster and more cheaply by a specialist than by a hearing.

Making compliance routine

Developers that stay out of trouble are not the ones with the most legal advice; they are the ones whose obligations sit in a system rather than in someone’s memory. Three habits do most of the work.

  • A dated obligations calendar. Licence conditions, reporting dates, escrow certifications, handover dates and defect liability expiry, each with an owner and a reminder.
  • One source of truth for project data. Progress, certification, escrow releases and reporting drawn from the same measured position, so the regulator, the bank and the buyers all receive the same picture.
  • Contract review at the point of change. Every variation, extension of time and specification substitution checked against the registered project and the sale contracts before it is agreed on site.

Dubai’s development regime rewards developers who treat these obligations as part of running the project, and it deals firmly with those who treat them as paperwork to be caught up on later. The buyer’s first instalment is the reason for all of it, and a developer who can show at every stage exactly where that money went and what it built has already answered most of the questions anyone will ask.

Related Services: talk to our Dubai real estate team about licensing, project registration and handover disputes.

DISCLAIMER

This article is for informational purposes only and does not constitute legal advice.

Additional Resources

Explore more of our insights on related topics:

Call Us NowChat With Our Team On WhatsApp