ISO 19650 is the international standard for the management of information over the whole life cycle of a built asset using building information modelling (BIM). First published by ISO in 2018 and derived from the UK’s BS 1192 and PAS 1192 series, it has rapidly become the reference framework for information management on engineering, construction and infrastructure projects worldwide. In the United Kingdom, compliance with ISO 19650 is required on all publicly-funded construction projects. In the European Union, France, and across the Middle East, adoption is accelerating as clients and contracting authorities increasingly specify ISO 19650 in their contractual requirements.

For Document Controllers, Information Managers, and Project Directors on complex EPC projects, understanding ISO 19650 is no longer optional. This guide provides a practical, field-oriented interpretation of the standard and explains how its requirements translate into day-to-day document control practice.

What ISO 19650 Actually Covers

ISO 19650 is a multi-part standard. The parts most relevant to project documentation management are:

• ISO 19650-1: Concepts and principles — defines the terminology, the information management lifecycle, and the relationship between the different governance documents
• ISO 19650-2: Delivery phase — specifies the processes for information management during project delivery (design, procurement, construction)
• ISO 19650-3: Operational phase — addresses information management during asset operation and maintenance
• ISO 19650-5: Security-minded approach — guidance on information security management in the context of BIM

The standard does not specify which EDMS to use, which document management platform to deploy, or which file formats to adopt. It defines a framework of governance requirements: who is responsible for information, what information must be produced, how it must be exchanged, and how it must be validated before delivery.

The ISO 19650 Governance Framework: Key Documents

ISO 19650 introduces a set of governance instruments that structure the information management process. Understanding these documents is essential for any document control professional working on an ISO 19650-compliant project.

The ISO 19650 Information Management Process

ISO 19650-2 defines an eight-step process for managing information during the delivery phase of a project. Understanding this process helps document control professionals align their workflows with the standard’s requirements.

• Step 1: Assessment and need — the appointing party defines the OIR (Organisational Information Requirements) and the project-level AIR (Asset Information Requirements)
• Step 2: Invitation to tender — the appointing party prepares the EIR and includes it in tender documentation
• Step 3: Tender response — the appointed party prepares and submits a pre-contract BEP and MIDP
• Step 4: Appointment — contract is awarded; the BEP and MIDP are confirmed
• Step 5: Mobilisation — the appointed party establishes the CDE, confirms the TIDP, and mobilises the information management team
• Step 6: Information production — information is produced against the MIDP schedule, progressing through CDE states (WIP → Shared → Published)
• Step 7: Information delivery — packages of information are formally delivered to the appointing party at defined Project Information Delivery Milestones
• Step 8: Project close-out — the Project Information Model (PIM) is finalised and transferred to the appointing party as the basis for the Asset Information Model (AIM)

CDE State Management: How It Works in Practice

One of ISO 19650’s most operationally significant requirements is the CDE state model. Every piece of project information must move through defined states, each with its own access controls, metadata requirements, and approval actions. This is not merely theoretical — it directly affects how the EDMS must be configured and how the document control team manages the workflow.

The four CDE states and their practical implications are:

• Work In Progress (WIP): Information is being produced. Access is limited to the producing team. Documents in WIP state are not shared with other parties. In EDMS terms, WIP documents reside in a private working area, not in the shared register.
• Shared: Information has been checked by the originating team and is ready for review by other project participants. In Aconex terms, this is equivalent to a document issued for inter-discipline review. The document is accessible to defined reviewers but has not yet been approved for use.
• Published: Information has been reviewed, approved, and authorised for use. This is the “Issued for Construction” or “Approved for Design” equivalent. Published information constitutes the project’s validated information baseline.
• Archived: Information is superseded or no longer current but is retained for record purposes. Proper archiving is essential for close-out and for maintaining the documentary record in case of contractual disputes.

ISO 19650 and Document Control: Where They Converge

For experienced document control professionals, ISO 19650 will feel familiar in many respects. The standard codifies practices that competent document control teams have been applying for years — but it provides a formal, internationally recognised framework that gives these practices contractual standing.

The key convergences between ISO 19650 and traditional document control practice are:

• The MIDP corresponds to the MDR: both are master registers of project deliverables with issue dates and status tracking
• The CDE states correspond to document status codes: WIP = draft, Shared = IFR (Issued for Review), Published = IFC or AFC, Archived = superseded
• The EIR corresponds to the client’s document requirements schedule in a traditional EPC contract
• The BEP corresponds to the Document Control Procedure (DCP) and the EDMS configuration plan

TERADOK’s Project Information Governance service covers the full ISO 19650 implementation scope, from EIR analysis to BEP preparation, CDE configuration, and MIDP management. For project-level document control implementation, see our Document Control Consulting service.

Common ISO 19650 Implementation Challenges

Organisations implementing ISO 19650 for the first time encounter predictable challenges. Understanding them in advance allows project teams to plan mitigation actions:

• EIR quality: Many clients produce EIRs that are vague, incomplete, or copied from a template without customisation. A poorly written EIR creates ambiguity about what information is actually required, leading to disputes at delivery milestones. TERADOK supports clients in developing EIRs that are technically precise and operationally realistic.
• BEP as a compliance exercise: Contractors often prepare a BEP because it is contractually required, not because they intend to use it as a working document. The BEP should be a live operational reference, updated at each project stage and reviewed at key milestones.
• CDE governance: Deploying an EDMS as the CDE is not sufficient. The CDE must be configured to enforce the state model, with appropriate access controls, metadata requirements, and workflow triggers. Without governance, the CDE becomes a shared drive with a more expensive interface.
• MIDP maintenance: Like the MDR in traditional document control, the MIDP must be maintained throughout the project. A MIDP that is set up at mobilisation and then abandoned is operationally useless at close-out.

Frequently Asked Questions about ISO 19650