BEP Automation: Generate and Email a Clean Plan

A BEP is not just a document. It is a structured agreement between project stakeholders, consultants, clients, internal teams, and external partners. Even on small projects, it should exist.

The challenge has never been creating one. It takes a few hours. We already have a template. We fill in the necessary project information and issue it. The real problem is what happens next.

In large offices managing dozens of projects, the BEP quietly becomes a static PDF. It gets archived, rarely revisited, and almost never updated. Over time it disconnects from the model, from ACC, and ultimately from the actual state of the project.

Treating the BEP as Structured State

Instead of treating the BEP as a document, we treat it as structured project state.

Project metadata lives in ACC.
User roles and permissions live in ACC.
Software versions and model parameters live inside Revit.

Rather than manually retyping this information, the system queries those sources directly.

Through the Revit API, we extract application version data, model build information, shared parameter configurations, and discipline identifiers. From ACC, we retrieve active team members, role assignments, email distribution lists, and core project metadata.

These inputs form a canonical BEP state.

The document itself is no longer authored manually. It is generated from templates using the live project data. When a new user joins, the BEP updates. When software versions change, it reflects that change. When discipline roles shift, the responsibility matrix and distribution adjust automatically.

Shifting the Role of the BIM Manager

The BIM Manager is no longer responsible for managing formatting or chasing email chains.

The responsibility shifts to validation:

• Is the ACC data correct?
• Is the Revit model configured properly?
• Are discipline responsibilities aligned?

Project-level customization is still possible. But the baseline agreement becomes automated, versioned, and traceable.

Each generated BEP is timestamped, stored, and distributed through a controlled list. Every issued version has an audit trail.

Why This Matters

While a BEP is not always requested at the beginning of a project, it becomes critically important when scope disputes arise, when LOD expectations are questioned, or when legal responsibility is reviewed.

A live, traceable, system-generated BEP protects the team. It defines modeling levels, exchange cadence, and discipline boundaries with clarity.

This is no longer a static document.

It is a governed artifact generated from the live digital project environment.

The BEP evolves with the model.