This video explains the information protocol and eSignature workflows in the ISO 19650 appointment process. The written guide below covers what an information protocol is, why it creates the contractual foundation for managing project information, how it defines roles, responsibilities, legal obligations, and data standards, and how eSignatures and structured appointment documents streamline approvals and keep everything connected in one controlled workflow.

Why the information protocol is the contractual backbone of ISO 19650

The information protocol is the sharp end of the ISO 19650 appointment process. It is the document that defines the roles, responsibilities, legal obligations, and agreed standards that all parties must follow when they exchange and manage project data. The protocol lists where to find all information management resources — the Exchange Information Requirements (EIR), the Asset Information Requirements (AIR), and related documents — and serves as the contractual foundation that makes these processes enforceable rather than aspirational.

Beyond listing resources, the information protocol defines information ownership and rights. This ensures clarity on who owns each piece of data, who has the authority to use it, and how it must be protected. Design models might be owned by the architect, for example, but shared access must be regulated for coordination purposes. Without this clarity, projects risk legal disputes and workflow disruptions when teams disagree about who has the right to use, modify, or distribute specific data. The protocol also enforces compliance with ISO 19650 requirements by ensuring all shared information is validated and meets predefined standards before being distributed, guaranteeing that the data shared across teams is consistent, reliable, and aligned with the project’s agreed standards.

An effective information protocol starts with defining clear objectives. Every party must understand their roles and responsibilities for managing and producing information, aligned with the EIR and ISO 19650 standards. The protocol provides legal and contractual clarity so everyone knows their obligations, rights, and liabilities upfront. Key components include roles and responsibilities from the appointing party through to the lead appointed party and all appointed teams, information management procedures, compliance with ISO 19650 standards, intellectual property rights, and data security protocols. Review and approval processes are also specified to ensure the quality of every deliverable. The key content areas cover workflows for producing, sharing, and validating information, naming conventions, security requirements, and legal obligations including licensing and intellectual property rights.

The critical step that gives the protocol real weight is incorporating it into the contract. Adding a clause such as “the parties agree to comply with the information protocol at appendix X” makes it legally binding. The completed protocol is attached as an appendix or schedule to the contract, tying everything together and making the protocol enforceable. Once the contract is finalised, the appointment chain flows from the appointing party to the lead appointed party, and then from the lead appointed party to the appointed parties, creating back-to-back contracts with legal obligations that flow through the entire supply chain. Using smart field templates to generate appointment documents means that information is populated automatically across multiple contracts, reducing manual input and ensuring consistency. Documents can be filtered by team to include only the specific contractual obligations assigned to each party, and eSignature workflows ensure that approvals happen quickly with a clear digital audit trail stored in the common data environment.

How to create and manage the information protocol

1. Define the objectives of the information protocol – Establish the foundation by documenting the roles and responsibilities of every party, aligning with the EIR and ISO 19650 standards, and providing legal and contractual clarity on obligations, rights, and liabilities.
2. Identify key components – Include roles and responsibilities across the full appointment chain, information management procedures, compliance requirements, intellectual property rights, data security protocols, and review and approval processes for every deliverable.
3. Document key content areas – Define workflows for producing, sharing, and validating information. Specify naming conventions, security requirements, legal obligations, licensing terms, and intellectual property rights to ensure the protocol covers both technical and legal aspects comprehensively.
4. Incorporate the protocol into the contract – Make the protocol legally binding by adding a compliance clause and attaching the completed protocol as an appendix or schedule to the structured contract.
5. Create appointment documents using templates – Use the Docs module with smart field templates to generate appointment documents efficiently, reducing manual input and ensuring consistency across multiple contracts in the supply chain.
6. Filter requirements by team – Export appointment documents with filtered scope so each appointed party receives only the contractual obligations relevant to their role, rather than the entire project scope.
7. Route for eSignature approval – Define who needs to approve each document, generate the approval request, and use the eSignature process to collect typed or drawn signatures electronically. Signed documents are stored in the CDE with a complete audit trail.
8. Apply metadata-driven file naming – Use the CDE’s naming convention tools to concatenate metadata into standardised file names that follow ISO 19650 requirements automatically, ensuring every exported and signed document is correctly named and traceable.

What you’ll learn

• What an information protocol is – How the protocol serves as the contractual foundation for managing project information, defining roles, responsibilities, legal obligations, and agreed standards for data exchange.
• Information ownership and rights – Why clearly defining who owns each piece of data, who can use it, and how it must be protected prevents legal disputes and workflow disruptions during the project.
• Compliance enforcement – How the protocol ensures that all shared information is validated against predefined standards before distribution, maintaining consistency and reliability across the project.
• Contractual weight – Why incorporating the information protocol into the contract as a binding appendix makes it enforceable and ensures that all parties are legally committed to following the agreed processes.
• The appointment chain – How agreements flow from the appointing party to the lead appointed party and then to appointed parties, creating back-to-back contracts with legal obligations throughout the supply chain.
• eSignatures and streamlined approvals – How electronic signature workflows replace slow paper-based processes, enabling faster approvals with a clear digital audit trail stored in the common data environment.

Common questions

Explore further

• Creating the information protocol and eSign contract – The full expert course lesson covering the information protocol and eSignature process in detail.
• eSign AEC project documents – How electronic signatures work for construction and design project documentation.
• EIR, PIR, and BEP documents with Plannerly – How the complete set of information requirement and delivery documents connects across the project lifecycle.
• ISO 19650 concepts and workflows – The full help centre collection covering how each component of ISO 19650 works together in practice.