The 2026 ISO 19650 Draft Revision and the Information Management Problem AI Exposes

ISO 19650 set out to make project information a governed asset. ISO 19650-1:2018 already provides a whole-life information-management framework beyond model files. The 2026 draft Part 1 revision uses “Information management” in its title and remains under development. Connecting AI agents to project records adds a practical question: can retrieval distinguish current, approved information from superseded material? Without that control, an agent may rely on an outdated document. Here’s what that means for capital projects, and what it asks of the record you hold today.

Building a hyperscale data centre, a new process unit at a refinery or a municipal water treatment plant takes dozens of organisations, each sharing and working on thousands of project documents. Each of them produces information the others depend on. The design changes, equipment gets substituted, the permit comes back with conditions attached. Somewhere in that traffic, a decision can get made on a document that was superseded three weeks earlier.

ISO 19650 aims to manage such risks coherently: it is the international standard for managing information across the life cycle of a built asset, while treating information as an asset in its own right. The client states what it needs and when, and the delivery teams agree who produces what. The project defines a common data environment workflow, information states and responsibilities. Technical solutions may be distributed; status and approval evidence need to remain meaningful across their interfaces.

The published framework already covers broader information management using Building Information Modeling (BIM).

ISO lists ISO/DIS 19650-1 as the draft replacement for ISO 19650-1:2018. Its title uses “Information management”, but whole-life information management is already within the published 2018 scope. The DIS ballot began on March 10, 2026; the catalogue records a decision for a new DIS ballot on August 18, 2026. The draft remains under development, so do not treat 2027 as a committed publication or effective date.

A draft revision should not be treated as a published requirement. The practical issue for AI retrieval is already present: project records need explicit status, approval and supersession controls.

There is much more to a project than the model

Model governance matters, but project information extends beyond models. A BIM model is structured data, not a picture: elements can carry identifiers and technical properties defined by the project requirements. Authoring responsibilities, revision controls and clash-review tasks still need to be defined and verified on the project.

Around and outside that model sat everything else. Method statements and factory acceptance test reports. Weld maps, inspection records, punch lists. Variation orders, permits and the correspondence that came with them, vendor data books, warranties.

On a large capital project this runs to hundreds of thousands of documents, and it is where a great deal of the risk lives. A permit condition that nobody traced to the affected work package is a potential blocker. A commissioning certificate that cannot be found at handover is a delay, and sometimes a dispute.

That material was rarely ungoverned in the absolute sense of the term. It was governed by the hard manual work done by experts going over folder structures, naming conventions, a shared drive and a document controller with a long memory. That holds up as long as the people involved stay put and pay attention. The flip side is that manual work involves the risk of human error.

The standard never asked for this split. Its unit of currency has always been the information container: any named set of information, which includes a contract as readily as a model file.

A model-only implementation can leave gaps in the wider record. Check the project requirements for contracts, permits, commissioning evidence and operational data rather than assuming those records fall outside the published framework.

The model remains part of the wider project information record.

Scope: Where the gap shows

Handover, usually, because that is where somebody has to live with the result.

A water treatment plant runs for thirty years or more. The people operating it in 2050 will not be the people who built it, who will have likely moved on or retired. And the contracts that produced the information will have expired decades earlier.

When the model arrives in good order, and the surrounding record does not, the operator inherits a plant it cannot fully account for. Maintenance planning starts from an incomplete asset register, and a regulatory audit turns into an exercise in digging out historical facts.

The same pattern shows up on data centre campuses built out in phases, where the team commissioning hall four needs to know exactly what was approved in hall two.

Most owner-operators have a version of this story. What is new is who reads the record next.

AI: An over-confident reader raising the stakes

The controls the standard defines are signals to a trained reader. Suitability codes, revision status, approval states: an engineer who opens a drawing marked for information rather than for construction knows not to build from it, and hesitates when the status looks unclear. That hesitation is doing more work than anyone ever wrote down.

Agents are now being pointed at exactly this material. An assistant may produce a confident answer from incomplete documentation unless retrieval, uncertainty handling and review are configured and tested.

Consider a hypothetical agent asked to confirm the commissioning status of a set of equipment on a large energy project. It searches, finds a signed certificate, and reports the system as complete. That certificate was superseded after a retest, and the later document sits in a different folder under a different naming convention because it came from a different contractor.

Nothing in the record told the agent which one governed. A document controller who knew about the retest would have caught it, or at least paused. In this scenario, an answer can appear settled even though retrieval missed the superseding record. Test the scenario instead of assuming the agent will detect the conflict.

The weakness was always there. Human judgement was covering for it. Removing human review can expose that weakness. Define when an answer needs review and how conflicting or superseded records are handled.

This bites hardest outside the model, which is the second half of the problem. Model environments carry version control by design. Contracts, permits and certificates often do not, and those are exactly the documents an agent gets asked about when someone wants to know whether work can start, or what was warranted and by whom.

What the revision and rise of AI agents change together

A new landscape is emerging quickly. ISO 19650-1:2018 already covers whole-life information management; its draft replacement remains under development. At the same time, agents that may not reliably infer the standing of a project-critical document are being connected to project records.

So what can you do to anticipate and act?

Status has to bind, not advise. A naming convention is a request. The record itself has to carry the state of a document in structured fields that retrieval can filter and test, with the superseded version demonstrably retired rather than merely older, with a process that remains practical for ordinary documents.

The scope has to match the record. Governing the model well and the rest loosely leaves the exposure where it already is. Consistent rules across design, construction, commissioning and operations can reduce gaps between systems. Verify metadata, status and evidence when information moves between them.

AI has to work inside the governance. An assistant connected to uncontrolled sources may inherit gaps in the record. The useful version starts from the control model, respects permissions and approval states, and excludes superseded documents from current-use answers while retaining authorized historical access.

So where does that leave managers of large infrastructure and capital projects?

You already know that while the asset outlives the project, the information has to outlive both. It also needs clear, testable signals for AI retrieval. The draft is not the published replacement, and its eventual publication does not by itself establish a project's effective date. Use the current catalogue and the edition specified by the contract while improving today's record.

The long and short of it:
ISO 19650-1:2018 already covers whole-life information management. ISO/DIS 19650-1 is its draft replacement, not a published new requirement or a confirmed 2027 effective date. Control the wider project record now, including approval status and supersession, and test AI retrieval against those controls.

Frequently asked questions

When does the ISO 19650 revision take effect?

ISO/DIS 19650-1 remains under development. ISO lists ISO 19650-1:2018 as current, reviewed and confirmed in 2024. Check the catalogue and the edition specified by the project contract; the draft listing does not establish a confirmed 2027 effective date.

Does the ISO 19650 revision replace BIM?

No. The draft title uses “Information management”, but BIM remains part of the framework. ISO 19650-1:2018 already applies to whole-life information management; do not infer that non-model records only enter scope with the revision.

What does ISO 19650 cover beyond the model?

Any named set of project information: permits, variation orders, inspection records, commissioning certificates, vendor data books and more. On a large project that runs to hundreds of thousands of documents.

Why does the revision matter for AI agents?

This is an implementation risk, not an AI-specific requirement established by the draft catalogue. An agent may use a superseded document if retrieval fails to distinguish its state. Test current, withdrawn and superseded examples, preserve the relevant approval evidence and require review for project-critical answers.

Learn more

• Discover AODocs AI-native Document Controls for Engineering, Construction, Energy or Capital Projects.