If you already do this for a living: The “who needs it and why” question. Teams that know the standard well still produce information nobody asked for, because the requirements were never traced to a person and a decision.
- Watch out
- What it costs
- Experienced readers
- Remember
- In BIMpedia
A design team spends months adding manufacturer data, cost codes and 3D details to every element because “ISO 19650 says so”. The client wanted room data for space planning and fire door data for the fire strategy, and neither is complete at the stage gate.
The team asks four questions first: who needs what, when, and how it is checked. The answers fit on one page: room data at stage 3, fire data at stage 4, both as IFC properties, checked before each share. Effort goes where someone is waiting for it.
If you have read job adverts for BIM roles, you will have seen “ISO 19650” everywhere. It is easy to assume it is a modelling standard that tells you how to build a Revit model. It is not. ISO 19650 is a series of standards about managing information over the life of a building or infrastructure asset.
The core idea
The series answers four questions for every piece of project information:
- Who needs it? The client, the facility manager, the contractor, the next design stage.
- What exactly do they need? Not “a model”, but specific information that supports a decision.
- When do they need it? At agreed milestones, not whenever someone finishes.
- How will it be checked and shared? Through an agreed process in a common data environment.
Everything else in the standard is machinery to make those answers explicit and traceable.
Requirements flow downwards
The appointing party (usually the client) describes what it needs. Those needs are passed to the lead appointed party, typically the lead designer or main contractor, who coordinates a delivery team. Inside that delivery team, task teams produce the information: architects, engineers, specialists.
Each level responds to the level above with a plan. You will meet the key documents in the next lesson: the requirements going down and the execution plans and delivery plans coming back up.
Requirements flow from the client’s needs into the EIR; the delivery team answers with the BEP and delivery plans.
Roles, not titles
ISO 19650 does not require anyone to be called “BIM Manager” or “BIM Coordinator”. It describes responsibilities: someone must define requirements, someone must plan delivery, someone must check information before it is shared. On a small project, one person might hold several of these. On a large one, they are spread across companies.
As a coordinator, you usually sit inside a task team or at lead appointed party level. Your work — clash tests, coordination meetings, issue logs, model checks — is how the delivery team proves its information is fit to share.
Information has a status
Information is not simply “done” or “not done”. It is produced in a common data environment (CDE) and moves through states, from work in progress to shared, published and finally archived. Each move is a decision that someone has checked the information is suitable for its next use.
ISO 19650 has several parts. Part 1 explains the concepts, Part 2 covers the delivery phase (design and construction), Part 3 the operational phase, Part 4 information exchange, and Part 5 a security-minded approach. Coordinators spend most of their time in the world of Part 2.
Key takeaways
- ISO 19650 is a framework for managing information, not a modelling standard or a software requirement.
- Every requirement flows down: the appointing party says what it needs, delivery teams plan how and when to provide it.
- Roles matter more than job titles: appointing party, lead appointed party and appointed parties.
- Information is produced in a common data environment and moves through agreed states before anyone relies on it.
Your notesSaved locally
Related tool
Agenda, attendance, issue log, actions and minutes. Roll open issues into the next meeting.
Open Coordination Meeting Pack →