ISO 19650 · delivery side

BEP template — the delivery team's response

The BIM Execution Plan (BEP) describes how the delivery team meets the requirements from the EIR — roles, processes, software, model structure and delivery planning.

Create a BEP, guided →

What is the BEP?

The BEP (BIM Execution Plan) — the German "BAP" — is the delivery team's answer to the client's EIR. Where the EIR states what is ordered, the BEP describes the how: with which roles, methods, tools and schedules the required information will be delivered.

Pre- and post-appointment

ISO 19650 distinguishes two stages. The pre-appointment BEP is part of the tender and shows how the team intends to meet the requirements. After award it becomes the post-appointment BEP — the binding delivery plan, including the Master Information Delivery Plan (MIDP).

What goes in?

Terminology: BEP = BAP (German). The BEP is never a standalone wish list — it is always the response to a specific EIR. No EIR, no basis for the BEP.

Common mistakes

Generate it

In the generator you carry over the requirements from the EIR and answer targeted questions on roles, technology and delivery planning. The result: a consistent, ISO 19650-compliant BEP as DOCX/PDF — with a clean link back to the requirement side.

FAQ

What is the difference between BEP and BAP?

Both mean the BIM Execution Plan. BEP is the ISO 19650 / English term, BAP the German one — same document.

Who writes the BEP?

The delivery team — the lead appointed party with the task teams. It is the response to the EIR.

What is the difference between TIDP and MIDP?

The TIDP is a single team's delivery plan; the MIDP is the overall plan merged across all teams — both part of the BEP.

› Back to all ISO 19650 documents