Guide · BIM Execution Planning

What a BIM Execution Plan Should Contain

A BIM execution plan is where a project team commits, in writing, to how it will produce and manage information. This guide sets out what the plan should contain under ISO 19650-2:2018, how the tender-stage plan differs from the one used after appointment, and the mistakes that make a plan useless on site.

Ask About BEP Support

What the plan is for

The appointing party, usually the client or its representative, states what information it needs and when in the Exchange Information Requirements (EIR). The BIM execution plan (BEP) is the delivery team's answer. The EIR says what. The BEP says how, by whom, with what and by when.

ISO 19650-2:2018, the part of the standard that covers the delivery phase of an asset, places the plan at two points in the process. During tender response, the prospective lead appointed party establishes the delivery team's BEP so the client can judge the proposed approach. During appointment, the plan is confirmed with every task team and becomes the working document for the job. The two are often called the pre-appointment and post-appointment BEP.

Check the edition and the client standard: this guide refers to ISO 19650-2:2018. Some clients publish BIM standards and templates of their own that sit on top of it. In Qatar, the Public Works Authority (Ashghal) does so for its projects. Where a client standard applies, the BEP has to follow it, so read the contract and the EIR before using any generic template, including this one.

Pre-appointment and post-appointment BEP compared

Pre-appointment BEPPost-appointment BEP
WhenSubmitted with the tenderConfirmed at appointment, then maintained through the project
PurposeLets the client assess the proposed approach, capability and capacityTells every task team how to work
Responsibility matrixHigh level: which team produces which part of the modelDetailed: what information, by whom, to what level, at which milestone
Delivery plansA delivery strategyTask information delivery plans, combined into a master information delivery plan
StatusA proposalAgreed by the whole delivery team, and updated when things change

The sections a BEP should contain

Templates differ, but a plan that covers the nine items below answers what ISO 19650-2 asks the delivery team to establish.

Project information and the people responsible

The project, the stages covered, and the named individuals who carry out the information management function for the delivery team and for each task team. Names, not job titles, because a plan with no names has no owner.

Information delivery strategy

How the team will meet the EIR: the approach to collaboration, the objectives for producing information, the organisation of the team, and how the work is split between task teams.

Federation strategy

How the information model is divided into separate models, by discipline, building, zone or level, and how those models are brought back together for coordination. This decides file sizes, who can work at the same time, and how clash detection is organised.

Responsibility matrix

Which task team produces which elements of the model and which deliverables, developed after appointment into a detailed matrix that also states the level of information need and the milestone.

Information standard, methods and procedures

Naming of files and objects, classification, units, coordinates and origin, level of information need, model checking and approval routines. Where the client's standard already fixes these, the BEP records any additions or amendments the team proposes.

Software, hardware and IT schedule

Authoring, coordination and review software with versions, exchange formats such as IFC and BCF, and the common data environment. Agreeing versions here avoids the upgrade made by one team halfway through that locks the others out.

Information delivery plans

Each task team's information delivery plan lists what it will issue and when. The lead appointed party combines them into the master information delivery plan, which is aligned with the design and construction programme.

Capability, capacity and mobilisation

An honest assessment of each task team's skills and resources, and the plan to close any gaps: training, recruitment, software, testing of the data environment and exchange methods before production starts.

Risk register

The risks to delivering information on time, for example late design information, an untested exchange format or a single point of failure in the team, with the action and the owner for each.

Coordination: the part most plans leave vague

Many plans state that clash detection will be carried out and stop there. A plan that works on site also states which model pairs are tested, at what tolerance, how often, who chairs the coordination meeting, how issues are tracked and what counts as resolved. That is the clash matrix and the coordination cycle, and it belongs in the BEP or in an appendix to it.

Six mistakes that make a BEP useless

Copying the last project

A plan that still names the previous client's team, software versions or zones tells the reader nobody checked it.

Restating the EIR

The client already knows what it asked for. The plan has to say how the team will deliver it.

Promising more detail than is needed

Fabrication-level models at concept stage cost money and slow the team down. State the level of information need per stage.

No named people

Roles without names cannot be held to anything. Update the names when people change.

Untested exchanges

The first IFC export should not happen in the week of the first submission. Test the exchange during mobilisation.

Never updated

The plan is a live document. Review it at each stage and whenever the team, scope or software changes.

How Alftek supports BIM execution planning

Alftek prepares BIM execution plans as part of its BIM consultancy in Qatar, and works to the plan agreed with the project team on every modeling and coordination engagement. Our workflows are aligned with ISO 19650.

ISO 19650 information management

How the standard's requirements are applied on Qatar projects.

Explore ISO 19650 BIM in Qatar →

BIM consultancy

BEP, implementation planning, templates and standards, and QA/QC.

Explore BIM Services in Qatar →

Coordination

The clash matrix and coordination cycle the plan describes, run for you.

Explore Clash Detection →

Modeling

Architectural, structural and MEP models produced to the plan.

Explore BIM Modeling in Qatar →

Source and further reading: ISO 19650-2:2018, Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM), Information management using building information modelling, Part 2: Delivery phase of the assets. The UK BIM Framework publishes free guidance on applying it. This guide is a summary for orientation and does not replace the standard or your contract.

Frequently asked questions

What is a BIM execution plan?

A BIM execution plan (BEP) is the document in which a delivery team explains how it will manage and produce the information a project requires. It answers the appointing party's information requirements: who does what, to which standards, in which software, in what order and by which dates.

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

The pre-appointment BEP is submitted with the tender and shows how the team proposes to manage information, so the client can assess the approach, capability and capacity. After appointment the same plan is confirmed and developed in agreement with every task team, and it becomes a live project document supported by the detailed responsibility matrix and the information delivery plans.

Who writes the BEP?

Under ISO 19650-2 the lead appointed party establishes the delivery team's BEP, with input from each task team. On a Qatar building project that is typically the lead consultant at design stage and the main contractor at construction stage. A BIM consultant can draft and maintain it on their behalf.

Is a BEP the same as the EIR?

No. The Exchange Information Requirements are written by the appointing party and state what information is required and when. The BEP is the delivery team's response and states how that information will be produced and managed.

How long should a BEP be?

As long as it needs to be to remove ambiguity, and no longer. A plan that people actually open is worth more than a thorough one nobody reads. Put standards, schedules and matrices in appendices and keep the body of the plan to the decisions the team has to follow.

How often should the BEP be updated?

Whenever the team, the scope, the software or the programme changes, and at the start of each project stage. A BEP that still describes the tender-stage team during construction is a common audit finding.

Need a BEP for a Qatar project?

Send Alftek's Doha-based team the EIR or the BIM clauses in your contract. We will tell you what the plan needs to cover and quote for preparing it.

Request a Free Quote