- NexSysIT Editorial Team
- 23 Sep 2026
- 9 min read
ISO 19650, Explained for Australian Practices That Have Just Been Asked for It
ISO 19650 is the international standard for information management over the whole life cycle of a built asset using building information modelling (BIM), from initial design through construction to the operational phase and end of life. It is not a software standard. It isn’t a modelling standard either, and it doesn’t tell you which CDE to buy. What it does is define who has to produce what information, when, in what state, and how it moves between the people on a project. That’s why it arrives in a practice as a tender clause rather than as a technical decision.
Most explanations of the ISO 19650 standard are written for a BIM manager at a Tier 1 contractor, and this one is written for the director of a forty-person practice who has just been sent an appendix that says the common data environment shall comply with ISO 19650-2, and who wants to know what that means for the file server, the software bill and the Friday afternoon issue. Our digital platform team has run enterprise Autodesk Construction Cloud deployments at Hassell, Silver Thomas Hanley and Mirvac over thirty years in AEC. This is the version we give clients.
The five parts of the ISO 19650 information management process, and the two that matter to a practice
The ISO 19650 series is published in parts. Part 1 sets the concepts and principles for the project team and, later, the asset owner: the idea of information requirements flowing from the appointing party down through the delivery team, the information container, the common data environment and its states. Part 2 specifies how information is managed during the delivery phase of an asset, which is design and construction, and it’s the part tenders cite. Part 3 covers the operational phase and asset management, once the building is in use and the project information model becomes the asset information model, Part 4 covers information exchange, and Part 5 covers a security-minded approach to information management, which government clients reach for when the project is a hospital, a defence site or a rail corridor.
Australia adopted the first two as AS ISO 19650.1:2019 and AS ISO 19650.2:2019, identical adoptions published at the end of 2019, with NATSPEC producing the National BIM Guide, BEP templates and the AIR, PIR and EIR templates that go with them. For a design practice, Parts 1 and 2 are the whole conversation. Part 5 turns up on secure government work, and Parts 3 and 4 are somebody else’s problem until you’re doing facilities management.
Appointed party, lead appointed party, EIR, BEP: the vocabulary tenders use, translated
ISO 19650 has its own language, and most of the fear it causes is vocabulary. The appointing party is the client, and the lead appointed party is whoever holds the head contract for the information, usually the lead consultant at design stage and the head contractor at construction stage. Appointed parties are everyone else, organised into task teams. That’s most practices. Information requirements come in layers: organisational (OIR), asset (AIR), project (PIR), and the one you’ll actually be handed, the exchange information requirements or EIR, which says what the client wants delivered, when, in what format and at what level of information need.
Your answer to the EIR is the BIM execution plan, the BEP. A pre-appointment BEP goes in with the tender and says how you’d do it; a post-appointment BEP is agreed once you’ve won and becomes the rulebook for the job. The master information delivery plan, the MIDP, is the schedule of every information container, which is the standard’s word for a model, a drawing set, a schedule or a document, with who produces it and when. If you can produce a BEP and a MIDP that answer the EIR, you are most of the way to compliance before anyone touches software.
The common data environment (CDE) and its four states
The common data environment is the part of the standard that touches IT, and it’s the part people get wrong by assuming it means a product. A CDE is a process as much as a platform: a central repository with controlled access where information containers move through defined states, each with a suitability status, and a record of who moved them and when. It’s the backbone of project delivery under the standard, and process comes first.
The standard defines four. Work in progress, where a team is developing information nobody else should rely on yet. Shared, where it’s been checked and made available to other teams for coordination. Published, where the appointing party has authorised it for use. And archive, where every superseded version is kept for the record.
Autodesk Construction Cloud, Aconex, ProjectWise and 12d Synergy can all be run as a CDE, and so, with discipline, can a well-structured file server. What makes it a CDE is that the states exist, the transitions are gated by a check and an authorisation, and there’s an audit trail. What makes it fail is a project drive where “Issued” is a folder someone drags files into on Friday.
What Australian clients now require
Three things changed the temperature. Infrastructure NSW’s Digitalisation and Data Policy, released in 2025, requires information requirements and the common data environment on state infrastructure projects to follow ISO 19650, with an 18-month transition period for agencies. Transport for NSW had already published its contractor CDE standard, which defines work in progress, shared, client shared and published states and expects every deliverable to move through them. Queensland has required BIM on government construction projects worth $50 million or more since 1 July 2019, and the state’s guidance points at the same standard.
None of that binds a private developer, and plenty of commercial work still runs on a shared drive and an email chain. But the Tier 1 contractors who deliver the state work bring the same information requirements to their private projects, because it’s cheaper to run one process than two, and they pass the EIR down to every consultant on the job. That’s how a residential practice with no government clients ends up reading ISO 19650-2 on a Tuesday.
What it means for the practice's IT
Here’s the view some BIM consultants would argue with: ISO 19650 compliance is 80 per cent process and 20 per cent platform, and practices spend the money the other way round. The platform questions are real but short: can the CDE hold the four states with gated transitions and an audit trail, can it give a subcontractor access that expires with the contract, and can the archive be produced years after practical completion, indexed by project and immutable? Where is the data held, since the South Australian and Western Australian supplier frameworks now ask you to state it? And is the central model on infrastructure that Autodesk supports for worksharing, rather than a sync client that Autodesk’s knowledge base says gives an experience that “would be no”?
The process questions take longer and cost less, and they’re what keeps project information up to date across the whole project team. Naming conventions that follow the standard’s container identification, so a file name tells you the project, originator, volume, level, type, role and number without opening it. A BEP template the practice can fill in an afternoon, and a MIDP that’s a spreadsheet, not a product. A named person who owns the shared and published transitions on each project, because a gate nobody guards isn’t a gate. Most practices that fail an ISO 19650 audit fail on those, not on software.
What it costs
For a forty-person practice already on Autodesk Construction Cloud or a comparable platform, the platform cost of compliance is close to zero, because Autodesk Docs comes with the AEC Collection and the states are configuration. The cost is time: a BEP template, naming conventions, a MIDP format and a half-day of training, which we’d put at two to four weeks of a BIM manager’s attention spread over a quarter. For a practice on a file server with no CDE, the platform is the cost, and it’s worth reading the cloud storage guide before buying one, because the CDE and the project file server are different things and practices keep buying one to do the other’s job.
A caveat, though. If you’re a five-person studio doing houses and shop fit-outs for private clients, nobody is going to send you an EIR, and building a full ISO 19650 process is a solution to a problem you don’t have. Adopt the naming convention, because it’s free and it’ll save you an hour a week. Leave the rest until a tender asks.
Where to start
Read the EIR you’ve been sent, all of it, and mark every line that names a deliverable, a format, a date or a state. That list is your MIDP in draft, so then check whether your current platform can hold four states with a gate and a log, and if it can’t, decide whether the fix is configuration or a new platform. Then write the BEP, using NATSPEC’s template rather than a blank page. The order matters. Practices that buy the platform first end up with a CDE that has the states and nobody using them, which is the audit finding every assessor has seen a hundred times.
- Written by
Written and reviewed by the NexSys engineers, design technology specialists and consultants who build and support IT for architecture, engineering and construction firms across Australia. Every price, rule and vendor statement is checked against its source on the date shown.
- The five parts of the ISO 19650 information management process, and the two that matter to a practice
- Appointed party, lead appointed party, EIR, BEP: the vocabulary tenders use, translated
- The common data environment (CDE) and its four states
- What Australian clients now require
- What it means for the practice’s IT
- What it costs
- Where to start
Recent Posts
- Workflow Automation for Architecture and Engineering Firms: 2026
- IT Support for Architecture Firms With Internal IT Teams
- Cloud Infrastructure for Revit and BIM Workloads: A Guide
- IT Asset Management for AEC Firms: Digital Efficiency and Compliance
- BIM’s Next Leap: Automation, Validation, and Data Trust in AEC
Get your CDE assessed against the standard
A half-day review of how your projects move through work in progress, shared and published, what your clients’ information requirements actually say, and what would need to change. Book a strategic review and we will start there.