BIM Detail Levels: Complete Guide to LOD 100-500 for engineering Projects

BIM detail levels is the contractual language that tells everyone on a project how far they can trust a model element. Get it right and design, coordination, procurement and handover run on the same information. Get it wrong and someone fabricates from a model that was never meant to be fabricated from. This guide covers what LOD 100 to 500 actually mean, how LOD differs from Level of Detail and from ISO 19650’s Level of Information Need, what Dubai Municipality now requires at permit submission, and how to write LOD into an EIR and BEP so it holds up commercially.

What Is Level of Development (LOD) in BIM?

Level of Development (LOD) is a specification that defines how complete and how reliable a BIM model element is at a given point in a project. It answers one question: how far can a downstream team depend on this element for design decisions, coordination, quantities, fabrication or operations?

LOD is not a measure of how detailed a model looks. A beautifully rendered element with no reliable dimensions is low LOD. A visually plain element carrying verified geometry, material data and a manufacturer reference is high LOD.

The practical consequence is contractual. When a specification says “structural steel to LOD 350 at design freeze”, it is not describing an appearance. It is stating that connections and supports will be modelled accurately enough that a clash report run against them can be trusted.

Level of Detail vs Level of Development vs LOI vs LOIN

Four terms, routinely used as if they were one. They are not, and the difference matters most on projects working to ISO 19650 — which increasingly means projects in the UAE.

The distinction that catches teams out is the last one. LOD says “model to level 350”. Level of Information Need says “define the purpose, then define exactly the geometry and data required to serve it — and no more.” The ISO approach deliberately avoids a single number, because a number is a blunt instrument: an element can carry excellent geometry and useless data, or the reverse, and still be called LOD 350.

On a Dubai project running to ISO 19650, expect the information requirements to be expressed as purpose-driven exchange requirements rather than a single LOD number. Many teams handle this by keeping a familiar LOD matrix as a working shorthand while defining the actual deliverable in ISO 19650 terms — which is workable, provided both documents agree.

Where the LOD Framework Came From

Knowing the lineage matters, because contracts reference specific documents and those documents differ.

• AIA E202–2008, Building Information Modeling Protocol Exhibit. The American Institute of Architects introduced the concept with five levels: 100, 200, 300, 400 and 500.
• AIA G202–2013, Project Building Information Modeling Protocol Form. The updated protocol that superseded E202 and is the version most US-derived contracts now cite.
• BIMForum LOD Specification. Published and updated on a near-annual cycle, this is the working document practitioners actually use. It defines each level element by element rather than in the abstract, organised by CSI Uniformat, and it is where LOD 350 was introduced — filling the gap between design-level geometry and fabrication-level detail. The BIMForum specification is why the scale has six levels in practice while the AIA protocol has five.
• ISO 19650 series. The international framework for information management across the asset lifecycle. It does not use the LOD ladder; it uses Level of Information Need, defined per purpose.

LOD 100 — Conceptual

What the element is: a symbol, generic mass or placeholder. It communicates that something exists in roughly this place, at roughly this size.

What you can rely on: spatial studies, massing, gross area and volume, orientation and site fit. Anything derived from an LOD 100 element is an estimate produced by analogy, not a measurement.

What you cannot rely on: quantities for pricing, clash detection, or anything that touches procurement. Quantities read off an LOD 100 model look like numbers and behave like guesses.

Typical use in practice: early feasibility on a plot, comparing massing options, initial area schedules for a developer’s business case.

LOD 200 — Schematic

What the element is: a generic system or component with approximate size, shape, location and orientation. A duct is a duct of about this size in about this route; it is not yet a specific duct.

What you can rely on: spatial coordination at system level, early clash awareness between major systems, order-of-magnitude budgeting, and confirming that the design fits.

What you cannot rely on: procurement quantities, fabrication, or a clash report you intend to issue as binding. Elements at LOD 200 are placeholders with dimensions, and clashes between placeholders are indicative only.

Typical use in practice: schematic design coordination, early services routing studies, checking that a ceiling void is deep enough before the design commits to it.

LOD 300 — Design Development

What the element is: specific geometry with accurate size, shape, location and orientation, plus material and performance data. The element is what it says it is, positioned where it says it is.

What you can rely on: construction documentation, permit and authority submissions, tender quantity extraction, and design coordination between disciplines.

What you cannot rely on: fabrication. LOD 300 does not carry connections, supports, hangers or the interface information that a fabricator needs. It also does not carry manufacturer-specific data.

Typical use in practice: the level most consultant deliverables are contracted at, and the level from which construction detail drawings and tender documentation are produced.

LOD 350 — Coordination and Interfaces

The level most often specified and least often understood. LOD 350 exists because LOD 300 is not enough to coordinate and LOD 400 is too much to model across a whole project.

What LOD 350 adds to LOD 300: the parts of an element that interact with other elements — supports, hangers, brackets, connections, penetrations, access and clearance zones, and the interface geometry where one system meets another.

Why that matters: most real clashes on a project are not duct-through-beam. They are hanger-through-cable-tray, valve-with-no-access-space, and pipe-that-fits-but-cannot-be-installed. None of those are visible in an LOD 300 model, because none of those components exist in it.

This is the level at which clash detection produces findings worth acting on. Running a federated clash report against LOD 200 or LOD 300 models generates noise; running it at LOD 350 generates a work list.

LOD 400 — Fabrication

What the element is: a specific manufactured product, modelled with the geometry, connections, assembly sequence and installation data required to make it and put it in place.

What you can rely on: shop drawing production, off-site fabrication, prefabricated modules, CNC output, and procurement against a specific product reference.

Who produces it: normally the contractor, subcontractor or fabricator — not the design consultant. LOD 400 carries means-and-methods information, which sits with the party responsible for construction. This distinction is a common source of scope disputes when a consultant is asked to deliver LOD 400 without the contractual position that goes with it.

Practical scope note: almost no project models everything at LOD 400. It is applied selectively to fabricated packages — structural steel, precast, ductwork, pipe spools, curtain walling, joinery. Our LOD 400 shop drawing service covers that output.

LOD 500 — As-Built and Facility Management

What the element is: a field-verified record of what was actually installed, carrying operational data — asset tags, commissioning records, warranty periods, maintenance requirements, equipment references.

The most common misconception: LOD 500 is not “LOD 400 plus more geometry”. It is a different kind of reliability — verification against site rather than development of design. An element can be geometrically simpler at LOD 500 than at LOD 400 and still be the more valuable model, because it is true.

What it enables: facility management handover, space and asset management, and the data foundation for a digital twin. Verification requires either survey, laser scanning or documented site confirmation — a model relabelled LOD 500 without verification is simply an LOD 400 model with a new name on it.

Is LOD 600 Real?

Short answer: not as a standard. LOD 600 does not appear in the AIA protocol or the BIMForum specification, and no recognised body defines it.

It circulates informally to describe an operations-phase model enriched with live performance data — energy consumption, occupancy and space utilisation, IoT sensor feeds, predictive maintenance. That is a real and valuable capability. It is simply not a level of development; it is a digital twin, and it is better described in those terms because the LOD ladder measures model reliability, not data integration.

If a client or tender document asks for “LOD 600”, the useful response is to ask what capability they actually want, and specify it as a data and integration requirement rather than accepting an undefined number into a contract.

LOD by Discipline: Architecture, Structure and MEP

A single project-wide LOD number hides more than it reveals, because the same level means different work in different disciplines. This is the table that belongs in your BEP.

BIM Requirements in the UAE and Saudi Arabia

This is where regional practice diverges sharply from the international guidance, and where most LOD articles stop being useful.

Dubai

Dubai has had a BIM mandate longer than most markets. Dubai Municipality introduced BIM as a requirement through Circular 196 in 2013, applying to defined categories of building — among them towers above a stated height, buildings above a stated floor area, specialised buildings such as hospitals and universities, and projects designed by foreign offices. Circular 207, issued in 2015, expanded the scope and kept the earlier circular in force, placing responsibility for application on the consulting offices.

A point worth noting for anyone planning deliverables: those circulars mandated the use of BIM without stipulating a minimum LOD. The obligation was to work in BIM, not to reach a specific numeric level.

More recently, Dubai Municipality has moved from mandating the process to requiring the deliverable. A circular issued in October 2023 (reference 9-1-2) introduced BIM model submission for new building permits, with IFC as the submission format, taking effect from the start of 2024. Dubai Municipality has publicly aligned with open standards — ISO 19650, IFC, IDS and BCF — as the basis for permit review and for city-scale information use.

What that changes for LOD planning: if the model itself is the permit submission, then model quality is no longer an internal coordination concern. Elements must be correctly classified and carry the properties the reviewing system expects, exported cleanly to IFC. A model that coordinates perfectly in Revit but exports to IFC with missing classification will fail at submission regardless of its LOD.

Abu Dhabi and the wider UAE

BIM has not been mandated at federal level across the UAE, so requirements vary by emirate, authority and client. Abu Dhabi’s Department of Municipalities and Transport operates its own standards regime, and major clients and developers frequently impose BIM requirements contractually regardless of any statutory obligation.

Saudi Arabia

In the Kingdom, BIM requirements are predominantly driven by client and project rather than by a single blanket national mandate. Large developers and giga-project programmes routinely specify BIM deliverables, LOD matrices and BIM Execution Plans as contract conditions, and the Saudi Building Code governs the technical content of what is modelled and submitted. In practice this means the LOD requirement comes from the employer’s information requirements, not from a municipal circular.

Writing LOD Into the EIR, BEP and LOD Matrix

LOD only has commercial force if it appears in the documents that govern the work. Three artefacts carry it.

1. Employer’s Information Requirements (EIR)

Issued by the client, before appointment. It states what information the client needs, why, in what format, and by when. The EIR is where LOD expectations originate; everything downstream should trace back to it. An EIR that says “BIM required” and nothing else transfers the entire definition problem to the supply chain, where it becomes a variation.

2. BIM Execution Plan (BEP)

The supply chain’s response: how the requirements will be met. It names the software and versions, the federation strategy, the common data environment, the naming and classification conventions, the coordination cycle, and the LOD matrix. Critically, it should also name which LOD reference document and edition applies.

3. The LOD matrix

A table with model elements down one axis and project milestones across the other, with the required LOD in each cell and a named party responsible for it. This last column is the one most often omitted and most often needed — LOD without a Model Element Author is a requirement with nobody attached to it.

A workable matrix has four attributes:

• Element-level, not discipline-level. “MEP — LOD 350” is not a specification. “Chilled water pipework — LOD 350 at design freeze” is.
• Milestone-based, not date-based. Tie levels to design freeze, tender issue, IFC and handover, so the matrix survives programme changes.
• Explicit about who authors each element at each stage, including the transfer point where authorship moves from consultant to contractor.
• Explicit about what is excluded. Stating that temporary works, formwork and site logistics are not modelled prevents an expectation from forming.

Our BIM documentation service covers matrix development and deliverable packaging, and the quantity side is covered in our guide to the construction bill of materials.

Seven LOD Mistakes That Cost Money

Frequently Asked Questions

Conclusion

Level of Development is a communication tool before it is a technical one. Its value comes from everyone on a project agreeing what a model element can be trusted for, at what point, and who is responsible for getting it there.

In this region there is a second layer. With Dubai Municipality moving to model-based permit submission in IFC, and with clients across Saudi Arabia specifying BIM contractually on major programmes, model quality has moved from an internal coordination concern to a submission and compliance one. The teams that handle that well are the ones who wrote the LOD matrix properly at the start, named who owns each element, and named the specification they are working to.