BIM Execution Plan (BEP): A Complete Guide for AEC Project Teams

What Is a BIM Execution Plan (BEP)?

A BIM Execution Plan is a project-specific planning document. It sets out how BIM will be implemented across a project, covering strategy, standards, roles, deliverables, and workflows from early design through to handover. It is somewhat like a team's implementation plan. It does not set the client's requirements, those come from the Employer Information Requirements (EIR). The BEP is the project team's formal response to the client's EIR and must be agreed upon by all project disciplines before production work begins.

The lead appointed party, usually the architect or a dedicated BIM Manager, authors the BEP.

BEP vs BIM Protocol

A BIM Protocol (such as those structured around ISO 19650 or the AIA G202 exhibit) sets the contractual framework. It defines what the employer expects, what standards apply, and what the legal obligations are around model authoring. The BEP sits underneath that. It is the operational plan the appointed team writes to show how they will fulfill those contractual expectations on this specific project.

Pre-Contract vs. Post-Contract BEP: Understanding the Lifecycle

A BEP is not a single document produced once. It evolves through the project. There are two distinct phases, each serving a different purpose. The pre-contract BEP is submitted during tender/bid phase and covers high-level approach, team capability assessment, and preliminary workflows. The post-contract BEP is developed after contract award and includes fully detailed model matrix, LOD milestones, CDE setup, and coordination protocols.

The post-contract BEP is not a separate document from scratch. It builds directly on the pre-contract version. Teams should track changes between the two that document how scope evolved, which responsibilities shifted, and where assumptions were revised after award.

Why AEC Firms Need a BIM Execution Plan

Prevents coordination failures

Without a BEP, disciplines operate independently. An architect models walls at LOD 200 while the structural engineer assumes LOD 300. The MEP team uses a different origin point. File naming is inconsistent. By the time federation happens, the clashes are extensive and the rework is expensive. A BEP establishes the shared rules before any of that happens.

Contractual protection

A well-documented BEP is a reference document for dispute resolution. If a client challenges a deliverable's accuracy, or a sub-consultant disputes responsibility for a coordination failure, the BEP is the record of what was agreed. Without it, scope arguments have no written anchor.

Procurement compliance

Many public sector procurement frameworks now require a BEP as a contractual deliverable. The UK mandates BEP compliance under ISO 19650. EU procurement frameworks increasingly follow suit. In the US, federal and state agencies using NBIMS-compliant workflows expect a BEP as part of project qualification. Failing to submit one or submitting a template copy that has not been tailored to the project can disqualify a bid.

Cross-discipline alignment

Architecture, structure, MEP, and civil engineers each bring their own software defaults, file conventions, and modelling habits. Without a BEP, every new project resolves these conflicts ad hoc, usually mid-design. The BEP locks in a shared coordinate system, a common unit of measurement, a consistent naming convention, and a handover schedule before Stage 2 begins.

Key Elements / Components of a BIM Execution Plan

A BEP is not a general statement of intent. Each section should be specific, measurable, and project-tailored. Let's take a look at its main components:

1. Project Information

Covers project name, contract number, client identity, lead appointed party, and version history. This section must be version-controlled. A BEP that does not track its own revisions creates more confusion than clarity, especially on projects that run for several years.

2. BIM Goals and Uses

Lists the specific BIM Uses selected for the project—for example: Design Authoring, 3D Coordination, Construction System Design, Record Modelling. Each use should have a defined priority level (primary or secondary), a responsible party, and a clear output. Using the BIM Forum Use Library as a reference ensures consistent terminology across disciplines.

3. Roles and Responsibilities

Defines the BIM Manager and Information Manager roles clearly. Includes a RACI matrix (Responsible, Accountable, Consulted, Informed) assigning model authoring responsibility to each discipline lead and sub-consultant. This section prevents the most common BIM coordination failure: everyone assuming someone else owns a model element.

4. LOD or LOIN Matrix

Specifies the Level of Development (LOD) or Level of Information Need (LOIN) under ISO 19650 required for each model element category at each project milestone. A wall assembly at RIBA Stage 2 may only need LOD 200. By Stage 4, it requires LOD 350. This matrix needs to be explicit and signed off by the client before design work starts.

5. Collaboration and File Protocols

Defines the Common Data Environment platform, file naming convention (referencing BS EN ISO 19650-2 or AIA G202 as appropriate), model federation strategy and coordination meeting cadence. This section governs how information flows between disciplines. It should be finalized before any model files are exchanged.

How to Create a BIM Execution Plan: Step by Step

A BIM Execution Plan is only useful if it reflects how your project will actually run. Generic templates copied from previous projects create the illusion of governance without the substance.

Step 1: Review the EIR

Before writing anything, read the Employer's Information Requirements in full. The EIR defines the client's expected BIM deliverables, preferred CDE platform, Level of Information Need at each project stage, and handover format. The BEP is your formal response to those requirements. If you haven't read the EIR carefully, your BEP is guessing. Pay special attention to any software or IFC schema restrictions the client specifies. These affect every discipline on the project.

Step 2: Identify BIM Uses

Select the BIM Uses relevant to the project from the BIM Forum Use Library. Align your selections with actual project goals, team capability, and what is contractually required. Don't list every possible use. Be selective. BIM Uses you cannot realistically deliver create contractual liability and erode client trust when they go unmet.

Step 3: Define Roles

Assign the BIM Manager and Information Manager roles before design work begins. These are not interchangeable. The BIM Manager owns the technical standards and model quality. The Information Manager owns the CDE, naming conventions, and document control. Document each discipline's model authoring responsibilities in a model matrix. If a sub-consultant is responsible for a particular building system, that needs to be written down and agreed.

Step 4: Set the LOD Matrix

Specify the Level of Development or Level of Information Need required for each building system at each project milestone. Reference AIA G202 for US projects, the BIM Forum LOD Specification for detailed guidance, or ISO 19650 Part 2 for international and UK work. Vague language like "models should be sufficiently detailed" is NOT enforceable. Specify LOD 200 at concept, LOD 350 at construction documentation, and so on.

Step 5: Establish Collaboration Protocols

Document the CDE platform, folder structure, file naming convention, model audit frequency, and clash detection workflow. Specify who runs coordination meetings, how often federated models are issued, and what the process is for flagging and resolving clashes. Get sign-off from all discipline leads before Stage 2 begins.

The Execution Gap: Why BEPs Fail at the Detailing Stage

Most BEPs are reasonably effective at the macro level; they assign roles, define coordination workflows, and specify LOD milestones. The gap appears when production begins. A BEP will define that wall assemblies must reach LOD 300 by Stage 3. What it rarely defines is how construction details get produced, from which sources, to which drawing standards, and by whom. Those decisions get made individually by each architect or engineer on the team, often inconsistently.

Reaching LOD 300 in the model does not mean your construction documents are ready. Significant 2D detail embellishment is still required—at every stage: junction conditions, thermal bridging details, waterproofing callouts, structural connections. The model tells you the geometry. The details tell you how to build it. These are different things, and BEPs rarely address the latter.

The knowledge retrieval problem

A BIM Manager writes detailing standards into the BEP. Architects agree with them. Then, under deadline pressure, an architect needs a parapet detail and spends an hour redrawing from scratch because the firm's previous approved version is buried inside a five-year-old Revit project nobody remembers. The standard existed. It just was not accessible.

BIM Execution Plan Templates and Resources

No BEP needs to be written from scratch. Here's a look at the most widely used standards and templates. Pick the one that matches your project type and contractual framework:

NIBS BEP Standard v4

The National Institute of Building Sciences publishes the US national standard. Their BEP module includes templates for project goals, BIM uses, information exchanges, and supporting infrastructure. Start here for US public projects.

Penn State BEP Guide

Penn State's Computer Integrated Construction program offers free BEP templates (version 2.2). Widely used in US academic and public sector work. Version 3 draft is available for review—includes updated LOD guidance.

AIA G202

The American Institute of Architects' BIM Protocol Exhibit. This is a contractual document you attach to your owner-architect agreement. It defines BEP requirements, LOD standards, and model authoring protocols. Not a full BEP, but the legal framework that makes your BEP enforceable.

ISO 19650

For UK and international projects, follow ISO 19650 Part 2. It defines the Employer's Information Requirements and the pre- and post-contract BEP structure. Mandatory for many public projects outside the US.

The PiAxis Advantage: Turning Your BEP from Theory into Reality

Writing a BEP is the relatively easy part. Enforcing it through hundreds of production hours across a large team is much harder. Most BEPs include a section on detailing standards, drawing conventions, preferred assembly details, and annotation formats. But a document sitting in a shared drive does not stop an architect from redrawing a roof junction from memory because they cannot find the approved version.

PiAxis helps with that by making the firm's own detail library searchable and instantly accessible inside Revit. The platform indexes a firm's entire project history—past Revit files, existing detail libraries, completed CDs—and turns that archive into a searchable knowledge base. Architects can search in plain English ("typical parapet with metal coping" or "window jamb brick cavity wall") and retrieve details from past projects in seconds, directly within their Revit environment. No folder navigation. No searching by file name. No guesswork.

Because the library is built from the firm's own vetted work, the details it surfaces already align with the firm's documentation standards, which are, in turn, the standards defined in the BEP. When the same verified detail is available to every architect on the team—whether they are a senior associate or a recent hire—the project naturally converges on a consistent standard.

BIM Execution Plan Checklist for Project Managers

A BEP without a clear implementation process is just a document. Use this checklist to make sure the right decisions are made at the right time before award and after it.

Pre-Award Checklist

This stage is about due diligence. Before submitting a tender, you need to confirm that your team can deliver what the client is asking for and that the BEP you submit reflects that honestly:

• EIR reviewed in full and all deliverable requirements documented
• Relevant BIM Uses identified and scoped against project type and team capability
• Team BIM software capability assessed against project requirements
• CDE platform identified and accessibility confirmed for all parties
• Preliminary LOD matrix drafted for each major building system at each tender milestone
• Information delivery schedule drafted, mapping what is delivered, by whom, and at which project stage
• COBie or asset data requirements identified and modelling responsibilities assigned accordingly
• BIM fee and resource requirements reviewed to confirm adequate allocation for integration tasks
• Pre-contract BEP reviewed and signed off by the BIM Manager before tender submission
• Potential coordination risks flagged and mitigation strategies included in the pre-contract BEP

Post-Award Checklist

Once the contract is awarded, the pre-contract BEP becomes the working document. This stage is about converting commitments into operational reality:

• BEP finalised, version-controlled, and distributed to all appointed parties
• Roles and responsibilities formally signed off by each discipline lead
• LOD matrix reviewed and approved by the client or their representative
• CDE platform set up, access tested, and naming convention agreed by all parties
• IFC export test completed by each discipline within the first two weeks, validated against agreed schema
• Clash detection workflow documented and first coordination meeting date scheduled
• Model federation process confirmed: who compiles the federated model, on what schedule, and using which platform
• First model audit date and frequency confirmed in the BEP
• Training needs identified for any team member unfamiliar with the CDE or required BIM workflows
• BEP review dates tied to RIBA stage gates or equivalent project milestones
• Communication protocol established for flagging non-compliance: who raises it, who resolves it, and within what timeframe

BIM Execution Plan Best Practices

Keep it project-specific

A BEP template is a starting point, not a finished document. Copying a BEP from a previous project without tailoring it to the current team, client, CDE platform, and LOD expectations is one of the most common and most costly mistakes. Each project has a different combination of team capabilities, procurement requirements, and coordination challenges.

Engage all disciplines early

The coordination protocol section of a BEP is most effective when the structural, MEP, and civil leads contribute to it directly before Stage 2 design work begins. If only the lead architect writes it, gaps appear when it hits the reality of multi-discipline model federation.

Make standards measurable

Avoid vague language. "High quality models" tells nobody anything. "All wall assemblies to reach LOD 300 by the end of RIBA Stage 3, modelled in accordance with the BIM Forum LOD Specification 2020, with file naming per [CDE naming convention]" is enforceable. Define specific LOD levels, file naming conventions, and audit frequencies that can be checked objectively.

Version control as standard

Treat the BEP like a design document. Version it at each project stage—RIBA 2, 3, 4, or equivalent. Track changes between versions. Distribute each revision formally to all team leads. A BEP with no version history is not a reliable contractual reference.

Stage gate reviews

Schedule a BEP review at each major project milestone. Scope changes, team changes, and client feedback all have implications for the BEP's coordination protocols, LOD targets and responsibility assignments. An unreviewed BEP quickly diverges from the project's actual delivery approach.

Lessons learned at project close

At project close, document what worked and what did not. Which BIM Uses were effectively delivered? Where did the LOD matrix prove unrealistic? Which coordination protocols broke down under production pressure? This information feeds directly into the firm's standard BEP template reducing the chance of repeating the same mistakes on the next project.

Conclusion: Streamlining Documentation with a Solid Foundation

A well-constructed BEP is the difference between coordinated BIM delivery and a fragmented model handover. It sets the standard every team member works to: defining what gets modelled, to what level of detail, by whom, and when. Without it, those decisions are made individually, inconsistently, and usually too late to avoid rework.

But a BEP alone isn't enough. If teams lack the tools or capability to apply it in daily production, its value breaks down. Detailing standards, coordination workflows, and data quality all depend on execution, which is where many BIM efforts struggle.

Successful firms treat the BEP as a living standard. They embed it into workflows, audit compliance regularly, and update it as projects evolve, maintaining discipline across every stage to consistently achieve BIM outcomes.