Connecting LOD 100 through 350 to what a model can be trusted for
Last updated:
Key takeaways:
- LOD defines element detail and reliability, 100 to 500.
- Prevents using models beyond their intended stage.
- Scan-to-BIM as-builts typically target LOD 200 to 350.
Level of Development, usually abbreviated LOD, is one of the most useful — and most misunderstood — concepts in BIM. It describes how much you can trust a given element in a model: whether a wall is a rough placeholder or an accurate, buildable representation. For owners and project teams, understanding LOD is the key to specifying a model that fits your needs and your budget, rather than paying for detail you will never use or receiving less than your project requires.
This guide explains LOD from 100 to 350 in plain language, what each level means in practice, and how to use the concept to commission the right model — especially when the model is built from a 3D laser scan of an existing building.
What LOD actually describes
LOD describes the reliability of a model element — how completely its geometry and information are developed. It is not a measure of how “finished” the whole model looks, but of how much confidence you can place in any given component. A higher LOD means an element’s size, shape, location, and relationships are more fully and accurately defined, so you can make decisions based on it.
A crucial point often missed: LOD is applied element by element, not to the model as a whole. In a single model, structural columns might be highly developed while interior partitions are rough, because the project needs precision in one and not the other. This granularity is what makes LOD a practical planning tool rather than a blunt label.
LOD 100: conceptual
At LOD 100, an element is a placeholder — a symbolic or generic representation that shows something exists but not its precise geometry. Think of a mass indicating “a building goes here” or a generic block standing in for equipment. LOD 100 is used in early conceptual design for overall massing, area, and orientation. You would never fabricate or coordinate from it; it exists to communicate intent.
LOD 200: approximate
At LOD 200, elements become generic systems with approximate quantities, size, shape, location, and orientation. A wall is a wall of roughly the right size in roughly the right place, but not yet precisely accurate. LOD 200 supports design development and coordination at a general level. It is useful for understanding how systems relate, but it is not yet reliable enough for fabrication or precise clash detection.
- LOD 100 — conceptualA placeholder. A symbolic or generic shape showing something exists but not its geometry — a mass saying "a building goes here". For early massing, area and orientation only.
- LOD 200 — approximateGeneric systems with approximate quantity, size, shape, location and orientation. A wall roughly the right size in roughly the right place. Useful for understanding how systems relate.
- LOD 300 — preciseAccurate size, shape, location, quantity and orientation, matching design intent. This is what most owners picture when they imagine a usable BIM model.
- LOD 350 — coordinatedAdds the connections and interfaces between elements — not just where a duct and a beam are, but how they meet. The level where field conflicts are actually caught.
- LOD 500 — verified as-builtThe top of the scale, describing an element verified against the constructed reality rather than against design intent.
LOD 300: precise
LOD 300 is where a model becomes genuinely reliable. Elements are modeled with accurate size, shape, location, quantity, and orientation — the geometry matches design intent precisely. This is the level most owners and design teams have in mind when they picture a usable BIM model. LOD 300 supports accurate documentation, quantity takeoffs, and coordination, and it is a common target for design deliverables.
LOD 350: coordinated
LOD 350 adds the connections and interfaces between elements — how systems attach to and interact with one another. At this level, the model includes the detail needed for multi-trade coordination and clash detection, showing not just where a duct and a beam are but how they meet. LOD 350 is often the target for construction coordination, because it captures the interfaces where field conflicts actually occur.
Why LOD matters for your budget
Every increase in LOD takes more time and costs more money, so specifying the right level is a direct budget decision. Asking for a blanket high LOD across an entire model sounds thorough but often wastes money modeling detail no one will use. The smarter approach is to specify LOD by system and area — high where precision matters, lower where it does not. A good modeling partner will help you make these choices so the model fits your actual needs.
- 100–500The full Level of Development scale, from conceptual placeholder to verified as-built
- 300The common target for design deliverables — accurate geometry supporting documentation and takeoffs
- 350The common target for construction coordination, because it captures the interfaces where clashes occur
- 1Decision that most controls scan-to-BIM cost and timeline — setting LOD system by system, up front
LOD and Scan-to-BIM
When a model is built from a 3D laser scan of an existing building, LOD becomes especially important. The scan provides accurate measured geometry, but how much of that detail is translated into intelligent model elements is an LOD decision. You might specify LOD 300 for the architectural shell and structure, LOD 350 for the mechanical systems you need to coordinate, and a lower level for elements that are only for context. Defining this up front, system by system, is the single most effective way to control the cost and timeline of a Scan-to-BIM project while getting exactly the model you need.
Source: BIMForum Level of Development (LOD) Specification.
Common questions about LOD
Is higher LOD always better?
No. Higher LOD costs more and is only worth it where the detail supports real decisions. Matching LOD to purpose is more valuable than maximizing it everywhere.
- Accurate size, shape, location and quantity
- Geometry matches design intent precisely
- Supports documentation and quantity takeoffs
- Coordination at a general level
- A common target for design deliverables
- Everything in LOD 300, plus interfaces
- Shows how systems attach and interact
- Detail needed for multi-trade clash detection
- Captures where field conflicts actually happen
- A common target for construction coordination
What LOD do I need?
It depends on the use. Conceptual planning may need only LOD 100–200; design documentation often targets LOD 300; construction coordination frequently calls for LOD 350 on key systems.
Is Level of Development the same as Level of Detail?
They are related but not the same. Level of Detail describes how much geometry an element shows. Level of Development also covers how reliable the element’s information is, which is why LOD specifications refer to Development.
Can different parts of a model have different LODs?
Yes, and they usually should. LOD is specified element by element, letting you invest detail where it matters and save elsewhere.
LOD gives owners and teams a shared language for how much to trust a model. Understanding levels 100 through 350 — and specifying them system by system — is how you commission a BIM model that fits your project and your budget, especially when building from scan data.
A practical LOD specification example
To see how LOD works in practice, imagine commissioning a Scan-to-BIM model of an office building slated for renovation. You might specify LOD 300 for the architectural shell — walls, floors, ceilings, and openings modeled to accurate size and location — because the design team needs reliable geometry to work from. For the structural frame, you might also target LOD 300 so loads and clearances are dependable. For the mechanical, electrical, and plumbing systems in the ceiling plenum, where the renovation will route new services, you might step up to LOD 350 so the model captures how ducts, pipes, and conduit interface and can be checked for clashes. For furniture and non-essential elements, LOD 100 or 200 is plenty. This mixed specification gives you precision exactly where the project needs it without paying to over-model everything.
- Start from what the model must doThe scan supplies accurate measured geometry. How much of it becomes intelligent model elements is a separate decision, driven by the work the model has to support.
- Set the shell and structureLOD 300 for architectural shell — walls, floors, ceilings and openings to accurate size and location — so the design team has reliable geometry to work from.
- Raise it where you coordinateLOD 350 for the mechanical systems you actually need to coordinate, where interfaces and connections decide whether things fit.
- Lower it where it is only contextElements present purely for orientation do not need the same treatment. Paying to model them precisely is money that buys nothing.
- Write it down before modeling startsDefining this up front, system by system, is the single most effective way to control cost and timeline while getting exactly the model you need.
LOD across the project lifecycle
LOD is not static; it typically increases as a project matures. Early conceptual work lives at LOD 100–200, where massing and general arrangement are all that is needed. As design develops, key elements progress to LOD 300, and as the team prepares for construction, critical systems advance to LOD 350 for coordination. Understanding this progression helps owners avoid a common mistake: demanding high LOD too early, before the design decisions that justify it have been made. Detail added before it is needed often has to be reworked, wasting effort. Letting LOD grow with the project keeps the model efficient and useful at every stage.
How LOD protects everyone on the project
Beyond budget, LOD serves as a communication tool that protects the whole project team. When everyone agrees on the LOD of each system, there is a shared, explicit understanding of what the model can and cannot be relied upon for. A contractor knows not to fabricate from an LOD 200 element; a designer knows an LOD 350 system has been coordinated. This shared language prevents the costly misunderstandings that occur when one party assumes a model is more definitive than it actually is. In that sense, a clear LOD specification is as much about managing expectations and risk as it is about geometry.
Common misconceptions about LOD
Two misconceptions cause most of the confusion around LOD. The first is treating it as a single grade for an entire model — “we want an LOD 350 model” — when in reality LOD is specified element by element and a well-planned model mixes levels deliberately. The second is equating LOD with visual detail or realism. A model can look highly finished on screen while its elements are only approximately accurate, or look plain while being precisely reliable. LOD is about the trustworthiness of the underlying geometry and information, not how polished the rendering appears. Keeping these distinctions clear helps owners specify what they actually need and evaluate what they receive.
- ConceptLOD 100 placeholders communicate intent — massing, area and orientation.
- Design developmentLOD 200 generic systems show how things relate, with approximate size and location.
- DocumentationLOD 300 geometry becomes genuinely reliable, supporting documentation and takeoffs.
- Construction coordinationLOD 350 adds the interfaces, so clash detection catches conflicts before the field does.
A final practical note: when you request a model, ask your provider to document the LOD of each major system in writing. This LOD table becomes a shared reference that everyone can check against, removing ambiguity about what the model represents and protecting both you and the modeling team from mismatched expectations at handover.
Does LOD guarantee accuracy?
Not by itself. LOD describes how completely an element is developed, but accuracy also depends on the source data behind it. This is why building a model from a precise laser scan matters: the scan supplies measured reality, and the LOD specification determines how much of that reality is translated into intelligent, usable model elements. Together, accurate capture and a clear LOD specification produce a model you can genuinely build from — one whose geometry you trust and whose level of detail matches the decisions it needs to support.
Related guides
Planning a project in the Pittsburgh region? CAD Construct LLC delivers 3D laser scanning, Scan-to-BIM, and virtual tours with field-verified accuracy. Request a scanning quote.
Related work: Browse real 3D and BIM models in our BIM portfolio.
0 Comments