What Is a BIM Execution Plan? A Complete Guide for Construction Projects

A BIM Execution Plan (BEP) is a project document that sets out how a team will create, exchange, and manage information in BIM. It covers who is responsible for what, which standards and software apply, what gets delivered and when, and how models are coordinated.

Teams prepare it before or at the start of BIM work so that everyone models, shares, and reviews information the same way. I

n North America, you will also see it called a BIM Project Execution Plan.

What Is a BIM Execution Plan?

A BIM Execution Plan is the agreed framework for how BIM will be carried out on a specific project. It turns general intentions (“we will use BIM”) into specific, checkable decisions: which models exist, who authors them, how they are named, when they are exchanged, and how problems are resolved.

Here is a short BIM execution plan definition:

A BIM Execution Plan (BEP) is a project document that defines how a team will implement BIM, including roles, processes, information requirements, deliverables, software, standards, and coordination procedures, so all stakeholders work to the same expectations.

In practice, a BEP usually covers:

Project goals and the intended BIM uses
Roles and responsibilities
Information requirements and deliverables
Software, file formats, and data environment
Modeling and naming standards
Coordination, review, and approval procedures

It is not a design document. It does not say what the building looks like. It says how the team will manage the digital information that describes it.

What Does BEP Mean in BIM?

BEP stands for BIM Execution Plan. The three words each carry weight:

BIM is building information modeling: the process of creating and managing information about a built asset, usually through coordinated 3D models and associated data.
Execution means the plan is about doing the work, not just stating aspirations.
Plan means it is a documented, shared agreement that the team can follow and audit.

If you are wondering what BEP is in BIM when you see it in a specification or RFP, it is almost always this document. Some regions and contracts use different wording. In the US, “BIM Project Execution Plan” is common, partly because of the widely used Penn State BIM Project Execution Planning Guide. In the UK and other markets following ISO 19650, you will see “pre-appointment” and “post-appointment” BIM execution plans. The BEP meaning in BIM is consistent across these: a plan for how BIM will be delivered on this project.

Why Is a BIM Execution Plan Important?

Most BIM problems on projects are not software problems. They come from unclear expectations: two consultants assume different model origins, a contractor expects data the designer never planned to include, or nobody knows who owns issue resolution. A BEP addresses this by putting agreements in writing before modeling begins.

Practical benefits include:

Clear responsibilities. Each party knows which models and deliverables it owns.
Defined information requirements. The team agrees on what data and level of detail are needed and for what purpose.
Standardized workflows. Everyone uses the same naming, coordination, and exchange procedures.
Better coordination. A defined schedule and process for federated model reviews.
Fewer disputes over deliverables. Formats, dates, and acceptance criteria are stated up front.
Controlled model exchanges. Everyone knows what is shared, at what status, and through which platform.
Documented review and approval steps. Nobody has to guess who signs off on what.

A BEP does not guarantee a coordinated project or eliminate clashes. It creates the conditions in which good coordination is easier, and it gives the team something concrete to measure against when things drift.

What Is Included in a BIM Execution Plan?

Content varies by project size, contract, and owner requirements. A small renovation may need a short document, while a hospital or airport program may need a detailed, multi-part plan. The components below are the ones you will see most often.

1. Project Information and BIM Goals

This section gives the project overview (location, type, phase, delivery method), lists the key stakeholders with contacts, and states the BIM objectives. Good objectives are specific, such as “coordinate structural and MEP systems before construction documents issue” or “deliver a structured asset model for facility operations.” Vague goals produce vague plans.

2. Roles and Responsibilities

The BEP names who does what. Typical roles include:

BIM Manager: owns the BEP, standards, and overall BIM process
BIM Coordinator: runs model federation, clash checks, and issue tracking
Architects and engineers: author discipline models
Contractors and subcontractors: develop fabrication or trade models, and consume design models
Model authors: the individuals responsible for specific models

Titles and reporting lines differ by firm and project. Some projects have a single BIM manager; others have one per organization plus an overall coordinator. The plan should reflect what is actually staffed.

3. BIM Uses

BIM uses are the specific purposes for which models will be used. Examples include design coordination, clash detection, quantity takeoff, 4D planning (schedule-linked models), 5D estimating (cost-linked models), visualization, facility management handover, and record model documentation. Not every project uses all of them. Selecting only the uses that add value keeps the plan realistic, and the chosen uses drive model detail and data needs elsewhere in the document.

4. Model Requirements and Deliverables

This section defines what will be modeled and delivered:

Required disciplines and model breakdown
Model development expectations (often expressed as level of development, level of information need, or similar, depending on the standard in use)
Native and exchange formats
Exchange points and milestones
Deliverable schedule, with responsible parties

Being specific here matters. “Architectural model” is not enough; state what elements are modeled, to what level of detail, by which milestone.

5. BIM Software and Technology

The BEP lists authoring tools, coordination platforms, the common data environment (CDE), file formats, and versions. Examples might include Revit for authoring, Navisworks or another platform for coordination, and IFC for open exchange. Software choices depend on project requirements and firm workflows, and no single platform is right for every team. What matters is that versions are aligned and interoperability has been tested rather than assumed. For software-specific behavior such as export settings, consult the vendor’s own documentation, for example, Autodesk’s help resources.

6. BIM Standards and Naming Conventions

This is where consistency is defined:

File and model naming
Folder structure
Model organization and worksets or equivalent
Category, layer, or parameter conventions where applicable
Shared coordinates and project origin
Units and tolerances

Small inconsistencies here, such as models with different origins, create hours of rework later. Teams that need to structure documents across disciplines often pair the BEP with broader BIM services and drawing standards.

7. Coordination and Clash Detection Procedures

The plan describes how models will be federated, how often coordination meetings occur, which disciplines are checked against each other, how issues are logged and assigned, and how resolution is confirmed. It should name who owns coordination and set response expectations. Review frequency is normally tied to design and construction milestones.

8. Information Exchange and Common Data Environment

This section covers how information moves between parties: which CDE is used, who has access, how files are marked with status and revision, and how review and approval work. Under ISO 19650, a CDE is a structured process and workspace for collecting, managing, and sharing information, typically using states such as work in progress, shared, published, and archived. Whether a project must follow ISO 19650 depends on the contract and client requirements. It is a framework, not a universal mandate.

Types of BIM Execution Plans

Terminology varies by contract, region, and organization, so treat these as commonly encountered concepts rather than a fixed system.

Pre-contract BEP: prepared during procurement or tender. A bidding team uses it to show how it would deliver the client’s information requirements, including proposed team, capabilities, and approach. It is typically less detailed.
Post-contract BEP: prepared after appointment. It confirms and expands the pre-contract plan into a detailed working document, with confirmed team members, schedules, and procedures.

The pre- and post-appointment language comes from ISO 19650. In US projects, especially private-sector work, the plan is often prepared once, after award, and may be called a BIM Project Execution Plan. Check what your contract or owner requires.

When Should a BIM Execution Plan Be Created?

Ideally before BIM work starts. In practice, timing depends on how the project is procured:

Tender or procurement: where the client requests one, a preliminary plan shows the bidder’s approach.
Appointment or contract stage: the plan is confirmed and detailed once the team is in place.
Kickoff: the team agrees on the final version before modeling begins.
During the project: the plan is updated when scope, team members, software, or requirements change.

A BEP is a living document. A plan written once and filed away will drift from reality, and teams will stop referring to it. Use version control and record what changed and why.

Who Creates a BIM Execution Plan?

There is no single answer. It depends on procurement route, contract terms, and team structure.

Client or owner: defines information requirements and may issue a template or minimum BEP requirements. Some owners write parts of the plan themselves.
BIM manager: typically writes and maintains the document on behalf of their organization or the project team.
Lead designer: often leads the plan during design phases, particularly on design-led projects.
Main contractor: often takes ownership during construction, especially in design-build or when trade models are central.
Project team: every discipline contributes its own section and agrees to follow the final plan.

On many projects, the plan is a collaboration, with one party coordinating and others reviewing. Teams that lack in-house capacity sometimes bring in specialist support, such as BIM execution planning services, to draft or review the document.

BIM Execution Plan vs BIM Standards vs EIR

These three items are related but not interchangeable. Note that “EIR” has two common expansions: Employer’s Information Requirements (traditional UK usage) and Exchange Information Requirements (the ISO 19650 term). North American owners may use different wording, so check your documents.

	BIM Execution Plan (BEP)	Information Requirements (EIR)	BIM / Project Standards
Purpose	Describes how BIM will be delivered on this project	States what information the client needs and why	Sets consistent rules for modeling, naming, and data
Typically defined by	Project team, led by BIM manager, lead designer, or contractor	Client or appointing party	Client, firm, or industry body; may be adopted or adapted by the team
When used	Tender through project delivery; updated during the project	Issued at procurement or appointment	Referenced throughout, often before the BEP is written
What it contains	Roles, uses, deliverables, software, workflows, coordination	Deliverables, formats, data needs, milestones, security	Naming conventions, model structure, units, parameters, classification

Put simply: the EIR says what the client needs, the standards say what rules to follow, and the BEP says how this team will deliver against both. Many BEPs reference or embed the relevant standards rather than rewriting them.

Example of a BIM Execution Plan Workflow

The following is an illustrative example for a hypothetical mid-size commercial office project. It is not a universal workflow, and the sequence will change with contract type and owner requirements.

Client establishes information requirements. The owner states what models and data they need at handover, including any asset data for operations.
Project team identifies BIM uses. The team selects design coordination, quantity takeoff, and record model handover, and decides 4D planning is not needed.
Responsibilities are assigned. Each discipline names a model author, and the general contractor’s BIM coordinator is designated to run coordination.
Software and CDE requirements are set. Authoring tools, versions, exchange formats, and the CDE are agreed and tested.
Model standards are defined. Naming, shared coordinates, and model breakdown are documented.
Coordination workflow is established. Weekly federation, agreed clash-check pairings, and an issue log with assigned owners.
Deliverables and exchange dates are defined. Model milestones are tied to design and construction phases.
The team follows and updates the BEP. Changes such as a new subcontractor or updated scope are recorded as revisions.

Common Mistakes in a BIM Execution Plan

Making the BEP too generic. A copied template with the wrong project name is obvious to everyone. Tailor it to actual scope, team, and BIM uses.
Not defining responsibilities. “The team will coordinate” is not an assignment. Name roles and owners.
Missing information exchange requirements. Specify who sends what, in which format, at which status, and when.
Unclear model standards. Ambiguous naming or coordination rules cause avoidable rework. Include examples.
Ignoring coordination procedures. Define meeting frequency, issue tracking, and how resolution is verified.
Not defining deliverables. Vague deliverables lead to disputes at handover.
Not updating the document. Schedule a review at each major milestone.
Requiring more than the project needs. Demands that do not match the project’s scale, budget, or team capability tend to be ignored. Right-size the plan.

How a BIM Execution Plan Supports Construction Coordination

Think of the BEP as the start of a chain:

BEP → BIM standards → modeling → coordination → issue management → deliverables

The BEP sets goals, roles, and procedures. Standards turn those into concrete modeling rules. Teams model to those rules, so files align when they are federated. Coordination reviews then find conflicts, which are logged and assigned through issue management. Resolved and approved information is finally issued as deliverables at agreed milestones.

If an early link is weak, later steps suffer. Unclear standards produce misaligned models, which produce noisy coordination results. The BEP does not replace skilled coordination, but it makes the process consistent and traceable. Where coordinated models feed drawings, it also helps to align with construction documentation workflows.

BIM Execution Plan Checklist

Use this as a starting point and adapt it to your project.

☐ BIM goals
☐ Project stakeholders
☐ Roles and responsibilities
☐ BIM uses
☐ Model requirements
☐ Software
☐ File formats
☐ Naming conventions
☐ CDE
☐ Coordination workflow
☐ Clash detection
☐ Information exchange
☐ Deliverables
☐ Review procedures
☐ Model milestones
☐ Revision procedures

Frequently Asked Questions About BIM Execution Plans

1. What is a BIM execution plan?
A BIM Execution Plan is a project-specific document describing how a team will deliver BIM. It records roles, BIM uses, software, standards, information exchange, coordination procedures, and deliverables. Its aim is to align all parties before modeling begins so that expectations are documented rather than assumed.

2. What is BEP in BIM?
In BIM, BEP refers to the BIM Execution Plan. You will see the abbreviation in RFPs, specifications, and project documents. Some markets also use “BIM Project Execution Plan.” The abbreviation always points to the document that explains how BIM will be carried out on a given project.

3. What does BEP mean in BIM?
BEP means BIM Execution Plan. “Execution” signals that it is about how the work is done, not only what is wanted. The related term EIR states client requirements, while the BEP explains how the delivery team will meet them using specific processes, tools, and responsibilities.

4. What is the purpose of a BIM Execution Plan?
Its purpose is to create shared understanding and a consistent process. It defines who is responsible for what, how models and data are exchanged, what standards apply, and how coordination happens. This reduces ambiguity between stakeholders and gives the team a reference for reviewing progress and resolving disagreements.

5. What should a BIM Execution Plan include?
Typical contents are project information and BIM goals, roles, BIM uses, model requirements and deliverables, software and CDE, naming and modeling standards, coordination and clash detection procedures, and information exchange rules. Include only what the project needs, and be specific enough that someone could follow it without asking the author.

6. Who prepares a BIM Execution Plan?
It varies. Often a BIM manager drafts it, with input from the lead designer, contractor, and disciplines. Clients may supply requirements or templates. On design-led projects, the designer may lead; on design-build projects, the contractor often does. Contract terms and procurement route decide the responsibility.

Final Thoughts

A BIM Execution Plan is the document that turns BIM intentions into an agreed way of working. It matters because it establishes responsibilities, information requirements, and coordination procedures before problems appear. It typically covers goals, roles, BIM uses, model requirements, software and CDE, standards, coordination, and information exchange. Used well and kept current, it gives project teams a consistent, traceable approach to BIM.

If your team needs help preparing or reviewing this documentation, Infallible Studio provides BIM execution planning support for AEC teams across the USA and Canada.