Monthly Register — November 2025

One project, three mandates, one set of drawings. Delivery teams working across Dubai, Abu Dhabi and the Kingdom of Saudi Arabia were saying that before Big 5 Global opened at the Dubai World Trade Centre on 24 November, and they were still saying it after the last session closed on the 27th. The hall gave the sentence a room. It did not give anybody a portal.

A late-November gathering of that size in Dubai always throws up a certain amount of weather — stages, demonstrations, somebody announcing that the region's next digital permit wave has arrived. The weather is not the story. What the weather was about is.

The most useful hour of a show like that is rarely on the programme anyway. It is two document controllers from different joint ventures standing by a coffee stand comparing naming strings, and finding out that they have each solved the same recut in a slightly different way.

What moved

The object those teams kept naming is a filing problem with a delivery date attached. A single appointment has to satisfy Dubai Municipality, an Abu Dhabi permit path and MOMRA, and those three authorities do not share a portal, a pack shape or a review clock. One project. Three filing systems. One drawing set that gets recut until each window accepts it.

That is not a new rule, and nobody should read November as the month it appeared. It was already the ordinary condition of live Gulf work. What the show did was make it audible to people who never sit in the document-control cabin: the commercial director, the partner's board, the visiting client representative who had assumed the model was the submission.

What it did not do was reduce the number of uploads anybody went home to. A BIM execution plan that says the job is aligned will not tell a controller which file the second portal is going to bounce. A model that is current in the authoring seat is not, by that fact, the pack Dubai will open, or the pack Abu Dhabi will open, or the pack a MOMRA window will open. Suitability codes on a title block do not travel if the portal wants a different naming string, a different sheet list, or a PDF where the model was the working object.

The labour that follows is clerical, expensive and almost entirely invisible in the fee. Somebody produces three containers from one issued set. Somebody keeps three revision stories that have to remain the same story if a later reader asks what was current on the day the concrete went in. Somebody explains, for the third time that month, that the cabin pack, the permit pack and the shared-drive pack are not three views of one state — they are three states that happen to share a building. That somebody is usually the document controller, and usually the only person in the room who can say, without looking anything up, which of the three is behind.

The clocks make it worse, because they are not the same clock. Comments come back from one window while a second has not yet opened the submission, and the design team answers both against a model that has moved on in the meantime. Whichever pack goes back first becomes, in practice, the version that gets built to, whatever the transmittal register says. None of that shows up on a programme as an information problem. It shows up as a permit date slipping, which is how it gets discussed at the progress meeting and why it never gets fixed.

Vendors were on the floor selling the cure, as they always are. A pitch offering one environment for the Gulf is not movement in itself; it is a cover on the habit this column has been describing since its first issue, a drawing pack with a new first page, now with a Dubai dateline. New vocabulary attached itself to the same recut through late 2025. Digital permit. Model submission. Common data environment. The test underneath is unchanged: can the job name the issued set — these sheets, this model state, this revision, released to these companies, for this purpose — and then show which recut of that set each authority actually holds? Three folders and a phone photograph of a stamp is not an answer, though it is a very common one.

Cross-border appointments make the recut heavier rather than different. A job sitting in two emirates, or in the Emirates and the Kingdom, still has one programme and one commercial story, and still has no single filing system. Teams that treat the ISO 19650 language in the execution plan as a substitute for three portal disciplines tend to discover at permit stage — the worst moment and the dearest one — that the published set had only ever been published to itself.

So the month's movement is a corridor conversation rather than a clause. The industry gathered in Dubai, argued about the right thing for four days, and went home to a pack that still has to be made three times.

What changed in the standards

An exhibition is not a publication, and no new part of ISO 19650 was published in November. A slide claiming the series has moved is not a part of it.

What the year had already put on the shelf does not acquire a November commencement because a hall opened. Part 6, on health and safety information, was the January text, and most BIM execution plans had still not absorbed it by the last working day of the month. Adoption, not a scoop.

The revision of Parts 1, 2 and 3 — concepts and principles, the delivery-phase process, operational-phase implementation — remained a drafting conversation. Committee drafts and comment labour belong to the ISO project record, and they do not get a fresh dateline because the industry happened to be in Dubai. Appointments describing themselves as ISO 19650 aligned were still aligning, if they aligned to anything, to the parts already published.

The Building Safety Act's information duties in England were already in force. They are not a Gulf permit rule and they are no substitute for one, which is worth saying out loud because the golden thread turns up in Gulf tender replies with some regularity now.

Gulf permit-stage BIM requirements remain a class of public-record rule wherever the text is public, and each has an owner. Dubai Municipality, the Abu Dhabi municipal path and MOMRA publish their own windows, their own pack rules and their own clocks. None of the three gets an invented circular number or a November commencement here, and if a national text or a portal rule did change during the month it belongs in a later correction, once it can be cited.

The distinction worth carrying out of November is not a number at all. A mandate is a public-record duty with an owner. A corridor conversation about "the three mandates" is a conversation. Collapsing Dubai, Abu Dhabi and MOMRA into a single GCC BIM requirement is how a team writes a slogan into a tender and then fails the second upload. Three texts do not become one text because they were discussed in the same week, by the same people, in the same building.

One thing to watch

Whether the three-mandate sentence survives the halls going dark — not as a brand, as a filing problem. Who can name the issued set. Which portal holds which recut. Whether the common data environment behaves like a state machine or a warehouse that can export three archives. Whether the permit model is the published set or a PDF with a new cover and a new file name. This issue is dated the day after the last hall closed, so the fortnight is still ahead of us. Ask again in the middle of December and see who is still arguing.

Watch the word aligned on a Gulf appointment. If it means the published ISO 19650 language plus three named portal disciplines, good — say which three, in writing. If it means a single upload to be adapted later, somebody has bought a rumour. And if three applications now claim to be the Gulf environment while the second municipality still rejects the pack, November changed nothing that matters.

Watch, too, whether one project, one model survives first contact with the second window. A model that cannot be recut into the pack an authority will actually open is an authoring file with a story attached. The honest test is whether anyone can still point at the same revision in all three stories after the stamp, or whether the cabin, the shared drive and the portal have already drifted apart.

If there is one thing to put into the next appointment while it is still being drafted, it is separation: exchange-information requirements that set out each authority's pack rules on their own terms, with the naming string and sheet list each window expects, rather than one line saying the job is 19650 aligned. Then name the person who keeps the three revision stories reconciled, and put hours in the fee for it, rather than assuming the document controller will absorb the work between other duties. That costs money at tender. It costs more at permit stage, paid by whoever has least time.

December closes the year, and there is no need to write that review early. The hall bought a room in which the three-mandate problem could be heard out loud, which is not nothing. It did not buy a second portal, or a third.