This video explains the key roles and responsibilities defined by ISO 19650 for BIM and information management. The written guide below covers the appointing party, lead appointed party, appointed parties, delivery teams, and task teams, how information flows between them, and how to structure these roles in a practical digital workflow with clear permissions and a responsibility matrix.

Why clear roles and responsibilities are essential for ISO 19650 delivery

One of the most common causes of confusion on projects is not knowing who is responsible for what. When roles are unclear, information gets duplicated, deliverables fall through gaps, and teams spend more time chasing updates than producing work. ISO 19650 addresses this directly by defining a structured set of roles that govern how information flows through a project, from the client who defines what is needed all the way to the task teams who produce it. Understanding these roles is not just a theoretical exercise. It is the foundation for building a workflow where every team member knows their obligations, every deliverable has a clear owner, and every handoff between parties is traceable.

The standard defines three primary roles. The appointing party is the client or owner who initiates the project and defines the information requirements. They set the foundation for everything that follows by specifying what information is needed, to what level of detail, and by when. The lead appointed party, typically the main contractor or lead designer, manages and coordinates information across all teams, acting as the bridge between the appointing party and the teams doing the work. The appointed parties, usually subcontractors and consultants, are responsible for producing the specific information required by their discipline and delivering it back through the lead appointed party.

Below this structure, task teams are the small, focused groups or individuals responsible for creating discipline-specific deliverables like models, drawings, or reports. Task teams operate within the appointed parties and produce the detailed information that feeds into the broader delivery plan. The delivery team encompasses the lead appointed party and all appointed parties working together to manage and coordinate information production. And the project team includes everyone involved, from the appointing party through to every task team, forming the complete structure that ensures the project is delivered as a coordinated whole rather than a collection of disconnected efforts.

In practice, defining these roles is only useful if they are connected to a system that enforces them. In Plannerly, teams can be created and structured to reflect the ISO 19650 hierarchy, with permissions set at the viewer, editor, or manager level so that each party has exactly the access they need. Team members are invited and assigned to their respective teams, and the scope module allows responsibilities to be assigned against specific deliverables so that every information requirement has a named owner. This creates a responsibility matrix that is live, traceable, and connected to the actual project data rather than sitting in an isolated spreadsheet.

ISO 19650 roles and how information flows

1. Appointing party defines requirements – The client or asset owner sets the project and asset information requirements, establishing what information is needed and why it matters for the project and the long-term management of the asset.
2. Lead appointed party coordinates delivery – The main contractor or lead designer takes responsibility for managing information across all appointed parties, ensuring the right information is produced and shared at the right time.
3. Appointed parties produce information – Subcontractors, consultants, and specialist teams execute their specific tasks and deliver the required information back through the lead appointed party.
4. Task teams create deliverables – Small, discipline-specific groups within each appointed party produce the detailed models, drawings, reports, and data that fulfil the contracted requirements.
5. Delivery team manages production – The lead appointed party and all appointed parties work together as the delivery team, coordinating task team outputs and managing the overall information production process.
6. Project team ensures alignment – Everyone from the appointing party through to the task teams forms the complete project team, with clear communication channels and defined handoff points at every level.

What you’ll learn

• The appointing party’s role – How the client defines information requirements that set the foundation for the entire project delivery structure.
• Lead appointed party coordination – How the lead designer or main contractor manages information flow between the client and the teams producing the work.
• Task team and delivery team structure – How delivery teams and task teams are organised to produce discipline-specific information that feeds into the master delivery plan.
• Digital role management – How to create teams, set permissions, and assign responsibilities in a platform that enforces the ISO 19650 role structure across every project activity.
• Responsibility matrices – How a detailed responsibility matrix connects every deliverable to a named team and individual, creating accountability that is traceable throughout the project.

Common questions

Explore further

• BIM coordinator responsibilities – A detailed look at the role of the BIM coordinator and how it fits within the ISO 19650 delivery structure.
• Managing document collaboration and responsibilities – How to assign and track responsibilities across collaborative project documents.
• The secret to BIM accountability: structured collaborative contracts – How structured contracts enforce the roles and responsibilities agreed at the start of the project.
• How Plannerly supports ISO 19650 workflows worldwide – Overview of how the platform implements ISO 19650 role structures across international projects.