What is LOD in BIM, and why it matters when you're checking as-built

Looking up through an unfinished steel structural frame against a clear blue sky.

If you've sat in a coordination meeting and heard someone say "that wall is only LOD 300, don't hold me to the dimension," you already know LOD causes arguments. It's one of the most misunderstood terms on a construction project, and it matters more once you start comparing what got built against the model.

LOD, in plain terms

Level of Development (LOD) describes how reliable a BIM element's geometry and data are at a given stage, on a scale most people shorthand as LOD 100 through 500. A duct modeled at LOD 300 might be positioned to real-world coordinates but not yet sized or routed exactly as it will be fabricated. The same duct at LOD 400 should match the shop drawing: dimensions, connections, and often the fabrication details are locked in.

The AIA's LOD spec is the usual reference, and most owner contracts cite specific LOD targets by discipline and phase. Structural steel might be required at LOD 350 at permit and LOD 400 before fabrication. MEP routing often stays at LOD 300 well into construction because the trade contractor hasn't finalized layout yet.

LOD tells you what the model is supposed to represent. It doesn't tell you what got built in the field. Those are two different questions, and conflating them is where as-built verification goes sideways.

LOD 300 vs LOD 400: what changes

The jump from LOD 300 to 400 changes what you're allowed to assume about an element's final dimensions and connections.

At LOD 300, an element's general size and location are set, but treat the exact dimensions as provisional. A beam might sit within a few inches of its final position, with bolt patterns and connections still pending. A 4-inch offset between a drone-captured point cloud and an LOD 300 model can be exactly what that LOD level predicted, rather than evidence of a field problem.

At LOD 400, the model is supposed to be fabrication-accurate. Connections, assembly details, and precise dimensions are modeled as they will be installed. A deviation against an LOD 400 element is a stronger signal that something in the field doesn't match the design intent, because the design intent itself is specific enough to hold the as-built to.

That distinction decides what you do with a flagged deviation. On an LOD 300 element, a few inches of variance is expected and rarely worth a change order. On an LOD 400 element, the same variance means the model's promise wasn't kept in the field. Comparing a reconstructed surface against an LOD 300 curtain wall and flagging every inch of variance is a good way to generate noise your team stops reading. Comparing the same surface against an LOD 400 steel connection and ignoring a 2-inch miss is how a clash makes it to final inspection.

Why this matters for as-built checks specifically

Most teams discover LOD mismatches the hard way, during a punch walk or a formal as-built survey at project close, when the gap between model and field has already been built around, finished over, and is now expensive to fix. By the time a surveyor flags a column that's 3 inches off, the slab above it is poured.

A monthly comparison between the current site condition and the design model, filtered to the elements that matter at their real LOD, catches that same deviation while it's still a change order instead of a demolition. That's the case for checking as-built condition against the model on a cadence instead of waiting for the formal survey.

Before you run any as-built comparison, confirm with your BIM lead which elements are specified past LOD 300. There's no point flagging a foundation wall's position against a model that was never meant to hold that tolerance. Spend that effort on the LOD 350 and LOD 400 elements, where a deviation means something, not a modeling artifact.

As-Built Compare registers a drone-captured site surface against your design model monthly and flags the elements that fall out of tolerance, so the gap shows up while it's still a quick fix instead of a line item in the closeout report.

If you're tired of finding out about deviations at project close, it's worth a look.

← Back to the blog