Revit BIM Levels Explained: LOD 100 to LOD 500 for Dubai Projects
August 15, 2026
No Comments
LOD — Level of Development — is the framework that defines how much detail and reliability a Revit model element should carry at a given project stage, ranging from LOD 100 (conceptual massing) through LOD 500 (verified as-built). Getting LOD right matters practically: model a curtain wall to LOD 400 detail during early concept design and you’ve wasted weeks on information nobody needed yet; leave the MEP model at LOD 200 going into construction and clashes get discovered on site instead of in the model, where they’re far cheaper to fix.
For Dubai projects specifically, LOD requirements aren’t just a modeling best practice — they’re increasingly tied to Dubai Municipality’s BIM submission requirements and contractual deliverables on projects over AED 100 million. This guide walks through each LOD level from 100 to 500, what it actually looks like inside Revit, and how it maps to real project stages on the ground in the UAE.
Level of Development describes two things about a Revit model element at any given point: how geometrically detailed it is, and how much you can rely on the information attached to it — dimensions, materials, performance data, manufacturer specifications. The LOD framework was formalized by the American Institute of Architects (AIA) and the BIMForum, and it’s now the de facto global standard referenced in BIM Execution Plans on projects across Dubai and the wider UAE.
LOD matters because it sets shared expectations across a project team. Without it, an architect might assume a structural column shown in early design is final and precisely located, while the structural engineer intended it purely as a placeholder — a mismatch that causes real coordination problems once trades start relying on model data. Defining LOD per element, per project stage, in the BEP removes that ambiguity before it becomes a costly mistake.
One of the most common points of confusion in BIM discussions is that “LOD” gets used to mean two different things: Level of Detail and Level of Development. Level of Detail refers purely to how much geometric detail an element has — how many polygons, how visually complex the model looks. Level of Development refers to both geometric detail and the reliability of the non-graphical information attached to the element — its specification data, performance values, and whether it’s still a placeholder or a confirmed, coordinated component.
This distinction matters practically. A highly detailed-looking door family with photorealistic hardware could still be at a low Level of Development if its fire rating, hardware specification, and exact dimensions haven’t been confirmed. The BIMForum’s LOD specification — the one referenced throughout this guide and the one used on most Dubai BIM Execution Plans — is Level of Development, not just visual detail.
LOD 100 is the earliest and least detailed stage, typically representing a project during concept and feasibility design. Elements at this level may not even exist as discrete Revit components yet — a building might be represented as a simple massing form showing overall shape, orientation, and approximate floor area, with no specific systems, materials, or exact dimensions defined.
At LOD 100, the model communicates overall design intent — building footprint, approximate height, general zoning — rather than anything a contractor could estimate cost from with confidence. Design teams use LOD 100 models for early massing studies, sun and shadow analysis, and preliminary area calculations submitted for concept approval.
By LOD 200, elements exist as actual generic Revit components — walls, floors, columns — with approximate size, shape, location, and orientation, but without final specification. A structural column at LOD 200 might be modeled at roughly the right size and grid location, but the exact section, material grade, and connection details haven’t been finalized.
LOD 200 corresponds to schematic design, when the overall building systems and layout are being established but before detailed engineering has locked anything down. Quantities and costs derived from an LOD 200 model should be treated as approximate — useful for budget-level estimates, not for procurement.
LOD 300 is where models become genuinely reliable for coordination and documentation. Elements are modeled with precise size, shape, location, orientation, and quantity — a structural column at LOD 300 has its final section size, exact grid position, and confirmed material specified. This is the level most construction documentation and permit submissions are built from, and it’s the LOD most Dubai Municipality submissions expect for building permit stage.
At LOD 300, disciplines can start meaningful coordination — architectural, structural, and MEP models can be federated and checked for clashes with confidence that what’s shown reflects the actual intended design, not a placeholder. This is typically the level at which teams first run serious Navisworks clash detection passes.
LOD 350 adds one critical thing on top of LOD 300: interfaces with other building systems. Where LOD 300 confirms a duct’s size and route, LOD 350 confirms exactly how that duct connects to structural penetrations, how it relates to ceiling systems, and how it interfaces with adjacent MEP elements — the connection points between systems, not just the systems themselves.
This level exists specifically because multi-discipline coordination needs more than each system individually modeled correctly — it needs the interfaces between systems resolved. On complex Dubai towers with tightly packed MEP zones above ceilings, LOD 350 coordination is often where the real clash-resolution work happens, well before elements move to fabrication detail.
LOD 400 elements are modeled with the detail needed for fabrication and assembly — exact dimensions, connection details, and installation information sufficient for a subcontractor to manufacture and install the component directly from the model. A structural steel connection at LOD 400 shows bolt patterns and weld details; an MEP model at LOD 400 shows exact pipe routing, hangers, and support details ready for shop drawing generation.
This is the level at which detailing platforms like Tekla Structures typically take over from analysis-focused tools, and it’s the level Dubai’s steel and MEP subcontractors expect before they’ll commit to fabrication. Reaching LOD 400 prematurely — modeling fabrication detail before the design is stable — wastes significant effort when upstream changes force rework; reaching it too late causes fabrication delays. Getting the timing right, discipline by discipline, is one of the BIM Manager’s core BEP responsibilities.
LOD 500 is the final level, representing the model as field-verified — confirmed as actually built, not just as designed. Elements at LOD 500 reflect real, as-constructed conditions, and the model becomes the basis for facilities management: asset registers, maintenance schedules, and warranty tracking handed over to the building owner or operator.
Dubai’s larger developments increasingly require LOD 500 as-built models as a formal handover deliverable, driven partly by asset owners wanting a genuinely useful digital twin rather than a stack of PDF drawings. This has extended BIM responsibility well past construction completion and into the operations phase — a scope shift that’s part of why BIM Manager roles increasingly touch facilities management, not just design and construction.
Dubai Municipality’s Digital Design Delivery process and typical consultant BEPs generally align LOD progression to project stage in a fairly consistent pattern, even though exact requirements vary by project and client.
| LOD Level | Typical Project Stage | What’s Confirmed | Common Use |
|---|---|---|---|
| LOD 100 | Concept / Feasibility | Overall massing, approximate area | Massing studies, early approvals |
| LOD 200 | Schematic Design | Approximate size, shape, location | Budget-level cost estimates |
| LOD 300 | Design Development / Permit | Precise size, shape, and location | Permit submission, initial coordination |
| LOD 350 | Detailed Design / Coordination | Interfaces between building systems | Multi-discipline clash detection |
| LOD 400 | Construction Documentation | Fabrication and assembly detail | Shop drawings, subcontractor fabrication |
| LOD 500 | Handover / Operations | Field-verified as-built condition | Facilities management, asset registers |
Getting LOD progression right on a real project comes down to a handful of habits that experienced Revit teams in Dubai consistently apply.
Teams managing LOD across large, multi-discipline models also benefit from automating LOD status checks rather than reviewing manually element by element. Building repeatable audit scripts is one of the more practical applications covered in Orbit’s Dynamo Course, which pairs naturally with Revit modeling skill for teams managing complex LOD progression across large projects.
LOD stands for Level of Development, a standardized scale from LOD 100 to LOD 500 describing how detailed and reliable a model element is at a given project stage, covering both geometric detail and the accuracy of information attached to the element.
LOD 300 confirms precise size, shape, and location for design and coordination purposes — it’s typically used for permit submissions and initial clash detection. LOD 400 adds fabrication-level detail, including connection information and assembly instructions, sufficient for a subcontractor to manufacture and install directly from the model.
Requirements vary by project and stage, but most Dubai building permit submissions expect models at LOD 300, with LOD 350 coordination and LOD 400 fabrication detail required as the project moves into construction documentation and subcontractor procurement. Larger developments increasingly require LOD 500 as-built handover for facilities management.
LOD requirements are typically defined in the project’s BIM Execution Plan (BEP), usually authored or approved by the BIM Manager in consultation with the client, design team, and relevant contractors, and documented per element category rather than as a single blanket requirement.
No. Modeling elements to a higher LOD than the project stage requires wastes time and effort on information that’s likely to change, and can actually slow a project down. The goal is matching LOD to what each stage genuinely needs, not maximizing detail everywhere.
Understanding LOD 100 through LOD 500 isn’t just an academic exercise for Revit users — it’s the shared language that keeps a multi-discipline BIM project coordinated, on schedule, and free of costly surprises during construction. Modeling to the right LOD at the right project stage, and knowing when a curtain wall needs LOD 200 versus LOD 400 detail, is one of the clearest markers of an experienced Revit professional versus a beginner.
For Dubai projects tied to Dubai Municipality’s BIM mandate, getting LOD progression right isn’t optional — it’s part of the deliverable. Orbit Training Center’s Revit BIM Course builds this LOD fluency directly into its project-based training, so graduates leave understanding not just how to model in Revit, but how to model at the right level of development for every stage of a real project.