An Employer’s Information Requirements document is one of the most important things a client can produce at the start of a project — and one of the most commonly misunderstood. A well-written EIR sets the project team up for success. A poorly written one creates confusion, drives up costs and becomes a source of dispute. This guide explains what an EIR is and how to write one that actually works.

What is an EIR?

The Employer’s Information Requirements (EIR) is a document produced by the appointing party (typically the client) that specifies what information they need from the project delivery team, how they need it formatted, and when they need it delivered. Under ISO 19650-2, the EIR is a formal pre-appointment document that forms part of the tender package and drives the project team’s BIM Execution Plan.

What Should an EIR Include?

Technical Requirements

• Software platforms and file formats to be used
• Level of information need for each project stage
• Naming conventions and classification system (e.g. Uniclass 2015)
• Model structure and federation strategy
• Coordination and clash detection requirements

Management Requirements

• The CDE platform to be used and how it will be administered
• Information review and approval workflows and timescales
• Key roles and responsibilities (Information Manager, BIM Manager etc.)
• Reporting requirements and frequency
• Security requirements (particularly relevant for sensitive or public sector projects)

Commercial Requirements

• Ownership and licensing of information and models
• Data security and confidentiality obligations
• Requirements for handover information including as-built models and O&M data
• How compliance with the EIR will be assessed and monitored

Common EIR Mistakes to Avoid

• Being too prescriptive about software. Specifying exact software versions can exclude capable teams and become outdated quickly. Focus on interoperability requirements and open file formats instead.
• Copying a template without tailoring it. A generic EIR that does not reflect the specific project type, scale or client’s actual information needs creates confusion and unrealistic expectations.
• Asking for more than you need. Requiring highly detailed models at early design stages adds cost and time with no benefit. Level of information need should be proportionate to the project stage and purpose.
• Not linking the EIR to the contract. The EIR should be incorporated into the appointments of all project team members so that information delivery obligations are contractually binding.
• Producing the EIR too late. The EIR must be ready before tender. Issuing it after appointment undermines the whole process.

How JC Virtual PMs Can Help

JC Virtual PMs supports clients in preparing EIRs that are clear, proportionate and fit for purpose — and supports delivery teams in reviewing and responding to EIRs through robust BIM Execution Plans. Whether you are a client looking to commission a project or a consultant preparing a tender response, we can help. Get in touch to discuss your requirements.