What approvals does a project in Dubai need?

Typically a stack rather than a single consent: planning and land use, building design compliance covering structural, fire and life safety, accessibility and services, specialist and third-party consents from utilities and other authorities, the construction permit itself, and finally completion and occupancy certification.

Why do approvals delay construction programmes?

Most often because third-party consents with long lead times are started late, because incomplete submissions cost a full review cycle rather than a quick rejection, because design changes made during review restart the clock, and because consents that could run in parallel are processed sequentially when dependencies have not been mapped.

Should approvals be considered during design or after it?

During. The statutory process runs alongside the design process rather than after it. When a design stage is signed off without the corresponding statutory input, later authority comments propagate backwards through every discipline that had already coordinated to the earlier position — and the cost is the recoordination, not the redesign.

Does the contractor handle approvals?

Some construction-stage permits sit with the contractor, but design approvals are the design team's responsibility and generally need to be secured before a contractor is meaningfully engaged. Treating approvals as a contractor issue leaves the design team's assumptions untested until it is expensive to correct them.

How Design Approvals Work in Dubai

Q: Who approves building designs in Dubai?

It depends on where the plot is. The emirate contains areas under the municipal authority alongside development zones, free zones and master-developer territories that operate their own regulatory regimes with their own regulations, submission processes and timescales. Confirming the governing authority for the specific plot is the first step on any project.

Approvals are usually described as a step at the end of design. They are better understood as a constraint that shapes the design from the first week.

Approvals are usually described as something that happens after design — a submission, a wait, a permit. That description is why programmes slip.

In practice the approval framework is a set of constraints that shapes the design from the first week, and a sequence of gates that determines when work can actually start. Understanding its structure is worth more to a client than knowing any particular form number.

Jurisdiction is determined by location, not by building type

The single most consequential fact about approvals in Dubai is that the authority you deal with depends on where the plot is.

The emirate contains areas under the municipal authority and a number of development zones, free zones and master-developer territories that operate their own regulatory regimes — with their own regulations, their own submission processes, their own review bodies and their own timescales. Two functionally identical buildings on plots a short distance apart can face materially different requirements and different programmes.

This is why the first question on any new project is not "what are we building?" but "where exactly is the plot, and who governs it?" Getting that wrong at the outset means designing to the wrong rulebook.

Approval requirements vary depending on jurisdiction, development authority and project type, and both the requirements and the bodies administering them change over time. The governing authority for a specific plot, the consents it requires and their review periods should be established at project inception and confirmed as current, rather than carried over from a previous project.

The layers, and why there are several

Approval is rarely a single consent. It is a stack, and the stack is what generates the programme.

Planning and land use — whether the intended use, density, height and massing are permitted on that plot. This is settled earliest and constrains everything after it.

Building design — whether the design complies with the applicable building regulations: structural, fire and life safety, accessibility, services and environmental requirements.

Specialist and third-party consents — typically the largest source of programme risk, because they involve parties outside the project. Utility providers, civil defence, transport and access authorities, environmental bodies, aviation where height is relevant, and the master developer or community authority where one exists. Each has its own review period, and they do not run to your programme.

Construction permit — the consent to begin, granted once the preceding layers are satisfied.

Completion and occupancy — inspection and certification confirming the building was constructed as approved and may be used.

The layers are sequential in principle and overlapping in practice. Much of the skill is knowing which can be progressed in parallel and which genuinely gate the next.

How approvals interact with design stages

The design process and the statutory process are separate sequences running side by side. Aligning them is a discipline in itself.

The failure pattern is consistent: a design stage completes and is signed off internally without the corresponding statutory input having been obtained. Work proceeds. Coordinated design is developed on an assumption. When the authority responds, the change propagates backwards through every discipline that had already coordinated to the earlier position.

The cost of that is not the redesign. It is the recoordination — structure, services, façade and fire strategy all adjusting to a change none of them caused.

Avoiding it means treating statutory milestones as programme constraints of the same weight as design milestones, and identifying at the outset which consents have long lead times so they can be started early. This is a core part of what design management and project management exist to do, and it is why we hold them as capabilities rather than as administration.

Where programmes actually slip

Third-party consents started late. Utility and specialist authority approvals frequently have the longest lead times and the least flexibility. Beginning them when the design is complete rather than when the relevant information first exists is the most common cause of delay.

Incomplete submissions. A submission missing required information does not fail quickly — it enters the queue, is reviewed, and is returned. The lost time is the full review cycle, not the time to add the missing item.

Design change after submission. Changing a design that is under review can restart the clock. Freezing the submitted scope for the duration of the review is worth more than the change usually is.

Assumed jurisdiction. Designing to the wrong regulatory regime because the plot's governing authority was assumed rather than confirmed is rare, expensive and entirely avoidable.

Sequential rather than parallel processing. Consents that could have run concurrently often run one after another simply because nobody mapped the dependencies.

Common misconceptions

"Approval is a formality once the design is good"

Approval tests compliance against a specific rulebook, not quality. A well-designed building that does not comply will not be approved, and compliance requirements shape design from the beginning.

"The same rules apply everywhere in Dubai"

They do not. Development zones and master-developer areas operate their own regimes. Location determines the rulebook.

"We can submit early and refine later"

Submitting incomplete information generally costs a full review cycle and can damage credibility with the reviewing body. Submitting when genuinely ready is faster.

"The contractor deals with approvals"

Some construction-stage permits sit with the contractor, but design approvals belong to the design team and must be secured before a contractor is meaningfully engaged.

What this means for a client

Confirm the governing authority for the specific plot before design starts — never assume it
Map every required consent and its lead time at project inception
Start long-lead third-party consents as early as the information allows
Align design stage sign-offs with the statutory milestones they depend on
Freeze scope while a submission is under review
Build realistic review cycles into the programme rather than best-case ones

Our practice produces high-quality documentation and navigates regulatory processes across jurisdictions, from Dubai and Abu Dhabi to projects across the Middle East, Africa and beyond. Our lead consultancy capability exists to hold design, technical and statutory inputs together under one accountable lead, and pre-concept work is where the regulatory reading should begin. If you are planning a project and want the approval route mapped before design starts, get in touch.

من الاستوديو.