Before Changes Become Rework

Trunk Tools’ Cortex AI platform is interesting because it is aimed at a very practical construction problem: drawings, specs, RFIs, submittals, schedules, and change orders do not always stay connected.

One detail stands out. The system is reported to find drawing changes even when they are not called out in a revision cloud. That is important because missed changes are one of the ways teams end up pricing, planning, or building from the wrong information.

The useful question is not whether AI can “understand construction.” It is whether it can help people spot the change, check the source, and deal with it before it becomes rework.

Trimble’s acquisition of Document Crunch is a good reminder that project information is not only drawings and models. Contracts carry obligations that affect notices, payments, scope, delays, risk, and responsibility.

The problem is that contract language often sits away from the daily project workflow. People usually go back to it when there is already a disagreement, delay, or claim.

If AI tools can help project teams see the relevant contract requirement at the right time, that could be useful. Not as a replacement for judgment, but as a way to stop important obligations being missed while the job is moving quickly.

The proposed ISO 19650 revisions are worth watching because they point to a wider shift in language: away from BIM as only a model issue, and toward information management across the full life of a building or asset.

That distinction matters. A model may be well built, but the real value comes when the information can be issued, reviewed, updated, handed over, and used by the next team.

For The Hub, this is the broader context behind many software announcements. The industry does not just need more digital information. It needs better ways to manage that information as responsibility moves from design to construction to operations.

Fieldwire’s BIM construction management piece makes a simple point: model information only matters if it can be used by the people doing the work.

A coordinated model may help in the office, but the field still needs clear drawings, tasks, locations, issue notes, and updates that work in real jobsite conditions. That includes mobile access, offline use, and a practical way to tie field issues back to the right plan or model location.

This is where many digital workflows succeed or fail. If the information cannot be used at the point of work, it is not really connected.

PCL and DroneDeploy expanding their reality capture partnership is a useful signal because it moves the conversation beyond drone photos.

Photos, 360 captures, scans, and site imagery are valuable when they help answer project questions: what was installed, what changed, what is complete, what is delayed, and what condition was present on a certain date.

The challenge is turning field capture into information that teams trust and use. Otherwise, it becomes another large collection of files that people only search through after there is a problem.

Autodesk is pulling more of the construction workflow under Forma.
The move from Autodesk Construction Cloud to Forma points to a wider platform push: design, preconstruction, construction, field work, and handover all sitting closer together. The question for contractors is whether that makes handoffs cleaner, or just puts more information inside a bigger system.

Procore is moving further into AI-assisted project work.
Procore’s Datagrid integration and “Digital Coworkers” announcement shows where the major project platforms are heading. The useful test will be practical: can the system connect RFIs, photos, drawings, contracts, and daily logs in ways that help teams avoid missing something important?

ISO 19650 changes point beyond BIM as just a model.
The proposed revisions are a reminder that the bigger issue is information management across the full life of a building or asset. BIM matters, but only if the information can be issued, reviewed, updated, handed over, and used by the next team.