How to Respond to BIM Requirements in Tenders: EIR Review and the Pre-Appointment BEP

Why Tenders Are Won and Lost on Information Management

Most firms treat the BIM section of a tender as an afterthought. The design team polishes the fee letter and the project approach, and two days before the deadline someone forwards the Exchange Information Requirements (EIR) to the BIM coordinator with a note that says “can you write something for this”. The result is a generic capability statement that reads exactly like the one every competitor submitted.

Clients have noticed. On projects run under ISO 19650, the BIM response is scored, not skimmed. Public-sector frameworks in the UK, Germany, Scandinavia, and the Gulf now weight information management at 10 to 20 percent of the quality score, and assessors are increasingly BIM-literate enough to spot a copy-paste answer. A tender response that engages with the client’s actual requirements, flags their gaps, and shows a credible delivery plan is one of the cheapest competitive advantages available to a mid-size firm.

This guide walks through the response workflow from the moment the tender package lands to the moment you submit: where the BIM requirements hide, how to decode the EIR, what a pre-appointment BEP must contain, how capability and capacity assessments work, and how to price the scope so you neither subsidise the client nor price yourself out.

Where BIM Requirements Hide in a Tender Package

The first practical problem is that BIM requirements are rarely in one document. On a typical invitation to tender you should expect to find them scattered across:

• The EIR itself. Sometimes a standalone document, sometimes an appendix to the employer’s requirements. This is the core: what information the client wants, when, in what format, and to what standard.
• The BIM protocol or information protocol. The contractual instrument that makes the EIR enforceable. In the UK this is usually the ISO 19650 compatible Information Protocol; other markets bolt BIM annexes onto FIDIC or national contract forms.
• The scoring criteria. Buried in the instructions to tenderers. This tells you how much the BIM answer is worth and what the assessors are told to look for. Read this before you write a single word.
• Technical appendices. CAD/BIM standards manuals, naming conventions, CDE procedures, asset data requirements, and sometimes a draft Master Information Delivery Plan (MIDP) skeleton.
• The pricing document. Look for whether information management is a priced line item or assumed to be absorbed in the design fee. This changes your commercial strategy completely.

Assign one person to index every BIM-relevant clause across the package on day one. Contradictions between documents are common, and finding them early gives you material for clarification questions, which is itself a scoring opportunity: a sharp clarification question signals competence before you have written anything.

Decoding the EIR: What the Client Is Actually Asking For

A well-written EIR flows from the ISO 19650 requirements chain: the client’s Organizational Information Requirements (OIR) drive Asset Information Requirements (AIR) and Project Information Requirements (PIR), which are packaged into the EIR you receive. If you have read our ISO 19650 guide, this chain will be familiar. When you review an EIR, extract answers to five questions:

1. What deliverables, at which milestones? Federated models, native files, IFC, COBie, drawings, schedules, point clouds. Map each deliverable to a project stage and note the acceptance criteria.
2. To what level of information need? Look for how the client defines geometric and alphanumeric detail per element per stage. Vague phrases like “LOD 350 for all elements” are a red flag you will handle in your response.
3. On which platforms? The Common Data Environment (CDE), model authoring tools, checking tools, and issue management. Note who pays for licences and who administers the CDE.
4. Under which standards? Naming conventions, classification system (Uniclass, OmniClass, national), coordinate strategy, exchange formats and versions (IFC 2x3 vs IFC4 matters for your export workflow).
5. With what management obligations? Meeting cadence, clash resolution responsibilities, model audit expectations, security requirements under ISO 19650-5, and the dreaded “the supplier shall provide all information the client may reasonably require” clause that you must bound in your response.

Build a simple requirements register in a spreadsheet: clause reference, requirement, your proposed response, cost implication, and any clarification needed. This register becomes the backbone of your pre-appointment BEP and later, if you win, of your delivery-phase BEP and MIDP.

Red Flags: Spotting a Copy-Paste EIR

Many EIRs are recycled from a previous project or downloaded from a template library, and responding to a broken EIR as if it were coherent is a trap. Watch for these patterns:

Red flag	What it tells you	How to respond
COBie demanded at every stage, including concept	Template reuse; the client has not thought about asset data	Propose COBie drops at defined milestones only, priced accordingly
”LOD 500 for the full model” at handover	Confusion between as-built verification and modeling everything	Offer a graded level of information need per element class
Software versions three releases out of date	The EIR predates the project	Confirm current versions via a clarification question
Clash-free model as a contractual obligation	Unbounded liability	Commit to a managed clash process with tolerances, not “zero clashes”
No named information manager on the client side	Nobody will review what you deliver	Propose the role, or offer it as a priced service
CDE unspecified but CDE workflows mandated	Cost and admin burden is unallocated	Ask, or price your own CDE and state the assumption

The key judgment call: never mock the client’s EIR, and never silently ignore its problems. The winning move is to acknowledge each requirement, state your compliant position, and propose a better-bounded alternative where the requirement is unworkable. Assessors reward tenderers who make their requirements deliverable.

The Pre-Appointment BEP: Your Core Deliverable

ISO 19650-2 splits the BIM Execution Plan into two lives. The pre-appointment BEP is a tender document: your proposal for how the delivery team would meet the EIR. The delivery-phase BEP is written after award, confirmed with the client, and maintained as a live document. Tenders are lost by submitting a delivery-phase-style BEP full of “to be confirmed” placeholders, and equally by submitting 80 pages of boilerplate. A strong pre-appointment BEP is typically 15 to 25 pages and covers:

Section	What good looks like
Response to the EIR	Clause-by-clause compliance statement from your requirements register, including proposed amendments
Delivery team organization	Named roles: information manager, task team information managers, discipline leads, with reporting lines
Capability summary	Evidence, not adjectives: named projects, delivered formats, CDE platforms operated
Mobilization plan	What happens in the first 30 days: CDE setup, standards alignment, kickoff workshops, template preparation
Information delivery strategy	Federation strategy, model breakdown, proposed exchange formats, survey and existing-data strategy
High-level responsibility matrix	Who produces what information per stage, at what level of information need
Risk register	The top 5 to 10 information risks with owners and mitigations
Proposed standards and methods	Your naming, classification, coordination, and QA approach, aligned to the client’s where specified

Write it in the client’s vocabulary. If the EIR says “information container”, do not say “file”. If the client names a CDE platform, reference your experience on that platform specifically. Generic text is the single most common reason BIM responses score mid-band.

Capability and Capacity Assessments: Proving You Can Deliver

ISO 19650-2 requires the lead appointed party to assess the capability and capacity of every task team, and clients increasingly push a questionnaire down the chain at tender stage. Capability means “can you do this kind of work”; capacity means “can you do it at the required volume, in the required window, alongside your other commitments”. Prepare a reusable evidence pack so you are not reinventing it per tender:

• Project evidence. Three to five reference projects with the formats delivered (IFC, COBie, federated models), the CDE used, the standards followed, and a named client contact. Match references to the sector of the tender where possible.
• People evidence. Short CVs for the proposed information manager and discipline BIM leads, including software certifications and ISO 19650 training. Name real people; assessors discount “a suitably qualified resource will be assigned”.
• IT evidence. Authoring and checking software with versions, CDE experience, remote working setup, and your information security posture. ISO 27001 or a Cyber Essentials equivalent increasingly appears as a pass/fail gate on public work.
• Capacity statement. A simple resource histogram showing the proposed team’s availability against the project timeline. This is the piece most firms omit, and it is precisely what distinguishes a real plan from a brochure.

Keep the pack versioned in your business development library and refresh it quarterly. A capability response assembled from maintained components takes hours; one written from scratch takes days you do not have inside a tender window.

The Mobilization Plan: Your First 30 Days on Paper

Assessors know that BIM projects fail at the start, not the end, so a concrete mobilization plan carries disproportionate weight. Lay out a dated sequence for the first month after appointment:

1. Week 1: Confirm the delivery-phase BEP with the client’s information manager. Agree amendments captured in your tender response. Stand up the CDE workspace, folder structure, and access controls, aligned to the workflows described in our CDE guide.
2. Week 2: Issue the project templates: model templates with agreed shared coordinates, naming rules, view templates, and starter families or objects. Run the project kickoff workshop with all task teams.
3. Week 3: Produce the responsibility matrix in full and draft the Task Information Delivery Plans (TIDP) with each task team lead.
4. Week 4: Consolidate TIDPs into the MIDP, run the first federation test with placeholder models, and verify the exchange pipeline end to end (native to IFC to the client’s viewer) before any real production begins.

A mobilization plan this specific does two jobs: it scores well, and it becomes your actual plan on day one if you win, which is exactly the point of the pre-appointment BEP.

Pricing the BIM Scope Without Guessing

The commercial failure mode is symmetric: firms either absorb information management invisibly in the design fee and haemorrhage margin, or they slap a defensive premium on the whole tender and lose on price. Estimate the scope like any other scope:

• Count the deliverables. From your requirements register: number of information exchanges, models per discipline, COBie drops, federation cycles, audit reports. Multiply by realistic unit efforts from your last comparable project.
• Separate roles from tasks. The information manager role (standing meetings, CDE administration, QA gates) is a recurring monthly cost across the whole programme. Model production effort scales with the project; management effort scales with the duration. Price them differently.
• Price the client’s gaps. Every unbounded clause you identified is either a clarification, a stated assumption, or a contingency line. An EIR demanding “all information reasonably required” without a defined level of information need should add explicit assumptions to your pricing, stated in the response.
• Make the invisible visible. Even when the tender forces a single fee, include a one-line breakdown showing information management as a distinct value. It signals maturity and protects you in scope-change negotiations later.

As a sanity check across typical building projects, dedicated information management effort commonly lands between 1 and 3 percent of the design fee, rising when the client demands heavy asset data deliverables like verified COBie. If your estimate falls far outside that band, revisit either your assumptions or the EIR’s realism.

Running the Response: Who Does What, and When

Treat the BIM response as a workstream with an owner, not a favour asked of the busiest coordinator. A workable split for a two-to-four week tender window:

• Bid manager owns the schedule, the scoring criteria, and consistency between the BIM response and the rest of the submission. Nothing undermines a tender like a BEP promising weekly coordination while the programme narrative says fortnightly.
• BIM manager or information manager owns the EIR review, the requirements register, the clarification questions, and the pre-appointment BEP content.
• Discipline leads validate that the proposed workflows and levels of information need are actually deliverable by their teams at the proposed effort.
• Commercial lead turns the requirements register’s cost column into the priced scope.

Sequence matters: EIR review and clarifications in the first quarter of the window, BEP drafting in the middle half, and internal review against the scoring criteria in the final quarter. Send clarification questions early; answers routinely arrive days before the deadline, and late answers that change your assumptions are grounds to restate them in your submission.

Common Mistakes That Sink BIM Tender Responses

• Restating the EIR back at the client. Compliance statements that paraphrase the requirement without saying how you will meet it read as evasion. Every “compliant” needs one sentence of method.
• Overpromising to score points. Committing to clash-free models, daily federations, or full LOD 500 as-builts wins the tender and loses the project. Your delivery team inherits every sentence.
• Ignoring the scoring criteria. If model-based quantity takeoff is worth 5 points and security-minded working is worth 1, the page allocation should reflect that, not your personal interests.
• No named people. Anonymous org charts with role titles only are heavily discounted by assessors who have been burned before.
• Submitting your standard BEP with the project name replaced. Assessors read many responses per framework; recycled text is obvious within a paragraph, especially when a competitor’s project name survives the find-and-replace. It happens more often than anyone admits.
• Treating the response as disposable. If you win, the pre-appointment BEP is the baseline for the delivery-phase BEP. Writing it as marketing fiction guarantees a painful confirmation meeting after award.

Best Practices for a Winning Response

1. Index every BIM clause across the whole package on day one and maintain a requirements register with a response and cost column per clause.
2. Read the scoring criteria before writing and allocate pages in proportion to points.
3. Ask sharp clarification questions early. They de-risk your price and demonstrate competence to the assessors.
4. Answer in the client’s vocabulary and mirror their document structure where the instructions allow it.
5. Name real people with real evidence and keep a maintained capability pack so assembly takes hours, not days.
6. Bound every unbounded requirement with a stated assumption rather than silence or refusal.
7. Include a dated 30-day mobilization plan. It is the highest-scoring content per page in most BIM responses.
8. Price management and production separately and sanity-check the total against comparable delivered projects.
9. Run an internal red-team review against the scoring criteria with someone who did not write the response.
10. Archive every response with its score and feedback. Framework debriefs are free consultancy; feed them into the next tender.

How to Start

If your firm has never run a structured BIM tender response, do not wait for the next live tender to build the machinery. Build the reusable parts now: a capability pack with reference projects and CVs, a pre-appointment BEP skeleton aligned to ISO 19650-2, a requirements register template, and a unit-effort sheet from your last two delivered projects. Then rehearse once on a past tender your firm lost, and compare what you would submit now against what was submitted then.

The professionals who lead this work are the ones who combine hands-on delivery knowledge with the ISO 19650 process vocabulary that clients score against. That combination is learnable. The courses at Archgyan Academy teach the Revit and BIM coordination workflows that real firms run, taught by a working BIM Coordinator, so the next time an EIR lands on your desk two days before a deadline, it is an opportunity instead of a fire drill.