BIM Goals & Uses
Define project-specific BIM objectives and intended digital uses.
BEP • BIM GOVERNANCE • INFORMATION DELIVERY
BIM Execution Plan & BEP Services
Define how BIM will actually be delivered on the project — including BIM uses, team responsibilities, model structure, LOD and LOI, coordination procedures, information exchanges, QA requirements and digital handover expectations.
Define
BIM Uses & Scope
Assign
Responsibilities
Control
Exchanges & QA
Deliver
Required Information
BIM Execution Planning
A BIM Requirement Needs an Execution Framework
A project may require BIM, but that requirement alone does not define how different teams should work together.
The BIM Execution Plan converts high-level digital requirements into project-specific procedures for modeling, coordination, information exchange, quality control and delivery.
It provides the practical operating framework that connects BIM expectations with day-to-day project execution.
Requirements → Responsibilities → Workflow → Delivery
BIM execution structured
around project-specific
information requirements.
BEP Development Capabilities
Define the Rules for Project BIM Delivery
The level of detail within a BEP should match project complexity, procurement strategy, BIM requirements and delivery stage.
Team Responsibilities
Clarify responsibilities for model creation, review, coordination and information delivery.
Model Breakdown Strategy
Define project models by discipline, building, zone, package or delivery need.
LOD / LOI Requirements
Establish required geometry and information development at defined project stages.
Modeling Standards
Define naming, structure, reference and model conventions.
Coordinate Strategy
Establish project origin, reference and federation expectations.
Coordination & Clash Protocol
Define federation, test structure, issue assignment and closure workflow.
Information Exchange Planning
Define required model and data exchanges at project milestones.
QA & Delivery Gates
Establish checks required before information is issued or accepted.
Core BEP Structure
Typical Sections Within a BIM Execution Plan
SECTION 01
Project Information
Project scope,
participants
and digital-delivery context.
SECTION 02
BIM Goals
Project-defined
BIM objectives
and expected outcomes.
SECTION 03
BIM Uses
Coordination,
documentation,
sequencing,
quantities,
handover
or other agreed uses.
SECTION 04
Project Roles
BIM-related
project responsibilities
and contacts.
SECTION 05
Model Structure
Discipline,
building,
zone
and package organization.
SECTION 06
Information Requirements
Required model
geometry,
data
and information content.
SECTION 07
Coordination Process
Federation,
issue review,
meetings
and clash workflow.
SECTION 08
Delivery Requirements
Required files,
milestones,
review gates
and final handover.
Model Responsibility Matrix
Define Who Is Responsible for Which Information
Coordination becomes difficult when multiple teams assume someone else owns a model element, interface or decision.
Architecture
Define responsibility
for architectural
model information
and interfaces.
Structure
Define responsibility
for structural
model information
and coordination.
Mechanical
Define responsibility
for HVAC equipment,
ductwork
and relevant systems.
Electrical
Define responsibility
for electrical
equipment,
containment
and system information.
Plumbing
Define responsibility
for plumbing
model information
and related interfaces.
Fire Protection
Define responsibility
for project-specific
fire-protection
model information.
Specialist Systems
Clarify ownership
for vendor,
specialist
or delegated-model content.
Coordination
Define who
federates models,
manages issues
and verifies closure.
Execution Control
A Detailed BEP Is Not Useful If the Project Team Does Not Follow It
The purpose of a BEP is not to create a long document that sits unused.
It should create practical rules that project teams can apply consistently throughout delivery.
Requirements Must Be Clear
Teams need to understand
what information
must be produced.
Responsibilities Must Be Assigned
Model ownership
and issue ownership
should not remain ambiguous.
Exchanges Must Be Controlled
Model exchanges
should follow
defined milestones
and revision controls.
QA Must Be Repeatable
Review criteria
should be clear enough
for consistent application.
BEP Development Workflow
From Project Requirements to an Executable BIM Plan
01
Review
Review project BIM requirements, scopes and delivery objectives.
02
Define
Establish BIM uses, deliverables, development levels and project roles.
03
Structure
Define models, naming, coordinates and information exchanges.
04
Coordinate
Establish federation, clash review and issue-management procedures.
05
Validate
Define QA gates, review criteria and delivery checks.
06
Maintain
Update the BEP when approved project requirements materially change.
Model Standards
Common Rules Reduce Avoidable Model Friction
File Naming
Define naming conventions for models, drawings, exports and other digital deliverables.
Model Naming
Establish consistent discipline, building, zone or package identifiers.
Views & Sheets
Define project-specific view and sheet naming where required.
Model Coordinates
Define origin, shared references and federation alignment.
Levels & Grids
Establish project expectations for reference geometry used across disciplines.
Required Parameters
Define data fields required for project-specific information uses.
Model Segmentation
Define when project models should be divided by building, zone, level or package.
Exchange Formats
Define required native, federated or project-defined exchange outputs.
Information Exchange Planning
Define What Is Exchanged, When and for What Purpose
EXCHANGE 01
Design Review
Models issued
for defined
design-review milestones.
EXCHANGE 02
Coordination
Discipline models
provided for
federation and
coordination review.
EXCHANGE 03
Preconstruction
Project information
exchanged for
constructability
and delivery review.
EXCHANGE 04
Shop Drawing Support
Approved project information
used for
downstream documentation.
EXCHANGE 05
Construction Updates
Revised model information
issued at
defined project stages.
EXCHANGE 06
As-Built Updates
Record information
exchanged during
closeout workflows.
EXCHANGE 07
Handover
Final project-defined
models and information
prepared for delivery.
EXCHANGE 08
Operations
Required asset
or facility information
transferred where included.
Coordination & Clash Protocol
Define How Coordination Issues Move to Closure
Model Federation
Define which models
are combined
and how often
coordination models are updated.
Clash Matrix
Define which
discipline interfaces
require systematic
clash testing.
Clash Criteria
Establish relevant
hard,
clearance
or project-defined checks.
Issue Classification
Group issues
by discipline,
type,
priority
or project zone.
Issue Assignment
Route coordination issues
to the responsible
project team.
Closure Verification
Define how
resolved issues
are rechecked
before closure.
Coordination Meetings
Define frequency,
participants,
inputs
and expected outputs.
Model Release
Define the conditions
required before
coordinated information
progresses downstream.
Revision Management
Keep coordination
decisions aligned
with current
project revisions.
Common Data Environment Workflow
Project Information Needs Clear Status & Revision Control
The BEP can define how files and models move through the project's chosen information environment.
STATE 01
Work in Progress
Information under
discipline development
and internal review.
STATE 02
Shared
Information issued
for project-defined
coordination
or review use.
STATE 03
Published / Issued
Information released
through the approved
project workflow.
STATE 04
Archived
Superseded or
historical information
retained according
to project requirements.
BEP Inputs & Outputs
Project Requirements In. Executable BIM Framework Out.
Typical Inputs
- Client BIM requirements
- Project scope information
- Consultant scopes
- Contractor scopes
- Required BIM uses
- Delivery milestones
- Existing BIM standards
- Model requirements
- Coordination requirements
- Digital handover requirements
Typical Outputs
- Project BIM Execution Plan
- BIM roles and responsibility matrix
- BIM use definition
- Model breakdown structure
- LOD / LOI requirements
- Naming conventions
- Coordinate strategy
- Information exchange requirements
- Coordination / clash protocol
- QA and delivery requirements
BEP QA & Delivery Gates
Define What Must Be Checked Before Information Is Issued
A project team should not need to invent acceptance criteria each time a model is delivered.
The BEP can establish repeatable checks for model readiness, coordination and information delivery.
File Naming
Check models
and files
against defined
naming rules.
Model Coordinates
Confirm model
alignment before
federation or exchange.
LOD / LOI
Review model
development against
project-stage requirements.
Model Health
Review project-defined
technical model
quality requirements.
Required Information
Confirm relevant
parameters
and information
are available.
Coordination Status
Confirm unresolved
coordination issues
are visible
before release.
Revision Status
Confirm deliverables
reflect the intended
project revision.
Delivery Completeness
Confirm required
files and
project-defined outputs
are present.
BEP Across the Project Lifecycle
Execution Requirements Can Evolve with the Project
Project Mobilization
Establish BIM uses,
responsibilities,
standards
and initial delivery procedures.
Design
Control discipline
model development,
exchanges
and design coordination.
Preconstruction
Expand federation,
constructability
and coordination workflows.
Construction
Manage project-defined
coordination,
updates,
revisions
and documentation exchanges.
Closeout
Define record-model,
as-built
and final
digital deliverables.
Handover
Prepare project-defined
model,
drawing
and asset information
for downstream use.
Scope & Authority
A BEP Organizes BIM Delivery — It Does Not Transfer Professional Responsibility
The BIM Execution Plan can define workflows, information requirements, responsibilities and coordination processes.
It does not independently change contractual design authority, professional engineering responsibility, code obligations or formal project approvals unless those matters are addressed through the appropriate contractual process.
BIM Responsibility
Define who creates,
coordinates
and delivers information.
Design Responsibility
Keep professional
design authority
with the responsible
project party.
Contractual Requirements
BEP procedures
should align with
applicable project agreements.
Change Control
Material changes
to execution requirements
should follow
the project's
agreed approval workflow.
Related Services
Connect the BEP to Actual Project Delivery
Frequently Asked Questions
BIM Execution Plan FAQs
What is a BIM Execution Plan?
A BIM Execution Plan defines how project BIM requirements will be implemented through modeling, coordination, information exchange, quality control and digital delivery procedures.
When should a BEP be prepared?
BIM execution planning is most useful when developed early enough to guide project mobilization, modeling and coordination workflows. It may then be updated as approved project requirements evolve.
Can a BEP define LOD and LOI requirements?
Yes. The plan can define project-stage requirements for model geometry and project information based on intended BIM uses.
Can a BIM Execution Plan include a clash matrix?
Yes. The BEP can define required discipline interfaces, clash-testing expectations, review responsibilities and issue-closure procedures.
Can a BEP define Common Data Environment workflows?
Yes. Project-specific file states, revision control, information exchange and approval workflows can be documented for the selected environment.
Does a BEP replace project contracts?
No. A BEP supports project BIM execution and information management. Contractual authority, professional responsibility and formal approvals remain subject to the project's agreements and responsible parties.
BIM Execution Planning
Need a Project-Specific BIM Execution Plan?
Share your BIM requirements, project team structure, required BIM uses, coordination expectations and digital delivery milestones.