🚩Red Flags in a BIM Execution Plan (BEP) 🚩
You’ve received a BIM Execution Plan (BEP) with a tender or project proposal. Great!, however, before you assume it’s solid, take a closer look. A bad BEP can quietly sink your timelines, cause issues during design, and make handover a nightmare…
Here are some RED FLAGS to watch out for when reviewing & approving a project BIM Execution Plan (BEP):
🚩 1. It’s mostly generic boilerplate 🚩
If the BEP reads like it was copied from a government template with little mention of your project specifics, run! A real BEP should reflect your goals, team structure, project stages, workflows & tools.
⚠️ ISO 19650-2 Clause 5.3.2: Emphasises that the pre-appointment BEP should reflect the specific Project's Information Requirements (IRs), ensuring that the BEP is tailored to Clients expectations & not be just a generic template.
📌 Why it matters: A generic BEP can lead to misaligned expectations, rework and confusion, costing time & money right from the start.
🚩 2. No clear roles or responsibilities 🚩
Who's doing what? If it's not clear who’s leading BIM coordination, managing the Common Data Environment (CDE) platform, or auditing models & data to ensure all BIM deliverables align with the Exchange Information Requirements (EIR) and Asset Information Requirements (AIR), then this BEP is dodging accountability.
⚠️ISO 19650-2 Clause 5.4.2: Mandates the establishment of a detailed responsibility matrix, clarifying who is responsible for each aspect of information management.
📌 Why it matters: Without accountability, tasks fall through the cracks. This leads to duplicated efforts, missed deliverables, and finger pointing when issues arise.
🚩 3. The naming conventions section is empty (or references another document) 🚩
One of the most common sources of issues? Poor file naming. If the BEP doesn’t include a clear naming convention or fails to reflect the Client’s required standards (especially for estate-wide CDEs like those used e.g. Universities, Hospitals or Supermarkets), expect future confusion & manual fixes.
⚠️ ISO 19650-2 Clause 5.1.6: Requires the definition of naming conventions for information containers, ensuring consistency and clarity in file naming.
📌 Why it matters: Poor naming slows everyone down. Clear, project-specific conventions prevent errors, enable smooth collaboration & make asset retrieval easier later.
🚩 4. There’s no model validation or audit process 🚩
A solid BEP should explain how models will be checked, how often, and by whom. “Trust us, we’ll check it” is not a BIM strategy.
⚠️ISO 19650-2 Clause 5.6.3: Stipulates that quality assurance checks must be undertaken before sharing, ensuring the integrity of the information.
📌 Why it matters: Without regular checks, issues go unnoticed until it’s too late, resulting in delays, non-compliance, and costly fixes during construction.
🚩 5. Clash detection sounds like a one-time thing 🚩
If clash detection is only ‘mentioned’… that’s a problem. Coordination is a process, not a checkbox! The BEP should outline when, how often & what software/tools will be used.
⚠️ ISO 19650-2 Clause 5.6.2: Highlights the need for continuous coordination & cross-referencing of information, indicating that clash detection should be an ongoing process.
📌 Why it matters: Ongoing coordination prevents rework and site delays. One-time clash detection won’t cut it in complex projects.
🚩 6. It’s vague about ISO 19650 or says “We’ll follow it” 🚩
Many BEPs throw in “We comply with ISO 19650” as a blanket statement, but real compliance means explaining workflows, CDE processes & naming conventions that align with this suite of Standards. If it’s not spelled out, it’s not compliant.
⚠️ISO 19650-2 Clause 5.3.2: Outlines the specific considerations that should be included in the BEP to demonstrate compliance with ISO 19650 not vague promises.
📌 Why it matters: Vague statements = unclear expectations. Clear ISO-aligned processes mean fewer disputes and smoother delivery.
🚩 7. There’s no mention of COBie, handover, or asset data 🚩
Expecting usable data at handover? You won’t get it unless it’s planned from day one. A good BEP includes the information structure, COBie requirements (if applicable), and data validation strategy.
⚠️ISO 19650-2 Clause 5.4.3: Calls for the establishment of EIR & AIR, which should include asset data deliverables e.g. COBie for effective handover, smarter operations & better performance.
📌 Why it matters: Without structured data (like COBie), building operations and maintenance become harder and more expensive. Good data = better building performance and long-term cost savings.
🚩 8. The BEP is scattered across multiple documents 🚩
A BEP should be a single, coherent document. If you need to jump between 5 x Word files, appendices, or separate naming documents, trust us it’s a headache!
Yes, parts can be extracted for the delivery team, but all core information should live inside the BEP!, including naming conventions and file structures. No detective work should be required.
⚠️ISO 19650-2 Clause 5.3.2: While ISO 19650 allows flexibility in the format of the BEP, it emphasises the importance of a coherent & comprehensive plan. Disjointed documents can lead to confusion & require to be consolidated for clarity and easier BEP Audits.
📌 Why it matters: Fragmented BEPs waste time and increase the risk of missing key info. A single source of truth improves understanding and auditability.
✅ Final Thought
A strong BEP is more than paperwork, it’s your project’s BIM roadmap. If you’re not sure what you’re looking at, or something feels off, it’s worth getting it reviewed.
At BIM KARELA, we help clients & contractors spot these red flags early and build solid, project-specific BEPs that work in real life!
👉 Need a 2nd opinion on your BEP or a tender submission?
We’ll help you check if it’s compliant & aligned with Client’s Information Requirements! Book your session here 👉 www.bimkarela.com/adhoc-bim-strategy-sessions-online
📚 Curious to learn more about Information Requirements, BIM Management or BIM audits? Explore our #BIMTalk articles 👉www.bimkarela.com/bim-talk