Preconstruction — Design Coordination

BIM Execution Plan (BEP)

The plan that defines how BIM will actually be delivered on a project.

Quick Answer

A BIM execution plan (BEP) is a document that defines how BIM will be delivered on a project — the goals, standards, software, model structure, level of detail, roles, and information exchanges. It aligns everyone on how models are built and shared, and under ISO 19650 it responds to the client's information requirements.

The Full Picture

A BIM execution plan exists because BIM only works if everyone agrees, in advance, how it will be done. Without a shared plan, one firm models to a different level of detail than another, files won't federate cleanly, naming is inconsistent, and coordination stalls. The BEP is the up-front agreement that prevents that chaos.

Mechanically, a BEP documents the project's BIM goals and uses, the software and formats each party will use, the model breakdown and coordinate system, level of development or detail at each stage, file-naming and folder standards, the common data environment, roles and responsibilities, and the schedule of information exchanges. Under the ISO 19650 framework, it's developed in response to the client's exchange information requirements, sometimes as a pre-appointment (bid) BEP and then a confirmed BEP after award.

In practice, the BEP is a living reference the team returns to whenever a modeling or exchange question comes up. Who owns the structural model? What level of detail is expected at design development? How are clashes tracked and exchanged? A good BEP answers these before they become arguments; a neglected one gets written to satisfy a contract and then ignored.

For preconstruction and VDC, the BEP sets the rules of the game for coordination. If models aren't built to a consistent structure and detail, clash detection and coordination drawings suffer. The BEP itself doesn't coordinate anything — it's the governance layer that makes downstream coordination possible.

Real Examples

→Pre-appointment BEP: Bidding a design-build job, a contractor submits a pre-appointment BEP describing how it will meet the owner's information requirements, which becomes part of the selection basis.
→Level of detail schedule: The BEP specifies that structural steel reaches a fabrication-ready level of development by construction documents, so downstream teams know what to expect at each milestone.
→Roles and exchanges: The BEP names the information manager, assigns model ownership per discipline, and schedules the coordination exchanges, so no one is guessing who delivers what, when.

Common Misconceptions

People assume: A BIM execution plan is just a software or IT document.

Actually: The BEP is primarily a process and governance document. It covers goals, roles, responsibilities, level of detail, information exchanges, and standards — how the team works, not just which tools they run. Treating it as an IT checklist misses that its real job is aligning people and deliverables.

People assume: You write the BEP once and you're done.

Actually: A BEP is meant to be a living document. Under ISO 19650 it often starts as a pre-appointment plan and is confirmed and updated after award, then revised as the team, scope, and exchanges evolve. A BEP frozen at kickoff and never revisited quickly drifts from how the project actually runs.

Does MeltPlan Solve This?

Not directly

A BIM execution plan is a governance and process document — it defines how a team will produce, exchange, and manage BIM models across a project. That's a planning and information-management task, not a document-review or takeoff problem, so writing or administering a BEP falls outside MeltPlan's scope. MeltPlan works downstream, reviewing the drawings and specs a project actually produces.

Frequently Asked Questions

What is a BIM execution plan?

It's a document that defines how BIM will be delivered on a project — the goals and uses, software and formats, model structure and coordinate system, level of detail, standards, roles, the common data environment, and the schedule of information exchanges. It aligns everyone on how models are built and shared.

What is included in a BEP?

Typically the project's BIM goals and uses, participating parties and roles, software and exchange formats, model breakdown and coordinate system, level of development at each stage, naming and CDE standards, clash and coordination process, and the information exchange schedule tied to project milestones.

What's the difference between a pre-appointment and a confirmed BEP?

Under ISO 19650, a pre-appointment BEP is submitted during bidding to show how a team would meet the client's information requirements. After award, it's developed into a confirmed BEP that reflects the actual delivery team, resources, and agreed methods.

Who is responsible for the BIM execution plan?

The delivery team — often led by an information manager or BIM manager — develops the BEP in response to the client's exchange information requirements. Each participating discipline contributes its scope, roles, and modeling commitments so the plan reflects the whole team.

Related Terms

BIM CoordinationCombining discipline models and resolving conflicts in 3D before they hit the field.Federated ModelSeparate discipline models linked into one coordinated whole, each author still in control.Clash Detection ReportThe ranked list of geometric conflicts a model check finds, ready for the team to resolve.Design CoordinationMaking every design discipline's work fit in the same physical space before it's built.Design MilestoneThe defined gates where a design set is issued, priced, and checked before it advances.PreconstructionEverything a contractor does to plan, price, and de-risk a project before ground breaks.

More Preconstruction — Design Coordination Terms

Sources

  1. ISO 19650-1:2018 — Information management using building information modelling — Concepts and principles
  2. National BIM Standard-United States (NBIMS-US), National Institute of Building Sciences
MELTPLAN