The BIM Execution Plan as a project's model-authoring contract, LOD requirements by discipline and phase, the Model Element Table, roles and responsibilities, model exchange protocols and file-naming conventions, and aligning the BEP with owner and contract requirements.
Every workflow covered so far in this program — parametric modeling in Module 5, multi-discipline linking and coordination in Module 6 — only runs smoothly on a real project because a BIM Execution Plan already answered the process questions before modeling started: which software and LOD each discipline commits to, who owns which decision, and how models actually move between teams. This module treats the BEP as exactly that governing document, working through how an LOD-by-phase matrix and a granular Model Element Table turn abstract policy into something a BIM Manager can actually audit, and why naming real roles with real authority is what prevents coordination conflicts from stalling with nobody empowered to resolve them.
By the end of this module you should be able to explain why a BEP has to be checked against the owner's actual contract requirements rather than written from a generic template, and why file-naming and exchange-protocol discipline — easy to treat as administrative trivia — is exactly what prevents the stale-link failures Module 6 introduced and Module 8's clash-detection workflow depends on you avoiding.