How to Create a BIM Execution Plan: Step-by-Step Guide

 

A BIM Execution Plan (BEP) is one of the most important documents for successfully implementing Building Information Modeling on an architecture, engineering, construction or infrastructure project. It defines how BIM will be used, who is responsible for each activity, what information must be produced, how models will be exchanged, which standards will be followed, and how quality will be controlled.

A well-prepared BIM Execution Plan helps architects, engineers, contractors, subcontractors, consultants, project managers and owners work from a common BIM strategy.

If you are wondering how to create a BIM Execution Plan, this guide explains the process step by step, including BIM objectives, project roles, LOD/LOIN, CDE, software, modeling standards, coordination, QA/QC, information exchange and final deliverables.

The approach also aligns with the principles of ISO 19650 information management. Under ISO 19650, a pre-appointment BEP can demonstrate the prospective delivery team's capability to meet the information requirements, while the appointed team's BEP becomes a practical delivery tool for managing information throughout the appointment.

What Is a BIM Execution Plan?

A BIM Execution Plan, commonly called a BEP, is a project-specific document that explains how BIM processes, information, people, technology and standards will be managed during a project's lifecycle.

In simple terms:

A BIM Execution Plan is the roadmap for how a project team will plan, produce, coordinate, review, exchange and deliver BIM information.

A BEP normally addresses:

• BIM goals and objectives
• BIM uses
• Project organization
• BIM roles and responsibilities
• Information requirements
• Level of Information Need
• Model development
• BIM software
• Common Data Environment (CDE)
• File naming
• Model federation
• Model coordination
• Clash detection
• Quality assurance and quality control
• Information exchange
• Project deliverables
• BIM meetings
• Model review procedures
• Training and onboarding
• Handover requirements

Autodesk also identifies project stages, LOD, project structure, BIM teams, BIM standards, information exchange and quality control as important components when developing a BEP.

 Why Is a BIM Execution Plan Important?

A BIM project can quickly become difficult to manage when different teams use different modeling methods, software versions, naming conventions, coordinate systems and information standards.

A good BEP establishes one agreed method of working.

The main benefits include:

1. Better BIM coordination

The BEP defines how architectural, structural and MEP models will be coordinated.

2. Clear responsibilities

Every BIM activity can be assigned to an individual, discipline or organization.

3. Consistent modeling

The project team follows common modeling standards instead of creating models independently.

4. Better information management

The BEP establishes how information is created, reviewed, approved, shared and archived.

5. Reduced design errors

A structured coordination and QA/QC process helps identify issues before construction.

6. Improved project communication

The team understands when information will be exchanged and who is responsible for reviewing it.

7. Controlled project deliverables

The BEP clearly identifies what models, drawings, schedules, data and other information must be delivered.

Pre-Appointment BEP vs Post-Appointment BEP

One of the most important concepts to understand is that the BEP can serve different purposes at different stages.

Pre-Appointment BIM Execution Plan

The pre-appointment BEP is generally prepared as part of the tender or appointment process.

Its purpose is to demonstrate that the prospective delivery team has the capability and capacity to meet the project's information requirements.

It may include:

• Proposed BIM methodology
• Team capability
• BIM software
• Proposed workflows
• BIM experience
• Information production methods
• Initial responsibilities
• Proposed coordination process
• BIM risks
• Proposed delivery approach

Post-Appointment BIM Execution Plan

After appointment, the BEP is developed or updated into the team's detailed delivery strategy.

It should establish the agreed:

• BIM processes
• Responsibilities
• Information delivery strategy
• Model production methods
• CDE workflows
• Software environment
• Naming conventions
• Coordination procedures
• QA/QC procedures
• Information exchange requirements
• Deliverables

Therefore, do not simply reuse a generic BEP template without adapting it to the project.

How to Create a BIM Execution Plan Step by Step

Step 1: Understand the Project Requirements

Before writing the BEP, collect and review all project information.

Typical inputs include:

• Employer's Information Requirements (EIR)
• Project brief
• Scope of work
• Contract documents
• Project program
• Design responsibilities
• Client BIM requirements
• Existing BIM standards
• Information requirements
• Required deliverables
• Applicable national standards
• BIM software requirements

Start by answering:

What information does the client actually need?

This question should drive the entire BEP.

If the appointing party has provided an EIR, the BEP should explain how the delivery team will satisfy those requirements.

Step 2: Define BIM Goals and Objectives

The next step is to define exactly why BIM is being used.

Do not write vague objectives such as:

"The project will use BIM to improve efficiency."

Instead, create measurable objectives.

For example:

BIM Objective	Measurement
Improve coordination	Reduce unresolved clashes before construction
Improve drawing accuracy	Coordinate drawings with approved models
Improve information exchange	Use defined CDE workflow
Improve quantity extraction	Generate quantities from approved models
Improve construction planning	Develop 4D construction simulations
Improve handover	Deliver validated asset information

Typical BIM uses may include:

• Design authoring
• 3D coordination
• Clash detection
• Design review
• Quantity takeoff
• 4D planning
• 5D cost management
• Construction sequencing
• Shop drawing production
• As-built modeling
• Asset information
• Facility management
• Digital twin preparation

Step 3: Identify BIM Uses

Create a BIM Use Matrix.

For example:

BIM Use	Design	Construction	Handover
3D Modeling	✓	✓	✓
Design Coordination	✓	✓
Clash Detection	✓	✓
4D Simulation		✓
Quantity Takeoff	✓	✓
Shop Drawings		✓
As-Built Model		✓	✓
Asset Information			✓

This prevents the project team from assuming that every BIM use applies to every project.

Step 4: Define BIM Roles and Responsibilities

Clearly identify who will manage each BIM activity.

Typical BIM roles include:

• Client / Owner
• Project Manager
• BIM Manager
• Information Manager
• BIM Coordinator
• BIM Lead
• Discipline Coordinator
• BIM Modeler
• Architect
• Structural Engineer
• MEP Engineer
• Contractor
• Specialist Subcontractor

Create a responsibility matrix.

Activity	BIM Manager	Architect	Structural	MEP	Contractor
BIM Strategy	A	C	C	C	C
Architectural Model	C	R	C	C
Structural Model	C	C	R	C
MEP Model	C	C	C	R
Clash Detection	A	C	C	C	R
Model QA	A	R	R	R	C
Model Submission	A	R	R	R	R

Use RACI terminology where appropriate:

• R – Responsible
• A – Accountable
• C – Consulted
• I – Informed

Step 5: Establish the BIM Information Requirements

Define what information each discipline must produce.

For example:

Architectural

• Walls
• Doors
• Windows
• Floors
• Ceilings
• Rooms
• Finishes
• Furniture
• Equipment

Structural

• Foundations
• Columns
• Beams
• Slabs
• Walls
• Structural steel
• Reinforcement where required

MEP

• HVAC
• Ductwork
• Chilled water
• Plumbing
• Drainage
• Fire fighting
• Electrical
• ELV
• Equipment

Each element should have the required geometry and information appropriate to its project stage.

Step 6: Define LOD or Level of Information Need

A common mistake is treating LOD as simply "more detailed modeling."

Instead, the BEP should establish the required level of information need for each project stage and deliverable.

Depending on the project's adopted standard, you may use:

• LOD 100
• LOD 200
• LOD 300
• LOD 350
• LOD 400
• LOD 500

Or define requirements using Level of Information Need, as used within ISO 19650-aligned workflows.

For example:

Stage	Architecture	Structure	MEP
Concept	LOD 200	LOD 200	LOD 200
Design	LOD 300	LOD 300	LOD 300
Coordination	LOD 350	LOD 350	LOD 350
Construction	LOD 400	LOD 400	LOD 400
Handover	As-built	As-built	As-built

The important point is to define what information is actually required, rather than adding unnecessary model detail.

Step 7: Establish the Common Data Environment

The Common Data Environment (CDE) is a critical component of an ISO 19650-oriented BIM workflow.

The BEP should identify:

• CDE platform
• Folder structure
• Access permissions
• Approval workflow
• Revision management
• Status codes
• Suitability codes
• File naming
• Information exchange
• Archive procedures

Potential platforms include:

• Autodesk Construction Cloud
• Autodesk Docs
• Bentley ProjectWise
• Trimble Connect
• SharePoint
• Other approved project CDE platforms

The BEP should clearly state where project information will be stored and how information moves through the workflow.

Step 8: Define BIM Software and Technology

Create a software matrix.

Activity	Software
Architectural Modeling	Revit
Structural Modeling	Revit / Tekla
MEP Modeling	Revit
Clash Detection	Navisworks
4D Simulation	Navisworks / Synchro
Cost Management	CostX / approved platform
Scan to BIM	ReCap / point-cloud platform
CDE	Autodesk Construction Cloud
Coordination	ACC Model Coordination

Also define:

• Software versions
• File formats
• Interoperability requirements
• IFC requirements
• Export settings
• Hardware requirements
• Cloud requirements

This prevents different project participants from unknowingly working with incompatible environments.

Step 9: Define Modeling Standards

Your BEP should establish the rules for model creation.

These may include:

Model setup

• Units
• Levels
• Grids
• Coordinates
• Project base point
• Survey point
• Shared coordinates

Modeling

• Naming conventions
• Worksets
• Families
• Templates
• View naming
• Sheet numbering
• Parameters
• Model breakdown

Documentation

• Drawing standards
• Annotation
• Tags
• Line weights
• View templates
• Title blocks
• Schedules

The objective is to make models produced by different teams consistent and interoperable.

Step 10: Establish the BIM Coordination Workflow

Define how multidisciplinary models will be coordinated.

A typical workflow is:

Author → Publish → Aggregate → Check → Clash Detect → Assign → Resolve → Recheck → Approve → Issue

For example:

1. Architecture publishes the latest model.
2. Structure publishes its model.
3. MEP teams publish discipline models.
4. BIM coordinator federates the models.
5. Clash detection is performed.
6. Issues are assigned.
7. Design teams resolve issues.
8. Updated models are published.
9. Clashes are rechecked.
10. Coordinated information is approved.

This process should be clearly documented in the BEP.

Step 11: Define Clash Detection Rules

Not every geometric intersection should automatically be considered a critical clash.

Create a clash matrix.

Discipline	Against	Priority
Architecture	MEP	High
Structure	MEP	Critical
Structure	Architecture	High
HVAC	Electrical	Medium
Plumbing	HVAC	Medium
Fire Fighting	HVAC	High

Define:

• Clash tolerance
• Hard clashes
• Soft clashes
• Clearance clashes
• Workflow
• Responsible person
• Due date
• Issue status
• Approval process

Step 12: Establish BIM QA/QC Procedures

A professional BEP must explain how models will be checked before issue.

Typical QA/QC checks include:

Model checks

• Model coordinates
• Levels and grids
• Naming conventions
• Duplicate elements
• Warnings
• Unused views
• Unused families
• Model performance
• Worksets
• Links

Geometry checks

• Missing elements
• Incorrect geometry
• Incorrect location
• Incorrect elevation
• Interdisciplinary clashes

Information checks

• Required parameters
• Asset information
• Equipment data
• Classification
• COBie requirements where applicable

Documentation checks

• Sheet numbering
• Drawing titles
• View references
• Tags
• Dimensions
• Revision information

The BEP should identify who performs the check, when it occurs and what evidence is recorded.

Step 13: Define Information Exchange and Deliverables

Create a BIM deliverables matrix.

Deliverable	Format	Responsibility	Stage
Architectural Model	RVT	Architect	Design
Structural Model	RVT	Structural Team	Design
MEP Model	RVT	MEP Team	Design
Federated Model	NWD/NWC/IFC	BIM Team	Coordination
Clash Report	HTML/PDF	BIM Coordinator	Coordination
Shop Drawings	PDF/DWG	Contractor	Construction
As-Built Model	RVT/IFC	Contractor	Handover
Asset Data	XLSX/COBie	Contractor	Handover

Also define:

• Submission date
• Revision
• Status
• Approval process
• File naming
• Required metadata

Step 14: Create the BIM Schedule

Connect BIM deliverables with the project program.

For example:

Design Development → Model Production → Internal QA → Coordination → Client Review → Approval → Construction

A BIM schedule can include:

• Model production dates
• Coordination dates
• Clash detection dates
• Review meetings
• Information exchanges
• Construction model dates
• As-built submissions
• Handover

This ensures BIM activities are integrated with the overall project schedule rather than treated as a separate exercise.

Step 15: Define BIM Meetings and Communication

The BEP should establish the meeting structure.

Typical meetings include:

BIM Kick-Off Meeting

Held at project commencement.

Weekly BIM Coordination Meeting

Used to review:

• Model status
• Clashes
• Design changes
• Information requirements
• Upcoming submissions

Model Review Meeting

Used to review significant model issues before formal submission.

BIM Management Meeting

Used for higher-level BIM strategy, risks and performance.

Define:

• Meeting frequency
• Participants
• Agenda
• Minutes
• Action owner
• Due date
• Escalation procedure

Step 16: Define BIM Risks

Include a BIM risk register.

Examples:

Risk	Impact	Mitigation
Incorrect coordinates	High	Establish shared coordinates before modeling
Incompatible software	Medium	Define software versions
Poor model quality	High	Mandatory QA/QC
Late design changes	High	Defined revision workflow
Missing information	High	Information requirement matrix
Large model size	Medium	Model segmentation
Poor user adoption	Medium	BIM training and onboarding

BIM risks should be reviewed throughout the project.

Step 17: Define Training and BIM Onboarding

A project may have participants with different levels of BIM experience.

The BEP should define:

• BIM induction
• CDE training
• Software requirements
• Modeling standards training
• Naming convention training
• Coordination workflow training
• QA/QC training
• Information exchange procedures

This is especially important when multiple subcontractors and specialist consultants are involved.

Step 18: Define Handover Requirements

Do not wait until the end of the project to define handover requirements.

The BEP should establish what information the owner needs.

Potential handover deliverables include:

• As-built BIM models
• Equipment schedules
• Asset information
• O&M information
• COBie data
• Product information
• Maintenance information
• Warranty information
• Space information
• Classification data

The required information should be defined early and progressively developed throughout the project.

Step 19: Review and Approve the BEP

The final BEP should be reviewed by the relevant project stakeholders.

Typical approval participants include:

• Client
• Project manager
• BIM manager
• Lead designer
• Architect
• Structural consultant
• MEP consultant
• Contractor
• Specialist subcontractors

The BEP should not be treated as a static document. If project requirements, software, responsibilities or information requirements change, the BEP should be reviewed and updated.

Autodesk's ISO 19650 learning guidance similarly emphasizes confirming the delivery team's BEP with the appointed parties and documenting proposed information production methods, responsibilities and technology requirements.

Recommended BIM Execution Plan Structure

A practical BEP can be organized as follows:

1. Introduction
2. Project Overview
3. BIM Goals and Objectives
4. BIM Uses
5. Information Requirements
6. BIM Organization
7. Roles and Responsibilities
8. BIM Management Strategy
9. Modeling Strategy
10. Level of Information Need / LOD
11. Project Coordinates
12. Model Breakdown Structure
13. BIM Software and Hardware
14. Common Data Environment
15. File Naming Convention
16. Information Exchange
17. Model Federation
18. Clash Detection
19. BIM Coordination
20. QA/QC
21. Model Review
22. BIM Meetings
23. BIM Schedule
24. BIM Deliverables
25. Risk Management
26. Training and Onboarding
27. Handover Requirements
28. Approval and Change Management
29. Appendices

This structure can be adapted according to the project size, procurement route, client requirements and information management approach.

BIM Execution Plan Checklist

Before issuing your BEP, check the following:

☐ Project BIM objectives defined
☐ BIM uses identified
☐ EIR reviewed
☐ Information requirements identified
☐ BIM roles assigned
☐ RACI matrix prepared
☐ LOD/LOIN defined
☐ Model breakdown established
☐ Coordinate system defined
☐ CDE identified
☐ File naming convention established
☐ Software versions defined
☐ Data exchange formats defined
☐ Model federation workflow established
☐ Clash detection process defined
☐ QA/QC process established
☐ BIM meetings scheduled
☐ BIM deliverables identified
☐ BIM schedule prepared
☐ BIM risks identified
☐ Training requirements identified
☐ Handover requirements established
☐ BEP review and approval completed

Common Mistakes When Creating a BIM Execution Plan

Mistake 1: Using a generic template

A BEP must be project-specific.

Mistake 2: Focusing only on software

BIM is not simply about Revit, Navisworks or another software platform. It is primarily about information management and project processes.

Mistake 3: Not defining responsibilities

If nobody owns a BIM activity, it is unlikely to be completed consistently.

Mistake 4: Defining LOD without information requirements

A highly detailed model can still be a poor BIM deliverable if the required information is missing.

Mistake 5: Ignoring the CDE

Poor information management can create duplicate, outdated or incorrectly approved project information.

Mistake 6: Not defining QA/QC

A model should not automatically be considered correct simply because it was produced in BIM software.

Mistake 7: Creating the BEP once and forgetting it

The BEP should evolve as project requirements and delivery conditions change.

Final Thoughts

A BIM Execution Plan is much more than a BIM document template. It is the project's practical roadmap for managing people, processes, technology and information.

A successful BEP connects the client's information requirements with the delivery team's actual working methods.

The most effective approach is:

Understand requirements → Define BIM objectives → Identify BIM uses → Assign responsibilities → Define information requirements → Establish LOD/LOIN → Set up the CDE → Define modeling standards → Establish coordination → Implement QA/QC → Define deliverables → Plan handover → Review and update.

For projects following an ISO 19650 approach, the BEP should be developed as part of a broader information management process rather than treated as an isolated document. UK BIM Framework guidance specifically positions the BEP alongside other information management resources and distinguishes its pre-appointment and delivery purposes.

If you are an architect, engineer, contractor, BIM manager, BIM coordinator, project manager, PMC or owner, learning to develop a project-specific BEP is an important BIM management skill.

A properly prepared BIM Execution Plan can help your project team establish clear responsibilities, consistent modeling standards, coordinated information, controlled deliverables and a repeatable BIM workflow.

Need help developing a project-specific BIM Execution Plan? Lupiter Technologies provides BIM consulting, BIM implementation, BIM coordination and BIM documentation support for AEC projects.

Frequently Asked Questions About BIM Execution Plans

What is a BIM Execution Plan?

A BIM Execution Plan is a project-specific document that defines how BIM will be implemented, managed and delivered throughout a project.

Who prepares a BIM Execution Plan?

The responsible party depends on the project's procurement and information management arrangements. A prospective lead appointed party may prepare a pre-appointment BEP, while the appointed delivery team develops the delivery BEP.

Is a BEP required for every BIM project?

The requirement depends on the project contract and information requirements. Where ISO 19650 is being applied, the BEP has defined roles within the information management process.

What should a BIM Execution Plan contain?

A BEP commonly contains BIM objectives, BIM uses, roles, responsibilities, information requirements, LOD/LOIN, modeling standards, CDE procedures, software, coordination, QA/QC, deliverables, schedules, risks and handover requirements.

What is the difference between EIR and BEP?

The EIR establishes the information requirements from the appointing party, while the BEP explains how the delivery team will meet those requirements.

What is the difference between LOD and LOIN?

LOD is commonly used to describe the development/detail of model elements, while Level of Information Need provides a broader approach to specifying the amount and type of information required for a particular purpose and project stage.

Can a BIM Execution Plan be used for construction projects?

Yes. A BEP can define BIM processes for design, coordination, construction, shop drawings, 4D planning, 5D workflows, as-built information and handover.

Conclusion

Creating a BIM Execution Plan should not begin with copying a template. It should begin by understanding what information the project needs, why that information is required, who will produce it, when it will be delivered and how it will be checked and exchanged.

When these requirements are converted into clear BIM processes, responsibilities, standards, workflows and deliverables, the BEP becomes a practical management tool rather than just another project document.

A strong BIM Execution Plan ultimately helps the project team move from “using BIM software” to actually implementing BIM as a structured project information management process.

---