What LOD do you need for scan-to-BIM construction documents? Most renovation and retrofit projects need LOD 300, the first Level of Development reliable enough for coordination, clash detection, and quantity take-off, which covers the majority of design-development and construction-document needs. Higher LOD, such as 350 or 400, is reserved for specific systems where MEP coordination or fabrication tolerance requires it.
What LOD Do You Need for Scan-to-BIM: 200, 300, or 400?
LOD 200 gives you approximate quantities, sizes, and spatial relationships – useful for early schematic design, not for construction. LOD 300 models exact geometry, shape, and location for each element, matched to the point cloud within an agreed tolerance – this is the level most construction documents are built on. LOD 350 adds interface and connection detail between systems, useful when different trades need to coordinate around a shared boundary. LOD 400 adds fabrication-level detail, typically scoped for prefabrication or highly complex MEP coordination work. LOD 500 documents the as-operated condition for facility management, which is a different use case from construction documentation entirely.
Answering what LOD you need for scan-to-BIM comes down to how the model will be used, not just the project type. It helps to think of these levels less as a technical scale and more as an answer to a business question: how much can you trust this model to make a decision without going back to check the real building? At LOD 200, the answer is “for planning purposes only.” At LOD 300, the answer is “reliable enough to detect a clash and order material against.” That distinction is why LOD 300 is the default target for most renovation construction documents.
Why Does LOD Matter for Renovation Projects Specifically?
Renovation work carries more existing-conditions risk than new construction, because the design team is working around conditions nobody fully documented. If the scan-to-BIM model is modeled at a lower LOD than the project actually needs, clashes get discovered in the field instead of on the screen, and that turns into change orders. If it’s modeled at a higher LOD than needed, the project pays for detail it never uses.
The cost curve between LOD levels is not linear. Moving from LOD 200 to LOD 300 is a meaningful jump in modeling effort, because the model has to represent exact geometry instead of approximate shapes. Moving from LOD 300 to LOD 350 or 400 is typically a much smaller jump in scanning effort, since the point cloud already contains the underlying accuracy. Most of the added cost at higher LOD comes from modeling time, not capture time, which is one more reason to scope LOD by element category instead of blanket-applying the highest level across the whole building.
How Do You Decide Which LOD to Request?
Set LOD by element category, not by the whole building. A renovation might need LOD 300 for structure and architectural elements, but LOD 350 for the mechanical room where new equipment has to fit into a tight existing space. Define this in writing with the documentation provider before modeling starts, so everyone is scoping the same deliverable.
A useful exercise is to walk through the project’s known pain points before setting LOD. If the renovation involves adding new mechanical equipment into an existing space, that room needs a higher LOD than a corridor that is only getting new finishes. If the project involves structural work, the structural elements need enough detail to support engineering calculations, not just visual reference. LOD should follow risk, not habit.
Who Should Be Involved in Setting LOD Requirements?
LOD decisions work best as a shared conversation between the architect, the MEP engineer, and whoever is managing the documentation capture, rather than a decision made by one party in isolation. The architect knows which spaces carry design risk. The MEP engineer knows which systems need tighter coordination tolerance. The documentation provider knows what is realistic to capture and model within the project timeline. Leaving any one of those perspectives out tends to produce a scope that is either overbuilt in the wrong places or underbuilt where it actually matters.
This conversation is worth having early, before a request for proposal goes out to a documentation provider. A scope built around specific, agreed LOD requirements per element category gets more accurate and comparable proposals than a generic request for “a scan of the building.”
How Does LOD Interact With the Deliverable Format?
LOD and deliverable format are related but separate decisions. A point cloud alone has no LOD in the traditional sense, it is raw measured data. LOD applies once that data is modeled into discrete elements, whether in Revit, another BIM platform, or a 2D CAD drawing. A project can request a high-accuracy point cloud alongside a lower-LOD model for most of the building, with select elements modeled to a higher LOD where the coordination risk justifies it. Being clear about this distinction when scoping the project avoids confusion between “how accurate is the scan” and “how detailed is the model.”
What Happens Next / How RCE Handles This
RCE scopes LOD by element category during the pre-capture conversation, working from the design team’s actual coordination needs rather than defaulting to one LOD across the board. The point cloud is captured once, at survey-grade accuracy, so the model can be built to whatever LOD each element requires without a second site visit. QC review confirms the delivered model matches the agreed tolerance before handoff, and the scope document records exactly what LOD was agreed for each element category, so there is a written reference if a question comes up mid-project.
Frequently Asked Questions
Q: Is LOD 300 enough for a renovation project?
A: For most architectural and structural elements, yes. Complex MEP coordination or historic building work sometimes needs LOD 350 or 400 for specific systems.
Q: What’s the difference between LOD and LOA?
A: LOD (Level of Development) describes how much design detail and reliability a model element has. LOA (Level of Accuracy) describes how closely the captured geometry matches the physical building. They’re related but not interchangeable, and a scope should specify both.
Q: Does a higher LOD always mean better documentation?
A: No. Higher LOD costs more time and budget. The right LOD is the one that matches what the design and coordination process actually needs for each element, not the highest number available.
Q: Can LOD be set differently for different parts of the same building?
A: Yes, and it usually should be. Structure and envelope might be LOD 300 while a mechanical room or a historic facade element is scoped to LOD 350 or 400.