LOD (Level of Development) in BIM is a standardized scale that defines how complete and reliable each element in a building information model is at a given project stage. It runs from LOD 100 to LOD 500 and tells everyone on a project what a model element can actually be used for, not just how detailed it looks.

If you have ever received a Revit model and wondered whether a wall thickness was a firm decision or just a placeholder, you have run into the exact problem LOD was created to solve. It gives architects, engineers, and contractors a shared vocabulary for the maturity of model content, so a downstream team knows when a dimension is reliable enough to order steel or pour concrete against. This breakdown covers what each level means, where the framework came from, and how to apply it without slowing your project down.

What Does LOD Actually Define in a BIM Model?

LOD measures the reliability of information, not the visual polish of geometry. A model element can look highly refined on screen and still carry a low LOD if its dimensions, position, and attached data are not yet committed. The framework asks one question for every element: how much can a downstream user trust this, and for what purpose?

That distinction matters because building information modeling is a collaborative process. Multiple disciplines author content into the same federated model at different speeds. The structural engineer might have firm column sizes while the mechanical layout is still conceptual. Without a way to label that gap, a contractor pulling quantities could mistake an early sketch for a construction-ready decision. LOD attaches a clear label to each element so reliance is intentional rather than assumed.

Each level carries three linked ideas: the geometry present, the non-graphic data attached to it, and the authorized uses that the element supports. A door at a given level is not just a shape. It also holds parameters such as fire rating, hardware set, and manufacturer once those values become firm. The authorized use is the practical permission that comes with the element, whether that is running a clash check, generating a quantity takeoff, or releasing it for fabrication. Reading LOD as all three together, rather than geometry alone, is what makes the scale dependable.

The Six Levels of Development Explained

The scale moves from rough concept to verified, as-built reality. Each step adds commitment: dimensions become firm, fabrication data gets attached, and the element earns more authorized uses. Here is what each level represents in practice.

LOD 100: Conceptual

The element is shown as a symbol, a generic mass, or a placeholder. There are no reliable dimensions. You might represent a whole floor as a single block to study massing or run an early area calculation. Treat any geometry here as approximate and tied to other elements for context.

LOD 200: Approximate Geometry

The element now has approximate size, shape, location, and orientation. A wall has a rough thickness and a placement, but the numbers are still subject to change. This level supports schematic design and early system analysis, such as preliminary energy or spatial studies.

LOD 300: Precise Geometry

Quantities, sizes, shapes, locations, and orientations are specific and measurable directly from the model. This is the level most architectural construction documents are built on. A dimension pulled at LOD 300 is a design decision you can rely on, though it does not yet describe how the element connects to others. For many design firms, LOD 300 is the contractual deliverable, since it carries enough certainty to produce drawings and schedules while leaving fabrication detail to the trades.

LOD 350: Connections and Interfaces

Everything from LOD 300, plus the details of how the element interfaces with adjacent systems. Bolt patterns, support angles, penetrations, and clearances appear here. This is the level where multidiscipline clash detection becomes genuinely meaningful, because the model now shows where systems physically meet.

LOD 400: Fabrication and Assembly

The element carries enough detail for fabrication, assembly, and installation. Think shop-drawing-level content: a steel connection modeled with its specific plates and welds, or a precast panel ready for the casting yard. Subcontractors and fabricators author much of this content.

LOD 500: Verified As-Built

The element is a field-verified representation of what was actually built, confirmed for size, shape, location, and quantity. LOD 500 is about verification rather than added geometric detail, which makes it the foundation for facility management and digital twin handover. Note that not every element needs to reach LOD 500. Owners usually request it only for assets they will operate and maintain, such as mechanical equipment, rather than every wall and slab.

LOD Levels at a Glance

The table below summarizes what each level delivers and the kind of decisions it supports.

LOD	Element Content	Typical Use
100	Symbol or generic mass, no reliable dimensions	Massing, early area and cost studies
200	Approximate size, shape, location	Schematic design, system analysis
300	Specific, measurable geometry	Construction documents, quantities
350	Geometry plus connections to other systems	Multidiscipline coordination, clash detection
400	Fabrication, assembly, and installation detail	Shop drawings, fabrication
500	Field-verified as-built element	Facility management, handover

Why Does LOD Matter for Project Delivery?

LOD matters because it turns model reliability into a contractual and coordination tool rather than an assumption. When a project agrees on target levels in advance, every team knows what they are receiving and what they owe. That clarity reduces the disputes that surface when one party relied on geometry the author never intended to be final.

On the coordination side, LOD makes clash detection meaningful. Running a clash check on two LOD 200 systems produces noise, because the geometry is still approximate and a flagged conflict may evaporate as the design firms up. Waiting until the relevant systems reach LOD 350, where connections and interfaces are modeled, gives clash results you can act on. Teams that schedule coordination around LOD targets spend far less time chasing false positives.

LOD also feeds estimating and scheduling. Quantity takeoffs pulled from an LOD 300 model carry a defensible level of accuracy, while the same exercise at LOD 100 produces order-of-magnitude figures at best. Linking LOD targets to project milestones lets cost and schedule data mature at the same pace as the design, so the numbers in a report match the certainty of the model behind them.

Where the LOD Framework Comes From

The numeric scale was defined by the American Institute of Architects in AIA Document G202-2013, which established model content requirements and authorized uses for five levels. The AIA framework set the legal and contractual language, while leaving the discipline-specific interpretation open.

To close that gap, BIMForum built on the AIA definitions and produced the detailed Level of Development Specification, an annually updated reference that illustrates LOD for hundreds of building systems, from cast-in-place concrete to ductwork. BIMForum also introduced LOD 350. For a wider view of how this fits into modeling practice, ArchDaily's overview of BIM covers why the methodology became central to coordinated design.

LOD vs Level of Information Need

One detail worth keeping straight: the international standard ISO 19650 moved away from fixed LOD numbers toward a concept called Level of Information Need. Instead of a single number, it describes the geometric information, alphanumeric information, and documentation required to satisfy a defined purpose, written in plain language. The thinking is that a number like LOD 300 can mean slightly different things to different people, while a purpose-driven requirement states exactly what must be delivered and why.

In practice, the two systems aim at the same goal: making sure information is reliable and fit for the decision it supports. Projects in the United States and much of North America still lean on the numeric LOD scale, while projects following ISO 19650, common across the UK and parts of Europe, frame requirements through Level of Information Need. Plenty of firms work across both, so a model author may map an internal LOD target onto an ISO 19650 information requirement for the same deliverable. Knowing both keeps you fluent across markets and contracts.

How to Apply LOD on a Real Project

LOD is most useful when it is assigned per element and per milestone, not applied as a single label across an entire model. A typical project sets target levels in a BIM Execution Plan: structural framing might reach LOD 350 at coordination, while interior partitions stay at LOD 300 for the same milestone. This element-by-element approach reflects how design actually progresses.

The author of each element also matters. The party who creates content at a given level is responsible for its reliability at that level, which is why G202 ties LOD to model element authorship by milestone. When a fabricator takes a structural element from LOD 300 to LOD 400, authorship and responsibility shift with it. Working from well-structured reference models speeds this up, and a library like the Autodesk Revit pack of BIM models shows how complete projects are organized at construction-document maturity.

A practical way to track all of this is a model element table, often called a LOD matrix. It lists each building system down one axis and project milestones across the other, with the target LOD recorded in each cell along with the responsible author. Schematic design might show structure at LOD 200 and the building envelope at LOD 200, while design development pushes both to LOD 300. The matrix becomes a single reference that the whole team can check, which prevents the common situation where two disciplines assume different levels for the same milestone. Reviewing it at each milestone, rather than only at the start, keeps expectations aligned as the design changes.

Avoid chasing high LOD for its own sake. Pushing every element to LOD 400 early in design adds modeling hours and creates a false impression of certainty, which can lead downstream teams to commit to decisions that are not actually fixed. Match the level to the decision the model needs to support at that moment, and raise it only as the design genuinely matures.

Putting It All Together

Bottom Line: LOD in BIM is a reliability scale, not a detail scale. It tells every party how far they can trust a model element and what they are allowed to do with it, from LOD 100 concept blocks to LOD 500 verified as-builts. Assign it per element and per milestone, tie each level to a real authorized use, and the framework keeps an entire project team honest about what the model truly means.