Nothing much happens on the last working day of December. The office is half empty, the site is on skeleton cover, and the only people still answering email are the ones chasing a signature they should have chased in November. It is a decent vantage point, though, because you can see the whole year from it, and 2024 did not produce a single dateline worth putting at the top of a page. No trade show, no award, no funding print carried the close of the year.
What the year produced instead was four conditions, all of them still true tonight, and all of them concerned with the same thing: who can prove what the project issued.
What moved
Sprawl first, because it was the condition rather than the exception. A mid-size job ran a model platform, a document platform, a field app, a commercial system, and a trail of email behind all of them. Each purchase was rational for the team that made it. None of them, singly, could tell you which revision the site was working to at half past nine on a wet Wednesday. Forty systems and no single source of truth was the diagnosis in the autumn and it was still the diagnosis in December.
The interesting part of that story in 2024 was the false remedy. Moving the same files into a more elegant cloud did not, by itself, produce an issued set of record, and it frequently made the underlying problem harder to see: the record looked unified because one login showed all of it, while the contract parties still could not take a complete copy home. Tidy is not the same as retrievable, and 2024 was the year a lot of teams learned the difference the expensive way.
Second, ISO 19650 as the language of the job — including on jobs where the common data environment was a shared drive with permissions. BIM execution plans cited the parts. Exchange information requirements borrowed the vocabulary. Suitability codes appeared on title blocks. The clause set was in use. The container discipline that clause set assumes — states, suitability, one published set — was not, on a large share of live projects, in use in the same way. That gap is not a 2025 problem waiting to arrive. It was the 2024 problem, and it was written in the standard's own words, which is what made it awkward to argue about in a progress meeting.
Third, in the United Kingdom, the golden thread completed its move from conference vocabulary to record duty. The Building Safety Act had put higher-risk buildings under a regulator that expected an identifiable, available, change-controlled set of information — not a folder named "golden thread" and left until practical completion. Teams spent the year working out what that meant for the issued set day to day rather than for the handover pack. The Grenfell Tower Inquiry's Phase 2 report, published on 4 September, kept building safety — products, competence, regulation — squarely in the public record; it was not, and was never described as, a new information-management standard. The consequence the Act already assumed is the one that bit: if you cannot produce the record when the principal accountable person or the regulator asks, what you have is a filename.
Fourth, in the Gulf, BIM-at-permit stopped being only a slide. Dubai Municipality's 2023 circular required Open BIM submissions with new building-permit applications from 1 January 2024, for specified classes of building — taller blocks, larger complexes, specialised buildings, government work. That is a public-record rule. Elsewhere in the GCC, clients and programmes kept talking about the model, or the information container, as part of the gate, and talk is not a decree; there was no nationwide commencement elsewhere to match Dubai's circular. What document controllers actually met was a permit conversation treating "published" as a submission object, and a habit that still tried to satisfy it with a PDF and a new cover sheet.
Four dialects, one year, one argument underneath.
What changed in the standards
No new part of ISO 19650 was published in 2024. The working texts most BEPs still pointed at were the parts already in circulation — information management through delivery, plus the adjacent parts for assets, exchange and security where a client had asked for them. They were not new this year. They were in use this year, which is the more useful fact.
Part 6, on health and safety information, spent the year in the draft machinery. The draft international standard's vote closed in February. The text was approved for the final draft in July. The final-draft ballot ran through October and November and closed on 28 November. By tonight the part is under publication and not yet the published standard. Comments were collected. That is the whole of the standards news, and it deserves no commencement date it has not earned.
In England, the Building Safety Act's information duties were already in force and did not arrive in December. On 31 October, sections 114 to 116 of the Leasehold and Freehold Reform Act 2024 commenced — a leaseholder-protection change to remediation orders rather than a new golden-thread clause. October's issue covered it and it has not changed since.
The Grenfell Phase 2 report is a public inquiry rather than a British Standard, and belongs here only as context: the year closed with the safety-information argument still live, and with no replacement text from the UK BIM Framework that would have rewritten the ISO parts BEPs already cite.
The Dubai circular remains the Gulf clause that can be named without embroidery — thresholds, Open BIM, permit application, first phase, 1 January 2024. Where other Gulf authorities have asked for BIM at the gate, the text is worth citing once it is public. A vendor's claim of a "nationwide mandate" is not.
One thing to watch
Whether the four stories start occupying the same conversation in January. ISO 19650 language without container discipline. Sprawl treated as normal. A UK duty that assumes a single, change-controlled record. A Gulf permit rule that treats the model as a submission. Four industries on the agenda, one issued-set problem in the room.
The fortnight test still applies, and it has held up all autumn. If people are still arguing in two weeks' time about which revision the site is building from, whether the golden-thread folder is genuinely the record, or whether the permit model matches the published set, the argument is real and worth following.
Three things to carry into January, then. Ask your client, at the next stage appointment, what they expect to receive at handover and in what form — before anybody builds the folder tree, not after. Ask your own team, once, to name the current issued set from a cold start and time how long it takes; that number is your baseline and it will not flatter you. And when the next platform or portal is proposed, make the exit test part of the acceptance criteria rather than a question somebody asks in year three, when the answer is expensive and the person who signed the contract has moved on.
Read next: Thirty-one questions to ask a CDE vendor before you sign, Writing exchange information requirements that actually get answered, Monthly Register — September 2024.