The 4 ISO 19650 roles explained simply — who does what and why it matters

The biggest source of confusion in ISO 19650 implementations is mapping the British roles onto local organisational reality. "Who is the Lead Appointing Party? The owner? The site manager? The contracting authority?". Let us clear it up, with concrete examples.

Role 1 — Appointing Party (Owner / Client)

The party that commissions the project and sets the information requirements (EIR — Exchange Information Requirements). In public tenders: the contracting authority. In private projects: the developer or investor.

Key responsibilities: writes the EIR, validates final outputs, accepts deliverables and decides retention / archiving for the operational (OPEX) phase.

Role 2 — Lead Appointing Party (Requirements coordinator)

When there are multiple Appointing Parties (for example, an owner plus an environmental authority and a regulatory authority), the Lead Appointing Party coordinates and consolidates their requirements. In simple projects, Appointing Party and Lead Appointing Party are the same entity.

In practice, this role usually goes to the project manager or technical consultant appointed by the owner.

Role 3 — Lead Appointed Party (Delivery team coordinator)

The appointed party that delivers the project and is responsible for coordinating all task teams. In public tenders: the consortium leader. In private projects: the lead design firm or general contractor.

Has authority to approve WIP → Shared transitions, coordinate clash detection and deliver information packages to the Appointing Party.

Role 4 — Task Team (Production team)

The team that actually produces the information — designers, engineers, modellers, drafters. They may be in your firm or at subcontractors. They have write access in their own discipline's WIP zone and read-only access to other task teams' approved documents.

Why correct assignment matters

Wrong role definitions in the BEP cause three immediate practical problems:

• Approvals that get stuck because nobody has formal authority
• Wrong permissions in the CDE — subcontractors with write rights on published documents
• Inability to demonstrate traceability in audit (who approved what)

How to check if your roles are correct

Three simple questions that tell you if the role framework is working:

• If a designer is away for a week, can another task team member continue without asking for special permissions?
• In the audit trail, does every approval have a single identifiable Lead Appointed Party?
• Do subcontractors see other parties' published documents but cannot modify them?

If the answer is "no" to any, the BEP roles matrix is not aligned with the CDE permissions — and needs fixing before the next deadline.