How to Respond to an EIR

Why Your EIR Response Matters More Than You Think

Most teams treat the EIR response as a compliance exercise - fill in the blanks, attach some CVs, submit before the deadline. But the pBEP is often the single document that determines whether you win or lose the appointment. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Step 1 - Read the EIR Properly

Before you start writing, you need to understand what the appointing party is actually asking for. EIRs vary wildly in quality - some are 80 pages of detail, others are a 2-page afterthought stapled to the tender package. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

What to look for

• Information delivery milestones - when do they want what? Map these to the project programme.
• LOD requirements per discipline - are they asking for LOD 300 at tender stage or LOD 200? This changes your resourcing.
• CDE requirements - are they mandating a specific platform (Aconex, BIM 360, Viewpoint)? Or is it your choice?
• Naming conventions - are they using ISO 19650 naming or a bespoke convention? This affects every file you produce.
• Clash detection expectations - what level of coordination is expected and at what stage?

Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium.

Step 2 - Scope Your Response

Don't start writing the pBEP yet. First, scope the response by mapping the EIR requirements against your actual capability and proposed team. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. This is where most teams fail - they write what they think the client wants to hear rather than what they can actually deliver.

Step 3 - Structure the pBEP

Your pBEP should mirror the structure of the EIR wherever possible. If the EIR has 12 sections, your response should address all 12 in the same order. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Essential sections

1. Project information - confirm you understand the scope, parties, and programme
2. Team and competence - who's doing what, CVs, relevant experience
3. Delivery approach - software, standards, modelling methodology
4. CDE and data management - your CDE proposal or how you'll work in theirs
5. Information delivery schedule - when you'll deliver what, mapped to milestones
6. QA/QC process - how you ensure quality before information reaches the CDE
7. Risk register - what could go wrong and how you'll mitigate it

Step 4 - Write to Win, Not Just to Comply

Compliance gets you to the shortlist. Specificity wins the appointment. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. The appointing party wants to see that you've read their EIR - not that you've filled in a generic template. Reference their project name, their specific requirements, their timeline. Show that this pBEP was written for this project.

Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Step 5 - Review Before Submission

Run the pBEP through a compliance check before submission. Map every EIR requirement to a section in your response. If anything is unanswered, flag it - either address it or explicitly state it's not applicable and why. Lorem ipsum dolor sit amet.

• Compliance matrix - create a simple table: EIR requirement → pBEP section → status (addressed / N/A / clarification needed)
• Internal review - have someone who didn't write it read it. Fresh eyes catch assumptions.
• File naming check - make sure the pBEP itself follows the naming convention you're proposing. If your own document doesn't comply, that's a red flag.

Common EIR Response Mistakes

After reviewing hundreds of pBEPs across the Gulf region, these are the most common errors we see.

• Copy-pasting from the last project - the appointing party can tell. Project-specific references from a different job are an instant credibility killer.
• Overpromising LOD - committing to LOD 400 when the timeline and budget only support LOD 300. Under-promise and over-deliver.
• Ignoring the CDE requirement - if they've specified Aconex, don't propose BIM 360. Work within their ecosystem.
• No RACI matrix - without clear responsibility assignment, the appointing party can't evaluate accountability. Always include one.
• Generic risk register - "model coordination risks" isn't specific. "MEP coordination risk due to parallel design development in packages 3 and 5" is.