If you've heard murmurs about the BIM Execution Plan getting renamed and wondered whether it's a meaningful change or just a documentation exercise, here's the honest practitioner's answer: it's mostly the latter, with one genuinely important shift underneath the name change.
The name change itself
Draft revisions to ISO 19650 Parts 1 and 2, released for consultation in March 2026, rename the BIM Execution Plan (BEP) to the Information Production Plan (IPP). The document's core function is unchanged — it's still the plan describing who delivers what information, and when, across a project. Final publication of the revised standard is expected in 2027, with the current 2018 standard remaining in force until then.
Source: ISO 19650 revision consultation materials and industry coverage, March 2026.
What actually changes underneath the renaming
| 2018 framing (BEP) | 2026 framing (IPP) |
|---|---|
| Focused heavily on design and construction-phase deliverables | Spans the full lifecycle, including operational/FM-phase information needs from the outset |
| Handover treated as a distinct, later milestone | Handover requirements considered from project inception, not bolted on at the end |
| "BIM" framed primarily as 3D modeling | Framed more broadly as "information management," reducing the misconception that BIM equals 3D geometry alone |
Why the lifecycle shift is the part that actually matters
The most consistent criticism of the 2018 ISO 19650 framework — including from UK BIM Framework practitioners reflecting on a decade of mandate experience — was that operational and facility management needs were treated as an afterthought, leading to handovers that technically met design/construction requirements but didn't actually serve the building owner's long-term data needs. The IPP's broader scope is a direct response: owner and FM information requirements are meant to shape decisions (like HVAC sensor specification, or asset tagging conventions) from early design, not be retrofitted at handover.
What this means practically, right now
If you're currently working to BEP-based documentation, you don't need to panic-rewrite anything before the 2027 final publication — the 2018 standard remains in force during the transition. What's worth doing now is starting to ask the IPP's underlying question earlier in projects: what does the owner or FM team need from this model after handover, not just during design and construction? Firms that adopt that habit now will have an easier transition when the renamed documentation becomes contractually expected.
A practical template adjustment
If you maintain a BEP template at the office level, the easiest forward-compatible update is adding an explicit "Asset Information Requirements" section early in the document — addressing FM/operational data needs alongside design and construction information, rather than only at a handover appendix. This single addition captures most of what the IPP framing is pushing toward, without waiting for the final 2027 standard to force the change.
ISO 19650 process literacy — including how to structure forward-compatible documentation — is taught in our Apex plan. Full curriculum on the Programs page.
Related reading: How to Actually Write an EIR: A Template Walkthrough
