ISO 19650 Revision in 2026: The End of 'BIM', the Rise of Information Management

On 10 March 2026, BSI and nima released the Draft International Standard (DIS) for the revised ISO 19650 — the world's leading standard for information management in construction projects. This is not a cosmetic update. It is the most substantial shift in digital construction since the standard was first published in 2018. The standard officially moves away from the term "BIM" in favor of "information management", merges the delivery and operational phases into a single process, and renames key documents. Here is what happened and why it matters to anyone working with BIM data.


What happened

On 2 March 2026, in an online webinar attended by over 900 participants, the working group announced the key changes to ISO 19650. The announcement was led by:

  • Dr Anne Kemp OBE — chair of nima (National Institute of Management Advisors), convenor of the ISO 19650 committee
  • David Churcher MBE — project leader for ISO 19650-1 and 19650-3
  • Paul Shillcock — co-author of the standard Draft revisions for Parts 1 and 2 have been open for public consultation since 10 March 2026, with the comment deadline set for 3 May. Part 3 is expected in early June. Final publication is projected for 2027.

David Churcher's core message:

"The fundamental principle of ISO 19650 is the same as it always has been — that information and data are valuable commodities that need to be managed properly in a collaborative environment. But the focus of the standard is very clearly now about the whole life of assets. We have removed the distinction between delivery phase and operational phase."

Architecture

The four key changes

1. A unified process replacing two separate phases

Before the revision, ISO 19650 clearly separated the delivery phase (Part 2) from the operational phase (Part 3). In practice, this led many firms to treat BIM as a design tool: after handover, the model went into a drawer.

The new revision merges both phases into a single information management process covering the entire asset lifecycle. This is a direct response to the biggest mistake of the UK BIM Mandate — neglecting the operational phase.

Instead of two separate cycles, the standard introduces a Unified 9-Step Information Management Process — one continuous workflow from concept through operation. From day one of a project, the team must consider what data the facility manager will need 20 years later.

What changes in practice:

  • Information requirements (EIR, AIR, PIR) must cover the entire lifecycle
  • The "data drop" disappears — information must flow continuously
  • Facility managers are engaged from the concept phase, not at handover

2. From "BIM" to "information management"

David Churcher stated it plainly: the emphasis is shifting from "BIM" as a term to "information management" and "information production". These phrases will be used to signpost specific activities in the process.

The reason is simple: the term "BIM" had become too ambiguous. For some it meant Revit, for others 3D modeling, for others a process, a standard, or a philosophy. Terminological confusion was holding back adoption. The revised standard says it clearly: it is about managing information, not about software.

The UK has already taken this step — renaming "BIM Mandate" to "Information Management Mandate". Now ISO is following the same path at an international level.

For us as software developers, this is an important signal: the value of plugins and integrations is shifting from "draw the model" to "ensure correct information lifecycle". This changes development priorities — data validation, open-format export (IFC), CDE integration, and information versioning become the core of the product, not nice-to-have features.

3. BEP becomes the Information Production Plan

The BIM Execution Plan (BEP) — one of the most important documents in any BIM project — is being renamed to the Information Production Plan (IPP).

The name changes, but the function remains: it is the document describing how information is created, managed, and delivered in a project. The new name more accurately reflects the scope — it is not about "executing BIM", but about planning the entire information production process.

For design firms, this means updating templates and documentation. For us, the developers, it is a signal that any tools generating BEP documentation (for Revit, Tekla, or other platforms) will need to be adapted. Field names, template structure, role mapping — all of it is up for review.

4. Links to new related standards

The Part 1 revision introduces references to two important related standards:

ISO 7817-1 — defining Level of Information Need. This replaces the ambiguous "LOD" term (Level of Development / Level of Detail), which has been interpreted differently across countries and organizations for years. Now there is a unified definition that plugin and validator developers can align with.

ISO 29481-1 — the IDM (Information Delivery Manual) standard, defining how and when information should be delivered between project participants.

These references create a coherent ecosystem of standards. ISO 19650 no longer operates in isolation but as part of a family, which simplifies the development of interoperable solutions.


What this means in practice

For design firms already working to ISO 19650

Short term — follow the public consultation, review the DIS drafts. Existing documentation (BEP, EIR — Exchange Information Requirements, templates) still works, but understanding the new language is essential.

Medium term — plan documentation updates: BEP → Information Production Plan, BIM terminology → information management. Train the team on the new approach.

Long term — think in terms of the entire asset lifecycle, not just the design phase. Involve facility managers in defining information requirements from day one.

For AEC software developers

This is a window of opportunity. Most existing BIM tools are designed around the model — Revit plugins, Tekla extensions, IFC converters. The new revision shifts the center of gravity toward data and its lifecycle.

What wins in the new paradigm:

  • CDE platforms that support the full lifecycle, not just the project phase
  • Data validators that check compliance with the IPP and information requirements
  • API integrations between models (Revit, Tekla, ArchiCAD) and operational systems (CMMS, IoT platforms, digital twins)
  • Agentic BIM — tools that automatically validate models against standards without manual QA At APIBIM, we see this trend in projects over the last year: client requests are shifting from "build us a plugin" to "ensure model integration with the operational platform and validate data at every stage".

For companies starting their BIM journey

Paradoxically, this is an excellent time to start. There is no need to learn the "old" BIM language first and then re-learn. You can build processes aligned with the new paradigm from the start: lifecycle-oriented, focused on information management, with FM engaged from the beginning.


Context: March 2026 in AEC

The ISO 19650 revision is not happening in a vacuum. The industry is shifting on several fronts in parallel:

  • Trimble released Tekla 2026 (11 March) with AI tools and real-time model-to-documentation synchronization
  • Autodesk connected Revit to Forma — Revit becomes the first "Forma Connected Client", with access to cloud analytics and the AI assistant directly from the interface
  • The BIM market is growing from $9.03 billion (2025) to a projected $15.42 billion (2030) — 11.3% annual growth. Drivers: cloud, AI, digital twins
  • Startups are challenging Revit — AEC Magazine writes about "agentic BIM": platforms that automatically validate models, detect inconsistencies, and check standards compliance in real time The direction is unambiguous: BIM is ceasing to be "a 3D modeling program" and becoming the information infrastructure of construction, integrated with AI, cloud, and IoT. The ISO 19650 revision is the official confirmation of an evolution already underway in the industry. The standard is not setting the direction — it is catching up with reality.

What to do now

Final publication is expected in 2027, but preparation must begin today. The core concepts — lifecycle information management, FM engagement from the start, structured information production — can be implemented without waiting for the final release.

Checklist for the coming months:

  1. Read the DIS drafts for Part 1 and Part 2 (available from 10 March 2026)
  2. Audit existing BEP templates and information requirements
  3. Identify points in current processes where information "breaks" between delivery and operations
  4. Update terminology in internal documentation and training materials
  5. If you develop BIM software — review the architecture with a focus on lifecycle data management

Bottom line

The ISO 19650 revision is not just a terminology update. It is a paradigm shift: from the model as an artifact to information as a continuous asset. From BIM as a design phase to information management as a discipline spanning the entire building lifecycle.

For the AEC industry, this means restructuring processes. For software developers, it means rethinking product strategy. For those just starting with BIM, it is an opportunity to build it right from the beginning — without the need to re-learn in a couple of years.

"BIM is dead, long live Information Management" — sounds provocative, but it captures what is actually happening. The standard is catching up with an industry that has long lived on data, not models.

Architecture

Sources

You might like this

What is Life Cycle Assessment in Construction?
Standardization

What is Life Cycle Assessment in Construction?

29 Jul, 2024
281
Dynamo BIM Guide. Visual programming for design automation
BIM

Dynamo BIM Guide. Visual programming for design automation

25 Apr, 2026
138
Do civil engineers need to learn algorithms to work with generative design methods?
Design

Do civil engineers need to learn algorithms to work with generative design methods?

28 Nov, 2022
243