Dubai Municipality, Abu Dhabi and MOMRA: three mandates, one project

Sit with a submissions lead on a multi-city job for an afternoon and you will watch three portals open in three tabs, each with its own credentials, its own idea of an acceptable filename, and its own idea of what the word model means. The industry still talks about "Gulf BIM" as though it were a single mandate. A project that has to satisfy Dubai Municipality, an Abu Dhabi municipal and planning stack, and the Saudi municipal and housing ministry that most appointments still call MOMRA is dealing with three information and submission regimes that share none of those things.

Thresholds, forms and platform names move about, and anyone quoting them from memory is usually a fortnight out of date. The pattern underneath them is steadier: one issued set is the source, and the three authority packs are extracts from it. Treat the extracts as the same zip uploaded three times and you will fail at permit in at least one jurisdiction — and, more expensively, lose track of which issued identity the works are actually building from.

Three mandates are not a region

A region is a market. A mandate is a named authority asking for a named pack, in a named format, from a named licensed party, at a named gate. Dubai Municipality is one such ask. Abu Dhabi — municipality, planning, and the Estidama Pearl track that sits beside them — is another. MOMRA's municipal building-permit track in the Kingdom is a third. Roll the three together as "the GCC requirement" and a coordinated design quietly turns into three unofficial sets.

The "one project" in the title is an information fact rather than a plot-boundary one. It is the appointment that keeps a single published coordinated set — architecture, structure, MEP, civil — and then has to produce authority-facing packs for more than one of those regimes. Sometimes the client really does hold plots in two cities. Sometimes the same typical is being rolled out. Often enough the appointment is written as one programme and the document-control desk is told, in one sentence, to "submit the BIM". There is no such deliverable, and whoever wrote the sentence is rarely the person who spends the next fortnight discovering it.

ISO 19650, FIDIC and the local building codes each have owners. What they share is an assumption: that you can say which container is authorised for which use. None of them assumes that a municipal portal, a sustainability worksheet and a construction common data environment are the same system of record.

The one issued set

An issued set is a bounded act — these containers, these revisions, this purpose, this list of recipients, this moment. On a multi-mandate job the purpose that matters first is authorised for extraction. The construction published set is allowed to be richer than any permit model. It is not allowed to be a different building.

What most desks actually hold is weaker than that. A federated model the coordinators live in. A drawing register the document controller keeps. A permit folder somebody zipped last month. An energy model the sustainability consultant never checked back into the same identity scheme. Each copy is sincere in its own corner; together they are four buildings wearing one name.

Diagnosis starts by naming the source and then defending it against the portals. An authority pack is a view. If that view cannot be traced back to a published container — same objects, same geometry that matters at the gate, same revision pairing — there is no mapping in place, only a courier.

What Dubai Municipality typically wants

Dubai Municipality's typical ask is a staged building-permit pack through a municipal digital service, not a login to your common data environment.

The core of the pack is stampable sheets: architectural, structural and MEP drawings that a licensed Dubai consultant can take responsibility for, plus the calculation and code-compliance reports sitting behind them. Plot, ownership and consultant-licensing documents travel with the pack; they sit outside the model and gate it.

Where a size, height or typology trigger applies, a model is asked for as well. This is a typical pattern rather than a quoted threshold, so check the current service: the municipality wants a permit model it can open, not the construction federation. Storeys, fire compartments, occupancy and the geometry proving the Dubai Building Code story are in scope. Fabrication bolts, temporary works and last week's coordination clash are not. Teams that upload the federated construction model because "it is more complete" are answering a question nobody asked, and they often fall over a file-size or object-scope check that a thinner model would have walked through.

Around the municipal pack sit the NOCs — electricity and water, roads and transport, telecoms, civil defence. None of them are Dubai Municipality's model and all of them can stop the same permit. Each has its own sheet lists, stamps and portals, and a green cell in the drawing register moves none of them.

Formats follow the gate rather than the authoring tool. PDF for stamping. CAD still common where the reviewing desk is a drawing desk. Native or IFC when a model is required. Portal naming, sheet indexes and file-size limits will not match the project naming convention, which is not a defect in the convention; it is a transform, and it needs writing down somewhere other than one person's head.

Completion is a later pack again. As-built sheets and a completion model are not automatically the last construction issue, and if the pairing has not been kept you will be rebuilding the permitted building from memory two years after the fact.

What Abu Dhabi typically wants

Abu Dhabi is already more than one desk. The typical pattern is a municipal building permit through government e-services, planning and plot controls that may sit with a different officer than the building permit, and a Pearl Rating submission under Estidama that is a third information object.

At a glance the building-permit pack looks like Dubai's: stampable architectural, structural and MEP sheets, licensed local responsibility, code-compliance reports, ownership and plot documents. That resemblance is how teams get hurt. The code family differs. The sheet list differs. The person who may stamp is not the person who stamped in Dubai. A title block reading "Gulf typical" has never been a licence.

Estidama is the cleanest demonstration that "the BIM" is the wrong unit of account. A Pearl submission wants energy and water performance, materials, and a rating story somebody can assess — usually a calculation model and a worksheet rather than a copy of the architectural coordination model. Handle it as a view of the issued set and you can still say which envelope, which plant and which revision the rating was run against. Handle it as a side consultancy and it will drift, until the building that was permitted is not the building that was rated.

Utility and civil-defence NOCs sit beside both packs. Industrial, airport and energy plots add sector overlays. None of those overlays is "Abu Dhabi BIM". Each is a destination row.

What MOMRA typically wants

MOMRA, on an appointment document, still means the Saudi municipal building-permit track: a national or municipal e-service, stampable sheets, a licensed Saudi consultant, and a demonstration that the Saudi Building Code has been applied. The ministry's public name has shifted. The information ask has not quietly become Dubai's.

The typical pack is architectural, structural, MEP and civil sheets, a geotechnical report, ownership and planning permissions, and a later occupancy or completion file. Civil defence is a separate track. Housing and municipal forms are not always the same desk. None of that is a BIM execution plan.

Saudi work is where two asks wear one word. A giga-programme client, or a delivery authority, will often write model, classification and handover requirements that look a great deal like ISO 19650, while the municipal form still wants drawings, stamps and reports. Mapping the issued set to MOMRA is not the same labour as mapping it to the client's information requirements, and teams that set out to "submit the BIM to MOMRA" usually end up putting a construction model through a drawing gate, or handing a municipal sheet pack to a client who asked for a structured asset register. Both failures are predictable. Both are avoided by naming the destination first.

Stamps do not travel, either. A London or Dubai licence is not a Riyadh licence. If the mapping table does not name the Saudi licensed author for each pack, the source set can be immaculate and the submission still cannot start.

How one issued set is mapped

Mapping is a table, not a folder called Permit. Each row is one source container and one destination.

Write, for every sheet, model or report that may leave the published set:

1. Source identity — container, revision, state, suitability, purpose.
2. Destination authority — Dubai Municipality, Abu Dhabi municipal/planning, Estidama, MOMRA municipal, or a named NOC body. Not "GCC."
3. Destination pack — permit drawings, permit model, Pearl file, code report, completion pack. One row, one pack.
4. Format transform — stampable PDF, CAD, IFC, native, worksheet. If the transform reads "upload the Revit," nothing has been mapped and somebody is hoping.
5. Identity transform — portal name, sheet index, file-size and language rules. The CDE name stays; the portal name is an alias. Overwrite the source name with the portal name and you cannot get home.
6. Licensed author — the person who may stamp in that jurisdiction. The information manager is not that person unless the appointment says so.
7. Revision pairing — design revision and authority-submission revision as two fields. Design Rev D is not automatically municipal submission 02. When the source revises, the previous destination pack has to be withdrawn, because no portal will do it for you.
8. Out of scope — what is deliberately not sent. Work in progress. Fabrication. Quantities. The unofficial hut set. A coordination federation that will choke a permit viewer.

1. 01
   Source identity

   What it capturesContainerrevisionstatesuitabilitypurpose
2. 02
   Destination authority

   What it capturesDubai MunicipalityAbu Dhabi municipal/planningEstidamaMOMRA municipalor a named NOC body — not "GCC"
3. 03
   Destination pack

   What it capturesPermit drawingspermit modelPearl filecode reportcompletion pack — one rowone pack
4. 04
   Format transform

   What it capturesStampable PDFCADIFCnativeworksheet
5. 05
   Identity transform

   What it capturesPortal namesheet indexfile-size and language rules
6. 06
   Licensed author

   What it capturesThe person who may stamp in that jurisdiction
7. 07
   Revision pairing

   What it capturesDesign revision and authority-submission revisionas two fields
8. 08
   Out of scope

   What it capturesWork in progressfabricationquantitiesthe unofficial hut set

One issued set, three extracts, traceable pairs, and a further extract for each NOC body that actually gates the permit. It is dull to maintain, and it is the only part of the arrangement that survives a portal migration.

Do not federate the three permit models back into the construction environment as though they were as-built. They are thinner on purpose. Once they become the unofficial coordination model, the works follow the permit building and the issued construction set becomes a rumour.

Nor should three document controllers run three registers with no pairing between them. That is how a typical window moves in Dubai, stays put in Abu Dhabi, and is still last month's unit in Riyadh.

Where the mapping fails

The failures are ordinary. Most people who have worked a multi-city job will recognise several.

One zip, three portals. Same filename, same objects, same missing stamp.

The permit model becomes the coordination model because it was the file that opened on a laptop in the meeting.

The Estidama energy model is called "the BIM" in the monthly report, so nobody notices that the envelope in the rating is two revisions behind the issued wall.

A UK naming convention is pasted into a portal that rejects the filename, so someone renames by hand at eleven at night and the register still shows the old identity.

The same consultant stamp is used in a jurisdiction that does not recognise it. The pack is complete. The pack cannot be accepted.

Construction level of information is dumped into a permit viewer. Either the upload fails, or it is accepted and then queried for objects the gate never asked about.

NOCs live in mailboxes. The model lives in the common data environment. The permit waits on a letter nobody can find.

Three mandates, one project, no table. That last one has nothing to do with software. It comes from an unwillingness to say out loud that Dubai Municipality, Abu Dhabi and MOMRA are asking different questions.

Limits

A mapping table is not a permit, a Pearl rating or a Saudi municipal acceptance, and anyone presenting it as one deserves the rejection they get. Dubai Municipality, the Abu Dhabi municipal and Estidama owners, MOMRA, civil defence, the utility companies, ISO 19650 and the contract forms all have owners, and their thresholds change — occasionally between the concept submission and the permit submission on the same plot. Read the current circular before you promise anybody a date.

What changes far less is the shape of the problem: one issued set, three extracts, and a pairing still legible after the portal has been replaced. Build the table early, keep it boring, and give a copy to whoever is going to be told to "submit the BIM" to three cities.

Read next: The UK golden thread and Gulf digital handover: what each region gets right, Delivering ISO 19650 on a Saudi gigaproject: field notes, Monthly Register — November 2025, Federated or single: when one CDE is not enough for a gigaproject.