BIM Documentation: Execution Plans, LOD Standards, and Coordination

How architects establish BIM Execution Plans, assign Levels of Development to model elements, and coordinate digital documentation across project teams using AIA digital practice documents and agency-specific BIM standards.

ARE · Project Management

Overview

BIM has become the standard method of project delivery for building design in the United States. But a BIM model without clear documentation protocols is a liability waiting to happen. That is where BIM Execution Plans and Level of Development standards come in.

A BIM Execution Plan (BEP or BxP) is the planning document that gets every team member on the same page before modeling begins. It defines who models what, to what level of detail, using which software, and following which file-sharing protocols. Without one, you get mismatched expectations, duplicated effort, and models that cannot be reliably coordinated.

Level of Development (LOD) is the framework that communicates how much a model element can be trusted. LOD is not about visual detail. It is about the degree to which the element's geometry has been thought through and the extent to which others can rely on it for decision-making. The LOD Specification, maintained by BIMForum and building on the AIA's LOD schema, provides standardized definitions from LOD 100 (symbolic representation) through LOD 500 (as-built conditions).

On the ARE, you need to understand both the contractual framework (AIA digital practice documents like E201/E202, G203, G204/G205) and the practical coordination requirements that agencies like GSA and the VA impose. The exam tests your ability to evaluate which LOD is appropriate for a given project phase, how BEP requirements affect project risk, and what happens when these protocols break down.

Essential

The BIM Execution Plan: Your Project's Digital Roadmap Every BIM-enabled project needs a BIM Execution Plan (BEP) established before design begins. GSA has required this since its 2018 P100 standards, and the concept has become standard practice industry-wide. The BEP is not optional documentation. It is the single document that prevents the most common BIM failures: mismatched software versions, unclear modeling responsibilities, and models that cannot be coordinated across disciplines. The 2022 AIA digital practice documents formalized the BEP through G203-2022, a prototype document that provides a framework for creating project-specific plans.

Professional

Consider a mid-size architecture firm that just won a federal healthcare project for the VA. The project manager receives the SEPS export file with the Program for Design and Preliminary Room Contents on day one. Before anyone opens modeling software, the team needs a BIM Execution Plan that accounts for the VA's specific requirements: LOD 300 for standard equipment, LOD 350 for architecturally significant equipment, room test-fits at two stages (design development and after equipment selection), and space reservations modeled as 3D volumes with 65-85% transparency. The project manager's first decision is which AIA BIM exhibit to attach to the professional services agreement. For a project where the owner wants the design and construction teams to share models, E201-2022 or E202-2022 applies. If the firm wants to limit model sharing to just the design team during early phases, E401-2022 covers that scope. The wrong choice here creates liability gaps.

TLDR

BIM Execution Plan (BEP): Established before design begins. Defines software, file protocols, modeling responsibilities, LOD assignments, coordination processes, and quality control. AIA G203-2022 provides the prototype framework.
LOD vs. Level of Detail: LOD measures how much you can rely on an element's geometry, not how detailed it looks visually. A generic pump and a specific pump can look identical in a model.
LOD 100-500: 100 = symbol/massing. 200 = generic placeholder, approximate. 300 = design intent, measurable. 350 = coordination with adjacent systems. 400 = fabrication/shop drawing detail. 500 = as-built (observed, not designed).
LOD requirements are cumulative from 100 through 400. LOD 500 is separate because it describes existing conditions, not a higher design level.
Model Element Table (G204/G205): Assigns LOD per element, per milestone, with responsible party and completion date. G205 is the simplified version for smaller projects.
AIA BIM Exhibits: E201/E202 for project-wide model sharing. E401 for design team only. E402 for construction team only. These are contract exhibits, not standalone agreements.
Key risk principle: Using BIM without agreed protocols places risk on the relying party. No protocol = your risk.
LOD 350 is the level for clash detection and construction coordination. Do not run interference checks on LOD 200 geometry.
BIM works with any delivery method. It is not exclusive to IPD, though it supports collaborative delivery most effectively.

ELI5

Picture a massive group project where ten different people are all building parts of the same LEGO set at the same time. Some are building walls, some are building the roof, some are adding the tiny furniture inside. If nobody agrees on the instructions first, you will end up with walls that do not line up, a roof that does not fit, and furniture that blocks the doors. That is exactly the problem a BIM Execution Plan solves. Before anyone starts building the digital model, the whole team sits down and agrees on the rules. Which software are you using? Who is responsible for modeling the structural columns versus the ductwork? How do you name your files? When do you share your work with the rest of the team? All of that goes into the BIM Execution Plan. Now, here is the tricky part.

AREProject Management

BIM Documentation: Execution Plans, LOD Standards, and Coordination

2 min read236 words

BIM Documentation: Why Your Execution Plan and LOD Standards Matter

Want to track your progress and access more study tools?

Create a free account