Why TECOM Approvals Get Rejected or Delayed — And How to Fix Each One

Programme cost: a full review cycle, typically 1–2 weeks.

This is the most common cause and the most frustrating, because the drawings are usually technically fine. They are simply formatted for the wrong reviewer.

What happens: a consultant experienced on Dubai mainland prepares a competent set to Dubai Building Code conventions and submits it to TECOM. It is returned at admin review — before any technical assessment — because it does not meet DDA Circular 400.

What Circular 400 requires that DM format does not:

• Monochrome DWF output rather than standard PDF or DWG export
• Yellow clouding marking previously approved areas not being modified
• Red clouding marking new proposed works
• Discipline-Level-Serial file naming, such as A-G-001

The clouding is the requirement most unfamiliar to DM-background consultants. Its purpose is to let the reviewer see instantly what changed against the approved baseline. Without it, the reviewer must manually compare drawings, and the set is returned.

The fix: prepare in Circular 400 format from the first draft. Converting a finished DM set is not a formatting pass — the clouding requires knowing what the approved baseline was, which means going back to the building's existing approved drawings. Starting in the right format costs nothing extra; converting later costs a redraw.

Programme cost: 1–4 weeks, and potentially a change of contractor mid-project.

These are two separate registration requirements and both stop the process cold.

Consultant registration. Drawings must be stamped by a consultant registered with DDA specifically. A Dubai Municipality registration does not substitute, and it is verified before technical review begins. There is no path where a DM-registered consultant's drawings proceed and get corrected afterwards — if the stamp is wrong, the drawings must be re-prepared and re-stamped by a DDA-registered consultant. That is a redraw, not an administrative fix.

Contractor registration. The appointed contractor must hold current TECOM registration before the NOC is released. In 2026 this is checked at NOC stage rather than at gate-pass stage, which means it now blocks the approval itself.

The failure pattern: a tenant appoints a contractor on price, drawings are prepared and submitted, technical review clears, and then the NOC cannot be released. The tenant either waits for the contractor to complete registration — which is not instant — or appoints a different contractor, having already agreed commercial terms, mobilisation dates and a programme.

The fix — and it takes minutes: before appointing anyone, ask for evidence of current registration. For the consultant, confirm DDA registration specifically, not "we do work in the free zones". For the contractor, ask for the registration certificate, not a reference to past projects in the community. If either cannot produce evidence, that is information worth having before signing rather than after.

Programme cost: 3–10 working days, and it is pure dead time.

The building management NOC is the most common admin rejection after drawing format, and it fails for a consistent reason.

What gets rejected: a letter stating only that the tenant is permitted to carry out fit-out works. This is the default template most building management offices issue when asked casually, and TECOM reviewers routinely reject it as insufficient.

What gets accepted: an NOC describing the actual scope — partitions, MEP modification, ceiling changes, wet area installation, shopfront alteration — closely enough that a reviewer can see the building consented to this scope rather than fit-out in the abstract.

Why it costs so much time: the rejection happens at admin review, so you lose the queue position. Then you go back to building management, who process the revised NOC on their own timeline, then you resubmit. Three to ten working days evaporate, none of it doing anything productive.

The fix: draft the NOC wording yourself — or have your consultant draft it — to mirror the submitted scope, and give building management that text to put on their letterhead. Most building management offices will issue what you ask for; they simply default to generic wording when the request is vague.

Also confirm at kick-off: whether a head-permit NOC is needed. Buildings holding a master permit covering all floors often require this in addition, and it is better discovered at the start than at submission.

Programme cost: 2–4 weeks. This is the single largest avoidable delay.

This one is not a rejection at all. Nothing goes wrong, no one makes an error, and the application is approved exactly as submitted. It just takes twice as long as it needed to.

The sequential approach: submit to TECOM, wait 7–14 working days for the NOC, then open the Civil Defence application, wait a further 2–4 weeks. Roughly six weeks before the contractor mobilises.

The parallel approach: submit both packages at the same time. Reviews run concurrently. Total: 14–21 working days.

There is no requirement to sequence them. The DCD application does not depend on the TECOM NOC being issued first. Sequencing happens for two reasons: consultants processing one thing at a time out of habit, or tenants not knowing both were needed until the first approval came back.

When Civil Defence is triggered:

• New or relocated partitions changing sprinkler coverage or escape routes
• Ceiling changes moving detector and sprinkler positions
• Any kitchen with cooking equipment requiring hood suppression
• Server rooms with gas suppression
• Occupancy load increases
• Changes to fire-rated compartmentation

The fix: assess DCD applicability at scoping stage, before drawings begin, and open both applications together. If you are unsure whether your scope triggers it, assume it does and confirm — the cost of checking is a conversation; the cost of finding out late is a month.

More detail in our Civil Defence approval guide.

Programme cost: one comment round, 3–7 working days.

This is the one genuinely technical cause on the list, and it is the most common design-stage comment across every Dubai authority, not just TECOM.

What happens: the submission shows new partitions but retains the original means-of-escape calculations. Adding walls changes travel distances, exit widths and dead-end corridor lengths — so calculations valid for the previous layout are no longer valid for the proposed one.

What reviewers check:

• Maximum travel distance to a protected exit
• Dead-end corridor lengths
• Exit door widths against calculated occupant numbers
• Door swing direction on escape routes
• Occupancy density for the proposed use

The 2026 change: reviewers increasingly expect these calculations shown on the drawings rather than supplied when requested. A set that could satisfy the requirement on request now attracts a comment for not showing it upfront.

Where it bites hardest: training rooms and classrooms in Knowledge Park and DIAC, where educational occupancy density drives exit width harder than open-plan office; and retail and F&B, where public occupancy raises the stakes on escape provision.

The fix: recalculate occupancy load and means of escape as part of drawing preparation, and show the calculations on the submitted drawings. This is a half-day of consultant time that prevents a week of review cycle.

Programme cost: weeks to months, because the fix sits outside the fit-out process entirely.

The mismatch problem. A fit-out designed for an activity not listed on the trade licence is rejected regardless of technical quality. This catches tenants who changed business model mid-lease — an office being fitted with a commercial kitchen, a retail unit converted to F&B, a warehouse being turned into a showroom.

The fix is not a drawing revision. It is a licence amendment or a Change of Use permit, which is a separate process on its own timeline. The fit-out submission cannot proceed until it resolves.

Check this at kick-off. Compare the licence activity against the intended use before commissioning any design. It takes five minutes and it is the difference between a normal project and a stalled one.

---

Recovering an application that is already stuck

If you received comments: address every comment explicitly, including any you disagree with — an unanswered comment stalls the whole resubmission. Revise the drawings, update the clouding to reflect the changes, and provide a written response schedule mapping each comment to the revision that resolves it. Resubmit under the same application reference.

If the application has gone quiet: follow up under the existing reference. Do not file a fresh application — that surrenders your queue position and starts the clock again. This is a costly and surprisingly common mistake made by people who assume silence means the application was lost.

If you were rejected at admin review: identify which document or format rule caused it before resubmitting. Resubmitting the same package with one thing changed, hoping it was that thing, wastes another cycle. Work through the full document checklist systematically.

If the contractor is the blocker: decide early between waiting for registration or changing contractor. Waiting is often the right call, but only if you have a realistic date. An indefinite wait is worse than a contractor change made decisively in week one.

Our TECOM approval team takes over stalled applications regularly — the first step is always diagnosing which of these six is actually the blocker, because the recovery path is different for each.