Table of Contents

A BIM Execution Plan (BEP) is a formal project document that defines how Building Information Modeling will be implemented, managed, and delivered on a construction project. It is the delivery team’s written commitment to the appointing party, outlining the people, processes, software, and standards that will govern how BIM information is produced and managed from the first design stage through to handover.

Under ISO 19650, the BEP is a mandatory deliverable. It is produced in two stages. The pre-contract BEP is submitted as part of the tender response, demonstrating the delivery team’s capability and approach. The post-contract BEP is developed after appointment, refining the pre-contract version into a detailed, project-specific plan that all team members work from throughout delivery.

For contractors, the BEP is not just a compliance document. It is a practical management tool that aligns disciplines, sets expectations, defines workflows, and reduces the risk of information failures that cause delays, rework, and cost overruns. A well-prepared BEP is one of the clearest signals of a contractor’s BIM maturity and project readiness.

Why Contractors Need a Comprehensive BEP Checklist

The BEP covers a wide range of topics, from team structure and software platforms to file naming conventions and quality control workflows. Without a structured checklist, it is easy for contractors to overlook critical components, particularly on fast-moving projects where multiple disciplines are being mobilized simultaneously.

A BEP checklist ensures that every required element is addressed before the project moves into active production. It gives BIM managers a structured review tool, helps onboard new team members to project standards, and provides a reference point for auditing compliance throughout delivery.

The checklist presented in this article is organized around the core sections of a BIM Execution Plan as defined by ISO 19650 and widely adopted BIM standards. Each section identifies what must be included, what questions must be answered, and what deliverables must be confirmed.

BEP Checklist Section 1: Project Information and Context

This section establishes the foundational information that frames the entire BEP. Every item here must be confirmed and documented before the BEP is finalized.

Project Details

Project name, reference number, and description confirmed
Project location and site address recorded
Project type (new build, refurbishment, infrastructure, fit-out) identified
Project programme with key milestones and handover dates documented
Procurement route confirmed (design and build, traditional, ECI, etc.)
Contract form and BIM-related contract clauses reviewed

Client and Appointing Party Information

Appointing party name, organization, and key contacts documented
Client’s Organizational Information Requirements (OIR) reviewed and understood
Asset Information Requirements (AIR) reviewed and mapped to project deliverables
Project Information Requirements (PIR) at each project stage identified
Exchange Information Requirements (EIR) received, reviewed, and confirmed as understood

Project Objectives and BIM Goals

Client’s specific BIM objectives confirmed (clash detection, COBie handover, facility management, digital twin, etc.)
BIM use cases for the project identified and agreed
Level of Information Need defined for each project stage and discipline
Any sector-specific standards or client-specific BIM standards identified (e.g. NHS BIM standards, Highways England requirements)

BEP Checklist Section 2: Delivery Team Structure and Responsibilities

A BEP must clearly define who is responsible for what. Ambiguity around roles is one of the most common causes of coordination failures on BIM projects.

Key Roles and Appointments

Lead Appointed Party identified and confirmed
BIM Manager or Information Manager appointed and named
Discipline BIM Coordinators identified for each contributing organization
BIM Authors assigned to specific model packages
Model checkers and quality reviewers assigned
Information Manager responsible for CDE administration confirmed

Responsibility Matrix

BIM Responsibility Matrix completed, mapping each model element to its authoring party
Handoff points between disciplines documented
Responsibilities for federated model coordination assigned
Responsibilities for clash detection, resolution, and sign-off assigned
Responsibilities for COBie data population assigned if required
Responsibilities for quality assurance at each CDE workflow stage confirmed

Supply Chain and Subcontractors

All subcontractors and specialist consultants contributing BIM information identified
BIM capability assessment completed for each contributing party
BIM training needs identified and addressed
Subcontractor BEP requirements communicated and confirmed
Information exchange protocols with the supply chain agreed

BEP Checklist Section 3: Standards and References

This section documents the standards, protocols, and reference documents that govern how information is produced on the project.

Applicable Standards

ISO 19650 Parts 1 and 2 confirmed as the governing information management standard
ISO 19650 Part 3 referenced if the project includes operational phase BIM requirements
National BIM standards or annexes applicable to the project region identified
Sector-specific standards identified and referenced (healthcare, education, infrastructure, etc.)
Classification system confirmed (Uniclass, OmniClass, NBS, or client-specified system)

Spatial Coordination Standards

Survey origin and project base point confirmed and documented
Coordinate system and survey datum agreed across all disciplines
Levels and gridlines confirmed, named, and shared across all model files
Tolerance requirements for model geometry defined
Modeling guidelines for each discipline agreed

Document and Drawing Standards

Document naming convention confirmed and distributed
Drawing sheet standards confirmed (title block, revision format, scale conventions)
Model file naming convention confirmed and documented
Layer and object naming conventions agreed for CAD deliverables where applicable

BEP Checklist Section 4: BIM Uses and Applications

BIM uses are the specific functions that BIM will perform on the project beyond basic 3D modeling. Defining these upfront ensures that models are built with the right data and geometry to support each intended use.

Design and Documentation

3D design modeling confirmed as a BIM use
2D drawing production from BIM models confirmed
Quantity takeoff from BIM models confirmed if required
Specification linking to model elements confirmed if required

Coordination and Clash Detection

Multi-discipline coordination confirmed as a BIM use
Clash detection software and process confirmed
Clash detection frequency and milestone schedule agreed
Clash severity classifications defined (hard clash, soft clash, workflow clash)
Clash resolution process and sign-off procedure documented

Construction Planning

4D construction sequencing confirmed if required
Site logistics modeling confirmed if required
Temporary works modeling requirements confirmed

Cost Management

5D cost estimating from BIM models confirmed if required
BIM-based quantity takeoff protocols agreed with cost consultants

Handover and Operations

COBie data requirements confirmed and mapped to model elements
Asset Information Model (AIM) requirements confirmed
Facility management system integration requirements identified
Digital twin requirements documented if applicable
Point cloud requirements for as-built verification confirmed if applicable

BEP Checklist Section 5: Software and Technology

Consistent software environments are essential for seamless information exchange. This section of the BEP confirms the tools that will be used across the project.

BIM Authoring Software

Architectural BIM authoring software confirmed (e.g. Revit, ArchiCAD, Vectorworks)
Structural BIM authoring software confirmed
MEP BIM authoring software confirmed
Civil and infrastructure BIM authoring software confirmed if applicable (e.g. Civil 3D, OpenRoads)
Mechanical CAD software confirmed for fabrication and product design deliverables

Coordination and Checking Software

Federated model viewer confirmed (e.g. Navisworks, Solibri, BIMcollab Zoom)
Clash detection software confirmed and version documented
IDS validation software confirmed if IDS compliance is required
Model checking and quality assurance tools confirmed

Common Data Environment (CDE) Platform

CDE platform confirmed and documented (e.g. Autodesk Construction Cloud, BIM 360, Trimble Connect, Aconex)
CDE administrator identified and assigned
CDE folder structure and naming confirmed
Access rights and permission levels defined for each contributing party
CDE workflow states confirmed (WIP, Shared, Published, Archived)
CDE training plan for all contributing parties confirmed

File Exchange Formats

Native file formats for each discipline confirmed
IFC export settings confirmed for each authoring software platform
IFC version confirmed (IFC 2×3, IFC 4, IFC 4.3 as appropriate)
COBie export format confirmed (spreadsheet, IFC, or other)
PDF and drawing exchange formats confirmed
Revision and version control process confirmed

IT and Collaboration Infrastructure

Hardware and software specifications confirmed for all contributing parties
Internet connectivity and remote access to CDE confirmed
Data security requirements reviewed and addressed
Software licensing confirmed for all project tools

BEP Checklist Section 6: Common Data Environment Setup and Workflows

The CDE is the backbone of ISO 19650-compliant information management. This section confirms that the CDE is configured correctly before production begins.

CDE Configuration

CDE platform provisioned and project environment created
Project base folder structure created and confirmed
Naming convention applied consistently across all CDE folders and containers
Metadata schema confirmed and applied (status codes, revision codes, discipline codes, etc.)
CDE access rights assigned to all contributing parties
CDE user acceptance testing completed

Workflow States and Suitability Codes

Work in Progress (WIP) area configured for each contributing party
Shared area workflow configured for coordination and review
Published area workflow configured for formally authorized information
Archive area configured for superseded and completed information
Suitability codes defined and communicated (e.g. S0 for WIP, S1 for coordination, S2 for information, S3 for construction, S4 for as-built)

Transmittal and Submission Protocols

Document submission process from CDE to appointing party confirmed
Formal transmittal process documented
Response and review timeframes agreed
Revision and resubmission process confirmed
Notification protocols for new publications confirmed

BEP Checklist Section 7: Level of Information Need

The Level of Information Need defines the appropriate depth and detail of information required from model elements at each project stage. This section must be completed for every discipline and every project milestone.

Geometric Information

Level of geometric detail confirmed for each element type at each project stage
Spatial coordination requirements confirmed
Clearance and maintenance zone requirements documented
Geometric simplification rules for federated model performance confirmed

Alphanumeric Information

Required property sets confirmed for each IFC entity type
Required classification codes confirmed for each element type
Required material information confirmed
Required manufacturer and product data confirmed for equipment and components
Required maintenance and operational data confirmed for handover elements

Documentation

Required drawing types and scales confirmed at each project stage
Required specification documents confirmed
Required reports and analysis outputs confirmed
Required certificates and compliance documentation confirmed

Stage-by-Stage Information Matrix

Level of Information Need matrix completed for all element types across all project stages
Matrix agreed with appointing party and confirmed in EIR response
Matrix distributed to all contributing parties
Compliance with IDS specification confirmed if applicable

BEP Checklist Section 8: Coordination and Clash Detection Process

Effective coordination is one of the primary benefits of BIM on construction projects. This section confirms that the coordination process is fully defined before production begins.

Federation Strategy

Federated model structure confirmed, defining how individual discipline models combine
Model splitting strategy confirmed (by floor, zone, building, system, etc.)
File size limitations and model performance guidelines confirmed
Reference file and linked model protocols confirmed

Coordination Meeting Schedule

Coordination meeting frequency confirmed
Attendees for each coordination meeting defined
Agenda and reporting format for coordination meetings confirmed
Issue tracking and resolution process confirmed

Clash Detection Process

Clash detection responsibility assigned
Clash detection software and process confirmed
Clash sets defined for each discipline combination
Clash severity definitions confirmed
Clash reporting format confirmed
Clash resolution timeframes agreed
Sign-off process for resolved clashes confirmed

Model Freeze and Milestone Submissions

Model freeze dates agreed for each coordination milestone
Submission requirements for each milestone confirmed
Acceptance criteria for coordinated model submissions confirmed
Process for managing late or non-compliant submissions documented

BEP Checklist Section 9: Quality Assurance and Information Compliance

Quality assurance is not optional under ISO 19650. Every piece of information must be checked, reviewed, and authorized before progressing through the CDE workflow.

Quality Control Responsibilities

Model author self-check responsibilities confirmed
Discipline coordinator review responsibilities confirmed
Lead appointed party authorization responsibilities confirmed
Independent model audit process confirmed if required

Model Quality Checks

Geometry checks confirmed (no duplicate elements, no overlapping geometry, no out-of-tolerance elements)
Property completeness checks confirmed
Classification checks confirmed
Naming convention compliance checks confirmed
IFC export validation checks confirmed
IDS compliance validation confirmed if applicable

Document Quality Checks

Drawing completeness and accuracy checks confirmed
Title block and metadata completeness checks confirmed
Revision control checks confirmed
Cross-reference accuracy checks confirmed

Quality Audit Schedule

Audit frequency confirmed across the project programme
Audit scope and depth confirmed at each project stage
Audit reporting format and distribution confirmed
Non-conformance process and corrective action procedure documented

BEP Checklist Section 10: Information Security

As BIM models become increasingly data-rich, information security is an important consideration, particularly on sensitive project types such as healthcare, government, defence, and critical infrastructure.

Security Classification

Project security classification confirmed
Security-sensitive information identified and documented
ISO 19650 Part 5 requirements reviewed and applied where relevant

Access Control

User access rights reviewed and applied on a need-to-know basis
Multi-factor authentication confirmed for CDE access where required
Procedures for revoking access upon team member departure confirmed
Data sharing restrictions with offshore or international team members confirmed

Data Handling

Data retention and archiving policy confirmed
Procedures for handling and transmitting sensitive model data confirmed
Incident reporting procedure for data security breaches confirmed

BEP Checklist Section 11: Training and Onboarding

A BEP is only effective if every team member understands and follows it. Training and onboarding are often underinvested areas that directly affect BIM quality on projects.

BIM Training Requirements

BIM training needs assessment completed for all contributing parties
Software training plan confirmed for any tools new to team members
ISO 19650 awareness training confirmed for project managers and site teams
CDE platform training confirmed for all users

Project Onboarding

BEP kickoff meeting scheduled and confirmed
BEP distributed to all contributing parties
Key contacts list distributed
CDE access confirmed for all users prior to production start
Coordination protocol briefing scheduled

BEP Checklist Section 12: Handover and Closeout

The final section of the BEP confirms the requirements for information handover at project completion, ensuring that the appointing party receives an information model that meets their asset management needs.

Asset Information Model (AIM) Requirements

AIM content requirements confirmed with appointing party
Asset data requirements mapped to model elements
COBie spreadsheet requirements confirmed if applicable
IFC handover file requirements confirmed
Naming and classification standards for AIM confirmed

As-Built Documentation

As-built model update process confirmed
Responsibility for as-built model production assigned
As-built drawing production requirements confirmed
Point cloud as-built verification requirements confirmed if applicable

Handover Process

Formal handover milestone confirmed in the project programme
Handover package contents list confirmed
Handover acceptance criteria confirmed with appointing party
Post-handover support period and responsibilities confirmed
Final CDE archiving process confirmed

Conclusion

A BIM Execution Plan is far more than a compliance document. For contractors, it is the master framework that governs how information is produced, coordinated, quality-checked, and delivered across every stage of a project. Getting the BEP right at the start is one of the most impactful investments a contractor can make in a project’s success.

This checklist covers every critical element of a BEP, from project context and team responsibilities to CDE setup, clash detection, quality assurance, and handover. By working through each section systematically before production begins, contractors ensure that their BIM workflows are aligned, their deliverables are defined, and their projects are positioned to meet the information requirements of even the most demanding clients.

As BIM standards continue to evolve and client expectations continue to rise, contractors who invest in robust, well-structured BIM Execution Plans will consistently outperform those who treat BIM as a box-ticking exercise. The BEP is the foundation of every successful BIM project, and this checklist is the tool that helps contractors build that foundation right.

FAQs About BIM Execution Plans

What is a BIM Execution Plan and why is it important?

A BIM Execution Plan (BEP) is a formal document that defines how BIM will be implemented on a specific construction project. It covers team structure, software, workflows, standards, and quality processes. It is important because it aligns all contributing parties to a common set of expectations, reducing the risk of information failures, coordination conflicts, and costly rework.

What is the difference between a pre-contract BEP and a post-contract BEP?

A pre-contract BEP is submitted as part of a tender response. It demonstrates the delivery team’s BIM capability and outlines their proposed approach to meeting the appointing party’s information requirements. A post-contract BEP is developed after appointment and refines the pre-contract version into a detailed, project-specific plan with confirmed resources, software, workflows, and schedules.

Who is responsible for producing the BEP?

The Lead Appointed Party is responsible for producing and maintaining the BEP. On a contractor-led BIM project, this is typically the main contractor’s BIM Manager or Information Manager, working in collaboration with discipline leads and key subcontractors.

What should a BEP include?

A comprehensive BEP should include project information, team structure and responsibilities, applicable standards, BIM uses, software and technology platforms, CDE setup and workflows, Level of Information Need definitions, coordination and clash detection processes, quality assurance procedures, information security measures, training plans, and handover requirements.

How often should the BEP be updated?

The BEP is a living document that should be reviewed and updated at key project milestones, such as the end of each RIBA stage or ISO 19650 project stage. It should also be updated whenever there are significant changes to the delivery team, software environment, or project requirements.

What is the relationship between the BEP and the EIR?

The Exchange Information Requirements (EIR) is issued by the appointing party and defines what information the delivery team must produce. The BEP is the delivery team’s response to the EIR, confirming how those requirements will be met. The BEP should directly address each requirement set out in the EIR.

Does every BIM project need a BEP?

Under ISO 19650, a BEP is required on any project where BIM is being used to manage information. In practice, any project where clients require structured BIM deliverables, clash-detected coordination, COBie data, or an Asset Information Model at handover should have a BEP.

What is a BIM Responsibility Matrix?

A BIM Responsibility Matrix is a table within the BEP that maps every model element or package to the party responsible for authoring it. It confirms who models what and removes ambiguity about ownership of each part of the information model.

How does the BEP relate to the Common Data Environment?

The BEP defines how the CDE will be set up, structured, and used on the project. It confirms the CDE platform, folder structure, naming conventions, workflow states, access rights, and submission protocols. The CDE is the environment in which the BEP’s information workflows are carried out.

Can a contractor use a standard BEP template?

Yes, and many experienced contractors maintain BEP templates that are adapted for each project. Templates save time and ensure consistency, but they must always be reviewed and customized to reflect the specific EIR, project requirements, team structure, and software environment of each individual project.

What happens if the BEP is not followed on a project?

Failure to follow the BEP typically results in inconsistent information quality, coordination failures, CDE non-compliance, and potentially contractual disputes. Under ISO 19650, non-compliance with the BEP can trigger formal quality non-conformances that must be addressed through a corrective action process.

How does the BEP support facility management after handover?

The BEP defines the information that must be captured in the model throughout the project, including the asset data, classifications, and properties needed by the facility management team. A well-executed BEP ensures that the Asset Information Model delivered at handover contains complete, accurate, and consistently structured data that can be directly ingested into CAFM and asset management systems.

BIM Execution Plan (BEP) Checklist for Contractors