Set information requirements your supply chain can check against
Information requirements say what information a client needs, when, and why. Under ISO 19650 the OIR sets the goals, the AIR and PIR turn them into asset and project needs, and the EIR tells each appointed party what to deliver at each exchange. In Plannerly they become one list every model is checked against.
Stop finding the gaps at handover. Ask for exactly the information you'll use to run the asset, and say why. Your OIR, AIR and EIR become one list, staged by milestone, that every appointed party signs for and every model is checked against.
Stop guessing what the client's EIR really wants. Split it into requirements each subcontractor can meet, by team and milestone, issue each one as a PDF, a spreadsheet or an IDS file, and check the models before they go to the client.
Stop modelling what nobody asked for. See what the client needs for each element at each stage before you model it, with the rule that checks it, so your team delivers what's asked and can show it.
Stop rewriting requirements for every client. Start from ISO 19650 templates, the buildingSMART Data Dictionary or your own library, stage them by milestone, and hand your client requirements the supply chain can check.
Teach information requirements as a working system, not a list of acronyms. Students build the OIR, AIR and EIR for a real project, stage them by milestone and check a model against them.
Free plan, no card. Task teams never pay to join your project.
app.plannerly.com
The problem
The EIR asks for everything, so nobody can check what was delivered
Most owners aren't sure exactly what to ask for, so the EIR is copied from the last job: a long PDF asking for everything, with no reason behind it. Teams model what they think is needed, and the gaps turn up at handover. The four steps below fix that.
Stop issuing an EIR nobody can check: start from the purpose, build one list, stage it, then check what arrives
Start from the purpose
Requirements copied from the last job ask for everything and explain nothing. Write the OIR from an ISO 19650 template: what your organisation needs to know to run its assets, and why.
Requirements with a reason behind them
Build one list
Five spreadsheets never agree. In Scope, list the assets and elements and add the information each one needs - from the library, the buildingSMART Data Dictionary, a CSV or by hand - each with the rule that checks it.
One structured list instead of five spreadsheets
Stage it by milestone
Ask for everything on day one and teams model what nobody needs yet. Assign each requirement at the information exchange where it's needed, with the level of information need for that stage.
The right information at the right exchange
Issue it to be checked
A PDF can't check a model. Give each task team its own requirements as a PDF, a spreadsheet or an IDS file, have them signed, and check the models that come back against the same rules in Verify.
Requirements every team can check against
See it work
Ask your project what is missing
In beta
Find the gaps with Javis
Ask Javis, Plannerly's project assistant, about your requirements and who owns them, in plain words. It answers from what the project records, and says what it can't confirm. Javis is in beta, so expect it to keep improving.
What exchange information requirements are in ISO 19650, and how they fit with the rest, in about five minutes.
Free live webinar
Surviving AI Model Checking
Agree it. Check it. Fix what failed. Everyone is talking about AI checking BIM models, but it only works if the model has something to be checked against. How to turn your information requirements into rules a model passes or fails, check every delivered model against them, and get each failure to the team that can fix it.
Nov19Thu
Free webinar on Zoom · 45 minutes · How to survive as a BIM Manager
Thursday 19 November 2026
10:00New York15:00London19:00Dubai
You'll leave with
Requirements a model either passes or fails
Every delivered model checked against them
Each failed check with the team that owns it
Free download
Don't copy the last job's EIR: get a starter requirements project and the EIR, OIR and AIR PDFs, free
Free download
Information Requirements Survival Kit: a starter project and the EIR, OIR and AIR PDFs
Stop copying the last job's EIR. Start from a requirements project for Plannerly, with the EIR, OIR and AIR explained in three PDFs from our free ISO 19650 training.
1 starter project
3 PDFs
Free
PDF
PDF
PLANNERLY
Information requirements starter project
OIR and EIR documents in Docs and a structured requirements list in Scope, staged by milestone and ready for your own assets and task teams.
Owners and designers who made their requirements checkable: 11,000 Excel rows replaced by automated checks, government model data checked against defined requirements, and structured BIM requirements across a global portfolio.
For owners the payoff is certainty at every exchange: JTC Corporation replaced 11,000 Excel rows with automated checks and cut model validation time by 95%.
Contractors know what their models will be checked against: Queensland's Department of Transport and Main Roads checks supply-chain model data against defined information requirements.
Design teams get requirements they can see and meet: Foster + Partners uses Plannerly to manage structured BIM requirements across its global portfolio.
Consultants turn requirements into a standard their clients can check: JTC automated compliance checks across 2,000+ object types and 27 model categories.
These are the requirements your students will be checked against on real projects: structured, staged and checked by software, not by eye.
Queensland Department of Transport and Main Roads · Government owner
Queensland's Department of Transport and Main Roads uses Plannerly Verify to check supply-chain model data against defined information requirements, giving the team more certainty that model deliverables contain the information they expect.
It highlights the need for due diligence when pulling all of the pieces of the puzzle together.
Bryan McSweeney, Manager - Special Projects · TMR
Government
Verify
Model Checking
Read the story
United Kingdom
Global practice
World-leading architecture studio
Making global BIM scope visible
Foster + Partners · Architecture
One of the world's most celebrated architecture studios uses Plannerly to manage structured BIM requirements across their global portfolio of landmark projects.
Trusted by one of the world's most iconic architecture practices to manage BIM requirements at a global scale.
Architecture
Global
BIM Management
See all case studiesOwners, design teams, contractors, consultants and educators - filter them by your kind of organisation.
What owners say
Owners on getting the requirements right
5 out of 5
It highlights the need for due diligence when pulling all of the pieces of the puzzle together to make sure there are no errors in the definition of our information requirements.
BMBryan McSweeneyManager - Special Projects, Digital Systems · Queensland Department of Transport and Main Roads
5 out of 5
Compliance checks used to be a black box. Now, every requirement is traceable and auditable.
JKJohn KiongDirector, Future of Building & Infrastructure · JTC Corporation
What contractors say
Contractors on checking models against requirements
5 out of 5
Plannerly cut the time we spent tracking scope and verifying models by 60%.
In the 12 years working in this industry, it's the first time I can say I have an up-to-date BEP ... the Scope module is the best way I've seen to display requirements so that everyone can interpret the data
TWTroy WhiteMott MacDonald
What consultants say
Consultants on requirements as a standard
5 out of 5
Plannerly accelerated our standards creation and virtually eliminated the burden to get updates to end users.
JRJohn RussoPresident · USIBD
5 out of 5
When you're helping governments go digital, you need a platform teams actually understand. That's Plannerly.
VLVoon LokManaging Director · AdRem IT Solutions
What educators say
Educators on teaching requirements in practice
5 out of 5
Many software companies get this wrong. They don't create content or videos. You can't ask me to bring your tool into my curriculum when there's nothing for students to learn from. Plannerly has all of that.
ZADr. Zulfikar AdamuAssociate Professor · London South Bank University
5 out of 5
Students love Plannerly and it makes my life so much easier!
PKPetro KaranxhaProfessor · George Brown College
Setup guides
Set up your information requirements in Plannerly, step by step
Short Help Center guides that walk you through each step in Plannerly. Open one beside the app and follow along.
What is an EIR (exchange information requirements)?
The exchange information requirements (EIR) tell an appointed party what information to deliver, to what standard and at which information exchange. Under ISO 19650-2 the appointing party writes an EIR for each appointment, drawn from its OIR, AIR and PIR, and each lead appointed party writes one for every task team it appoints. It covers the requirements themselves, the delivery milestones, the information standard, the production methods and procedures, and how deliveries will be accepted. The Level 3 lesson on the EIR walks through one.
What's the difference between OIR, AIR, PIR and EIR?
They're a chain. The OIR (organisational information requirements) says what an organisation needs to know to run its business and its assets. The AIR (asset information requirements) turns that into the data needed on each asset you'll operate and maintain, and the PIR (project information requirements) into what's needed for the key decisions on one project. The EIR then tells each appointed party what to deliver, and when, to meet them. If a requirement can't be traced back up the chain, you probably don't need it. Our free Learn ISO 19650 page has a PDF on each one.
Who writes the EIR?
The appointing party - the client or asset owner - writes the EIR for each lead appointed party, often with help from a consultant. The lead appointed party then writes its own EIR for each task team it appoints, adding anything it needs on top. The delivery team's BIM execution plan is its answer to the EIR.
What goes in an EIR?
At minimum: the information requirements (what's needed, about which elements or assets, to what level of information need), the information delivery milestones, the information standard (naming, classification and formats), the production methods and procedures, and the acceptance criteria. Supporting information such as existing surveys, models and documents often goes with it. Our ISO 19650 templates include an EIR to start from, and the UK BIM Framework's Guidance Part D on developing information requirements goes deeper.
What is the OIR in ISO 19650?
The organisational information requirements (OIR) describe the information an organisation needs to meet its business goals - running its estate, meeting regulations, planning maintenance and investment. They're written once for the organisation, not per project, and every AIR, PIR and EIR should trace back to them. The Level 3 lesson on the OIR explains how to write one.
What is the PIR in BIM?
The project information requirements (PIR) set out the information the client needs at the key decision points of one project - for example, to approve the design, the budget or the move to construction. They come from the OIR and shape the information delivery milestones in the EIR. See the Level 3 lesson on the PIR.
What is the AIR?
The asset information requirements (AIR) list the assets you'll need to operate and maintain, and the data you need on each one - manufacturer, serial number, warranty, maintenance intervals and so on. Our Help Center shows how to build an AIR in Plannerly, contract for it and check the models against it.
Is there a free EIR template for ISO 19650?
Yes. Our ISO 19650 templates include EIR, OIR and AIR templates, and the Information Requirements Survival Kit on this page adds the EIR, OIR and AIR PDFs from our free training. Open them in Plannerly on a free account and the requirements become a list you can assign and check, not a PDF to retype.
How do I make information requirements checkable?
Give every requirement a rule. In Plannerly each information requirement carries its own check - a value that must be there, a number in a range with its unit, a date or a text pattern - and is assigned to the elements and milestone it applies to. Export the requirements as an IDS file for the modelling tools, and the Verify module checks delivered models against the same rules automatically, colour-coding what passes, what's wrong and what's missing. More in model checking with IDS.
What is an appointing party in ISO 19650?
The appointing party is the organisation that receives information about the project and appoints the delivery teams - usually the client or asset owner, such as a government agency, a developer or a university. It sets the information requirements, appoints the lead appointed parties and accepts the information they deliver. Our Help Center explains the appointing party's responsibilities.
Can AI help write information requirements?
Yes, if you want it to - or write them yourself from the templates. In Plannerly AI can enrich and standardise requirements and write the regular expressions for naming rules, and you review everything before it's issued - see how to build an AIR. Episode 3 (22 October) goes further, with three ways into your project's requirements: the Plannerly API, your own AI through Plannerly MCP, or asking Javis. Watch Episode 3.
Can I set information requirements on the Free plan?
Yes. Build and stage your requirements on Free, on up to five projects, export them as an IDS file, and invite every task team to view them and comment. Free includes two e-signatures; Pro makes editors and e-signatures unlimited and checks the delivered models. The 14-day Pro trial includes model checking, with no card and nothing to cancel. Compare the plans.
Pricing
Start free, then pay per project when you're ready
Free$0forever
Five projects included
The account owner edits; everyone they invite can view
100 MB of project files
Explore Docs, Scope and Verify
You build the requirements, and everyone you invite can view and comment