Information requirements are lists of what must be delivered, for a decision someone has to make. They are not a contents page for a model. They sit inside the wider process described in ISO 19650 in plain English.
Four names, four audiences
- Organisational — what the appointing organisation needs across its projects. Asset registers, space data, carbon fields.
- Asset — what operators need after handover so they can maintain the thing. Valve tags, warranty dates, not presentation views.
- Project — what this project needs at each stage to make a decision. Planning geometry is not construction geometry.
- Exchange — the tender or appointment document that tells an appointed party which of the above they must produce, in which format, by when.
A worked test
If a requirement says “LOD 300 architecture model”, it has not said which rooms need areas, whether door fire ratings are mandatory, or who accepts the container. Rewrite it as a decision: at Stage 3 the cost plan needs gross internal area by function, from a Shared model, accepted by the lead appointed party.
Templates exist from the UK BIM Framework. Use those for a live appointment. This page only sorts the words.
Name the project information requirements that asked for the container, and the state the file is allowed to sit in. A file name that passes the checker is still the wrong file if the requirements asked for something else.
A worked chain from organisation to appointment
A housing association wants to plan maintenance better. Its organisational information requirement is a reliable register of building components and their condition. That drives an asset information requirement: for each new block, record every boiler, fire door and lift with its make, model, installation date and maintenance interval, in a format its asset system can import. For a new scheme, the project information requirement adds what the client needs to make decisions during design and construction, such as cost reports and design reviews at each stage. The exchange information requirement for the mechanical contractor then says precisely what that contractor must deliver: a schedule of boilers with stated attributes, at handover, accepted against a list of checks.
| Level | Example statement | Who writes it |
|---|---|---|
| OIR | Plan maintenance from a reliable component register | Appointing party |
| AIR | Each boiler: make, model, install date, service interval | Appointing party |
| PIR | Cost report and design review at each stage | Appointing party |
| EIR | Boiler schedule with stated attributes, at handover, checked against listed rules | Appointing party, for each appointment |
What makes a requirement checkable
- It names the information, not the software: “boiler schedule with these attributes”, not “a model”.
- It states when: a stage, a milestone or a date.
- It states the format, such as a spreadsheet template, IFC or COBie, if the receiving system needs one.
- It states how acceptance is checked and by whom.
- It says why, so the delivery team can make sensible choices where the requirement is silent.
Questions
Are EIRs the same as the old employer’s information requirements?
The term changed with ISO 19650. Exchange information requirements are tied to a specific appointment, and the same project may have several, one for each appointment.
What is the commonest weakness?
Requirements that describe a level of detail without saying what decision the information supports. The level of information need is meant to fix that by tying the amount of information to its purpose.
Rewriting a weak requirement
| Weak | Checkable |
|---|---|
| “Provide a BIM model.” | “At Stage 4, provide a federated architectural and structural model in IFC, with every room carrying its number, name and area.” |
| “Asset data to be provided.” | “At handover, provide a schedule of every boiler with make, model, serial number, install date and service interval, in the client’s template.” |
| “Drawings to an agreed standard.” | “All drawings named to the project naming convention and shared with a suitability code before each design review.” |
Each checkable version names the information, the time, the format and something a reviewer can test. The weak versions leave all of that to argument at the first delivery.
How many requirements should an EIR contain?
As many as the decisions need and no more. A long list of generic requirements copied from a previous project is harder to deliver and to check than a short list tied to this client’s decisions. Start from what the appointing party will do with the information, at which stage, and work back to the containers and attributes needed. Anything that does not support a decision or an asset system is a candidate for removal.
Who checks the information against the requirement?
The lead appointed party checks before authorising, and the appointing party checks before accepting. The acceptance criteria in the EIR tell both what to check, so write them so that someone other than the author could apply them.
Related: ISO 19650 in plain English · What a CDE is · File naming · Glossary
Sources
- BS EN ISO 19650-1:2018 and BS EN ISO 19650-2:2018, with the UK National Annex revised in 2021
- UK BIM Framework guidance
Last checked 14 October 2026. Official requirements stay in ISO 19650 and the UK BIM Framework. This is original guidance.