BIM LOD Levels Explained: 100, 200, 300, 400, 500

Explore BIM LOD levels 100 to 500, their importance, and applications in project lifecycle management.

Introduction

If you have spent any time working with BIM, you have almost certainly encountered the acronym LOD. You may have heard it used in a contract clause, seen it listed in a BIM Execution Plan, or watched colleagues debate whether a structural column is “LOD 300 or LOD 350.” And if you have ever felt uncertain about what those numbers actually mean — or noticed that different people seem to use the term differently — you are not alone.

Level of Development (LOD) is one of the most important and most misunderstood frameworks in the BIM world. It defines how much information — geometric and non-geometric — can be relied upon in a building model element at a given stage of a project. Getting LOD right has direct consequences for contract liability, clash detection quality, fabrication accuracy, and the long-term value of a model for facility management.

The confusion is compounded by the fact that the acronym LOD originally stood for Level of Detail in early BIM conversations, then was redefined to mean Level of Development by the American Institute of Architects in 2008 with the publication of AIA E202, a standard contract exhibit for BIM projects. The shift in terminology was deliberate: “detail” describes only geometry, while “development” captures both the geometry and the information reliability of a model element. That distinction matters enormously in practice.

The framework was later refined and expanded by the BIMForum, a North American industry coalition, which published the first edition of its LOD Specification in 2013. The BIMForum LOD Spec has been updated regularly since then and has become the de facto industry standard referenced in BIM contracts, project protocols, and employer information requirements (EIR) across the United States and increasingly worldwide.

This guide works through every LOD level in practical depth, clarifies the related concepts of LOG and LOI, explains how LOD is applied in real BIM workflows, and addresses the most common misconceptions that cause problems on projects.

LOD vs LOG vs LOI: Getting the Terminology Right

Before diving into the individual LOD levels, it is worth pausing on a set of related terms that are frequently conflated, even by experienced BIM professionals.

Level of Development (LOD) is the umbrella term. It describes the overall reliability of a model element — combining both its geometric representation and the information attached to it. When a contract says “all structural columns shall be modeled to LOD 350 by the end of design development,” it means both the geometry and the data must meet a defined threshold. LOD is defined per element, not per model.

Level of Geometry (LOG) refers specifically to the visual or geometric complexity of a model element. A LOG 100 element might be a simple extruded box representing a wall. A LOG 400 element of the same wall would include precise layer thicknesses, accurate reveals, embedded components, and any surface features that affect fabrication. LOG captures what the element looks like in 3D space and how accurately it represents physical reality.

Level of Information (LOI) refers to the non-geometric data attached to a model element — manufacturer names, product codes, fire ratings, acoustic ratings, structural properties, maintenance intervals, warranty data, and so on. An element can have high geometry detail (LOG 400) but minimal information (LOI 100), or vice versa. A placeholder mass in an early energy model might carry accurate thermal properties (high LOI) while being geometrically simplistic (low LOG).

Understanding this three-way distinction matters because different project stakeholders care about different aspects. A quantity surveyor primarily needs reliable LOI (areas, volumes, specifications) to produce accurate cost estimates. A clash detection coordinator needs accurate LOG (geometry, location, orientation). A facility manager needs rich LOI (product data, maintenance schedules, O&M documents) attached to verified geometry.

In the BIMForum LOD Specification, LOD encompasses both LOG and LOI considerations, but the individual element definitions clarify which aspects are required at each level. When reviewing a BIM contract or execution plan, always check whether LOD is being used in the combined sense or whether the author is really only specifying geometry requirements.

The BIMForum LOD Specification

The BIMForum is a working group affiliated with the Associated General Contractors of America (AGC). Its LOD Specification provides element-by-element guidance on what a model must contain at each LOD level. Rather than offering abstract definitions, the Spec includes descriptions and representative images for hundreds of specific building element types across architectural, structural, and MEP disciplines.

The Spec is free to download from the BIMForum website and is updated periodically to reflect industry practice. At the time of writing, it covers elements from foundations and concrete structure through curtain walls, mechanical systems, electrical distribution, and site work.

The BIMForum LOD Spec is important for several reasons:

It provides a common language that designers, contractors, and owners can reference without ambiguity.
It is written into BIM contracts and BIM Execution Plans (BEP) by reference, meaning parties agree that when they write “LOD 300” they mean the BIMForum definition, not their own interpretation.
It acknowledges that not every element type needs the same level of development at every project phase, allowing teams to create nuanced Model Element Tables (MET) that assign different LODs to different elements.
It distinguishes LOD 350 as a formal level, which many earlier frameworks did not, reflecting the practical reality of construction coordination workflows.

A BIM Execution Plan (BEP) is the project document — agreed between all parties — that specifies who models what, at what LOD, by what date, and in what software format. The BEP typically includes a Model Element Table that maps each element type to an LOD at each project milestone. Without this kind of explicit agreement, teams end up working to different expectations, which is one of the most common sources of BIM-related disputes on projects.

LOD 100: Conceptual

LOD 100 is the starting point. At this level, model elements are conceptual placeholders — they communicate intent and volume but are not meant to represent actual building components with any geometric precision.

A LOD 100 element is typically a simple mass, symbol, or schematic representation. A wall might be a solid rectangular extrusion with no layers, no thickness differentiation, and no material specification. A structural column might be represented by a vertical line or a generic cylinder. An HVAC unit might be a box with a label. These elements are often not even modeled as building elements in the conventional sense — they may be generic masses created for volumetric studies.

What information is typically attached at LOD 100:

Approximate area, volume, or height (for cost estimating purposes)
Conceptual system type (e.g., “mechanical system — VAV”)
No manufacturer, specification, or dimensional accuracy

When to use LOD 100:

Pre-design and feasibility studies
Massing studies to test building envelope concepts against site constraints
Early energy modeling using whole-building loads rather than system-level geometry
Area calculations for programming (gross floor area, rentable area)
Early cost estimating using cost-per-square-meter benchmarks

Practical example: At the feasibility stage for a mixed-use development, the architect creates a site massing model in Revit using generic mass families. Each floor plate is a single extruded mass with an area parameter attached. The cost consultant uses these area figures — not geometric takeoffs — to produce an order-of-magnitude estimate. No structural grid, no room layouts, no wall types: just massing. This is LOD 100 in action.

The important principle at LOD 100 is that any information derived from these elements carries significant uncertainty. A cost estimate based on LOD 100 might carry a +/-30% contingency. That is appropriate and expected.

LOD 200: Approximate Geometry

LOD 200 elements are modeled with generic geometry that represents approximate size, shape, quantity, and location. The elements are recognizable as specific building systems or components, but they use placeholder or schematic representations rather than the actual product or assembly.

The key word in the BIMForum definition is “approximate.” At LOD 200, you know roughly where something is and roughly how big it is, but you cannot measure directly from the model and trust the result.

What LOD 200 looks like in practice:

A wall modeled with a single-layer generic material at the approximate overall thickness, with no distinction between framing, sheathing, insulation, and finish layers
A rectangular duct that represents the approximate cross-sectional area of an HVAC supply duct but is not a specific duct type from a manufacturer
A structural beam at the approximate depth required by engineering, without a specific section size confirmed by structural analysis
A door modeled as a solid panel with approximate frame dimensions, without hardware, glazing details, or specific door family

What information is typically attached at LOD 200:

Approximate quantities and dimensions
Preliminary system types (e.g., “gypsum board partition”)
Schematic-level specifications

When to use LOD 200:

Schematic design (SD) phase
Preliminary spatial coordination — checking that major systems fit within available zones
Preliminary cost estimating with more refined unit rates than LOD 100
Early energy modeling using system-level geometry

Practical example: A mechanical engineer models the main air handling units and primary ductwork runs in a commercial office building during schematic design. The AHU is a generic box at the approximate height, width, and depth based on preliminary load calculations. The supply duct main is a rectangular duct at an approximate size. The model is shared with the structural engineer to check for major conflicts with primary beams. Neither party expects precise dimensions — the goal is confirming that the routing concept is feasible. This is LOD 200 coordination.

LOD 300: Precise Geometry

LOD 300 is the level at which model elements become geometrically accurate and measurable. At LOD 300, the quantity, size, shape, location, and orientation of a model element are specific enough that measurements taken directly from the model can be relied upon for construction documentation purposes.

This is the level at which the model becomes the primary source of dimensional control for a building system, and it is the minimum level required for meaningful clash detection between disciplines.

What LOD 300 looks like in practice:

A wall modeled with distinct layers: metal stud framing at a specific gauge and spacing, gypsum board at a specific thickness, insulation at a specific R-value and type, and a finish layer — each at accurate thickness, resulting in a precise overall partition thickness
A structural beam modeled as a specific wide-flange section (e.g., W410x75) at the correct elevation, span, and connection points
A door modeled as a specific family with the correct frame profile, leaf thickness, swing direction, hardware blocking, and clearance requirements
An HVAC duct modeled at the correct size, from a specific system type, at the correct elevation and routing — coordinated with other systems

What information is typically attached at LOD 300:

Specific material and product types (not necessarily a manufacturer, but a defined specification)
Dimensions accurate enough to produce construction documents
Orientation, location, and elevation verified against the design intent

When to use LOD 300:

Design development (DD) and construction documents (CD) phases
Clash detection and multi-discipline coordination
Generating accurate quantities for procurement and cost control
Producing 2D drawings extracted from the model (plans, sections, elevations)

Practical example: The architectural team completes the interior partition layout for a hospital ward floor. Every partition is modeled with its specific wall type (Type A1: 2-layer 5/8” gypsum board each side, metal stud framing, sound batt insulation). Doors are placed as specific families with correct swing directions and fire-rating parameters. The structural and MEP models are linked and coordinated in a federated model. A clash detection report identifies 23 hard clashes between MEP services and structural beams — all detectable because the geometry is precise. This is the workflow that LOD 300 enables.

LOD 350: Construction Documentation (The Overlooked Level)

LOD 350 was formally added to the BIMForum LOD Specification to address a gap that practitioners had long recognized: there is a meaningful difference between a geometrically accurate element (LOD 300) and an element that is ready to coordinate with adjacent building systems, including the connections, supports, hangers, and interfaces that actually make construction possible.

At LOD 350, model elements include information sufficient for the coordination of the element with other building systems. This means that not only is the element itself precisely modeled, but also the attachments, supports, and interfaces between systems are represented.

What LOD 350 adds over LOD 300:

Support and hanger locations for MEP services (pipe supports, duct hangers, cable tray supports)
Pipe and duct insulation, represented as a modeled element affecting spatial clearances
Structural connections modeled at sufficient detail to coordinate with attachments (bolt groups, base plates, clip angles)
Sleeves and penetrations through structural elements, with sizes and locations required by MEP systems
Coordination geometry showing interface conditions between architectural, structural, and MEP elements

When to use LOD 350:

Detailed multi-discipline coordination before construction
Producing coordinated installation drawings used by subcontractors in the field
Specialty contractor coordination (structural steel fabricators, mechanical contractors, fire protection)

LOD 350 is arguably the most important level for construction coordination, yet it is the most frequently omitted from early-stage BIM Execution Plans. Many project teams only realize they need LOD 350 when they discover that LOD 300 models are missing the supports and connections that generate the real coordination conflicts on site.

Practical example: A mechanical subcontractor receives the engineer’s LOD 300 duct model and discovers that there is no room for duct insulation or hangers between the duct and the bottom of the structural deck. The engineer modeled the duct itself accurately (LOD 300) but did not model insulation or support clearances. At LOD 350, the insulation jacket would be a modeled element and hanger drop locations would be included — making this conflict detectable in the federated model before any work was done in the field.

LOD 400: Fabrication

LOD 400 is the shop drawing level of BIM. At this stage, model elements contain sufficient detail and information for the actual fabrication and installation of building components. LOD 400 is primarily the domain of specialty contractors and fabricators, not designers or general contractors, and it is produced during the pre-construction or construction phase rather than during design.

What LOD 400 looks like in practice:

A structural steel connection modeled with specific plate sizes, bolt diameters, bolt spacing, weld sizes and types, and surface preparation specifications — directly from the fabricator’s shop drawings
A precast concrete panel with all embeds, lifting anchors, connection plates, reinforcement layout, and surface finish specifications modeled at full detail
A custom HVAC air handling unit modeled from the manufacturer’s submittals, including internal component layout, access door locations, and connection point sizes and types
A complex MEP assembly prefabricated off-site, with all fittings, valves, gauges, and supports included at actual dimensions

What information is typically attached at LOD 400:

Manufacturer and product model number
Fabrication dimensions (exact, not approximate)
Installation sequence information
Structural capacity data
Specific material grades, bolt grades, weld specifications

When to use LOD 400:

Fabrication of structural steel, precast concrete, prefabricated MEP assemblies, curtain wall systems
Off-site prefabrication and modular construction
Producing fabrication drawings and cutting lists directly from the model
Specialist trade contractors working from model-generated shop drawings

Practical example: A structural steel fabricator receives the structural engineer’s LOD 350 model and uses it as the starting point to produce a LOD 400 fabrication model. The fabricator adds specific bolt connections, gusset plates, shear tabs, and weld details to every connection node. The LOD 400 model is submitted to the engineer for review, approved, and then used to drive CNC cutting machines and drill patterns in the steel fabrication shop. The model is not a representation of the building — it is the instruction set for manufacturing.

LOD 500: As-Built and Field-Verified

LOD 500 is frequently misunderstood, and the misunderstanding has practical consequences. The most common misconception is that LOD 500 means “more detailed than LOD 400” — a sort of ultimate model with every nut and bolt included. This is incorrect.

LOD 500 does not describe a level of geometric detail. It describes a level of accuracy verification.

An LOD 500 element has been field-verified to match the as-constructed condition. The geometry and information reflect what was actually built, not what was designed or what was fabricated. This distinction matters because construction always involves variation from design: elements are shifted slightly to avoid unforeseen conditions, specifications are substituted during construction, dimensions change due to site conditions, and so on.

What LOD 500 means in practice:

The element’s location, size, and configuration have been verified against the physical structure using survey data, laser scanning, or inspection records
The information attached to the element (model number, installation date, commissioning data, warranty start date) reflects the actual installed product, not the specified product
The model can be used as a reliable basis for facility management, space planning, and future renovation work

What LOD 500 does NOT mean:

That the element has more geometric complexity than LOD 400
That every detail of a complex assembly is modeled (a field-verified structural column may still be a simple LOD 300-equivalent geometry — but its location and specification are confirmed)
That the model was necessarily produced by laser scanning (though 3D laser scanning is the most efficient method for large-scale as-built verification)

When to use LOD 500:

Handover of the building model to the owner/operator for facilities management
Post-construction verification projects (existing building documentation)
Operations and maintenance planning, space management, and building performance monitoring
Future capital works projects that require reliable existing conditions data

Practical example: At project completion, the facilities management team receives the contractor’s construction-phase model. Before using it for FM, a BIM coordinator conducts a field verification exercise using a total station and spot-checks 200 elements across mechanical, structural, and architectural disciplines. Elements that match construction to within the agreed tolerance are tagged LOD 500. Elements where the as-built condition differs — a relocated pipe, a substituted luminaire, a wall that moved 50mm — are updated in the model. The resulting LOD 500 model is ingested into the building’s asset management system (e.g., Archibus or Maximo) as the basis for maintenance workflows.

LOD Comparison Table

The following table summarizes the key characteristics of each LOD level for quick reference.

LOD Level	Geometry Detail	Information Content	Typical Use	Project Phase	Primary Author
LOD 100	Generic mass, symbol, or approximate shape	Approximate quantities, conceptual system type	Massing studies, feasibility, early cost estimating	Pre-design / Concept	Architect / Design team
LOD 200	Generic geometry at approximate size and location	Schematic specs, approximate dimensions and quantities	SD coordination, preliminary energy modeling, spatial feasibility	Schematic Design	Design team
LOD 300	Specific, accurate geometry — measurable directly from model	Specific product type, location, orientation, code compliance data	CD production, clash detection, quantity takeoff	Design Development / CDs	Design team
LOD 350	LOD 300 geometry plus connections, supports, and system interfaces	Interface and support requirements for coordinated installation	Multi-discipline coordination, subcontractor coordination drawings	Late CDs / Pre-Construction	Design team / Specialty contractors
LOD 400	Full fabrication detail — shop drawing equivalent	Manufacturer model, fabrication dimensions, weld/bolt specs, sequence	Fabrication, off-site prefabrication, CNC-driven manufacturing	Pre-Construction / Construction	Specialty contractors / Fabricators
LOD 500	Field-verified geometry (may not be more complex than LOD 300)	Verified as-installed data, commissioning records, warranty dates	Facilities management, asset management, future renovation	Post-Construction / Handover	Contractor / FM team

How LOD is Used in Practice

The Model Element Table (MET)

In any BIM-enabled project, the Model Element Table (MET) — sometimes called a BIM Model Matrix — is the key document that translates LOD requirements into actionable responsibilities. A MET lists every significant building element type down the rows, and the project milestones or work stages across the columns. Each cell is populated with:

The required LOD at that milestone
The responsible party (architect, structural engineer, MEP engineer, specialty contractor)

A well-constructed MET prevents the most common source of LOD misunderstanding on projects: different parties assuming different things about who is responsible for modeling what, at what level of development, and by when.

LOD in BIM Execution Plans

A BIM Execution Plan (BEP) is a project-level agreement — negotiated between the project owner (or their representative), the designer(s), and the contractor — that governs how BIM is used throughout the project lifecycle. The BEP typically includes:

The software platforms and file formats to be used
The federated model coordination process and schedule
The clash detection protocol and severity classifications
The Model Element Table with LOD assignments
Data exchange standards (COBie, IFC, etc.)
Handover requirements

When the BEP references LOD levels, it should always state which specification is being used (the BIMForum LOD Specification is standard in the US and increasingly elsewhere). Without this reference, “LOD 300” means whatever each party’s internal standards say it means — which may differ significantly.

LOD in Contracts

LOD requirements increasingly appear directly in BIM-related contract exhibits, addenda, or building information management (BIM) protocols. In the US, the AIA’s E203 (BIM and Digital Data Exhibit) and G202 (Project BIM Protocol) are commonly used for this purpose. In the UK, the ISO 19650 series provides equivalent guidance (using somewhat different terminology — “level of information need” rather than LOD). When a contract specifies LOD, the team must ensure the BEP and MET are aligned with those contractual requirements, because failure to deliver elements at the specified LOD can constitute a contract breach.

Common LOD Misconceptions

”Higher LOD = better model”

This is the most pervasive and most damaging misconception. A LOD 500 model is not inherently better than a LOD 300 model — it is appropriate for a different purpose. Modeling everything to LOD 400 during schematic design wastes significant time and budget, produces information that will almost certainly need to be redone as the design evolves, and creates a false sense of design resolution that does not actually exist.

LOD is a tool for matching the investment in model development to the decisions that need to be made at each project stage. A feasibility study does not need LOD 300 walls. A structural fabricator does need LOD 400 connections. Using the wrong LOD in either direction is inefficient.

”LOD 500 means a very detailed model”

As discussed above, LOD 500 means field-verified accuracy, not geometric complexity. A LOD 500 element might have the same geometric representation as a LOD 300 element — the difference is that it has been checked against the physical building and confirmed to match.

”LOD applies to the entire model”

LOD is defined per element, not per model. A model might contain LOD 300 walls, LOD 200 HVAC, and LOD 100 site elements simultaneously — and this is entirely appropriate if the project phase and the Model Element Table call for it. Saying “this is a LOD 300 model” is technically imprecise; the correct statement is “all architectural elements in this model have been developed to LOD 300."

"LOD defines who models what”

LOD defines the level of reliability and content of a model element. It does not define the responsibility for producing it. Two different elements at the same LOD might be the responsibility of different parties. The MET assigns responsibility; LOD describes the output.

”Clash detection only requires LOD 300”

Clash detection requires at minimum LOD 300 for hard clash detection (elements occupying the same space). But soft clash detection — checking clearances for maintenance access, thermal expansion, and code-required separations — may require LOD 350 geometry that includes insulation jackets, support systems, and access envelope geometry. Teams that run clash detection on LOD 300 models and find no conflicts are often discovering those conflicts again in the field because LOD 350 elements were never modeled.

LOD Requirements by Discipline

Different disciplines approach LOD differently, and the appropriate LOD at any given project stage varies by element type and use case.

Architectural: Architectural elements typically reach LOD 300 by the construction documents phase. Facade systems (curtain wall, cladding) often need to reach LOD 350 or 400 earlier than interior elements because facade contractors require detailed coordination information during the pre-construction phase.

Structural: Primary structural elements (columns, beams, slabs, foundations) typically reach LOD 300 at design development, with connections and embedments reaching LOD 350 for coordination. The fabrication model (LOD 400) is typically produced by the steel fabricator or precast manufacturer, not the structural engineer.

Mechanical, Electrical, and Plumbing (MEP): MEP systems are the most challenging discipline for LOD coordination because the density and interdependencies of ductwork, pipework, cable trays, and accessories require LOD 350 geometry to produce reliable coordination drawings. Many MEP contractors use the design engineer’s LOD 200-300 model as a reference and build their own LOD 350-400 coordination model during pre-construction.

Civil and Site: Site elements often remain at LOD 200 through design development, with LOD 300 reached for paving, utilities, and landscaping elements at the construction document stage. Survey-based existing conditions models (topography, existing utilities) are effectively LOD 500 by definition — they represent field-verified conditions, not design intent.

Conclusion

LOD is not an abstract theoretical framework — it is a practical tool that, when properly applied, prevents the most common causes of BIM-related disputes and field coordination failures. The key principles to carry forward are:

LOD defines the reliability of model elements, combining both geometric accuracy (LOG) and information richness (LOI).
LOD levels are defined per element, not per model, and should be assigned through a Model Element Table within a BIM Execution Plan.
The BIMForum LOD Specification is the industry standard reference and should be cited explicitly in BIM contracts.
LOD 350 is a critical level for construction coordination that is frequently overlooked in early BIM planning.
LOD 500 describes field-verified accuracy, not geometric complexity.
Higher LOD is not always better — the goal is to match the level of development to the decisions being made at each project stage.

For BIM managers, the practical task is to write these principles into the BIM Execution Plan at the start of every project, negotiate the Model Element Table with all parties, and enforce LOD requirements through federated model reviews at each project milestone. For designers and engineers, the task is to understand what LOD is required for the work at hand and to avoid over-modeling (wasting time on detail that will change) or under-modeling (producing elements that cannot support the decisions that need to be made).

BIM is a team sport. LOD is the language that lets the whole team play from the same rulebook.

Ready to Level Up Your Skills?

Explore our hands-on courses at Archgyan Academy — built for architects, BIM managers, and AEC professionals who want to learn by doing.

Understanding BIM LOD Levels: A Comprehensive Guide to 100, 200, 300, 400, 500