If you're a BIM manager scoping a tender, a client trying to understand why one bid quotes LOD 400 at nearly double the modelling hours of another, or a fabricator who keeps receiving models that look detailed but can't actually be built from, this is the distinction you need to get right before the contract is signed, not after the model turns out to be the wrong deliverable for what you needed.
LOD (Level of Development) numbers get thrown around loosely on Indian tenders, treated almost as a marketing adjective rather than a precise technical specification. The jump from 300 to 400 in particular is not a matter of "more detail" in some vague, general sense - it's the specific difference between a model built to show design intent accurately and one built to be handed directly to a fabricator who will cut steel, bend duct, or cast precast elements from exactly what's in the file. Confusing the two, or not being precise about which one is actually being paid for, is one of the more quietly expensive mistakes on an Indian BIM project.
What the LOD Scale Actually Represents
LOD 300: accurate enough to coordinate, not accurate enough to build from directly
At LOD 300, a modelled element has precise size, shape, location and orientation. If you measure a wall, a duct run, or a column in the model, that measurement will match the design intent accurately enough to check against other disciplines - to see whether a beam clashes with a duct, whether a column lines up with the grid, whether a stair fits in the available shaft. What LOD 300 does not include is the connection detail, the exact fixing method, or the fabrication tolerances that a factory or steel yard would need to actually manufacture the element. It's a coordination-grade model, and for the large majority of a typical building - finishes, general architectural elements, most of the structural frame - that's exactly the right level of detail to pay for.
LOD 400: the model becomes the shop drawing
LOD 400 adds fabrication, assembly and installation detail - connection types, exact bolt patterns, precise dimensions accounting for real-world manufacturing tolerance, and enough information that a fabricator genuinely doesn't need a separate 2D shop drawing to do their job. This is a fundamentally different modelling task, not an incremental refinement of LOD 300. Modelling a structural connection at LOD 400 means the BIM technician needs to understand how that connection will actually be fabricated and erected, not just what it needs to look like for coordination purposes. That's why the jump from 300 to 400 typically adds somewhere between 35% and 60% to the modelling hours for whatever package is being taken to that level - it's genuinely more specialised, more time-consuming work, done by people who understand fabrication, not just design intent.
| LOD | What it represents | Typical modelling-hour premium | Where it's specified |
|---|---|---|---|
| LOD 200 | Approximate size, shape and location - generic placeholder geometry | Baseline minus | Early concept/feasibility only |
| LOD 300 | Precise size, shape, location and orientation - accurate for coordination, not fabrication | Baseline | Design development, tender documentation, clash coordination |
| LOD 400 | Fabrication, assembly and installation detail - connections, fixings, exact dimensions | +35% to 60% modelling hours | MEP fabrication packages, structural steel, precast, curtain wall |
| LOD 500 | As-built, field-verified - matches constructed reality exactly | +15-25% over LOD 400 (verification pass) | Handover, facility management |
When the LOD 400 Premium Is Actually Worth Paying
The honest answer is: on most of a typical building, it isn't. A residential tower's internal partitions, most architectural finishes, and general MEP distribution rarely justify LOD 400 - LOD 300 gives you everything you need to coordinate cleanly and build from with normal site-level interpretation, the way construction has always worked. Where LOD 400 earns its premium is specifically on the packages that are actually being fabricated off-site: structural steel connections that a steel yard needs to cut and drill from, precast panels that a factory needs to cast to exact tolerance, curtain wall systems where panel-to-panel connection detail determines whether the facade actually fits together on site, and dense MEP risers where prefabricated spool pieces need to be manufactured before they ever reach site.
A hospital MEP riser package - a case where the premium pays for itself many times over
Picture a mid-size hospital project where the central MEP riser - carrying medical gas, chilled water, and multiple redundant electrical feeds through a tight vertical shaft - is modelled to LOD 400 specifically so that prefabricated spool sections can be manufactured off-site and craned into position during a narrow structural opening window. The additional modelling cost for that one riser package, relative to modelling it at LOD 300, is real - but it's a small fraction of what a single on-site clash discovery would cost once that shaft is poured and the prefabricated sections don't fit. This is precisely the kind of package where the LOD 400 investment isn't really optional if prefabrication is the plan at all; LOD 300 tolerances are simply too loose for a factory to build from with any confidence.
A residential tower where LOD 400 was requested for everything, and shouldn't have been
Contrast that with a fairly ordinary residential tower where a client, having heard that "higher LOD means better quality," specifies LOD 400 across the entire model in the tender documents. The BIM consultancy bidding on the work now has two honest choices: quote the actual cost of doing this (which will be substantially higher than the client is expecting, since almost none of a standard residential tower genuinely needs fabrication-level detail), or quietly deliver something closer to LOD 300 under an LOD 400 label and hope nobody checks closely. Neither outcome serves the client well, and both are avoidable if the tender had specified LOD 400 only for the packages that actually warranted it - the structural transfer beams, perhaps, or a precast facade element - rather than blanket-specifying it across a model where most of the content simply doesn't need that level of detail.
How LOD Gets Verified, or Doesn't
One of the more uncomfortable realities of LOD specification in India is that claimed LOD is frequently self-certified rather than independently verified. A model delivered as "LOD 400" may or may not actually contain the connection-level detail that label implies, and unless the client or a third-party BIM auditor is specifically checking model content against the LOD 400 definition, there's often no real verification step before the model gets used for procurement or fabrication decisions downstream. This is exactly where disputes tend to surface - a fabricator discovers mid-production that the "LOD 400" model doesn't actually have the connection detail they need, and the resulting delay and rework becomes a contractual argument about what was actually promised versus what was actually delivered.
The practical fix is straightforward even if it's underused: define LOD requirements per package rather than per project, write the specific LOD 400 elements into the contract explicitly (not just "LOD 400 where applicable"), and where the stakes are high enough - a large precast or structural steel package, for instance - consider an independent model audit before the model is released for fabrication rather than discovering gaps only once manufacturing has started.