A BIM Execution Plan defines how a project team will create, share, and use BIM — including scan-to-BIM scope and LOD.
Think of the BEP as the rulebook every discipline agrees to before modeling begins. It answers the practical questions that otherwise surface halfway through a project: which software and file formats will we exchange, how detailed does each element need to be, and who owns the federated model and coordinates it? Settling these upfront prevents rework, clash headaches, and the all-too-common situation where two teams deliver models that will not line up.
On projects that begin with a laser scan of existing conditions, the BEP is where the scan-to-BIM scope gets pinned down — how accurate the survey must be, what level of detail the resulting Revit model should reach, and exactly which deliverables the design team receives. A clear plan turns a raw point cloud into a model everyone can build on with confidence.
What a BEP covers
A well-written BIM Execution Plan documents a consistent set of items, regardless of project size:
- Project information and BIM goals — the reasons BIM is being used (clash detection, quantity takeoff, facilities handover) and the measurable outcomes each supports.
- Roles and responsibilities — who models what, who manages the federated model, and who runs coordination.
- Level of Development (LOD) — the geometric and information detail expected for each element at each phase.
- Coordinate system and units — a shared origin, project base point, and units so every model aligns.
- Software and file formats — authoring tools and the exchange formats (IFC, RVT, NWC) used between teams.
- Model structure and naming — how files are split, named, and organized in the common data environment.
- Collaboration process — meeting cadence, clash-detection workflow, and issue tracking.
- QA/QC and deliverables — model-checking routines and the schedule of what is handed over and when.
A BEP sets modeling standards, roles, file formats, coordinate systems, and LOD for each element — so everyone models to the same rules.
Why it matters for scan-to-BIM
When a project starts from reality capture, the BEP is where survey accuracy and model detail get translated into specifics. It should state the required registration accuracy of the point cloud, the tolerance the as-built model must hold to (for example, ±1/8″ for architectural elements), and the Level of Accuracy (LOA) of the captured data versus the Level of Development of the modeled result — two related but distinct ideas that are easy to conflate.
The plan also fixes the deliverable format: a native Revit model, a federated file for coordination, a cleaned and registered point cloud, or some combination. Defining this early means the scanning crew captures the right resolution the first time, and the modeling team knows exactly which elements to build and to what fidelity — no guesswork, no re-scans.
A clear BEP keeps existing-conditions models consistent and usable downstream. See scan-to-BIM.
Who writes the BEP, and when?
The BEP is usually drafted by the project’s BIM manager or lead modeler in collaboration with the design and construction teams, then agreed to by every party that will contribute a model. Ideally it is written during pre-design or very early design, before significant modeling effort is spent — a plan that arrives after teams have already built to different standards is far less useful. Many owners now require a BEP as a contract deliverable, and public agencies often supply their own template. On a scan-to-BIM engagement, the surveying provider should be brought in early so capture requirements are baked into the plan rather than bolted on afterward.
Pre-contract vs. post-contract BEPs
Industry guidance often distinguishes two versions. A pre-contract BEP is submitted with a bid to show how a team intends to meet the owner’s information requirements — it demonstrates capability and approach. A post-contract (or detailed) BEP is the working document produced once the team is appointed; it contains the finalized responsibilities, schedules, and standards the project actually runs on. Knowing which one you are being asked for prevents a lot of confusion during procurement.
How LOD shapes the plan
Level of Development is the backbone of most BEPs because it sets expectations for both geometry and data. LOD 100 is conceptual massing; LOD 200 is generalized systems with approximate sizes; LOD 300 is accurate, dimensioned geometry suitable for coordination; LOD 350 adds the interfaces between systems; LOD 400 is fabrication-ready; and LOD 500 represents verified field conditions. A BEP rarely applies a single LOD across the whole model — instead it assigns an appropriate level to each element by phase, so structural framing might reach LOD 350 for coordination while site elements stay at LOD 200.
For existing-conditions models built from a scan, LOD 300 is a common target: dimensionally reliable geometry a design team can renovate against. Pushing every element to LOD 400 is rarely worth the cost unless fabrication depends on it.
BEP and the common data environment
Most BEPs are written alongside a common data environment (CDE) — the shared, structured space where models and documents live. The plan should name the CDE, describe its folder structure and access rules, and define the states information passes through: work in progress, shared, published, and archived. Under ISO 19650 this workflow is central: the BEP explains how the team will meet the owner’s exchange information requirements, and the CDE is where that exchange actually happens. Spelling this out keeps file versions under control and gives everyone a single source of truth instead of email attachments and local copies.
How a BEP differs from a BIM standard
A BIM standard — whether ISO 19650 or an internal company template — sets general rules meant to apply across many projects. A BEP takes those rules and applies them to one specific job, with its own team, schedule, and deliverables. In practice the standard tells you how your organization does BIM; the BEP records what that means for this project. The two work together, and a good BEP will reference the standards it is built on.
Common BEP mistakes to avoid
- Writing it and shelving it. A BEP only works if teams follow it and update it as the project evolves.
- Vague LOD requirements. “Model everything to LOD 350” without element-by-element clarity leads to over- or under-modeling.
- No agreed coordinate system. The single most common cause of models that will not federate.
- Ignoring the handover. If facilities data is a goal, define the required attributes early — retrofitting them at closeout is painful.
- Leaving out the surveyor. On scan-to-BIM work, capture accuracy has to be specified, not assumed.
The payoff of getting it right
Teams sometimes treat the BEP as paperwork, but the projects that run smoothest are almost always the ones that took it seriously. A clear plan reduces clashes caught late in construction, shortens coordination meetings because everyone works from compatible models, and makes closeout far easier when the owner asks for usable facilities data. On renovation and retrofit work, where the scan-to-BIM model is the foundation for every downstream decision, that upfront clarity is the difference between a model people trust and one they quietly work around.
A simple way to start
If your team has never written a BEP, do not let the long templates intimidate you. Start with the four decisions that cause the most pain when left unanswered: the shared coordinate system, the authoring software and exchange formats, the LOD expected for each major element, and the list of deliverables with dates. Capture those on a single page, circulate it for agreement, and expand from there as the project demands. A short plan that everyone reads and follows beats a fifty-page document that sits unopened in a folder — the goal is shared understanding, not paperwork for its own sake.
Related reading
Bim dimensions 1d to 10d explained
BIM vs CAD: Know the Difference & Choose the Right Tool
Scan-to-BIM Workflow: From Point Cloud to Revit Model, Step by Step
FAQ
Do we need a BEP for a small project? A lightweight one still helps set LOD and formats.
Can you model to our BEP? Yes — we follow your standards.
Do small projects need a BEP?
Even a short, one- or two-page plan helps. It does not have to be exhaustive; it just needs to settle software, coordinate systems, LOD, and deliverables so everyone works the same way.
How long is a typical BEP?
Anywhere from a couple of pages for a simple job to fifty-plus pages for a large public project with detailed information requirements. Length matters less than clarity.
Who approves the BEP?
Usually the owner or their representative, with sign-off from each contributing discipline. Once agreed, it becomes the reference everyone is held to.
When should a BEP be updated?
Whenever the project’s scope, team, or deliverables change materially — a new consultant joins, the LOD targets shift, or the handover requirements are revised. A living BEP is far more valuable than one frozen at kickoff.
Is a BEP required by ISO 19650?
ISO 19650 does not use that exact term, but it requires an equivalent: a plan setting out how the delivery team will meet the appointing party’s information requirements. In practice, a well-built BEP is how most teams satisfy that requirement.
Can the surveying company help write the scan-to-BIM portion?
Yes — and it is a good idea. A provider who captures existing conditions daily can advise on realistic accuracy, resolution, and LOD targets so the plan is achievable and cost-effective.
Get field-verified existing conditions in Pittsburgh
CAD Construct LLC delivers survey-grade 3D laser scanning, as-built drawings, scan-to-BIM, and 360° virtual tours across Pittsburgh & Western PA. Request a free quote or call (800) 967-2627.
0 Comments