BIM Execution Plan

What is a BIM Execution Plan?

A BIM Execution Plan (BEP) is a written document agreed between a client and the delivery team that specifies how information will be created, structured, exchanged, and verified on a building information modeling project. It answers the practical question: who models what, to what level of detail, in which format, and when do they deliver it?

The BEP is not an optional best-practice guideline, it is the contract that governs BIM execution on multi-party projects. Without it, teams working on the same building often produce incompatible files, duplicate effort, miss deadlines, and lose coordination. The BEP prevents this by establishing a single agreed protocol.

How does the EIR drive the BEP?

The causal chain is straightforward. The client (the appointing party or employer) first publishes an Exchange Information Requirement (EIR) that sets out their information needs for the project. The EIR is the client's brief to the market: it defines what information must be delivered, in which data format, to which level of detail, and by which date.

When teams submit a tender, they respond to the EIR with a pre-appointment BEP that shows how they propose to meet those requirements. This BEP demonstrates the team's capability and intent. After contract award, the team develops a detailed, post-appointment BEP that confirms the exact methods, software, personnel roles, and schedules by which the EIR will be satisfied. The EIR is the demand; the BEP is the answer.

What is the difference between pre-appointment and post-appointment BEP?

This distinction is often the first confusion point for teams new to structured BIM delivery. Two separate BEPs serve different purposes.

The pre-appointment BEP is a marketing and capability document. The post-appointment BEP is the operational rule book. Many projects fail because this distinction is blurred and the pre-appointment version is treated as if it were a binding commitment.

What does a BIM Execution Plan actually contain?

A complete BEP covers the following areas:

• Roles and Responsibilities: Named individuals or organizations for each function. A key role is the Information Manager (sometimes BIM Manager or BIM Coordinator), who oversees file naming, model assembly, quality checks, and coordination. Other roles include discipline leads (architect, structural engineer, MEP engineer, contractor), clash manager, and data steward.
• Model Breakdown: Which discipline produces which model (architectural, structural, mechanical, electrical, plumbing, etc.). How models are federated (assembled together for coordination). Which elements each discipline is responsible for.
• Level of Information Need (LOIN): How detailed each model element must be at each stage (design development, tender, construction, handover, operation). Early phases may show only outlines; later phases include material data, cost, maintenance schedules, and asset information.
• Naming and Classification Conventions: How files are named, numbered, and organized in folders. Which classification system is used (Uniclass, OmniClass, local standards). How elements within models are tagged and categorized so they remain identifiable when models are combined.
• Shared Coordinate System and Project Origin: Where the project sits in national or local coordinates. How local surveys are reconciled. Which discipline sets the master coordinate system; how others align to it.
• Software and Exchange Formats: Which applications are used (Revit, ArchiCAD, Tekla, etc.) and which versions. Which neutral format is used for coordination exchange, typically IFC (Industry Foundation Classes). Whether openBIM principles apply or vendor-locked formats are permitted.
• Common Data Environment (CDE): Which platform hosts shared files (SharePoint, Synchro, Trimble Connect, etc.). How document status is tracked (work in progress, shared for review, published, archived). Who has upload, review, and approval rights. How versions are named and superseded.
• Coordination and Clash Detection: How often models are exchanged (weekly, bi-weekly, monthly). Which software performs clash detection. What clash severity thresholds trigger action. Who owns clash resolution. How BCF (BIM Collaboration Format) issues are logged and tracked.
• Quality and Validation: Who audits models for completeness, standard compliance, and accuracy before submission. What happens if a model fails review. Approval sign-offs required.
• Delivery Milestones: Dates by which each model version must be delivered to the CDE. Handover deliverables (as-built models, asset data, O&M manuals). Post-handover support period.

The BEP also typically references ISO 19650, the international standard that provides the vocabulary and framework for these practices (terms like EIR, CDE, and Level of Information Need are defined in ISO 19650). For IFC-based projects, it may also reference the Model View Definition (MVD) that describes which IFC entities and properties are mandatory.

When is a BIM Execution Plan truly needed?

The honest answer reveals why the BEP exists. A family house designed and built by one architect and one contractor does not need a BEP; verbal agreement and a shared folder suffice. A two-party project (architect and contractor) does not strictly need one either, though writing one imposes useful discipline and provides a fallback if the relationship is contentious.

The BEP becomes genuinely necessary when three or more parties must exchange models: multiple consultants (architect, structural engineer, MEP engineer, quantity surveyor), the contractor, and site teams all working with overlapping model data. In this scenario, incompatible naming, misaligned coordinate systems, and unclear responsibility cause cascading delays and errors. The BEP solves this by establishing one protocol everyone follows.

For a solo architecture practice in Slovakia, the BEP is primarily relevant in two contexts. First, when a client (typically a larger developer or public institution) issues an EIR and requires compliance with their BEP template; the practice must then understand and follow it. Second, when the practice serves as the BIM lead on a project and must coordinate other consultants and contractors; in this case, writing or adapting a BEP is necessary project management. On smaller, owner-led residential projects, the practice may never write a BEP and instead deliver models in agreed formats without the formal planning layer.

What does a BEP require in practice?

The effort varies sharply by project scale. On a small, single-discipline project, a BEP can be a three-page template filled with the essentials. On a large mixed-use development with ten trades, it grows into a 50-page document with appendices, schedules, and linked technical standards.

The BEP must be reviewed and agreed before modeling begins. Changes mid-project (new software, additional consultant, schedule slip) require BEP amendment and re-signature. A BEP that drifts from what the team is actually doing is worse than no BEP at all, because it creates false confidence in coordination. Federated model assembly, BIM coordination, and openBIM delivery all depend on the BEP being current and enforced.