Monthly Register — October 2025

The lanyard is in a drawer by now. Autodesk University ran from 16 to 18 September at the Music City Center in Nashville, with a digital pass running alongside it, and by the last working day of October the useful residue is not the session list. It is a handful of questions that surface in licence renewals and joint-venture meetings roughly six weeks after anybody stopped talking about the keynote.

Six weeks is about the interval. Somebody comes back from a week like that, or watches it from a desk on the digital pass, and a fortnight later they are asked whether next year's common data environment should follow the roadmap they saw. A joint-venture partner is asked to open an account nobody budgeted for. A document controller is asked whether the issued set is "already on the platform", as though a login were a published state.

What moved

The public shape of the week was not mainly about a new drawing tool. It was about where project data is supposed to live once authoring is finished: in a hosted repository, reached through the host's own interfaces and its partner connections, rather than by handing native files across a table. Industry clouds, application programming interfaces, artificial intelligence applied to the hosted record, the model as data. File exchange is the thing being quietly taken off the slide.

That is a commercial strategy, and there is nothing scandalous about a vendor having one. It is also an information-management event whether or not the conference billed it as such, and late October is when it lands on a live job — in a renewal, in an exchange-information requirement, in a partner's commercial manager asking what a seat costs and who is paying for it.

Two things get run together in that conversation and are worth separating. Legal ownership of an uploaded model is not the same animal as operational ownership of the project record. Most platform terms already say plainly that the customer keeps intellectual property in what they upload, and that sentence is both true and largely beside the point. It does not answer what a document controller has to live with after the hall goes dark.

Can the current issued set be reconstructed if the subscription lapses, the joint venture ends, or the employer names a different common data environment at the next stage? Does an export carry the metadata that made the files usable — revision, suitability, transmittal history — or does it hand over a bag of natives and PDFs? If the host's preferred route is an interface into its own cloud, what happens to a party that is not licensed for that cloud? Who holds the audit trail showing who approved what, and on which date, when the project goes to dispute? And if an assistant has been trained on the hosted record, does a departing party leave with a copy of what that assistant was reading, or only with whatever somebody remembered to download?

None of that is peculiar to one vendor. It applies to any hosted common data environment, any industry cloud, and any hyperscaler folder wearing a project system's badge. Nashville is the month's lead because it is the loudest public statement of the pattern, not because the pattern belongs to whoever stated it. A year ago the same argument ran here in the week the conference sat; this year the conference sat in September and the argument turned up anyway, six weeks behind the badge.

It bites hardest on jobs already running forty systems that still cannot name the issued set. Moving those files into a more elegant cloud does not create a single source of truth on its own, and it can make the opposite problem harder to spot. The record looks unified because one login displays it, while the contract parties remain unable to take a complete copy home. Clerical labour does not evaporate because the folder is prettier; it moves to whoever gets asked to prove the published container without the host's password.

A rough filter for the roadmap you were shown. If it constrains export, it is news. If it only promises connection, it is marketing. Six weeks on, the thing to extract from a week like that is a habit rather than a product shortlist: treat portability, exit and the issued set as acceptance tests, not as footnotes to a demonstration.

What changed in the standards

Thin, as October usually is. No new part of ISO 19650 was published this month. 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 October news, and it does not become a commencement because a conference season happened.

The UK BIM Framework did not issue a replacement text to mark that season either. The Building Safety Act's information duties in England were already in force — they did not arrive because a roadmap mentioned a golden thread. Gulf permit-stage BIM requirements that came into force earlier remain a class of public-record rule wherever the text is public. The revision conversation around the series is weather rather than a published replacement: working groups collecting comments, national bodies circulating drafts internally. When a month can say where the drafting has actually reached, it will.

What October does produce, after a platform week, is a different sort of text altogether. A BIM execution plan with a new platform paragraph. An exchange-information requirement naming a preferred cloud. A tender reply claiming ISO 19650 alignment because a slide used the same words. A standard names an information requirement; a roadmap names a preferred path. Confusing the two is how a job ends up contracted to a login instead of to a deliverable, and it happens in the drafting, quietly, without anybody quite deciding it.

Two brochure words to watch while that drafting is going on. Interoperable, when all it means is that an interface exists. Open, when the openness cannot be exercised by a party outside the authoring licence. If a specific circular or national annex did move in October, it belongs in a later correction once it can be cited.

One thing to watch

Whether the month's lead still matters once the slides are shut. The test is not whether anyone remembers the general session; it is whether document controllers are still arguing in a fortnight about export, exit, and who can reconstruct the issued set without the original host's login. If they are, the argument has legs, and it sits alongside the systems-sprawl diagnosis and the ninety-day audit rather than in a conference recap.

The autumn calendar makes this easy to test. Licence renewals are being drafted now. Employers are being asked to nominate a common data environment for the next stage. Joint-venture boards are being asked whether one platform will finally shrink the stack. Apply the same question that worked on the June halls: does the proposal change a published container, or only a slide? If connection means another party has to buy a seat before it can read what was issued, what has been bought is a funnel. If the export drops suitability, revision and transmittal history, what has been bought is a bag of files.

Two things to ask for while the renewal is still in draft, which is when you have more leverage than you will have at any point afterwards. Ask for a written exit: a defined export, listing which metadata travels with it, in a format a party outside the authoring licence can open. Then ask, in the same conversation, who is funding the seats the partners were never quoted for. Neither request is free. An exit clause is a negotiation and it may cost you a discount somewhere else. The alternative is finding out the answer during a dispute, which costs a great deal more and arrives at the worst possible moment.

Theatre dies in a week. Ownership arguments run for years, and October is the month you find out which of the two you actually bought.