Level of Development is one of the most misunderstood concepts in scan-to-BIM. Project teams routinely specify LOD 300 or 350 for every element in the model without considering whether that level of detail actually serves their project goals. The result is bloated models, extended timelines, and budgets that could have been spent on work that moves the project forward.
Understanding what each LOD level actually delivers, and matching that to your coordination and construction needs, is one of the highest-value decisions a VDC manager can make on a scan-to-BIM project.
LOD 200 gives you approximate quantities, size, shape, and location of elements. For many scan-to-BIM applications, this is exactly what you need. Space planning, feasibility studies, and early-phase coordination all work effectively with LOD 200 models.
A common scenario: you need to verify that a proposed mechanical room layout will fit within an existing space. LOD 200 representation of structural elements and major existing utilities gives you the spatial envelope. You do not need exact flange widths or precise insulation thicknesses for that analysis.
The cost difference is significant. LOD 200 modeling typically runs 40-50% less than LOD 300, and delivery timelines compress by a similar margin. For projects where the scan-to-BIM model serves as a reference rather than a coordination document, LOD 200 is the right answer.
LOD 300 delivers specific system geometry with accurate size, shape, location, and orientation. This is the level most MEP coordination workflows require. Clash detection at LOD 300 produces actionable results because elements are sized and positioned accurately enough to identify real conflicts.
For scan-to-BIM specifically, LOD 300 means pipes are modeled at their actual diameter, ducts at their actual cross-section, and structural members at their actual profile. Connections, supports, and accessories may be simplified or omitted, but the primary geometry is dimensionally accurate.
Most general contractors and MEP coordinators should default to LOD 300 for scan-to-BIM work that feeds into active coordination. It provides the accuracy needed for clash detection without the overhead of modeling every hanger rod and valve.
LOD 350 adds supports, connections, and interfaces between systems. This level is appropriate when the scan-to-BIM model will be used for fabrication support, installation sequencing, or detailed spatial coordination in congested areas.
Mechanical rooms, interstitial spaces, and ceiling plenums with tight clearances may justify LOD 350 for specific zones even when the rest of the building is modeled at LOD 300. This targeted approach delivers high detail where it matters without inflating the entire model.
The key question is whether downstream users will actually leverage the additional detail. If your coordination team runs clash detection but does not use the model for fabrication or installation planning, LOD 350 is paying for detail that sits unused in the file.
The most cost-effective scan-to-BIM projects use mixed LOD strategies. High-complexity zones get LOD 300 or 350. Open areas, storage spaces, and zones with minimal MEP get LOD 200. The overall model serves its coordination purpose without carrying unnecessary geometric weight.
Defining these zones before modeling begins is critical. A clear LOD map, typically shown on a floor plan with color-coded zones, prevents scope creep and sets expectations with the modeling team. It also prevents the common problem of a modeler spending three days detailing a utility corridor that only needed generic representation.
Effective LOD specifications in scan-to-BIM RFPs include three components: the default LOD for the project, any zone-specific LOD overrides, and explicit descriptions of what each LOD level includes for each discipline. Generic statements like "model to LOD 300" leave too much room for interpretation.
Include sample images or reference models showing acceptable deliverables at each LOD level. This eliminates the ambiguity that leads to rework requests and scope disputes between the project team and the scan-to-BIM provider.