What Is LOD in Construction? Levels 100 to 500

LOD in construction stands for Level of Development, a standardized framework that defines how much information a digital building model contains at each stage of a project. It gives architects, engineers, contractors, and owners a shared language for describing exactly how reliable and complete a Building Information Model (BIM) is at any given point, from early concept through facility management.

The BIM Forum developed the LOD Specification starting in 2011, with a working group drawn from both design and construction professionals across major disciplines. The specification has been updated regularly since then, with the most recent version released in 2025 (now available in both English and Spanish). It remains one of the most widely referenced standards in the industry for setting model expectations on a project.

The Six LOD Levels, From 100 to 500

LOD uses a numbered scale where higher numbers mean more information and greater reliability. Each level builds on the one before it, adding geometric precision, component detail, and non-graphic data like material specifications or manufacturer information.

  • LOD 100 (Conceptual Design): The model shows basic shapes and sizes without detailed information. Think of a rectangular block representing a building’s overall massing. It communicates design intent and nothing more.
  • LOD 200 (Schematic Design): Elements now include approximate quantities, sizes, shapes, and locations. A wall has a rough thickness and position, but not its exact construction layers. This level supports spatial analysis and early design exploration.
  • LOD 300 (Detailed Design): The model contains specific sizes, shapes, and detailed components with accurate geometry. This is the level used for producing construction documents and coordinating between disciplines like structural, mechanical, and electrical.
  • LOD 350 (Construction Documentation): Elements include detailed assemblies and their interfaces with other building systems. This level was created specifically to bridge the gap between design documents and fabrication-ready models.
  • LOD 400 (Fabrication and Assembly): Models at this level contain enough detail for components to be fabricated or assembled directly from the model. Steel connections, duct fittings, and hardware are all modeled precisely.
  • LOD 500 (As-Built / Facility Management): The model reflects what was actually installed in the real world, verified against field conditions. It serves as the building’s digital record for ongoing maintenance and operations.

Why LOD 350 Exists

LOD 350 deserves special attention because it solves a specific, costly problem. At LOD 300, a model has enough detail for permit drawings and design coordination within a single discipline, but it lacks the information needed for full cross-trade coordination. An HVAC duct at LOD 300 has accurate size and routing, but it may not show how it connects to structural supports or clears a plumbing run nearby.

LOD 400, on the other hand, requires fabrication-level detail that often isn’t available yet when trades need to coordinate their work. LOD 350 fills that gap. At this level, every element is modeled with its quantity, size, shape, orientation, and its interfaces with other building systems. A structural beam, for example, would show not just its profile and position but also the connection plates and clearances that affect adjacent mechanical or electrical components. This makes it possible to catch clashes and resolve conflicts before they become expensive problems on the job site.

Level of Development vs. Level of Detail

These two terms sound similar but measure different things. Level of Detail describes the visual complexity of a 3D model’s geometry: how intricate it looks when rendered or viewed on screen. You can have a visually detailed model that is full of placeholder geometry with no reliable data behind it.

Level of Development, by contrast, describes how much you can trust the information in the model. A wall modeled at LOD 300 isn’t just visually accurate; its dimensions, material layers, and position are reliable enough to use for construction documents. The distinction matters because a highly detailed rendering can give a false sense of completeness. LOD tells project teams what decisions the model can actually support.

How LOD Works in Contracts

LOD isn’t just a technical guideline. It carries real legal weight on projects that use BIM. The American Institute of Architects created a standard protocol form (G202) that uses LOD to define project deliverables. This document includes a Model Element Table that specifies the LOD each building component must reach at each project milestone, along with which team member is responsible for developing it.

One of the most important contractual principles is that project participants can only rely on a model element’s accuracy to the extent consistent with its assigned LOD for that milestone. If a structural column is designated LOD 200 at schematic design, no one should be making fabrication decisions based on its exact dimensions, even if the modeler happened to include more detail than required. This protects teams from liability when model elements contain data that exceeds the minimum requirements for their current LOD.

The protocol also requires that when any team member discovers a conflict in the model, regardless of project phase or LOD, they must promptly notify the responsible parties. This creates a clear chain of responsibility that helps prevent coordination failures from turning into construction errors.

What Each Level Means in Practice

Not every element in a model needs to reach the same LOD at the same time. A project’s BIM execution plan typically assigns different LOD targets to different building systems at different milestones. Structural steel might need to reach LOD 400 before fabrication begins, while interior partitions might only need LOD 300 for construction documents.

At the early stages (LOD 100 and 200), the model supports big-picture decisions: Does the building fit the site? Do the floor-to-floor heights work? Are the major systems in roughly the right locations? These levels are about testing concepts and comparing options, not committing to specifics.

At LOD 300 and 350, the model becomes a coordination tool. Different disciplines overlay their models to identify clashes. A duct routing through a beam’s web, a pipe running through a cable tray’s path: these conflicts get caught digitally rather than discovered during installation. LOD 350 is particularly valuable here because it ensures every trade has modeled enough of their connections and interfaces for meaningful clash detection.

At LOD 400, the model drives fabrication. Steel fabricators, curtain wall manufacturers, and mechanical contractors can extract shop drawings and cutting lists directly from the model. The geometry and connection details are precise enough to manufacture from.

At LOD 500, the model transitions from a construction tool to an operations tool. Field-verified data replaces design assumptions. Installed equipment locations, actual routing paths, and operational information like maintenance schedules and warranty data get embedded into the model. Building owners and facility managers then use this as-built model as a living reference for the building’s entire operational life.

Why LOD Matters for Project Teams

Without a shared understanding of model reliability, teams waste time and money. A contractor who assumes a model is fabrication-ready when it’s only at schematic design will order materials to wrong specifications. A designer who over-develops model elements too early spends hours on detail that will change. An owner who expects facility management data from a model that was only developed to LOD 300 will be disappointed at handover.

LOD eliminates these misunderstandings by making expectations explicit. When a project specifies that structural elements must reach LOD 350 by the coordination phase and LOD 400 by fabrication, every team member knows exactly what they need to deliver and when. It creates accountability, reduces rework, and gives everyone a clear benchmark for measuring progress.