Why Trakhees Approvals Get Rejected or Delayed in 2026

Trakhees CED uses its own drawing standard, completely incompatible with Dubai Municipality's DBC 2026 format and DDA's Circular 400 standard. A consultant who prepares a DM- or DDA-format set for a Trakhees submission triggers an automated layer-validation failure before any engineer reviews the drawings.

What specifically fails: DM-style layer names (A-WALL-EXT and similar) don't match Trakhees's own layer naming convention. Site plans at DM's standard 1:500 scale don't meet Trakhees's 1:200 requirement. Structural calculations submitted inline within the drawing set, rather than as the separate certified PDF Trakhees requires, are treated as missing.

The fix: confirm your consultant is currently Trakhees-registered and is drawing to the current Trakhees CED template — not adapting a DM or DDA set. This is not a five-minute correction once discovered; the drawing set typically has to be redrawn from the base layer structure up, which is why this single cause accounts for the largest share of multi-week Trakhees delays.

From 2026, Contractor All-Risk Insurance and Workmen Compensation Insurance certificates must be uploaded at the point of Trakhees portal submission — not produced later when physical works are about to begin, as was accepted under the previous process.

Consultants and contractors still working from pre-2026 practice submit without these certificates, expecting to provide them at the construction-start stage as before. The submission is held at document validation until both are uploaded, adding a delay that has nothing to do with the design and everything to do with an outdated checklist.

The fix: have both certificates ready and current before the portal submission is made, not scheduled for later in the programme.

Trakhees registration is entirely separate from DM and DDA registration. A consultant or contractor registered with DM but not with Trakhees cannot submit to the Trakhees e-Permit portal — the portal rejects the login itself, before any documents reach a reviewer.

This surfaces in two ways: a consultant assumed their DM accreditation was sufficient, or — more expensive — a contractor was appointed and construction was scheduled before anyone confirmed current Trakhees registration, discovered only when the CED permit is ready to be released and the contractor cannot be attached to it.

The fix: verify both consultant and contractor Trakhees registration certificates before appointment, not after drawings are approved. The check takes minutes; the consequence of skipping it is a stalled project with an already-agreed contractor who cannot legally proceed.

For any Palm Jumeirah works within 3 metres of the plot boundary, Trakhees CED requires a geotechnical investigation report in its 2026 template. Reports prepared to the previous format — including reports that would have been accepted in 2025 — are rejected at document validation, not returned for engineering comment.

This catches property owners and consultants who commissioned a geotechnical survey before confirming the current template was in effect, or who are reusing an older report from a previous, unrelated application on the same plot.

The fix: confirm the current Trakhees geotechnical template with your consultant before commissioning the survey, not after receiving the report.

Trakhees CED will not accept a submission for a Nakheel-community project without the Nakheel NOC reference already secured and entered into the drawing title block. Consultants unfamiliar with the Nakheel-first sequence sometimes submit to Trakhees in parallel with the Nakheel application rather than after it, expecting to add the reference once issued — this is rejected outright rather than held pending.

A related and equally common cause: the Nakheel NOC application itself is submitted with generic scope wording ("renovation works," "villa modification") rather than a description specific enough for Nakheel's design review to assess against community guidelines — Nakheel rejects generic applications before Trakhees is ever reached.

The fix: apply for the Nakheel NOC first, with a scope-specific description, and only begin the Trakhees CED submission once the NOC reference is in hand.

JLT sits within the Trakhees zone, but DMCC — not Trakhees — is the master developer, and a DMCC building management engineering NOC is required before the Trakhees CED submission proceeds. Consultants used to a straightforward Trakhees CED process for other zones sometimes miss this JLT-specific pre-condition, submitting to Trakhees directly and having the application held pending DMCC sign-off — a delay that can run 7–21 working days depending on the building, longer than Trakhees's own review typically takes.

The fix: confirm the DMCC NOC requirement and initiate that application in parallel with drawing preparation, rather than discovering the requirement at Trakhees submission stage.