Across large-scale construction and infrastructure projects, misalignment between stakeholders is one of the most consistent sources of delay, rework, and cost overrun. Architects interpret a brief one way; structural engineers model it another; contractors receive drawings that contradict each other at the coordination stage. A well-written BIM Execution Plan (BEP) exists precisely to prevent this — establishing the shared rules, responsibilities, and data standards that every party on a project works to from day one.
This guide covers what an effective BEP contains, the distinction between pre- and post-contract versions, how to write one step by step, and the practical challenges of keeping diverse stakeholders genuinely aligned throughout a project lifecycle.
What Is a BIM Execution Plan?
A BIM Execution Plan is a project-specific document that defines how Building Information Modelling will be implemented across a project. It translates the client's information requirements into clear obligations for the design and construction team — specifying who produces what, in which software, to what level of detail, and by when.
Under ISO 19650, the international standard for managing information over the whole life cycle of a built asset, BEPs are a formal deliverable. The standard defines the BEP as the principal mechanism by which the appointed party responds to the client's Employer's Information Requirements (EIR) — setting out the proposed approach, capability, and resources for BIM delivery.
A BEP is not simply a software checklist. It addresses:
- Project BIM objectives — the specific use cases BIM will serve (clash detection, quantity extraction, facilities management handover, etc.)
- Information delivery milestones — what model data is required at each project gateway
- Level of Development (LOD) and Level of Information (LOI) — the geometric and data richness expected from each discipline at each stage
- Common Data Environment (CDE) — the shared platform and naming conventions for all project information
- Roles and responsibilities — who the BIM Manager, Information Manager, and Task Information Manager are, and what each is accountable for
- Software and format requirements — the authoring tools, exchange formats (IFC, NWD, RVT), and version compatibility
Pre-Contract vs Post-Contract BEPs
One of the most important distinctions in professional BIM practice is between the pre-contract BEP and the post-contract BEP — a distinction that is often overlooked on projects where the document is treated as a formality rather than a genuine management tool.
The pre-contract BEP is produced by the bidding team in response to the client's EIR before appointment. It demonstrates how the team proposes to meet the information requirements — what resources they have, which tools they will use, and how they plan to coordinate across disciplines. It is, in effect, a capability statement and a commitment.
The post-contract BEP is developed after appointment, once the full project team is assembled. It is the operational document: it incorporates the actual software versions in use, the agreed CDE platform, the full responsibility matrix, the clash detection workflow, and the information delivery plan aligned to the project programme. The post-contract BEP is a living document that is updated as the project evolves.
Projects that conflate the two — using a single vague BEP document throughout — typically find that responsibilities are unclear by the time detailed design and coordination work begins, which is exactly when clarity matters most.
Core Components of a Comprehensive BEP
Whether pre- or post-contract, an effective BEP covers a consistent set of core components. On larger projects these may be elaborated into separate supplementary documents; on smaller projects they may sit within a single concise file.
Project information — name, location, project type, contract form, key dates, and the identity of the client and appointing party.
BIM strategy and objectives — the specific BIM uses the project will deliver, such as design coordination, 4D programme simulation, cost estimation via 5D, or COBie handover for facilities management.
Roles and responsibilities — a responsibility matrix mapping each information deliverable to the task team responsible for producing it, and the individual responsible for authorising it. Under ISO 19650, this distinguishes between the Information Manager (overseeing the CDE), the BIM Manager (technical coordination), and Task Information Managers (discipline leads).
Information delivery plan — a schedule of model exchanges and data deliverables aligned to the project programme, showing what is required at each major milestone: concept design, scheme design, detailed design, construction issue, and handover.
CDE protocols — the platform (ACC, BIM 360, Revizto, or similar), folder structure, naming convention (typically following BS EN ISO 19650-2 Annex A), revision status codes, and approval workflows.
Software and interoperability standards — authoring software and versions for each discipline, exchange formats (IFC version, NWD, PDF), and any model splitting or federation approach for large projects.
Quality control procedures — model audit frequency, clash detection schedule, tolerance standards, and the process for raising, tracking, and closing model issues.
BIM Tools That Support Effective BEP Delivery
The CDE and coordination tools specified in the BEP directly affect how well teams can execute it. The three platforms most commonly specified in 2025 are:
| Tool | Strengths | Limitations |
|---|---|---|
| Autodesk Construction Cloud (ACC) | Fully integrated from design through construction; strong sheet management and RFI workflows | Higher licensing cost; some teams find migration from BIM 360 complex |
| Revizto | Excellent real-time issue tracking and walkthrough functionality; widely adopted for clash coordination meetings | Less suited to document management workflows than ACC |
| Navisworks Manage | Industry-standard for federated model review and clash detection; deep integration with Revit and Civil 3D | Primarily desktop-based; limited real-time collaboration |
For most projects in 2025, a combination is practical: ACC or a similar cloud CDE for document management and information workflow, with Navisworks or Revizto for coordination sessions. The BEP should specify both, with clear protocols for each.
Writing a BEP: A Step-by-Step Approach
Producing an effective post-contract BEP follows a consistent sequence regardless of project type or size:
-
Review the EIR — identify every information deliverable the client has required, the formats specified, and the milestones they are tied to. The BEP must respond to each requirement explicitly.
-
Assemble the project information — collect software versions, CDE platform details, and discipline lead contacts from all task teams. Gaps at this stage become ambiguities later.
-
Draft the responsibility matrix — assign each deliverable to a named task team and individual. Use the ISO 19650 responsibility structure as a framework.
-
Define LOD and LOI by stage — use the project work stages (RIBA Plan of Work or equivalent) to set expectations for geometric and data content at each milestone.
-
Establish the CDE structure — agree the platform, folder hierarchy, and naming convention with all parties before any models are issued. Retroactively reorganising a CDE mid-project is disproportionately disruptive.
-
Set the clash detection schedule — define frequency, who runs the federated model, who attends coordination meetings, and how issues are tracked and closed.
-
Review with all task teams — circulate the draft BEP and allow each discipline lead to confirm their sections are accurate. The BEP should be agreed, not imposed.
-
Issue and maintain — formally issue the BEP under the project revision system and commit to updating it when the team, scope, or tools change.
Keeping Stakeholders Aligned in Practice
A BEP is only as effective as the communication culture it sits within. Documents alone do not align teams — consistent process does.
Several practices consistently make the difference on well-run BIM projects:
Regular model coordination meetings held on a fixed schedule — fortnightly for most active design stages — keep clash detection results visible and prevent issues from accumulating. Attendance by discipline leads, not junior technicians, ensures decisions can be made in the room.
A single source of truth in the CDE eliminates the parallel email-chain problem that undermines many projects. Every drawing, model, and specification must have one authoritative location in the CDE; anything outside it is unofficial.
Clear revision and supersession protocols mean every team member knows which version of a document or model is current. The status codes defined in ISO 19650 (Work in Progress, Shared, Published, Archived) provide a ready-made framework.
Structured issue tracking — using the clash and issue management tools in Navisworks or Revizto — creates an auditable record of coordination decisions that can be referenced when disputes arise during construction.
How Adyantrix Approaches BEP Development
At Adyantrix, we develop BEPs for projects ranging from individual residential schemes to large mixed-use developments and infrastructure works. Our approach is grounded in ISO 19650 compliance and practical coordination experience — which means we write documents that are actually used on site, not filed and forgotten.
We support clients across the full BEP lifecycle: producing the EIR where the client needs help defining their requirements, writing the pre-contract BEP in response, and developing and maintaining the post-contract BEP as the project team is appointed. We also audit existing BEPs for projects where coordination has broken down and the document no longer reflects how the team is actually working.
Our BIM consulting team works alongside architectural BIM services, structural modelling, and clash detection coordination — so the BEP we write is directly connected to the models we produce.
Frequently Asked Questions
Ready to Improve Your BIM Coordination?
If your project is experiencing coordination gaps, unclear responsibilities, or a BEP that no longer reflects reality on the ground, Adyantrix can help.
We offer BEP review, BEP authoring, and full BIM project coordination services. Contact our BIM consulting team to discuss your project requirements.
Conclusion
An effective BIM Execution Plan is the difference between a project where BIM delivers measurable efficiency gains and one where it adds process overhead without clear benefit. The document itself is not the goal — the shared understanding it creates is. When every stakeholder knows what they are responsible for producing, in what format, to what standard, and by when, coordination becomes a managed process rather than a daily negotiation.
The BEP is where that clarity begins.
