ISO 19650 Updates for 2026: The Enterprise Guide to BIM Compliance in SIGNAX

Alexander Popov, CTO of SIGNAX and creator of SIGNAX DOCS — an ISO 19650-aligned CDE running on construction projects worldwide — has been watching the 2026 revision process closely. Worth reading what he actually thinks before diving into the details:

"The 2026 update is evolutionary rather than revolutionary. Most changes clarify and refine existing requirements without altering the core principles of the standard. The most notable addition is the new Submitted status, which provides a clearer representation of information that has been delivered for review but hasn't yet received final approval. The remaining updates are primarily aimed at improving consistency, clarity, and practical application of the standard."

For enterprise teams, the changes he flags break down as follows. Parts 2 and 3 are merging into one information management process covering the full asset lifecycle, which means the split between project delivery and operations is going away — information flows from design through operation, no handover wall. The standard is also moving off BIM-specific language: EIR becomes Information Production Requirements, BEP becomes Information Production Plan (IPP), and MIDP/TIDP merge into a single Information Production Schedule (IPS). A unified information management process replaces the separate project and operations flows, alignment with ISO 7817, ISO 29481, and openBIM standards including IFC is made more explicit, and information governance, accountability, and traceability get more weight throughout. Core ISO 19650 principles and CDE workflows stay put — this is clarification and easier implementation, not a structural overhaul.

What follows is the full breakdown: what's changing, what isn't, and what it means for SIGNAX configuration.

From BIM standard to lifecycle information management

ISO 19650 is the international framework for how information should be organised and managed across the life of a built asset. It covers collaborative processes, roles, and key concepts — information containers, common data environments, information requirements — from early design through construction and into operations.

The series has six parts:

• Part 1 — Concepts and principles
• Part 2 — Delivery phase of assets
• Part 3 — Operational phase of assets
• Part 4 — Information exchange
• Part 5 — Security-minded information management
• Part 6 — Health and safety

Three concepts underpin everything else.

Information containers are named, persistent units of information — a model, a drawing, a schedule, a document — each with defined attributes: status, revision, classification. Think of them as the atoms of ISO 19650.

The Common Data Environment is not just a file server. It's a workflow-driven, single source of truth where those containers move through defined states — Work in Progress, Shared, Published, Archived — via controlled gateways and approvals. Without that workflow discipline, you just have storage.

Why any of this matters: poorly managed information causes data loss at project close-out, rework from using the wrong version, and teams wasting hours hunting for files that should be two clicks away. ISO 19650 CDE workflows exist specifically to prevent that. The 2026 updates refine this framework — they don't dismantle it.

What’s changing in ISO 19650 in 2026

1. Parts 2 and 3 are merging

This is the headline change. Parts 2 (delivery) and 3 (operations) are being combined into a single, unified information management process that spans both project delivery and asset operation. Part 3 is being rescoped into implementation guidance — practical how-to support for applying the unified process inside real organisations.

2. The delivery/operations split goes away

The revised standard explicitly removes the boundary between project-phase and operational-phase information management. The logic is straightforward: data created during design should flow directly into the asset information model and serve operations — not get handed off awkwardly at handover and then siloed in a different system.

For enterprise teams, this means less "project vs. FM" thinking and more "single information backbone across the full lifecycle."

3. The language is shifting from BIM to Information Management

Several familiar terms are being reframed:

• EIR becomes information production requirements
• BEP becomes Information Production Plan (IPP)
• MIDP/TIDP consolidates into an Information Production Schedule (IPS)

The intent is to draw a clearer line between information management — governance, coordination, accountability — and information production — models, drawings, data. Both matter; they're just different jobs.

4. A cleaner 9-step information management process

The revisions introduce a single, clearer process that runs across the asset lifecycle and replaces the separate project and operations flows. Details are still under consultation, but the direction is: easier to implement globally, clearer on who's responsible at each step, and better aligned with existing practice models like the UK BIM Framework and ISO 19650 BPMN diagrams.

5. A new "Submitted" state in the CDE workflow

This is one of the most operationally significant changes for teams working inside a CDE every day, and it's easy to underestimate.

The 2018 edition defined four container states: Work in Progress, Shared, Published, Archive. The 2026 draft inserts a fifth — Submitted — between Shared and Published:

The Submitted state formalises a transition that the 2018 framework left ambiguous: the moment a container crosses from internal team circulation to external submission — to the appointing party, a third-party reviewer, or an authority. Under the 2018 model, there was no formal status for a container that had left the team's hands but hadn't yet been accepted and published. In practice this created real ambiguity: was something "published" the moment you sent it, or only after the client confirmed receipt and acceptance? Teams handled this differently, CDEs handled it differently, and audit trails suffered.

The 2026 draft resolves this cleanly. The two transitions now mean distinct things:

• Shared → Submitted: the container has been internally approved for a specific use and formally passed to an external party
• Submitted → Published: the appointing party has accepted it and it enters the authoritative record

This matters for enterprise CDE configuration. Any SIGNAX environment aligned to ISO 19650 will need to support the Submitted state as a first-class workflow step — not a workaround folder or a status code — with its own access controls, notifications, and audit trail. The good news is that the underlying logic already exists in ISO 19650-aligned workflows; it's a formalisation of something teams were already doing informally. The adjustment is structural rather than conceptual.

6. Tighter alignment with related standards

The 2026 drafts pull in supporting standards more explicitly — ISO 7817 (Level of Information Need), ISO 29481 (Information Delivery Manual), and openBIM standards including IFC. ISO 19650 is part of a broader ecosystem, not a standalone framework.

One important caveat: these are still consultation documents. The 2018/2020 editions remain in force until the revised standards pass international consensus and are formally published.

Centralize project data, streamline document reviews, and keep your entire team on the same page.

CDE for construction

To SIGNAX DOCS

What isn’t changing

Quite a lot, actually. The core mechanics of ISO 19650 stay intact:

• Container-based collaborative working remains the fundamental model
• CDE workflows — WIP, Shared, Published, Archived — with their check/approve/authorise transitions remain unchanged
• The principle of a single agreed source of information, accessible on a need-to-know basis with auditable transitions, remains central
• Proportionality is still built in: the standard continues to allow scaling down for smaller or less complex projects

ISO 19650-4:2022 on information exchange also stays critical, setting out process steps, decision points and review criteria for exchanges between project and asset information models.

This matters for planning purposes. Your existing CDE investments, container naming conventions, approval workflows, and information requirements aren't obsolete — they need calibrating for updated terminology and a lifecycle perspective, not rebuilding from scratch.

What the 2026 changes mean for enterprise teams

For owners, developers, general contractors, PMCs, and BIM consultancies, the practical impact falls into four areas.

Information management roles get more formal. The revisions explicitly separate information management (governance) from production, and push for clear IM roles at both organisational and project levels. If your enterprise currently relies on BIM coordinators to absorb IM responsibilities informally, that gap becomes more visible.

Your CDE needs to support the full lifecycle. A CDE that functions as a project filing system is no longer sufficient. It needs to support continuous flow from the Project Information Model into the Asset Information Model, using open formats and interoperable processes. Handover is not a wall — it's a transition.

Information requirements need to be outcome-driven. The move away from rigid OIR/AIR/PIR structures towards outcome-driven requirements means asking "why does this stakeholder need this information and what decision does it support?" — not just "what format does it come in?" That's a more useful question, but it takes more thought upfront.

People and process matter more than software. Large-scale ISO 19650 adoption consistently lives or dies on training and change management, not platform selection. That means training information management champions, clarifying the BIM vs. IM distinction inside teams, and building continuous improvement into the way workflows are maintained.

How SIGNAX aligns with ISO 19650 today

SIGNAX is built as a unified environment for documentation, BIM, and AI-driven workflows — which maps naturally onto ISO 19650's push towards lifecycle information management and CDE-centric delivery.

As an ISO-aligned CDE. ISO 19650 requires a CDE where information containers move through defined states under controlled gateways, with access granted on a need-to-know basis. SIGNAX delivers this by treating every model, document, issue, and data view as an information container with standards-based metadata — status, revision, classification, suitability — and recording who checked, approved, and authorised each transition for a complete audit trail. With the 2026 introduction of the Submitted state, SIGNAX is positioned to reflect that five-stage workflow natively: a container submitted to the appointing party sits in a clearly defined status, with its own access controls and notification triggers, rather than occupying an ambiguous grey zone between internal sharing and formal publication. Granular access control down to container or workspace level also covers the security-minded requirements of ISO 19650-5.

As the operational engine for IM workflows. The ISO 19650 process model distinguishes clearly between appointing parties, lead appointed parties, and appointed parties across its eight (soon nine) step process. SIGNAX can map IM responsibilities — requirements definition, coordination, review, acceptance — to concrete tasks and approvals in the platform, and surface lifecycle status views that show, at any point, which containers meet which requirements and where bottlenecks are forming.

For information requirements and Level of Information Need. SIGNAX allows owners and lead appointed parties to encode information requirements and LoIN directly into project templates — geometry, information, and documentation expectations per object, phase, and BIM use. Those requirements connect to automated quality checks and dashboards, so non-conforming containers get flagged before they advance to Shared or Published states. National annex conventions — naming codes, status codes, classification systems — are also supported, so regional compliance doesn't require separate workarounds.

For openBIM and digital twin continuity. SIGNAX supports IFC and other open formats as primary deliverables, meaning models and data can flow from design tools into asset management and digital twins without losing structure or meaning along the way.

As an AI-native information management platform. The 2026 revisions — with their emphasis on lifecycle information management, separation of management and production roles, and alignment with LoIN and IDM — provide a standards-backed foundation for what SIGNAX is already building towards: AI that operates as an information management co-pilot, checking completeness against requirements, monitoring CDE workflows, and surfacing at-risk containers, while every AI output sits inside a fully traceable, ISO-aligned information model. As autonomous systems and robotics integrate further with project data, that structured-data foundation becomes the prerequisite, not an option.

Practical checklist: getting ready for ISO 19650 2026

1. Baseline your information management maturity.

Map current roles, processes, tools, and CDEs against the existing ISO 19650 lifecycle. Where are the gaps between what the standard expects and what your teams actually do?

2. Refine your information requirements.

Move your OIR/AIR/PIR and EIR structures towards outcome-driven information production requirements. Encode Level of Information Need consistently across BIM uses and project phases.

3. Update your CDE workflow for the Submitted state.

Audit your current WIP/Shared/Published/Archive configuration in SIGNAX and plan how the new Submitted state will be implemented. Define clearly what triggers the Shared → Submitted transition (internal approval for external submission), what happens during Submitted (appointing party review), and what triggers Submitted → Published (formal acceptance). This is operational work, not just a settings change — notifications, access controls, and audit trail requirements all need revisiting.

4. Harden your SIGNAX CDE configuration.

Beyond the Submitted state, audit file naming conventions, metadata, access control, and the full state workflow. Confirm everything is explicitly aligned with ISO 19650 and your national annex — and that the configuration is reproducible across projects, not just set up correctly on one flagship scheme.

5. Clarify IM roles and responsibilities.

Define who is responsible for information management versus information production at both organisational and project levels. Map those responsibilities to concrete workflows and permissions in SIGNAX.

6. Start updating templates and contracts now.

Prepare to transition from BEP/MIDP/TIDP language to IPP/IPS and unified lifecycle processes. When the revised standards publish, you want to make minor edits to existing templates — not rebuild them.

7. Invest in training.

Raise ISO 19650 and CDE literacy across your SIGNAX user base through internal champions and targeted training. The platform can only do what informed teams configure it to do.

8. Engage with the consultation.

If your organisation operates SIGNAX DOCS CDEs at scale, your experience is exactly what national standards bodies need to hear during the 2026 consultation period (open until June 2026). Use it.

The 2026 ISO 19650 updates don't make your existing BIM work obsolete. They codify a shift that's already happening: information is a strategic asset that needs to be governed across the full lifecycle of an asset, not just managed during the project phase.

For SIGNAX users, the direction is clear. The platform is built for exactly this — a standards-aligned CDE, a lifecycle information hub, and an AI-native workspace. The question isn't whether to adapt to the new framework. It's how fast you can get your configuration, your roles, and your teams ahead of it before the revised standards are formally published.

Note: The 2026 ISO 19650 revisions are consultation documents open for review until June 2026. The 2018/2020 editions remain the current applicable standards. Follow your national standards body for publication timelines.

References

• ISO/DIS 19650-1:2026 — Back to the Future. Shelidon. March 18, 2026. https://www.shelidon.it/iso-19650-2026/
• ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Information management using building information modelling — Part 1: Concepts and principles. International Organization for Standardization.
• ISO 19650-2:2018 — Information management using building information modelling — Part 2: Delivery phase of assets. International Organization for Standardization.
• ISO 19650-3:2020 — Information management using building information modelling — Part 3: Operational phase of assets. International Organization for Standardization.
• ISO 19650-4:2022 — Information management using building information modelling — Part 4: Information exchange. International Organization for Standardization.
• ISO 7817-1:2024 — Level of information need for built environment information modelling. International Organization for Standardization.
• ISO 29481-1 — Building information models — Information delivery manual — Part 1: Methodology and format. International Organization for Standardization.