What Does LOD 100 to LOD 500 Actually Mean for Your Project?

TL;DR

LOD (Level of Development) is a five-tier scale used in BIM that describes how much information a model element carries. LOD 100 is conceptual mass; LOD 500 is field-verified as-built. Specifying the wrong level — too low and the model can’t support the use case, too high and the project pays for fidelity it doesn’t need — is one of the most common and most expensive mistakes in BIM procurement. The right LOD matches the intended use of the model, varies by element category, and should be specified in the Exchange Information Requirements (EIR) before tender.

Definitions, in plain language

LOD (Level of Development) is a five-tier scale used in BIM. Each tier defines how complete an element is in geometry and how reliable it is in attributes. The American Institute of Architects’ AIA G202 is the most widely cited reference; ISO 19650 uses Level of Information Need (LOIN), which expresses the same concept differently.

EIR (Exchange Information Requirements) is the client’s written specification for what information they need at each project stage — including the LOD per element category.

QTO (Quantity Take-Off) is the extraction of material and labor quantities from the model. Defensible QTO requires LOD 300 minimum.

Element category is a group of model components that share modeling conventions — walls, doors, MEP ducts, structural beams, site elements, and so on.

The conversations behind this article

“The client wrote ‘LOD 500’ in the EIR. We’re already deep in design. Are we under-delivering?”

“We’ve been told to model everything at LOD 400. The fee doesn’t support it. What’s negotiable?”

“What’s the difference between LOD 350 and LOD 400 for an MEP duct, in real terms?”

“We’re a small consulting firm. The procurement team copied an EIR from a giga-project tender. We don’t think they understand what they asked for. How do we push back?”

These questions come up every time a project goes from concept to detailed design. The answers aren’t theoretical — they have direct cost and risk implications.

What does each LOD level actually mean?

LOD 100 — Conceptual

Generic shapes and approximate areas. A massing study. Useful for early feasibility, sun-path analysis, and stakeholder buy-in. Do not expect quantities or coordination value at this level. Walls might be represented as a single plane with no thickness; doors as openings.

LOD 200 — Generic systems

Approximate size, shape, location, and orientation. Suitable for early-stage coordination and high-level clash review. Quantities are still indicative only. A wall has a thickness but doesn’t yet carry material specifications. Equipment is modeled as a generic block in roughly the right place.

LOD 300 — Specific systems

Accurate dimensions, locations, and quantities. Hard clash detection becomes meaningful. This is the standard level for design development and most coordination work in the Saudi market. A wall now has its specified materials, structure, and finishes. A duct has size, route, and connections.

LOD 350 — Coordinated assemblies

Adds connection details, supports, and interfaces between elements. Critical for projects with significant prefabrication or where multiple disciplines are tightly integrated. The “missing” level between 300 and 400 — and increasingly the level Saudi tenders specify for MEP coordination.

LOD 400 — Fabrication-ready

Detailed enough that elements can be procured, fabricated, and installed directly from the model. Required for prefabrication-heavy MEP scopes, modular construction, and any context where the model goes to a fabricator. Hangers, supports, insulation, manufacturer-specific data — all present.

LOD 500 — Field-verified as-built

A representation of what was actually built, verified on site. Required for FM handover and as the canonical operations record. Often produced via Scan to BIM at project close, with attributes populated for COBie handover.

How should a project choose the right LOD?

The right LOD is the one that matches the intended use of the model, not the one that sounds most impressive. Three diagnostic questions surface the answer:

1. What decisions will be made from this model? Visualization for stakeholder buy-in needs LOD 200 at most. Fabrication needs LOD 400. The use case dictates the level.
2. Will the model become the FM record? If yes, target LOD 500 with proper COBie data structure for the handover deliverable. If not, LOD 400 is usually sufficient for the construction phase.
3. Is there a Quantity Take-Off requirement? Defensible QTO needs at least LOD 300, ideally LOD 400 for trades with significant cost weight (MEP, structural steel, façade).

Why specify LOD by element category, not as a blanket figure?

This is the single biggest optimization most clients miss. LOD does not need to be uniform across the model. A well-written EIR specifies LOD by element category and project stage. Examples:

Specifying the entire model at LOD 400 because “higher is safer” pays a premium for fidelity that has no operational value. Specifying everything at LOD 300 underspecifies the elements that actually need fabrication-grade detail.

The cost difference between a model specified well by category versus a blanket LOD 400 is significant — often 20-40% of the BIM scope, depending on the project mix.

What does LOD specification look like in a typical Saudi tender?

Tenders in 2025-2026 across the Kingdom typically specify:

• Hospitality and mixed-use — LOD 400 for MEP (especially for prefabrication), LOD 350 for architectural finishes, LOD 500 at handover for the FM record.
• Government, healthcare, education — LOD 400 for services with strict adherence to ministry standards (e.g., Ministry of Health BIM Manual), LOD 500 for the operations dataset.
• Infrastructure (Riyadh Metro, NEOM Spine, the Saudi Landbridge) — LOD 400-500 with linear referencing and 5D cost integration.
• Residential at scale (ROSHN, NHC) — LOD 350 with prefabrication-ready details for repeated unit types.

The pattern: higher LOD where there’s prefabrication, where there’s a high cost-of-rework risk, or where the model becomes the FM record.

What should a firm do this week if facing an LOD specification problem?

Three practical steps:

1. Read the EIR carefully and compare against AIA G202 or ISO 19650 LOIN definitions. If the EIR says “LOD 500” without specifying intended use, it likely needs clarification.
2. Map LOD by element category, not project-wide. Author a counter-proposal that specifies LOD per category. Most clients accept a thoughtful counter-proposal once they understand the cost implication.
3. Document assumptions in the BEP. Whatever LOD is agreed, document it in the Pre-Contract BEP with examples per element category. This is what saves the project from disputes later.

How does OnePoint engage on LOD scoping?

• EIR review — We read the client’s EIR, identify ambiguities, and propose a defensible interpretation. Output: a marked-up EIR with questions for clarification.
• LOD scoping workshop — A two-hour session with the project team to agree LOD per element category against the actual use cases. Output: a per-category LOD matrix that goes into the BEP.
• BEP authoring — We write the Pre-Contract or Post-Contract BEP that locks in LOD and exchange formats, defensible against client audit.

See OnePoint’s BIM Modeling and 3D Coordination services →

Frequently asked questions

Is LOD 500 the highest, so should we always aim for it?

No. LOD 500 means “field-verified as-built” — it’s a record of what was actually constructed, not a design level. Specifying LOD 500 at design stage is meaningless. The right specification is LOD 400 at design and construction with LOD 500 at handover, and only if the model becomes the FM record.

What’s the difference between LOD 350 and LOD 400?

LOD 350 adds connection and interface details to LOD 300. LOD 400 adds fabrication-ready detail: specific manufacturer data, exact hangers, insulation, install instructions.

Does ISO 19650 use LOD?

ISO 19650 uses Level of Information Need (LOIN), which decomposes LOD into geometrical (LOG) and information (LOI) components. The concept is the same; the vocabulary differs.

Can the model be at different LODs for different stages?

Yes — and it should be. A typical project progresses: LOD 100-200 at concept, LOD 300 at design development, LOD 400 at construction documentation, LOD 500 at handover.

What if our team doesn’t have LOD 400 capability?

Either build the capability (12-18 months of consistent project exposure plus training) or partner with a specialist who delivers the LOD 400 scope while transferring process.

Key takeaways

• LOD is a five-tier scale describing how much information a model element carries.
• The right LOD matches the intended use of the model — not the highest available.
• LOD should vary by element category and project stage.
• Saudi tenders increasingly specify LOD 400 for MEP and LOD 500 at handover.
• Three diagnostic questions surface the right specification quickly.

Related reading

• Why Is BIM No Longer Optional in Saudi Arabia?
• Scan to BIM: When the Drawings Don’t Exist (Or Lie)
• 4D and 5D BIM: Making Schedule and Cost Visible
• COBie and the Asset Data Question Most Owners Forget
• Choosing a BIM Partner: 7 Questions That Tell You What You’re Buying

OnePoint is a Saudi-registered BIM Solutions practice based in Riyadh, established in 2017. To discuss a project, request a quote or reach us at info@onepoint.com.sa.