Monthly Register — July 2025

Renewals are the honest part of July. Somewhere in the second week a commercial manager circulates a spreadsheet of everything the project subscribes to, and the room spends an hour making discoveries: two document platforms, a field app with no identifiable owner, a model environment that arrived with a framework agreement, and a block of seats bought for a bid that closed last year. Mid-year is when the stack gets looked at, usually by people who do not use most of it.

That, plus the funding print that will eventually attach itself to the first six months, is what July offers. June's London halls have closed. There is no trade show this month obliged to carry the half. Which leaves a quieter question: can a job that bought another login in the spring now name one published set?

What moved

The half-year construction-technology wrap reports arrive after the half, and the houses that compile them will publish their own totals and league tables in their own time. What is describable now is the shape of the six months as information managers actually meet it.

Capital in this sector still does not land evenly, and the bias is consistent enough to be predictable. It clusters around work that demonstrates well in twenty minutes: project and field execution, commercial and insurance tooling, preconstruction and design productivity, and anything that can carry the artificial-intelligence label. Those categories generate announcements. They generate category maps. They generate the half-yearly argument about whether the period was "up" or merely "selective".

The narrower object attracts far less of that attention. Call it the information layer: containers with suitability, a published set that is the same object the site will plot from, a record that can say which revision a subcontractor was working from in March and who sent it to them, an audit trail a contract party can take home. None of that films well. There is no dashboard in it and no obvious before-and-after, which is presumably why it is rarely the category the print celebrates. It is, however, exactly the layer a live job is still arguing about a month after the new login arrives, usually between a document controller who wants one place to publish from and a package manager who wants the app his gangs already open.

Underneath the funding conversation sits the renewal meeting, which is where most consolidation genuinely happens. Three products get described as one suite. A field app, a document platform and a model environment turn up on the same invoice. Somebody asks whether two logins can be retired, and somebody else says yes with more confidence than the answer deserves. This is not a named acquisition. It is ordinary July weather in a budget meeting, and in my experience it tends to be decided on licence cost per head rather than on which system anybody would rely on in a dispute.

Consolidation of logos is not consolidation of the record. A suite that still produces a folder here, a field application there, and a model platform sharing no published state with either is sprawl under a single purchase order. Adding a newly funded application to a stack that already runs a model platform, a document platform, a field app, a commercial system and a long trail of email is not the same act as funding the record. Merging two of those seats under one brand does not, by itself, retire the unofficial PDF set.

The distinction that matters on a job has never been software against no software. Either a system makes another container, or it holds containers in states and can tell you which state is current. Read the half-year print for that distinction and it mostly fails. The deck says platform. The renewal says another seat, or the same seats under one logo. The plotter still takes a USB.

Where the sentence of the half is that money went to "AI-enabled" construction software, apply the test March already named. Does the tool read a register, or does it wrap a folder? Can a party who was not in the authoring licence open the published set? If the answer is a chatbot over last week's export, the money has not touched the problem it was raised against.

That is not a complaint about investors, who are funding what they can evaluate, and it is not a complaint about a mid-year tidy either. But it is worth being clear about what the print does and does not purchase. Forty systems and no single source of truth was the diagnosis in the autumn. It was still the diagnosis at the end of the first quarter. It is the diagnosis at the half. A larger cheque to the fortieth system does not close the gap, and neither does a merged invoice.

What changed in the standards

Nothing publishable. No new ISO 19650 part appeared in July, and the UK BIM Framework issued no replacement text to mark the half-year.

Part 6, on health and safety information, was published back in January and remains the working text for classifying and sharing health and safety information through the information-management process. It is not July news, and it is not a commencement. Execution plans that pointed at the older published parts for delivery, assets, exchange and security were not given new numbers this month. A mid-year refresh that adds an artificial-intelligence paragraph, or a new platform name, to one of those plans has changed no clause at all.

The revision conversation around the series is weather rather than a published replacement. Working groups collect comments; national bodies circulate drafts internally. That is as far as the sentence honestly goes this month, and anyone telling you more than that in July is telling you about a meeting they were not in. More on it when there is something citable to point at.

The Building Safety Act's information duties in England were already in force and did not arrive with the half. Gulf permit-stage BIM requirements remain a class of public-record rule when the text is public. And a pitch deck that says "ISO 19650 aligned" — or a suite saying the same thing after two logins became one — is not a clause. That belongs in a vendor conversation.

One thing to watch

When the half-year tables print, later than this and under someone else's byline, do not read the headline total. Read the mix. Did capital go to systems that can prove the issued set, or to another workflow that produces more files?

Read the consolidation sentence the same way. If "one platform" turns out to mean one invoice and three published folders, the job has bought a discount rather than a state. If a stack review retires a login and the unofficial PDF set survives it, the tidy never reached the plotter. If three applications still each claim to be the common data environment after the brands were merged, nothing has moved where the work happens. And if document controllers are still arguing about which system is the record a fortnight after a newly funded tool lands, that argument belongs in the weekly spine rather than in a purchase report.

The thing to ask for lands in the renewal conversation, and it is cheap to ask. Before signing, have the account manager reconstruct one package as it was issued three months ago — revision, suitability, recipients — from the system you are renewing, while you watch. If that needs an export and a call to support, you are renewing a container, not a record. Commercial leads sign these agreements, so they are the ones who can make the demonstration a condition of signing, and it will cost them a meeting to do it.

What the first half bought is more software and, on a growing number of jobs, fewer invoices. What it mostly did not buy is the record.