BIM Execution Plan (BEP) Review Checklist

Our checklist model setup guide mentioned that any fix taking over 30 minutes should become “a task in your BEP review” rather than a pre-issue patch. Here’s what an actual BEP review checks.

The checklist

1. Naming conventions still match reality. If your worksets or file naming have drifted from what the BEP documents (common after a new discipline joins mid-project), update the BEP — don’t let the document and the practice silently diverge.
2. LOD/LOI targets per milestone are still achievable on schedule. A BEP written at kickoff often sets Level of Development targets optimistically; review whether the current modeling pace actually supports the next milestone’s LOD commitment, or whether it needs renegotiating with the client now rather than discovering the gap at delivery.
3. CDE (Common Data Environment) folder structure and permissions match the current team. New subconsultants added after kickoff frequently get folder access as an afterthought — verify permissions match who’s actually contributing, not just who was listed at project start.
4. Coordination meeting cadence matches actual clash volume. If clash counts have dropped significantly (good coordination progress) or spiked (new discipline linked, major design change), the BEP’s meeting frequency should be revisited — weekly meetings on a project generating 5 clashes a week is overhead; biweekly meetings on a project generating 200 is negligence.
5. Responsibility matrix still lists the right people. Team turnover is normal on long projects; a BEP naming a BIM coordinator who left three months ago isn’t a process document anymore, it’s a stale artifact nobody trusts.
6. File exchange format requirements are still followed. Check that IFC exports (if required by the BEP) actually validate against the specified schema version — a “we export IFC” checkbox in the BEP doesn’t confirm the export is usable by the receiving party.
7. Clash tolerance and priority definitions still reflect current risk. Early in a project, structural vs. architectural clashes might be top priority; as MEP routing intensifies, headroom and MEP-vs-MEP clashes often become the higher-risk category — the BEP’s clash priority matrix should shift with the project phase, not stay fixed from kickoff.

Why this order

Items 1-3 are structural/administrative — cheap to check, easy to let drift silently. Items 4-5 are process/people — these change with project dynamics and need active revisiting, not passive assumption. Items 6-7 are the technical substance of coordination — verify these aren’t just documented but actually happening as specified.

Common mistake

Treating the BEP as a document written once at kickoff and referenced only when a client asks for it. A BEP that hasn’t been revisited since project start is describing a team, schedule, and risk profile that no longer exists by the time you’re mid-project — reviewing it against these 7 points before each milestone is what keeps it a working process document instead of contractual paperwork nobody follows.