BIM LOD Explained: Levels of Development 100 to 500

Level of Development (LOD) is a specification language for BIM models. It defines how much geometric and non-geometric information a model element contains and, critically, what that information can be relied upon for.

LOD is defined by the BIMForum LOD Specification (based on the original AIA G202 framework) and is the standard framework used in BIM Execution Plans across the US construction industry.

LOD 100 Conceptual

What it is: A placeholder element. The object exists in the model but its geometry is symbolic or approximate. Think of it as a massing study.

What you can use it for: Area calculations, early energy analysis, project feasibility.

Example: A mechanical unit represented as a box with approximate dimensions. No duct connections, no clearance zones modeled.

LOD 200 Approximate Geometry

What it is: The element has approximate size, shape, location, and orientation. Quantities can be estimated but not relied upon for procurement.

What you can use it for: Design coordination, early clash detection (with caution), preliminary constructability reviews.

Example: A duct run shown as a single line with approximate width/height. Elevation is approximate. Fittings not modeled.

LOD 300 Precise Geometry

What it is: The element is modeled with accurate size, shape, location, and orientation. It reflects the actual specified component. Quantities can be used for procurement.

What you can use it for: Full coordination-level clash detection, RFI management, construction document production, permit drawings.

Example: A duct run at the correct elevation, with the correct dimensions, including fittings and hangers at coordination clearance.

This is the standard coordination LOD for designers.

LOD 350 Coordination-Level Detail

What it is: LOD 300 geometry plus the interfaces and connections between elements hangers, supports, sleeves, and penetrations are modeled.

What you can use it for: Prefabrication coordination, structure-MEP interface coordination, detailed clash analysis.

Example: A duct run including hanger locations, beam clamp types, and sleeve sizes for wall penetrations. This level of detail enables prefab shop drawings directly from the model.

LOD 350 is increasingly required on complex healthcare and pharmaceutical projects where MEP prefabrication is a project strategy.

LOD 400 Fabrication-Ready

What it is: The model is accurate enough to fabricate directly from. Every component, connection, and assembly is modeled to fabrication tolerances.

What you can use it for: Shop drawing production, prefabrication, direct-to-field installation.

Example: A prefabricated MEP rack with every fitting, valve, hanger, and support modeled at actual dimensions and in exact position.

LOD 400 is expensive to produce and should only be required where fabrication from the model is the actual project strategy.

LOD 500 As-Built

What it is: The model reflects field conditions as constructed. It is verified against what was actually built.

What you can use it for: Facility management, future renovation planning, digital twin population.

Example: An updated Revit model that reflects field-verified duct routing, equipment locations, and access panel positions the physical building as it was actually built.

LOD 500 is the most misunderstood LOD. It does not mean "more detailed than LOD 400." It means "verified against reality." A LOD 500 element may have less geometric detail than a LOD 400 fabrication model but is guaranteed to reflect as-built conditions.

How to Use LOD in Your BEP

The BIM Execution Plan (BEP) should include a LOD matrix a table listing every model element by discipline and project phase, with the required LOD at each milestone.

Common LOD mistakes:

• Requiring LOD 400 for everything (over-modeling, high cost, trade resentment)
• Accepting LOD 200 for coordination (under-modeling, coordination gaps, wasted meeting time)
• Not specifying LOD at all (every sub models to their own standard, models do not coordinate)

"A LOD 500 element is not more detailed than LOD 400. It is verified against reality. That distinction matters for every facility manager who will use the model after handover."

Where LOD Comes From: The BIMForum Standard

LOD was originally defined in AIA Document G202-2013, *Project Building Information Modeling Protocol Form*, which introduced five levels (100–500) to provide a shared language for what model elements can be trusted at each project phase. The BIMForum — a non-profit industry organization — subsequently developed the BIMForum LOD Specification, published and updated periodically, which provides element-by-element LOD definitions for hundreds of building components across all major disciplines.

The LOD Specification is available as a free download from the BIMForum website and is the standard reference document for BIM coordination in the US. Most major GC BIM Execution Plans reference the BIMForum LOD Specification by version number to avoid ambiguity about what each LOD means for a given element type.

Frequently Asked Questions About BIM LOD

What is the difference between LOD and LOI in BIM?

LOD (Level of Development) describes the geometric completeness and reliability of a model element — what it looks like and how precisely it represents the actual component. LOI (Level of Information) describes the non-geometric data attached to the element — specifications, manufacturer data, maintenance parameters, cost data. A LOD 300 element with high LOI might include material specs, fire rating, manufacturer model number, and warranty information. A LOD 300 element with low LOI might just be an accurate 3D shape with no data attached. Both dimensions matter, especially for owner handover models used in facility management.

Is LOD 400 required for all MEP coordination?

No — LOD 400 is only required when components will be fabricated directly from the model. MEP coordination requires LOD 300 at minimum; LOD 350 when the project includes prefabrication of racks or assemblies. Requiring LOD 400 across all MEP systems on a project that is not using model-to-fabrication workflows means paying for fabrication-level detail that nobody uses and burning subcontractor modeling resources on geometry the coordination team never needed.

When do LOD requirements change during a project?

LOD requirements typically escalate in phases. During design development, LOD 200–300 is typical for most systems. Before coordination begins in earnest (usually after GMP), the BEP should require LOD 300 for all systems going through clash detection. For prefabricated assemblies, LOD 350–400 is required before shop drawings are issued. The as-built model at handover should be LOD 500 — not more geometrically detailed than construction-phase models, but verified against field conditions.

Who is responsible for defining LOD requirements on a project?

The VDC Manager or BIM Manager at the general contractor sets LOD requirements in the BIM Execution Plan, typically in collaboration with the design team for design-phase models. Each subcontractor is responsible for modeling their scope to the specified LOD by the agreed milestones. The VDC coordinator reviews submitted models for LOD compliance before federating them for clash detection. Accepting an LOD 200 model for a LOD 300 coordination review — without flagging the deficiency — is one of the most common ways coordination programs fail.