What LOD actually describes
Level of Development is one of the most useful — and most misunderstood — concepts in BIM. At its core, LOD answers a deceptively simple question: how much can I trust this element? It is not a measure of how detailed a model looks, but of how reliable its geometry and attached information are for a given purpose. A photorealistic object at an early design stage can still be LOD 100 if its size and position are not yet committed.
That distinction matters because teams downstream make decisions based on what the model promises. The widely referenced specification published at BIMForum exists precisely to give everyone a shared vocabulary for that reliability, element by element.
The levels: 100 through 500
The numbered levels form a maturity ladder. LOD 100 is conceptual — a placeholder mass. LOD 200 carries approximate geometry, size, and location. LOD 300 is precise enough to coordinate and document. LOD 350 adds the interfaces between systems that coordination depends on. LOD 400 is detailed enough for fabrication, and LOD 500 represents a field-verified as-built condition.
LOD is not about how detailed a model looks — it is a promise about how much you can rely on what it tells you.
Crucially, different elements in the same model can sit at different levels at the same milestone. Structure might reach LOD 350 while interior partitions remain at 200. Mapping that mix is part of disciplined delivery, which connects directly to our BIM modeling services.
LOD versus LOI
A frequent source of confusion is the relationship between Level of Development and Level of Information (LOI). LOD captures geometry and data reliability together; LOI refers specifically to the non-graphical information — parameters, classifications, performance data — attached to an element. International guidance maintained by bodies such as the National Institute of Building Sciences helps teams keep the two concepts straight so data deliverables are not lost behind geometry talk.
Keeping LOI explicit pays off at handover, when the data — not the polygons — is often the deliverable. Our piece on IFC and OpenBIM for interoperability looks at how that information survives the move between tools.
Aligning LOD with the BEP
- Define target LOD per element and per project milestone, not globally.
- Record who is responsible for advancing each element's level.
- State LOI requirements alongside geometric expectations.
- Tie LOD milestones to coordination and review gates.
- Capture all of it in the BIM Execution Plan so expectations are contractual.
An LOD schedule only works when it lives in the BEP and everyone signs up to it. Starter templates and checklists are available in our free resources.
Frequently asked questions
What do LOD 100 to 500 mean?
LOD describes how reliable a model element is: 100 is conceptual, 200 is approximate geometry, 300 is precise geometry, 350 adds interfaces between systems, 400 is fabrication-ready, and 500 is verified as-built. Each level defines what you can trust the element for.
What is the difference between LOD and LOI?
Level of Development (LOD) captures how reliable an element's geometry and associated information are together, while Level of Information (LOI) refers specifically to the non-graphical data attached to an element. They are tracked together but describe different aspects of model maturity.
Want help setting LOD targets for your next project? Request a free quote or explore more in our Insights library.
Cadeonn delivers federated Revit models, clash coordination, and LOD-controlled BIM for architects and engineers serving the U.S. market. Extend BIM capacity without long hiring cycles: request a quote or see BIM services.