A short one, because August was short of anything worth reporting. Half the people you would need for a decision were on leave, and the other half spent the month covering for them. Design offices thin out. Tender desks stay quiet until September. Site programmes, of course, do not: concrete arrives, steel goes up, and the unofficial PDF set keeps circulating while the people who wrote the execution plan are somewhere with better weather.
No show, then, no anniversary and no published clause. What is worth writing down is where the revision of ISO 19650 Parts 1, 2 and 3 had actually reached by the end of the month, because a good many people will come back in September and say something confident about it. Better to have the stage straight before the confident version starts circulating in tender responses.
What moved
Parts 1, 2 and 3 — concepts and principles, the delivery-phase process, and operational-phase implementation — were under revision. None of that is August news. Systematic reviews in 2023 and 2024 had already come back in favour of opening the 2018 and 2020 texts. Working drafts occupied the winter. Committee drafts were registered in early April, and the committee-draft comment period closed on 29 May. Those dates belong to the ISO project record, and they do not acquire a fresh dateline because August happened to be empty.
By the last working day of the month the revision sat between two stages and at neither of them. The comment window was shut. A Draft International Standard had not been registered. Public enquiry had not opened. A June industry briefing — a briefing, not a circular — named 867 comments from ten countries against the three committee drafts, and a three-day working-group meeting had already taken place in early July. What was going on through late August was the ordinary, unpublished labour of turning those comments into DIS text. That is drafting. It is not a publication, and it changes no clause a BIM execution plan can point at.
Which brings you to the mismatch worth recording. The series most jobs still name as their information-management language was being rewritten in committee, and every one of those jobs was being run on the published 2018 and 2020 parts, plus whatever local habit had grown up around them. The habits are the stubborn part. On a large share of live work the issued set is still a folder of PDFs. Suitability codes still sit on title blocks the plotter ignores. Common-data-environment states are still, on too many appointments, folder names. The revision will have to speak to those objects eventually. In August it had not spoken in any text the industry could comment on in public.
You can see the gap clearly enough in a fortnight of cover. The document controller holding two projects while a colleague is away is not thinking about concepts and principles. She is thinking about a package that went out on Friday with a suitability code somebody changed in a title block and nowhere else, and about a request for information that names a folder rather than a revision. That work carries on at the same rate in August as in any other month, and it is the work the revision either reaches or does not.
So a pitch that says "aligned to the coming revision" is aligned to nothing an appointment can cite — a drawing pack with a new first page.
What changed in the standards
No revised ISO 19650-1, 19650-2 or 19650-3 was published in August, and the UK BIM Framework issued no replacement national text over the summer.
The working texts most execution plans still pointed at were the published ones already in circulation: Part 1 and Part 2 from 2018, Part 3 from 2020, Part 4 from 2022, Part 5 from 2020, and Part 6 — health and safety information — from January 2025.
The rest is stage rather than substance, and the distinction earns its keep here. A committee draft is not a clause. A comment is not a commencement, and a working-group meeting in July is not a national annex. The honest sentence for the month is that the revision of Parts 1, 2 and 3 had left committee-draft consultation and had not yet entered Draft International Standard enquiry, and that appointments claiming ISO 19650 alignment were aligning — if to anything — to the 2018 and 2020 language. If a specific circular or a published DIS ballot did move in August, it belongs in a later correction, once somebody can cite it.
Gulf permit-stage BIM requirements remain a class of public-record rule when the text is public; none of that arrived in August. The Building Safety Act's information duties in England were already in force, and they did not arrive with the holidays either. Duties that were live in July were live all through the shutdown, whoever happened to be covering the inbox.
One thing to watch
Watch for the next public stage rather than the next slide. The working group's own public timetable, as briefed to the industry earlier in the year, pointed at DIS text through the autumn and a public enquiry in 2026; no submission date worth quoting exists yet. When a Draft International Standard does go out, the question to put to it is whether it changes the objects document controllers actually argue about — container states, suitability, an issued set that is the same object the site will plot from — or only the cover language on an execution plan.
There is also a small thing to do in September, when the offices fill and the tenders restart, and it costs a question rather than a budget. Watch the word "aligned" and make people finish the sentence. If it means the 2018 text, that is a perfectly respectable answer and nobody should be embarrassed by it. If it means a committee draft the appointment cannot cite, somebody has bought a rumour and will be defending it at handover instead. Appointing parties can settle this in a line of the information requirements, and it is easier to settle now than in a fortnight's tender flurry. Anyone presenting a "revision update" internally can reasonably be asked which published part the BEP names today.
What the summer bought is time in committee. It did not buy a new working text, and it retired not one folder.
Read next: What ISO 19650 actually requires of a common data environment, clause by clause, The last mile: getting information to a gloved hand in direct sunlight, Monthly Register — May 2025.