ISO 19650 is a series of standards for managing information over the life of a built asset when building information modelling is used. It is about process: who asks for information, who produces it, how it is named, checked, shared and accepted. It is not a modelling guide, a software shortlist or a clash-tolerance table.
The parts, and what each is for
| Part | Edition | What it covers |
|---|---|---|
| Part 1 | 2018 | Concepts and principles. The vocabulary the other parts use. |
| Part 2 | 2018, UK National Annex 2021 | The delivery phase: from the appointing party’s requirements to handover. This is the part most people mean. |
| Part 3 | 2020 | The operational phase: managing information about an asset in use. |
| Part 4 | 2022 | Information exchange: the checks applied when a container moves between parties and states. |
| Part 5 | 2020 | Security-minded information management: deciding what is sensitive and controlling it. |
| Part 6 | 2025 | Health and safety information, replacing PAS 1192-6. |
Revisions of Parts 1 and 2 are in progress and are expected to be published in 2027. Until then, the 2018 editions apply. Editions were checked on 14 October 2026; see the standards list.
The roles, without the diagram
The appointing party says what information it needs and appoints others to produce it. A lead appointed party takes on a share of the work and coordinates the appointed parties below it. Together they form a delivery team, made up of task teams. Information management is a function, not always a job title. Someone looks after the CDE process. “The BIM person” is not a role the standard recognises.
The requirements, from top to bottom
Requirements cascade. The appointing party’s organisational information requirements explain why the organisation needs information at all. Asset information requirements and project information requirements turn that into what is needed for an asset and for a project. Exchange information requirements are the version written into an appointment: what this delivery team must hand over, in what form, by when. The information delivered builds a project information model during delivery and an asset information model for operation.
The delivery team answers with a BIM execution plan saying how it will meet the requirements, and with information delivery plans. Each task team writes a task information delivery plan. The lead appointed party combines them into the master information delivery plan. A responsibility matrix says who produces what. See information requirements for how to write one that can be checked.
The delivery cycle in Part 2
- Assessment and need. The appointing party sets the requirements, the information standard and the information protocol, and sets up the CDE.
- Invitation to tender. The requirements and acceptance criteria go out with the tender.
- Tender response. Bidders submit a pre-appointment BEP and evidence of capability.
- Appointment. The BEP is confirmed, the delivery plans are agreed and the requirements become contractual.
- Mobilisation. Teams test the CDE, the naming and the exchange formats before real work starts.
- Collaborative production. Containers move through work in progress and shared and are checked before they leave a task team.
- Information model delivery. The lead appointed party authorises and the appointing party accepts the model, which is then published.
- Project close-out. Information is archived and lessons are captured.
What the UK National Annex adds
Part 2 leaves some choices to each country. The UK National Annex settles them for UK projects: the fields of a container name, the status (suitability) codes and the revision format. The fields run project, originator, functional breakdown, spatial breakdown, form, discipline and number (in the 2018 annex, the third to sixth were volume or system, level or location, type and role). The site’s file-naming guide explains the logic and the file-name checker tests a name against a project convention. Neither is the annex. Use the published annex and the UK BIM Framework guidance for the real code lists.
What people pretend the standard says
It does not require a named piece of software. It does not set a millimetre clash tolerance. It does not say every project must exchange IFC. It does not define a “level” of BIM; it uses level of information need to describe how much information is enough for a purpose. It does require that exchange formats, naming and acceptance are agreed rather than discovered at the first upload.
A short worked case
A school extension. The appointing party’s EIR asks for a coordinated architectural and structural model at stage 4, with door and room schedules. The structural task team’s TIDP lists its model, its general-arrangement drawings and a calculation package, each with a due date. The lead appointed party adds those to the MIDP. When the structural model is ready for coordination it moves to Shared with a suitability for coordination. It is not yet Published. Only after the lead appointed party authorises it and the appointing party accepts it against the EIR does it become Published for construction.
Official text stays with ISO and BSI. UK guidance is published by the UK BIM Framework. This page is a reading aid, not a substitute for either.
Related: What a CDE is · CDE states · File naming · Information requirements · Glossary
Sources
- BS EN ISO 19650-1:2018 and BS EN ISO 19650-2:2018, with the UK National Annex revised in 2021
- UK BIM Framework guidance
Last checked 14 October 2026. Official requirements stay in ISO 19650 and the UK BIM Framework. This is original guidance.