"What LOD is this model?" is one of the most common questions asked on a BIM project, and one of the most commonly answered incorrectly — not because people don't know the LOD scale exists, but because LOD is frequently treated as a single number applied uniformly across an entire model, when it's actually meant to be assessed element by element, and covers two distinct dimensions — geometric detail and embedded information — that don't always progress together.
Understanding what each LOD tier actually means in practice, with concrete examples rather than abstract definitions, is essential for anyone specifying, reviewing, or contracting for BIM deliverables, since a mismatch between what a client expects at a given LOD and what a modeling team actually delivers is one of the most common sources of dispute on Indian BIM projects.
What LOD Actually Measures
Level of Development (LOD), as defined by the American Institute of Architects' LOD framework, widely adopted internationally including in India, describes the degree to which a model element's geometry and attached information can be relied upon by project team members. It has two components that are often conflated but are genuinely distinct: geometric detail (how visually and dimensionally precise the element's shape is) and information content (what data, beyond geometry, is attached to the element — material specifications, manufacturer data, performance characteristics). An element can have high geometric detail but minimal attached information, or vice versa, which is why a single "LOD 300" label applied loosely to an entire model can be misleading without clarifying which dimension, or both, that designation actually refers to for specific element categories.
| LOD level | Geometric detail | Typical project stage | Concrete example: a structural column |
|---|---|---|---|
| LOD 100 | Conceptual — generic massing, symbol, or placeholder | Concept design | A generic box representing a column's approximate location and footprint, no specific dimensions |
| LOD 200 | Approximate geometry with generalised size, shape, and location | Schematic design | A column sized approximately, generic material, general location confirmed |
| LOD 300 | Precise geometry, accurate size, shape, and location for coordination | Design development / construction documentation | A column with exact dimensions, precise location, ready for clash detection |
| LOD 350 | LOD 300 detail plus interfaces with other building systems | Construction documentation, coordination-heavy projects | The same column, now showing connection details to beams and slabs |
| LOD 400 | Fabrication-level detail, ready for construction | Shop drawing / fabrication stage | The column modeled with exact fabrication details — bolt holes, weld locations |
| LOD 500 | As-built — verified field condition | Post-construction / handover | The column's model updated to reflect exactly what was actually built and verified on site |
Why LOD 350 Exists as a Separate Tier
LOD 350 is sometimes treated as an unnecessary intermediate step between 300 and 400, but it serves a genuinely distinct purpose on coordination-intensive projects: it specifically addresses how an element interfaces with adjacent systems — connection details, interface geometry — without requiring the full fabrication-level detail LOD 400 demands. On projects with heavy MEP coordination, requiring LOD 350 specifically for interface-critical elements (rather than jumping straight from 300 to full fabrication detail) can be a more efficient allocation of modeling effort, since it captures what's needed for rigorous coordination without the added cost of fabrication-level detail on elements that don't yet need it.
Why LOD Matters Contractually, Not Just Technically
LOD designations increasingly appear explicitly in BIM Execution Plans and, on more sophisticated Indian projects, in contract documents themselves — specifying which LOD is required for which element categories at which project stage. This contractual dimension matters because LOD mismatches are a common and costly source of dispute: a client expecting LOD 400 fabrication-ready detail from a deliverable contracted at LOD 300 will be dissatisfied with a model that, while entirely compliant with what was actually contracted, doesn't meet their (incorrectly calibrated) expectation. Clear, specific LOD specification at contract stage — ideally down to the level of individual element categories, not just a single blanket project-wide LOD figure — is one of the most effective, low-cost ways to prevent this kind of expectation mismatch from becoming a costly dispute later in the project.
A Practical Scenario: LOD Mismatch in Practice
Consider a commercial office project in Gurugram where the BIM Execution Plan specifies LOD 300 for structural elements at the construction documentation stage — entirely standard and appropriate for that project phase. The client's facility management team, reviewing the model ahead of handover planning, expects to find manufacturer data and maintenance specifications for structural elements, information that LOD 300 doesn't require and typically doesn't include, since that level of operational data is more commonly associated with LOD 500 as-built deliverables specifically prepared for facility management handover. The resulting friction isn't really a modeling quality problem — the LOD 300 structural model may be entirely correct and complete for its contracted purpose — it's a specification and expectation-setting gap, where nobody clarified early in the project that facility management data requirements needed a distinct LOD 500 deliverable, separately scoped and budgeted, rather than assuming it would simply emerge from the construction documentation model.
Practical Guidance for Specifying LOD Correctly
Rather than specifying a single LOD figure for an entire project, effective BIM Execution Plans specify LOD by element category and project stage — structural elements at LOD 300 for construction documentation, MEP elements at LOD 350 given coordination needs, with an explicit LOD 500 as-built deliverable scoped separately for handover, rather than assumed to be a byproduct of the construction model. This level of specificity takes more effort to define at project kickoff, but it is precisely the effort that prevents the kind of mismatched expectations that otherwise surface, expensively, much later in the project when they're harder and costlier to resolve.