Skip to main content

Create an EIR in Plannerly (and an OIR or PIR)

Start an Exchange Information Requirements (EIR) document from Plannerly's ISO 19650 templates, add structured requirements in Scope, then review, publish and export it. The same steps create an OIR or PIR.

Contents

TL;DR - In Docs, open Library (or Add from Library in an empty project), choose Plannerly Templates, then ISO 19650 Example Templates - English, and select Add beside EIR. The same list has OIR, PIR, AIR and BEP templates. Fill in the SmartFields and sections, add the structured information requirements in Scope, share the EIR for review, publish it and export it for the tender.


Who this is for

Information managers and project managers working for the appointing party (the client), and students working through the ISO 19650 assignments. You need to be able to edit Docs in the project.

Why it matters

Under ISO 19650 (see the ISO 19650 workflow in one diagram), the Exchange Information Requirements (EIR) tell each appointed party what information to deliver, when, and why. A clear EIR is what the delivery team's BEP answers, and what every model is checked against later. The OIR, PIR and AIR feed into it: the organization's goals, the project's goals, and the information needed to run the finished asset.


1. Add the EIR template

  1. Open Docs in your project and select Library on the toolbar. In an empty project, select Add from Library.
  2. Open the drop-down at the top of the Library, choose Plannerly Templates, then ISO 19650 Example Templates - English. Other languages are in the same list.
  3. Hover EIR and select Add. The EIR opens as a new document in your project.
Plannerly Docs Library showing ISO 19650 Example Templates - English with the Contract Example, OIR, PIR, AIR, EIR and BEP templates, and Add beside EIR
1: Library. 2: Plannerly Templates, ISO 19650 Example Templates - English. 3: Add beside EIR.
Want to see a finished one first? Add the Contract Example (for ISO 19650 Specialist) from the same list. It holds pre-filled ISO 19650 contract documents, including an EIR, for a sample office building, used in the free ISO 19650 Specialist assignments.

2. Fill in the EIR

  • SmartFields: the highlighted fields, such as the project name and the appointing party, fill in once and update everywhere they appear. See SmartFields: write it once, use it in every document.
  • Sections: work through each section, keep what applies to your project and remove what doesn't. Focus on the information you need and why, not on how the team will produce it - that belongs in their BEP.
  • Owners: give each section an owner so it's clear who writes what. See Assign section owners and @mention them.

3. Add the information requirements in Scope

The document explains your needs; the requirements themselves work best as structured data that every task and model check can use.

  1. In Scope, select Requirements on the toolbar.
  2. Add requirements with Browse Library, Create New or Import requirements (CSV).
  3. Assign them to the tasks, at the milestone when the information is due.

See Add information requirements from a library and Assign information requirements to tasks.

4. Review, publish and export

  1. When a section is ready, change its status from In Progress to Shared so reviewers can suggest edits, then to Published once it's agreed. See Share a document for review, then publish it.
  2. Export the EIR as a PDF or Word file for the tender package. See Export to PDF, get it signed and make a Word copy.

Create an OIR or a PIR

Use the same steps and choose OIR or PIR in the Library instead of EIR.

  • OIR - Organizational Information Requirements: the appointing party's mission and goals, and why the organization needs information at all.
  • PIR - Project Information Requirements: the project's goals, the information that already exists, the key decision points and what the client expects from delivery.
  • AIR - Asset Information Requirements: the information needed to operate and maintain the finished asset. See Create an AIR for asset information requirements.
Why this matters: an EIR that traces back to the PIR and AIR is easier to defend. Every requirement can answer "we need this because...", and every model check later points back to something the client actually asked for.

If it doesn't work

I can't see Plannerly Templates in the Library

An account admin may have switched them off for your projects - see Choose which templates appear in project Libraries.

The template's sections look empty

The EIR template gives you the structure to fill in. For a filled-in example, add the Contract Example (for ISO 19650 Specialist).

I can't edit a section

Only sections that are In Progress can be edited. A Published section is read-only until a manager returns it to In Progress.


Common questions

Is there an EIR template I can use?

Yes. In Docs, open Library, choose Plannerly Templates, then ISO 19650 Example Templates - English, and add EIR.

Is there a filled-in EIR example?

Yes. The Contract Example (for ISO 19650 Specialist) in the same list includes a pre-filled EIR.

What's the difference between the EIR and the BEP?

The EIR is the client saying what information it needs. The BEP is the delivery team explaining how it will provide it. See How to create a BEP.

Can I create the EIR in another language?

Yes. The Library has the ISO 19650 example templates in many languages, including French, Spanish, German, Italian, Portuguese, Polish, Japanese and Arabic.



Learn ISO 19650 with Plannerly's free certified courses - short videos, practical assignments and a certificate at each level.