This video explains what Exchange Information Requirements (EIR) are and why they are central to ISO 19650 project delivery. The written guide below covers how the EIR brings together organisational, asset, and project information needs into one structured document, why defining purpose, format, milestones, and quality standards matters, and how database-driven workflows make EIR creation practical and scalable across teams and appointments.

Why exchange information requirements bring clarity to project delivery

On any project that involves multiple teams, disciplines, and systems, the risk of confusion about what information needs to be delivered, when, and in what format is significant. The Exchange Information Requirements exist to solve this problem. The EIR is where the different layers of information need — the Organizational Information Requirements (OIR), the Asset Information Requirements (AIR), and the Project Information Requirements (PIR) — come together into one clear, structured guide that every party on the project can follow. Without a well-defined EIR, each team interprets expectations differently, formats vary across deliverables, and critical information arrives too late to support the decisions it was meant to inform.

The challenges are real. On large projects with many data sources, each system tends to have its own rules and conventions, which creates confusion when teams try to exchange information across organisational boundaries. Different stakeholder groups care about different things: operations teams need maintenance data, finance teams need cost data, design teams need spatial and performance data. Balancing these needs without losing sight of the project goals requires a single point of reference that everyone can align to. As a project evolves, information needs change too, and keeping the EIR up to date becomes a coordination challenge in its own right. The EIR addresses all of this by establishing a shared set of rules and expectations before any work begins.

Building an effective EIR starts with defining the purpose of the information exchange. The EIR must explain why information is needed and specify the form and format it should take — whether that is a 3D model, a PDF report, a spreadsheet, a checklist, a certificate, or a drawing. This clarity about format ensures that teams are not left guessing how to package their deliverables and reduces the back-and-forth that slows projects down. The EIR then needs to align with the broader requirements hierarchy, connecting organisational goals, asset care needs, and project-specific deadlines into a single coherent set of expectations. Setting clear information exchange milestones ensures that the right data is available when key decisions need to be made, rather than arriving in bulk at the end of the project when it is too late to act on.

Quality standards are another essential component. High-quality information can only be produced when teams understand exactly what “acceptable” looks like. By defining quality criteria in the EIR, from naming conventions and classification systems to level of information need and verification requirements, the appointing party gives every team a clear target to aim for. Once finalised, the EIR is included in tender and appointment documents so that contractors, consultants, and delivery teams know what is expected from day one. This early clarity reduces the chance of misunderstandings and gives tendering parties the confidence to price accurately and plan their information delivery properly. Managing the EIR in a database-driven workflow rather than static documents makes it far easier to filter, sort, and target specific requirements to the right teams, creating more focused and relevant appointment documents for each party.

How to build and manage exchange information requirements

1. Define the purpose of each information exchange – Start by documenting why each piece of information is needed, who will use it, and what decisions it supports. This ensures that every requirement in the EIR has a clear business justification.
2. Specify the form and format – For each requirement, define whether the information should be delivered as a model, drawing, spreadsheet, certificate, checklist, or other format. Clear format expectations eliminate ambiguity and reduce rework.
3. Align with OIR, AIR, and PIR – Map each exchange requirement back to its source in the organisational, asset, or project information requirements. This traceability ensures that the EIR is complete, avoids duplication, and demonstrates that every requirement serves a genuine need.
4. Set information exchange milestones – Define when each piece of information must be delivered, aligning with the project programme and the Master Information Delivery Plan (MIDP) so that data arrives in time to support critical decisions.
5. Define quality and acceptance criteria – Specify the standards each deliverable must meet, including naming conventions, classification, level of information need, and verification methods, so teams understand exactly what is acceptable.
6. Structure requirements in Plannerly’s Docs module – Use the Docs module to build the EIR document with templates, smart fields, and structured sections that cover project goals, data exchange rules, formats, milestones, and standards in one place.
7. Break requirements down by phase in the Scope module – Use the Scope module to organise EIR requirements by project phase — design, construction, and operations — so each team sees exactly what is relevant to their stage of delivery.
8. Finalise and include in appointment documents – Share the completed EIR with all project parties through their appointment documentation so that compliance criteria are understood from the start of every contract.

What you’ll learn

• What an EIR is – How Exchange Information Requirements bring together the OIR, AIR, and PIR into one structured guide that defines what information must be exchanged, in what format, and at which stages.
• Why unclear exchange requirements cause problems – How projects struggle when multiple teams, systems, and stakeholder groups operate without a shared understanding of information expectations, leading to inconsistencies, rework, and missed deadlines.
• Purpose, form, and format – Why defining the reason for each information exchange and specifying the exact delivery format — model, drawing, spreadsheet, certificate — eliminates ambiguity and keeps teams aligned.
• Milestones and timing – How setting clear information exchange milestones ensures that data is delivered when key decisions need to be made, not just at project completion.
• Quality and compliance criteria – How defining acceptance standards in the EIR helps teams understand what “good enough” looks like and gives the appointing party confidence that deliverables will meet expectations.
• Database-driven EIR management – How structuring exchange requirements in a database rather than static documents makes it easier to filter, assign, and target requirements to the right teams for more focused tender and appointment processes.

Common questions

Explore further

• EIR: Exchange Information Requirements – The full expert course lesson covering EIR structure, purpose, and practical workflows.
• EIR, PIR, and BEP documents with Plannerly – How the complete set of information requirement documents connects and can be managed using templates.
• How to create professional project documents like EIR, PIR, and BEP – A practical walkthrough of building information requirement documents from templates.
• ISO 19650 standards explained in 1 hour – A broad overview of the full ISO 19650 framework and how each component fits together.