What is a BIM Execution Plan? A Practical Guide for Contractors (2026)

Inclusive language

The short answer: A BIM Execution Plan (BEP) is a formal document that outlines how Building Information Modeling will be used on a specific project. It details what BIM tasks will be done, who’s responsible for which models and results, what level of detail is expected in each phase, along with the software and file formats that’ll be used. Plus, it covers how models will be shared and kept version-controlled, and how clashes will be detected and handled. In the UK, BEPs follow ISO 19650 and fit the client’s info exchange needs. In the US, they tend to be made specifically for each project by a BIM Manager or main consultant. Plus, there are two kinds – one’s made before a contract, during bidding, and another comes later with all the detailed project specifics.

Every construction project using BIM requires a BIM Execution Plan. Without it, teams independently choose software, naming, structure, and LOD details, leading to conflicts that cause coordination issues. These problems waste time and money fixing things later.

A BIM Execution Plan prevents this. It’s the agreed-upon rulebook for how BIM will run on a certain project. Written before anyone starts modeling, all parties agree on it. Then, they reference it throughout the whole project.

This guide spells out what a BIM Execution Plan is and what it includes. It also looks at the difference between pre-contract and post-contract BEPs. Plus, it covers how ISO 19650 lays out BEP needs in the UK. Also, it tells contractors in the USA and UK what to do before making one.

What is a BIM Execution Plan (BEP)?

A BIM Execution Plan, or BEP for short, sometimes called BIMxP or BIM Delivery Plan, is a formal document. It outlines how BIM Modeling Services are implemented, managed, and reviewed during a construction project.

This tackles the questions that going untouched cause coordination failures.

• What will BIM be used for on this project: clash detection, 4D scheduling, quantity extraction, facility management?
• Who is responsible for producing each discipline model and at what Level of Detail?
• Which software and file formats will be used, and are they compatible across the full project team?
• How will models be shared, approved, and version-controlled?
• When will clash detection run, who manages it, and how are resolutions tracked?
• What are the naming conventions and layer standards that all teams must follow?

The BEP isn’t a BIM model, nor is it a schedule or cost plan. It’s the governance document that lets coordinated BIM delivery happen. It aligns all project participants on the same standards and expectations before any modeling even starts.

Why Does a BIM Execution Plan Matter?

The most common reason BIM projects fail isn’t due to software; it’s because of process issues. Teams often work in isolation, using different LOD assumptions, naming conventions, and file structures. When models are federated for clash detection, they do not align. Resolving these alignment problems costs time that the project does not have.

A well-written BEP prevents this by establishing shared standards before work starts. This is especially important for BIM Coordination Services, where multiple discipline models need to align before clash detection begins.

Fewer coordination errors

When all discipline teams model to the same LOD requirements with the same naming conventions, federated model assembly is straightforward, and clash detection runs cleanly. Without a BEP, every coordination meeting starts with resolving process problems rather than design problems.

Faster clash detection cycles

A BEP sets the rules for clash detection, deciding how often it happens, who’s in charge, what kinds of issues are top priority, and how fixes are followed up on. This turns clash detection into a system that finds problems early when they’re easier and cheaper to solve.

Clear accountability

The BEP’s responsibility matrix clearly lays out who produces each model element, the LOD level, and deadlines. When things are missing or wrong, it’s obvious who needs to fix it, no confusion there. A core part of structured BIM coordination

Compliance with ISO 19650 and client requirements

On UK public sector projects and many large private developments, a BEP is a contractual requirement. Clients issue Exchange Information Requirements (EIR) and expect a BEP in response. On US federal projects, BIM requirements are typically defined in project-specific BIM guidelines. In both cases, having a structured BEP demonstrates professional BIM capability to the client.

Better handover

Projects that use a BEP from the start produce structured, well-organized model data at handover. Facility managers receive accurate As-built BIM Services with consistent naming and data that supports long-term asset management. Projects without a BEP typically deliver models that are too inconsistent to use effectively for operations.

Pre-Contract vs Post-Contract BEP: What is the Difference?

A BIM Execution Plan exists in two forms, produced at different stages of the project lifecycle. Understanding the difference is important for contractors responding to tenders and for teams appointed to deliver BIM work.

Factor	Pre-Contract BEP	Post-Contract BEP
When produced	During tendering before contract award	After contract is awarded
Who produces it	Prospective supplier responding to EIR	Appointed delivery team
Level of detail	High-level proposed approach and capabilities	Detailed specific workflows, tools, responsibilities
Purpose	Demonstrate BIM capability and approach to client	Guide actual BIM delivery throughout the project
Key contents	BIM goals, proposed software, team structure outline	MIDP, naming conventions, clash detection protocol, CDE setup
ISO 19650 reference	Pre-appointment BEP	Delivery team BEP

Pre-Contract BEP

The pre-contract BEP is made before a contract is awarded, during the tendering phase. It’s where prospective suppliers show the client how they plan to implement BIM Consulting Services, demonstrate their capabilities, and meet the project’s information needs. They do this by formally responding to the client’s Exchange Information Requirements (EIR).

A pre-contract BEP is intentionally high-level. It lays out BIM goals, the team’s software skills, a first draft of roles, and a general info-sharing method. It commits to an approach but isn’t a detailed plan itself.

Post-Contract BEP

Once the contract is given out, the chosen team makes the post-contract BEP. This one’s way more detailed and involves input from all key players, subcontractors, BIM managers, discipline leads, and coordinators. So everyone’s specific insights get included.

The Master Information Delivery Plan in the post-contract BEP sets out every model and document the team will produce, who will create each deliverable, which tools they will use, and when they will deliver them within the project timeline. This is especially important for teams delivering Construction Documentation Services from coordinated BIM models.

Under ISO 19650, the post-contract BEP becomes the Delivery Team’s BEP. This then serves as the main info management guide during their appointment. So, teams can rely on it throughout their contract period.

What Should a BIM Execution Plan Contain?

The contents of a BEP change based on project type, jurisdiction, and what the client needs. Yet, no matter the specifics, a solid BEP always includes certain parts.

Component	What It Covers	Why It Matters
Project Information	Project name, location, client, scope, key dates	Establishes the baseline context for all BIM decisions
BIM Goals and Uses	What BIM will be used for: clash detection, 4D scheduling, quantity extraction, facility management	Determines software requirements and model scope
Roles and Responsibilities	Who is the BIM Manager, Information Manager, task team leads, and what each is accountable for	Prevents coordination gaps when multiple disciplines are involved
LOD Requirements	What Level of Detail is required at each project stage, per discipline	The single most common source of coordination failure when undefined
Software and File Formats	Revit versions, Navisworks settings, IFC export requirements, DWG standards	Ensures models are compatible across the full project team
Common Data Environment	Which CDE platform is used BIM 360, Procore, Aconex and how files are named, approved, and issued	Version control prevents teams working from outdated models
Naming Conventions	File naming, layer naming, element naming standards aligned to ISO 19650 or project-specific requirements	Consistency across all deliverables, essential for federated model assembly
Clash Detection Protocol	Who runs clash detection services, how often, what clash types are prioritized, how resolutions are tracked	Without a defined protocol, clash detection becomes a one-time event rather than an ongoing process
Information Delivery Schedule (MIDP)	What models and documents are delivered, by whom, at what project stage	The master schedule for all BIM deliverables aligns design and construction timelines
Quality Control Process	How models are checked before issue, who reviews, what is checked, and what sign-off is required	Prevents errors propagating through the federated model

For big projects, such as commercial high-rises and data centers, you need to cover all 10 components in detail. On smaller projects, the team can keep the brief shorter, but it should still define LOD requirements, software stack, naming conventions, and CDE setup. Project teams should never guess or assume these requirements, regardless of project size.

BIM Execution Plans and ISO 19650

ISO 19650 handles info throughout a built asset’s entire life cycle using BIM. It replaced PAS 1192-2:2013 in 2018. Now, it’s the main guideline for BIM info management in the UK, Europe, and also more and more in the US and Australia.

Under ISO 19650, the BEP sits within a structured information management framework:

• The Appointing Party (client) issues Exchange Information Requirements (EIR) defining what information they need, when, and in what format.
• The prospective delivery team responds with a pre-appointment BEP demonstrating their capability to meet the EIR.
• After appointment, the delivery team produces the Delivery Team BEP, the detailed execution plan covering the MIDP, CDE, naming conventions, and all coordination protocols.
• The MIDP (Master Information Delivery Plan) within the post-contract BEP defines the complete information delivery schedule for the project.

UK contractors on public or big private projects need to be ISO 19650 compliant. It’s becoming standard in contracts. To meet BIM requirements, they must grasp the BEP’s role in the ISO 19650 system and tell the difference between pre-appointment BEPs, those for the delivery team, and the EIR.

US contractors get similar guidance from the National BIM Standard, NBIMS-US. However, project teams usually define BEP requirements separately for each project through a specific BIM Execution Plan, rather than following one fixed national rule.

How to Create a BIM Execution Plan: Step by Step

For contractors producing a BEP for the first time, the process follows a consistent sequence regardless of project type or jurisdiction.

Step 1: Review the Exchange Information Requirements

Before writing anything, read the client’s EIR carefully. The BEP is a direct response to the EIR. Every section of the BEP should address a specific information requirement that the client has set. If the client has not issued an EIR, request one or define your own project information requirements as the basis for the BEP.

Step 2: Define BIM Goals and Uses

Clearly define how the project team will use BIM on this project. Clash detection is the most common use. 4D scheduling, 5D cost extraction, Scan to BIM Services, and facility management handover are all valid BIM uses. But we need to define them from the start. They impact model structure, LOD requirements, and software selection, you see.

Step 3: Define Roles and Responsibilities

Figure out who the BIM Manager, Information Manager, and task team leads are for each group. Make a responsibility matrix to show who creates, checks, and OKs each model part. Being clear about this stops issues down the road.

Step 4: Agree LOD Requirements by Stage

Figure out how detailed each part needs to be throughout the project. One big mistake is thinking LOD 300 will work for everything. The architect might think that’s fine, but the MEP contractor needs LOD 350 to actually make stuff. To avoid this, set it straight in the Building Execution Plan and make sure everyone agrees to it before moving on.

Step 5: Define the Software Stack and CDE

To start, agree on what tools to use for modeling, federation, and clash detection. Usually, projects pick Revit for modeling, Navisworks for finding clashes, and BIM 360 for the common data environment. Also, set file naming rules, organize folder structures, and create an approval process for model issues.

Step 6: Define the Clash Detection Protocol

Define how often the team will run clash detection and which discipline combinations they will check. Include clash tolerances to use and rules for categorizing and tracking clashes. Having a solid plan turns clash detection into an ongoing coordination effort, not just a one-time task.

Step 7: Produce the Master Information Delivery Plan (MIDP)

The MIDP sits within the BEP and sets out the information delivery details: what the team will share, who will share it, which tools they will use, and when they will deliver it at each project stage. It must match the overall plan and get updates when that plan changes, too.

Step 8: Review and Issue for Agreement

Circulate the draft BEP to all key project participants before finalizing. The BEP only works if everyone agrees to it. Before work begins, get a written sign-off from the discipline leads, BIM Manager, and the client’s information manager.

Common BIM Execution Plan Mistakes to Avoid

Producing a BEP after modeling has already started

The most common mistake. A BEP produced retrospectively is a documentation exercise, not a governance tool. By the time it is written, teams have already made incompatible decisions about LOD, naming, and software that are difficult to reverse.

Leaving LOD undefined or vague

Writing ‘LOD 300 or higher’ is not a LOD specification. Define the exact LOD required for each discipline at each project stage. If MEP needs LOD 350 for fabrication, state this explicitly. Vague LOD requirements are the primary driver of coordination delays on commercial projects.

No named BIM Manager

A BEP without a named BIM Manager has no owner. Someone must enforce its rules, run coordination meetings, manage clash detection cycles, and update the MIDP for changes. Without that, the BEP just lacks direction and accountability.

Treating the BEP as a one-time document

The BEP is a live document. Project teams should review and update the BEP when the programme changes, when they appoint new subcontractors, and when scope changes affect model requirements. If the team files the BEP away and forgets it, the document stops working as a governance tool and becomes paperwork.

Ignoring the CDE setup

The Common Data Environment stores all project info. If it lacks the proper folder structure, naming rules, and approval process, teams might use old models. The Basic Environment Plan needs to explain the CDE setup clearly. That way, anyone joining the project can quickly find the files they need.

What This Means for Your Next Project

A BIM Execution Plan isn’t about bureaucracy. It’s the practical foundation that makes coordinated BIM delivery work. When projects spend time on a good BEP before modeling begins, they usually have fewer mistakes, catch issues faster, pass off projects smoother, and avoid redoing things on site.

The contractors and developers getting the most out of BIM aren’t always using the fanciest tech. Instead, they excel because they set clear info needs, discuss and agree on them with the whole team, and stick to those rules consistently.

If your organization is commissioning BIM work and hasn’t provided Exchange Information Requirements, your BIM supplier can’t create a BEP that actually meets your project’s needs. If you produce BIM work and the client has not given you an EIR, ask for one or define the project information requirements before you open the first model.

FAQs