📊 LOD 100 to 500: The Level of Development Framework for BIM Projects

Level of Development vs. Level of Detail: Why the Distinction Matters

The single most important clarification in the LOD framework is this: LOD stands for Level of Development, not Level of Detail. This distinction, established by the BIMForum LOD Specification and codified in the AIA Document G202 (Building Information Modeling Protocol Form), is not merely semantic. It changes how you contractually define model responsibilities and how you communicate expectations across a project team.

Level of Detail describes how much visual information is packed into a model element — how many bolts are shown on a connection, how fine the mesh is, how many geometric curves define a pipe fitting. Level of Development describes how reliable the information in that element is. An LOD 300 wall carry a precise dimension that can be used for takeoffs and permit drawings. An LOD 200 wall may look similar on screen but its dimensions are approximate and cannot be relied upon for construction.

In practice, a high-detail visual model can have low LOD (an architect's early massing with elaborate materials applied), while a sparse-looking analytical stick model can carry LOD 400 data if every section and connection has been verified. Always evaluate LOD by the reliability of the embedded information, not the visual complexity of the geometry.

The authoritative reference is the BIMForum LOD Specification, updated regularly and available at bimforum.org. It defines LOD requirements for dozens of element categories across all disciplines. The AIA G202 form is the contractual document teams attach to BIM contracts to assign LOD responsibility by author and phase.

LOD 100: Conceptual

At LOD 100, a model element exists as a symbol or a generic representation of an overall concept. It may be a massing volume representing a building, a single line representing a wall, or a colored zone representing a mechanical room. Key characteristics:

• No specific geometry — dimensions are not derived from the element itself
• Location may be approximate
• Used for early feasibility studies, energy massing analysis, and site planning
• Quantities derived from the model at this level are order-of-magnitude estimates only
• Typical deliverables: conceptual massing models, site analysis, rough area takeoffs

In Revit, LOD 100 typically corresponds to the Conceptual Mass environment. Tools like the Energy Analysis in Revit 2024+ can analyze a massing model before a single wall is placed. This is the phase where floor-plate efficiency ratios, building orientation for solar gain, and gross area by use type are established.

LOD 200: Generic

At LOD 200, elements are modeled as generic systems with approximate quantities, size, shape, location, and orientation. Information is not yet specific enough to use for fabrication or precise coordination, but it is reliable enough to confirm system compatibility and major spatial allocations.

• Approximate dimensions — correct order of magnitude but not field-verified
• Generic family types (a duct is shown as a rectangular duct, but the gauge and liner are not specified)
• Useful for early MEP coordination, interference checking at major system level
• Equipment shown in approximate locations and sizes, not final selections
• Structural system layout established but connection details not modeled

LOD 200 is the typical level expected at Design Development (DD) phase for most elements. Clash detection at LOD 200 catches gross spatial conflicts (a major mechanical duct running through a structural beam zone) before they become expensive field problems.

LOD 300: Specific

LOD 300 is the workhorse of construction document production. Elements are modeled as specific assemblies with accurate quantity, size, shape, location, and orientation. Non-graphic information can also be attached. This is the level at which permit drawings and most design-bid-build CDs are produced.

• Accurate dimensions that can be used for quantity takeoffs and cost estimating
• Specific family types representing the actual design intent (24-inch wide x 12-inch deep concrete beam at specific gridline)
• Room/space data attached to BIM elements
• Manufacturer performance specifications may be included as parameters
• Suitable for permit submission, design review, and owner pricing

One critical point: LOD 300 geometry is modeled as the designer intends it to be constructed, but it has not been field-verified or fabrication-engineered. A duct at LOD 300 follows the design path through the ceiling plenum; at LOD 350/400, it accounts for actual hanger locations, access door placement, and sheet metal shop routing.

LOD 350: Interfaces and Coordination

LOD 350 is an intermediate level added by the BIMForum Specification to address the gap between design intent (LOD 300) and fabrication (LOD 400). Elements at LOD 350 include information needed to coordinate with adjacent building systems and elements.

• Interfaces to adjacent and interconnecting elements are explicitly modeled (duct flanges, pipe couplings, anchor bolts at column bases)
• Support and hanger systems are modeled in sufficient detail for coordination
• Primary use case: trade coordination on complex projects where MEP, structure, and architecture must resolve conflicts before fabrication
• Steel connections may be modeled at LOD 350 to confirm fit without full shop drawing detail
• Fabrication-ready coordination drawings and composite clash-free models are LOD 350 deliverables

On large hospital, laboratory, or data center projects, the MEP coordination BIM model is typically brought to LOD 350 through a virtual design and construction (VDC) coordination process before any trade issues shop drawings. This process is increasingly performed in platforms like Autodesk Construction Cloud, Trimble Connect, or Navisworks Manage.

LOD 400: Fabrication and Assembly

At LOD 400, elements are modeled at a level of detail and accuracy sufficient for the fabrication and assembly of that element. This level is primarily used by specialty contractors and fabricators.

• Field dimensions — element sized and located as it will actually be built
• Fabrication information included: material specs, weld symbols, surface treatments, hardware
• Can be used to drive CNC machines, laser cutting, or automated prefabrication
• Structural steel: all members, connections, base plates, anchor rods, gusset plates fully detailed
• Mechanical: duct segments with exact lengths, fittings, gauge, liner, and labeling for shop spool sheets
• Electrical conduit: each run, bend, offset, fitting, and junction box

LOD 400 models are almost never created by the design team — they are produced by specialty subcontractors using the LOD 350 coordination model as a starting point. Tekla Structures is the dominant platform for structural steel LOD 400; CADmep/ESTmep/Fabrication are common for MEP. The LOD 400 model is contractually the fabricator's document, not the engineer's.

LOD 500: As-Built / Facility Management

LOD 500 is the verified as-built condition. Elements have been field-verified to confirm their actual size, shape, location, quantity, and orientation. LOD 500 is the target for FM handover and operations.

• Actual installed conditions — not design intent, not the fabrication model, but what was actually built and verified
• Manufacturer data, operations and maintenance manuals, warranty information linked to BIM elements
• Asset tags and serial numbers attached to equipment families
• Used for CAFM/CMMS integration (Archibus, Maximo, FM:Interact)
• Supports planned preventive maintenance scheduling, space management, and future renovation

Achieving true LOD 500 is expensive and rarely done on all elements. In practice, project teams define which elements require LOD 500 verification — typically major equipment (AHUs, chillers, switchgear), primary structural elements, and life-safety systems. Reality capture (laser scanning, photogrammetry) is increasingly used to verify as-built conditions for critical systems.

LOD by Discipline: A Reference Table

Phase	Architecture	Structure	MEP
Schematic Design	LOD 100–200 (massing, major zones)	LOD 100 (structural system concept)	LOD 100 (equipment rooms, major risers)
Design Development	LOD 200–300 (rooms, assemblies)	LOD 200–300 (member sizes, grid)	LOD 200 (system layout, approx routing)
Construction Documents	LOD 300 (permit-ready geometry)	LOD 300 (permit structural drawings)	LOD 300 (design intent, sized systems)
Trade Coordination	LOD 300 (frozen for coordination)	LOD 300–350 (connections at interfaces)	LOD 350 (coordinated, clash-free)
Fabrication/Construction	LOD 300 (reference)	LOD 400 (steel fabrication model)	LOD 400 (spool sheets, prefab)
FM Handover	LOD 500 (key spaces verified)	LOD 500 (major elements verified)	LOD 500 (all equipment, tagged)

LOD in the BIM Execution Plan

The BIM Execution Plan (BEP) is the project document that defines how BIM will be used, who is responsible for which elements, and what LOD is expected at each phase. A well-written BEP includes an LOD Matrix: a spreadsheet or table that assigns every major element category a responsible author and an LOD expectation at each project milestone.

The LOD Matrix typically follows BIMForum element categories and assigns:

• Author: which firm or trade is responsible for modeling the element
• LOD at each milestone: SD, DD, CD, Coordination, Fab, As-Built
• Non-graphic information: what parameters must be populated at each LOD

Common BEP mistake: teams list LOD 400 for all elements at CD phase, which is impossible for the design team to deliver. The BEP should reflect what the design team can realistically provide, with LOD 400 clearly assigned to the responsible fabricator.

Common Mistakes in LOD Practice

Confusing Revit's view detail level with LOD. Revit offers Coarse, Medium, and Fine display states for views. These control what is shown on screen but have nothing to do with LOD. A Fine view can display an LOD 100 element in full graphic richness. These are independent concepts.

Over-modeling for the phase. Modeling to LOD 400 during design development wastes hours and creates files that are slow to navigate, difficult to change when the design evolves, and often inaccurate because the design has not yet been resolved. Model to the LOD the phase requires — nothing more.

Treating LOD as a visual standard. Owners and PMs sometimes request "detailed models" meaning they want things to look complete, which is a Level of Detail request. Educate stakeholders that LOD is about information reliability, not visual appearance.

Not assigning LOD in contracts. Without an AIA G202 or BEP LOD matrix in the contract, teams have no defined responsibility for what the model contains. Disputes arise at handover when the owner expects an FM-ready LOD 500 model but the design team only delivered LOD 300.

LOD Impact on File Size and Performance

One practical consequence of LOD decisions is model performance. Highly detailed geometry — parametric rebar, sheet metal seams, bolt patterns — exponentially increases file size and regeneration time. As a rule of thumb:

• LOD 100–200 models: fast, lightweight, suitable for early-phase iteration
• LOD 300 models: manageable with proper workset structure and linked models
• LOD 350 coordination models: should be federated (Navisworks NWD/NWC) rather than live Revit for performance
• LOD 400 fabrication models: typically maintained in separate fabrication software (Tekla, CADmep), not inside the Revit design model

The best-performing BIM programs keep the design model at LOD 300, export a coordination NWC for clash detection, and maintain LOD 400 fabrication models in specialized tools — bringing them back into the federated model only for as-built verification. This workflow keeps Revit models responsive and separates design-intent data from fabrication data cleanly.