Project location

The emirate decides which authorities can even apply — pick the project's location first, and every step after filters itself automatically.

United Arab Emirates — tap an emirate to zoom to it and select it; tap it again, tap the sea, or press Esc to zoom back out

Covered by the portal Selected Coming soon

What type of project is this?

This narrows the requirement list further — a villa doesn't need the same NOCs as a master plan.

Which authorities does this project fall under?

Filtered to —. First pick the one authority that issues the final building permit, then add every common service authority that also applies.

Building-permitting authority

pick exactly one

⚠ A project sits under only one building-permitting body — DM, DDA, Trakhees and RAK Municipality can't apply to the same project at once, so this list is single-select.

Common services authorities

pick as many as apply

ℹ Authorities whose whole NOC list is pulled in together. Anything picked one NOC at a time — RTA, DEWA, Civil Defence, telecom, district cooling — is in the next step.

Master Developer

pick as many as apply

ℹ Only applies if the project sits inside a master developer's jurisdiction. Skip if not applicable — and if the developer isn't listed, add it by name below.

Added developers are recorded on the tracker and travel with the approval request. They pull in no NOCs on their own yet — their requirement lists still need to be built in the Authorities Hub.

Services

Situational NOCs that only apply depending on the project — near an airport, discharges to stormwater or sewer networks, district cooling, and similar. Each item below is its own NOC — pick individually, skip anything that doesn't apply.

Project details

All fields required — used to label the generated tracker and set the timeline's start date.

Project name*

Project code*

Owner name*

Plot / location*

Target design-NOC start date*

Approval rounds Submissions per approval, including the first. 3 = submit, comments, resubmit, comments, resubmit.

Comment turnaround (calendar days) Our time to implement each round of comments and resubmit. Design production time is added separately by the team.

Phase scope*

Design only

Design + Supervision

Generated tracker

🔗 Link mode is on. Click the predecessor activity, then the successor. New links are created Finish→Start with zero lag — change the type or add lag in the relationship panel. Press Esc or the button again to stop.

Seq	ID	Authority	NOC / Requirement	Dur	Start	Finish	Float	Predecessors

Schedule

✋ drag a bar to move or resize it · ⌨ type over the number on a bar to set its duration · 🔗 Link and ✂ Unlink to change relationships

Critical path (zero float) Has float Pinned start (constraint) Relationship

Changing the sequence. Drag a row by its handle, or use the arrows in the Seq column, to move a NOC up or down. The table, the Gantt and both exports all follow that order, and activity IDs renumber to match. Relationships stay attached to the activity itself, so reordering never rewires the network — if you want the logic to follow the new sequence, use Re-chain in this order, which rebuilds the default Finish→Start chain and discards hand-drawn links.

How the schedule is built. Dates are calculated forward from your start date in calendar days, the way the authorities and your own trackers count them: an activity starts as soon as every predecessor allows it. The backward pass then gives total float, and anything with zero float is drawn in red as the critical path. Default links chain each authority's NOCs Finish→Start behind the AOR appointment — that is a starting point, not gospel, so relink anything that actually runs in parallel.

Durations marked "~ (est.)" weren't stated in the Authorities Hub source — confirm them with the authority, or drag the bar's edge to set the real figure (which clears the estimate flag). Dragging a bar's middle pins its start as a Start On or After constraint, shown with a dashed edge; clear it from the relationship panel. Edits only change this project's tracker copy — they never touch the reference durations in the Authorities Hub.

Primavera P6 export comes in two flavours. .xer is P6’s own format and imports through File → Import → Primavera XER. P6 XML (MSPDI) writes MSPDI XML with a WBS level per authority, all four relationship types with lag, activity constraints, total float and the critical flag, plus a Mon–Fri 8-hour calendar. Import it through File → Import → Microsoft Project XML and the network comes across with the links intact.

Sign in required

This page is under construction

Build the whole programme in three choices

Project location

What type of project is this?

Which authorities does this project fall under?

Building-permitting authority

Common services authorities

Master Developer

Services

Project details

Generated tracker

—

Schedule