ISO 19650, in five minutes.

ISO 19650 is the international standard for managing information across the whole life of a built asset, from the first business case to decades of operation. Strip away the jargon and it answers one question: how do you make sure the right information, at the right quality, reaches the right people at the right time, and keeps doing so long after the project ends?

This page is the short version. Six parts, four foundational ideas, one principle underneath all of it. Five of the six have their own in-depth guide; start with Part 1 at the bottom.

The principle underneath everything

Before the parts, the one idea they all serve: every piece of information produced on a project should trace back to a decision someone actually needs to make.

An owner needs to run a building for fifty years. A client needs to approve each stage. A contractor needs to coordinate trades without clashing. Each of those is a decision, and each decision needs information to be made well. ISO 19650 is the discipline of naming those needs up front, specifying exactly what answers them, and governing the information so it can be trusted when the decision arrives.

Get that right and the standard's machinery, the requirements, the data environment, the level of detail, the naming, all follows. Get it wrong and you produce thousands of files nobody uses while missing the handful that mattered.

The standard has six parts

Each part covers a different phase of the asset's life. Together they run from "what do we even need" through delivery, operation, exchange, security, and health and safety.

The four ideas that hold it all up

Four concepts from Part 1 do most of the work. If you only ever learn four things about ISO 19650, learn these.

1. The requirements cascade

Nothing is produced without a traceable need. Requirements flow down, the owner's strategic needs (OIR) inform what each asset and project needs (AIR, PIR), which become the formal brief to the delivery team (EIR), which the team answers with a delivery plan (BEP, MIDP, TIDP). Top to bottom, every file traces back to a business reason. → Full depth in Part 1.

2. The Common Data Environment

A CDE is not a shared folder. It is the single governed place all project information lives, with four defined states (WIP → Shared → Published → Archived), two approval gates between them, access control, and a complete audit trail. The platform plus the process. → Full depth in Part 1.

3. Level of Information Need

How much detail should an element carry right now? LOIN replaces the old single "LOD" number by separating three things, geometry, data (alphanumeric), and documentation, so each can be demanded independently, per element, per stage. You ask for exactly enough, no more. → Full depth in Part 1.

4. Naming & information containers

Every file in the CDE is an information container with a structured, machine-readable name. A consistent field convention, project, originator, discipline, zone, type, sequence, status, revision, means anyone can identify a file's contents, author and status without opening it, and the CDE can validate, search and report automatically across tens of thousands of files. → Full depth in Part 1.

The acronyms, decoded

Common questions about ISO 19650

What is ISO 19650?

ISO 19650 is the international standard for managing information across the whole life of a built asset, from the first business case through decades of operation. It sets out how information is specified, produced, checked and handed over, so the right information reaches the right people at the right quality.

What are the parts of ISO 19650?

Part 1 covers the concepts and principles. Part 2 governs the delivery phase, while a project is designed and built. Part 3 covers the operational phase. Part 4 addresses information exchange. Part 5 sets out the security-minded approach. Part 6, published in 2025, covers health-and-safety information. Parts 1 and 2 do most of the day-to-day work on a live project.

What is the difference between ISO 19650-1 and ISO 19650-2?

Part 1 is the framework: the concepts, principles and vocabulary. Part 2 is the operational detail for the delivery phase, the process for producing and exchanging information while a project is designed and built. Part 1 is the why; Part 2 is the how.

Is ISO 19650 mandatory?

ISO 19650 is a standard, not a law. It becomes binding when a contract or a set of information requirements calls for it, which is common on UK public work and increasingly on major programmes across the UAE and the wider GCC. Where a client's EIR references it, compliance is contractual.

What is the difference between BIM and ISO 19650?

BIM is the modelling and the information it carries. ISO 19650 is how that information is managed: who produces what, to what standard, checked by whom, and where it lives. You can model without it; you cannot deliver consistently at scale without something like it.