Danny Bentley
← Writing
Feb 16, 2026·4 min read
bepautomationbimaecrevit

BEP Automation: Generate and Email a Clean Plan

A reusable workflow pattern that assembles a clean BIM Execution Plan from structured inputs and distributes it automatically by email.

TL;DR: Most BEPs become static PDFs the moment they are issued. This workflow treats the BEP as live, structured project state. It pulls from Revit and ACC, generates a versioned document, and distributes automatically. The BIM Manager shifts from author to validator.

A BIM Execution Plan is not just a document. It is a structured agreement that defines how a project will be modeled, coordinated, and delivered. It sets expectations for consultants, clients, internal teams, and external partners.

Even on small projects, it should exist. The challenge has never been creating one. Most firms already have a template. A BIM Manager fills in the project information, formats the deliverable, and issues it. That part takes a few hours.

The real problem is what happens after.

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 from how the project actually evolves. By the time someone needs to reference it (a scope dispute, an LOD question, a responsibility review) it no longer reflects reality.

The problem is not the document. It is the disconnect.

The information that a BEP captures already exists in other systems:

  • ACC holds project metadata: name, number, phase, address, active team members, role assignments, and email distribution lists
  • Revit holds model configuration: application version, shared parameters, workset structure, discipline identifiers
  • BIM standards define the rules: Level of Development expectations, naming conventions, exchange cadence, and responsibility boundaries

On most projects, a BIM Manager manually retypes this information into a Word document or a PDF template. When a team member changes, when software is upgraded, when a discipline's responsibilities shift — the BEP does not update. It drifts.

Treating the BEP as structured state

Instead of treating the BEP as a document to be authored, this workflow treats it as structured project state to be assembled.

BEP Automation WorkflowLive Data SourcesACC — Project DataName · Number · Phase · AddressACC — Teams & RolesMembers · Disciplines · EmailsRevit — Model ConfigVersion · Params · WorksetsBIM StandardsLOD · Naming · ConventionsBEP EngineTemplate + Live StateMerge · Validate · GenerateOutputsVersioned BEPPDF · Timestamped · StoredResponsibility MatrixDisciplines · LOD · OwnershipEmail DistributionControlled List · Audit TrailBIM Manager ReviewValidate · Override · Approve · IssueCanonical State · Every Version Stored · Every Issue Trackedfeedback

The diagram shows the full flow. On the left, live data sources feed into the BEP Engine at the center: ACC project data, team rosters, Revit model configuration, and BIM standards. The engine merges template structure with live state, validates the result, and generates three outputs on the right.

  1. A versioned BEP document (timestamped PDF)
  2. A responsibility matrix (disciplines, LOD, ownership)
  3. An email distribution with a controlled recipient list and audit trail

The BIM Manager sits below the engine. Not as the author. As the reviewer. Their role shifts to validation and oversight: Is the ACC data correct? Is the Revit model configured properly? Are discipline responsibilities aligned? They can override, approve, and issue. A feedback loop runs from the BIM Manager back to the data sources, ensuring corrections propagate upstream.

Everything flows to canonical state. Every version is stored. Every issue is tracked.

What changes for the BIM Manager

The BIM Manager is no longer responsible for formatting tables, chasing email chains, or reconciling outdated role assignments.

The responsibility shifts to validation:

  • Is the ACC project data current and correct?
  • Is the Revit model configured to match the agreed standards?
  • Are discipline responsibilities and LOD expectations aligned across teams?
  • Is the distribution list accurate before the BEP is issued?

Project-level customization is still possible. The BIM Manager can override any section before issuing. But the baseline agreement is automated, versioned, and traceable.

Each generated BEP is timestamped, stored, and distributed through a controlled list. Every issued version has an audit trail. When the project changes (a new team member, a software upgrade, a shift in discipline scope) the next version of the BEP reflects those changes automatically.

Why this matters

A BEP is not always requested at the start of a project. But it becomes critically important when questions arise later. When scope disputes surface. When LOD expectations are challenged. 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. It is not a static document filed away at kickoff.

It is a governed artifact, generated from the live digital project environment, that evolves with the model.

Key Takeaways

  • Treat BEP content as structured state, not a document to be authored manually
  • Pull live data from ACC and Revit so updates stay consistent across versions
  • Version every issued BEP with timestamps and audit trails
  • The BIM Manager's role shifts from author to validator and oversight

The goal isn't just better documentation. It's better buildings.