ISO 19650 is the international standard for managing information across the life cycle of a built asset using BIM. If you have worked to the old UK BS 1192 suite, much of it will feel familiar — ISO 19650 took those principles international and tidied up the language.
For a contractor, the standard is less about software and more about process: who is responsible for information, how it is checked, and where it lives. Here is what it means in practice.
What ISO 19650 is, in plain language
At its core, ISO 19650 is a way of agreeing — before work starts — what information a project needs, who produces it, to what quality, and when it is handed over. It treats information as a deliverable in its own right, planned and checked like any other part of the works.
The goal is simple: the right information, in the right place, at the right time, trusted by everyone using it.
The parts of the standard
ISO 19650 is published in several parts. You do not need to memorise them, but it helps to know which is which.
- Part 1 — concepts and principles
- Part 2 — the delivery (design and construction) phase
- Part 3 — the operational phase of assets
- Part 4 — information exchange
- Part 5 — a security-minded approach to information management
The new vocabulary
ISO 19650 renames some familiar roles to make them contract-neutral. The shift is worth learning because it appears in every tender and BEP.
- Appointing party — the client (formerly the employer)
- Lead appointed party — the main contractor or lead consultant
- Appointed party — a subcontractor or task team
- EIR — Exchange Information Requirements (what the client asks for)
- OIR / AIR / PIR — organisational, asset, and project information requirements
- LOIN — Level of Information Need (what each deliverable must contain)
The Common Data Environment and its states
The Common Data Environment (CDE) is the single source of truth for project information. Every information container moves through four states, and understanding them is the single most useful thing a site team can take from the standard.
- Work in Progress (WIP) — a team's private, in-development information
- Shared — checked and released for coordination with other teams
- Published — formally approved and authorised for use
- Archive — a retained record of what was issued and when
What changes for your team
Day to day, the biggest change is discipline around the CDE. Information does not get emailed around; it is produced in WIP, checked, shared, and only used downstream once it is in the right state. That removes the 'which version is current?' problem that causes most rework.
The second change is planning. Instead of information appearing when someone gets to it, the MIDP and TIDP schedule each deliverable to a milestone — so the model and the drawings arrive on the programme, not after it.
Getting compliant — a short checklist
You do not become ISO 19650 compliant by buying a tool. It is a process the whole team agrees to follow. A pragmatic starting point:
- Read the EIR and respond with a BIM Execution Plan
- Stand up a CDE and enforce its four states
- Define LOIN per stage so teams build to need, not to habit
- Schedule deliverables via the MIDP and TIDP
- Run a model-audit step before anything moves to Shared or Published