LOD 100 to 500 Explained: How to Specify BIM Detail That Teams Can Deliver
LOD 100 to 500 explained for owners and BIM teams: what each level means, how to specify tolerances, Scan to BIM implications, and QA/QC acceptance criteria.
BimzstudioMar 16, 202614 min
LODLevel of DevelopmentBIM specificationScan to BIMQA/QCRevit
LOD 100 to 500 Explained: Specifying BIM Detail Without Guesswork
Level of Development (LOD) is one of the most quoted—and most misused—concepts in BIM. Owners ask for “LOD 400 models,” contractors argue the model is “only LOD 300,” and Scan to BIM proposals bury critical assumptions in a single acronym. When LOD is unclear, projects overpay for unnecessary detail, under-deliver on critical interfaces, or discover during fabrication that the model never claimed the precision people assumed.
This guide explains LOD 100 to 500 in practical language, shows how to write enforceable LOD matrices, connects LOD to Scan to BIM accuracy and QA/QC, and shares how EU and U.S. teams typically apply these levels on real projects.
Specify LOD by category and tolerance, not as a single slogan.
LOD describes how developed an model element is—not how photorealistic it looks. In widely referenced AIA/BIMForum usage, LOD communicates geometric reliability and the degree to which an element can support downstream uses such as coordination, quantity takeoff, or fabrication.
The recurring project problem is specification by slogan:
“Provide LOD 500 for the whole building.”
“Model everything to LOD 400.”
“As-built LOD” with no tolerance, no category matrix, and no acceptance test.
Those slogans create three failure modes:
Budget blowouts from modeling every hanger, fillet, and decorative reveal.
False confidence when a visually detailed model is still poorly located relative to reality.
Contract disputes when parties interpret the same LOD number differently.
For Scan to BIM, the stakes are higher. Existing conditions are irregular. A duct modeled “to LOD 400” may still be in the wrong place if registration or modeling QA/QC failed. LOD must therefore be paired with:
Element category definitions
Allowed geometric simplification rules
Model-to-cloud tolerances
Information requirements (parameters, classification, phasing)
Without that package, LOD is a label—not a deliverable.
Why It Happens
LOD numbers feel precise but are socially defined
LOD frameworks are consensus tools. They help teams communicate, but they are not substitute for project-specific requirements. People treat “LOD 350” as if it were a machine tolerance. It is not. It is a development milestone description that still needs local definition.
Visual detail is confused with reliability
A highly detailed family can be placed incorrectly. A simpler object can be accurately located and sized for coordination. Stakeholders often equate edge count and hardware graphics with higher LOD.
Different standards ecosystems coexist
Teams may mix:
AIA/BIMForum LOD concepts
ISO 19650 Level of Information Need
National standards and employer information requirements
Software browser “detail levels”
These are related but not identical. Cross-walking them poorly creates false equivalence.
Scan to BIM scopes inherit design-BIM language
Design LOD assumes elements are being authored toward construction. As-built LOD must also state what was measured, what was inferred, and how deviation from the point cloud is accepted.
Commercial proposals compete on a single number
Vendors may bid “LOD 400” cheaper by silently excluding categories, simplifying geometry, or skipping QA. Buyers comparing only the number select the wrong partner.
Industry Examples (EU / USA)
European practice
In many EU projects, LOD language appears alongside ISO 19650 information management. Sophisticated clients specify information need by milestone rather than a single building-wide LOD. Examples:
Infrastructure and public buildings: Clear exchange information requirements; geometry detail varies by discipline and use.
Industrial retrofit in Germany/Netherlands: High geometric reliability in process/MEP zones; lighter architectural context elsewhere.
Heritage projects in Italy/France: Selective high detail for conservation interfaces; documented distinction between measured and reconstructed geometry.
European teams increasingly ask not only “what LOD?” but “what decisions must this information support at this stage?”
United States practice
U.S. design-build and CM-at-risk projects often reference BIMForum LOD interpretations in BIM Execution Plans:
Commercial high-rise: LOD 300 for design coordination; trade partners develop LOD 400 fabrication models for selected systems.
Healthcare: Higher expectations for MEP coordination detail and clearances.
Scan to BIM renovations: Owners request LOD 300/350 as-builts for architecture/MEP, with tighter tolerances in tie-in zones.
Federal and institutional work: Formal BEP and model element tables are more common than informal email scopes.
Across both regions, successful teams use matrices—not one number—and verify deliverables with reviews and, for existing conditions, point-cloud deviation checks.
Technical Explanation
LOD 350–400 is where fabrication and coordination expectations rise.
LOD 100 — Conceptual
Meaning: Symbolic or generic representation. Area, height, volume, location, and orientation may be approximate.
Typical uses: Massing studies, early feasibility, campus planning placeholders.
Not for: Coordination, quantities you will buy, fabrication, or as-built claims.
LOD 200 — Approximate geometry
Meaning: Elements are generalized systems or assemblies with approximate quantities, size, shape, location, and orientation.
Typical uses: Schematic design, early system routing concepts.
Risk: Looks “real” enough that non-BIM stakeholders over-trust it.
LOD 300 — Precise enough for coordination
Meaning: Elements are defined with graphics and information sufficient for coordination and typical construction documentation uses. Size, shape, location, and orientation are suitable for the stated tolerances of the project.
Typical uses: Design coordination, many Scan to BIM as-builts for renovation planning, clash detection at system level.
Scan to BIM note: LOD 300 as-built usually means major architectural/structural/MEP elements are modeled to match scan-derived dimensions within agreed tolerance—not that every accessory is present.
LOD 350 — Coordination-ready interfaces
Meaning: Adjacent element interfaces are developed so disciplines can coordinate connections and penetrations more reliably.
Caution: Requesting LOD 400 from a Scan to BIM architect for all existing conditions is often wasteful. Existing hanger-by-hanger modeling may not improve renovation design unless prefabrication against as-built constraints demands it.
LOD 500 — Field-verified as-built
Meaning: Elements are a field-verified representation in terms of size, shape, location, quantity, and orientation.
Critical clarification: LOD 500 is about verification, not automatically about ultra-high geometric ornament. A verified LOD 300-shaped element can be more valuable than an unverified ornate model. In Scan to BIM, LOD 500 claims require documented field methods and QA/QC evidence—typically registered point clouds and deviation reports.
LOD vs LOI / Level of Information Need
Geometry development and alphanumeric information should be specified separately. You can have:
High geometric LOD with thin attributes
Moderate geometry with rich asset data for FM
ISO-oriented projects often prefer explicit information need statements over overloaded LOD numbers.
Suggested LOD matrix (example)
Category
Design coord.
Prefab corridors
Existing Scan to BIM
FM handover
Exterior walls
300
300
300 verified
300 + assets
Primary structure
300–350
400 (steel trade)
300 verified
300
Main ducts
300–350
400
300–350 critical zones
selected assets
Diffusers
200–300
400 if prefab
often symbolic/omitted
asset points
Heritage ornament
n/a
n/a
selective detail / mesh
documentation links
Best Practices
LOD 500 means verified field conditions — not a prettier LOD 300.
Never specify one LOD for an entire facility unless the facility is tiny and uniform.
Publish a model element table with categories, LOD, notes, and exclusions.
Define intended uses for each milestone (coordinate, fabricate, maintain).
Pair Scan to BIM LOD with tolerances (e.g., 95% of sampled wall faces within ±15 mm of cloud).
State simplification rules (straighten slightly bowed walls? yes/no; max deviation allowed).
Separate trade fabrication models from design/as-built models when appropriate.
Require sample-area approval before full production.
Use QA/QC checklists tied to the LOD matrix, not generic visual review.
Align BEP language with contracts and payment milestones.
Educate non-BIM stakeholders so shaded views are not mistaken for fabrication authority.
Rows = element categories. Columns = project stages. Cells = LOD / information need / notes.
Step 3: Add geometric rules and exclusions
Explicitly exclude or simplify ceiling tiles, small conduit, furniture, temporary objects, etc., unless required.
Step 4: Define acceptance tests
For design BIM: coordination readiness reviews.
For Scan to BIM: registration metrics + deviation sampling + completeness checks.
Step 5: Price and schedule against the matrix
If the matrix changes, commercial terms change. This prevents silent scope erosion.
Step 6: Calibrate on a pilot zone
Model one floor plate or plant room. Review against expectations and adjust rules.
Step 7: Produce, federate, and verify
Run clash detection at the LOD you actually modeled for. Do not expect LOD 200 placeholders to behave like LOD 400 spools.
Step 8: Handover with an LOD responsibility matrix
Document what was verified in field, what remains design-only, and what must be updated after changes.
Case Study
Project: Hospital wing renovation, United States Owner request (initial): “LOD 400 as-built of the entire wing.”
Reality check:
Full LOD 400 of existing conditions would include exhaustive accessory modeling with limited design benefit.
Critical need was accurate shafts, gravity systems, main medical gas routes, and structural constraints for a new imaging suite.
Revised matrix:
Architecture/structure: LOD 300, scan-verified
Primary MEP mains and shafts: LOD 350, scan-verified
Equipment in imaging tie-in zones: higher detail + clearances
Secondary small-diameter runs outside intervention zones: omitted or indicative
QA/QC: deviation reports for all intervention rooms and corridor racks
Outcome: The team delivered faster, spent detail budget where clinical downtime risk was highest, and used clash detection effectively because interface geometry was trustworthy. The owner still received an as-built suitable for design and construction—without paying for fabrication-level noise across non-critical rooms.
Common Mistakes
Equating LOD 500 with “super detailed.” Verification ≠ denser graphics.
Asking Scan to BIM vendors for LOD 400 everywhere. Often unnecessary and poorly verified.
No exclusions list. Scope arguments are guaranteed.
Changing LOD midstream without commercial adjustment.
Using fine detail to hide poor coordinates.
Ignoring information requirements. A geometrically rich, parameter-empty model fails FM use.
Copy-pasting another project’s LOD matrix. Asset type and use cases differ.
Accepting models without sample deviation checks on Scan to BIM work.
Expert Tips
Write LOD in verbs. “Suitable for coordinated penetration layouts,” not just “LOD 350.”
Create two columns: geometry LOD and data readiness. Prevents overloaded numbers.
For existing buildings, add a ‘confidence’ tag. Measured / partially measured / inferred.
Make trade partners responsible for true LOD 400 of their scopes. Design teams coordinate; fabricators detail.
Show owners side-by-side examples of LOD 300 vs 400 for the same corridor—budget conversations become concrete.
Tie payment milestones to approved matrices and pilot zones.
Keep a living exclusions log during scanning and modeling.
Remember performance. Higher LOD across a tower can cripple model usability.
Future Trends
Shift from universal LOD numbers to Level of Information Need in ISO-aligned projects.
Automated QA assists comparing clouds to models for as-built verification claims.
Use-case-based model views delivering different fidelity to contractors, FM, and executives from one governed dataset.
Clearer Scan to BIM standards language distinguishing visualization meshes from LOD-stated BIM elements.
Contracts that pay for verified outcomes (tolerance compliance) rather than claimed LOD labels.
LOD will remain useful shorthand—but the winning teams will specify evidence, not just numbers.
How Owners Should Buy LOD (Without Getting Surprised)
Owners and client-side project managers can protect budget and quality with a short procurement pattern:
State the decisions the model must support in the first ninety days after delivery.
Require a draft model element table as part of every serious proposal—not only a price and an LOD slogan.
Ask for a sample of prior work showing model-to-cloud overlays for Scan to BIM scopes.
Separate unit rates for LOD 300 verified architecture, LOD 350 congested MEP zones, and true fabrication-support detail.
Hold a pilot approval gate before authorizing full-building production.
Pay for verification evidence (deviation sampling, registration reports) as an explicit line—not an assumed courtesy.
This approach usually costs less than a poorly scoped “LOD 400 everywhere” purchase, because detail budget lands where risk lives. It also makes apples-to-apples vendor comparison possible. Two firms quoting “LOD 300” may still differ by a factor of two in effort if one includes above-ceiling mains and the other models only visible architecture.
For multi-phase campuses, consider a portfolio LOD playbook: standard rules for offices, tighter rules for labs and plants, and heritage addenda where conservation authorities require measured evidence. Consistency across buildings reduces staff training time and improves FM reuse.
FAQ
1. What is the difference between LOD 300 and LOD 400?
LOD 300 supports coordinated design and typical construction documentation uses with reliably sized and located elements. LOD 400 is developed for fabrication and assembly, usually by trades, with manufacturing-level detail.
2. Is LOD 500 the same as Scan to BIM?
No. Scan to BIM is a method for creating models from reality capture. LOD 500 means field-verified as-built status. A Scan to BIM model can be verified to support LOD 500 claims only if QA/QC and field methods are documented.
3. Do I need LOD 400 for renovation design?
Often no. Many renovations succeed with verified LOD 300/350 as-builts plus selective higher detail in tie-in zones. Request LOD 400 where prefabrication or install-critical interfaces demand it.
4. Can one element have different LOD over time?
Yes. Elements progress through project stages. Track milestone requirements in the BEP and model element table.
5. How does LOD relate to point cloud density?
Indirectly. Higher LOD claims for as-builts generally need sufficient cloud completeness and accuracy in the relevant zones—but dense clouds alone do not create high LOD models.
6. What should be in an LOD matrix?
Categories, stages, target LOD, information requirements, tolerances, exclusions, responsible party, and acceptance method.
7. Why do EU projects talk about information need instead of only LOD?
ISO 19650-oriented practice emphasizes specifying the information required for decisions at each stage—geometry and data—rather than relying on a single composite number.
8. How can we verify LOD deliverables?
Through reviews against the matrix, clash readiness tests for coordination LOD, fabrication workshops for LOD 400, and model-to-cloud deviation sampling for as-built verification.
Summary
LOD 100 to 500 explained simply: the numbers communicate development reliability for stated uses, not decorative complexity. LOD 100–200 support early concepts; LOD 300–350 support coordination; LOD 400 supports fabrication; LOD 500 indicates field verification. Projects fail when a single LOD slogan replaces a category matrix, tolerances, exclusions, and acceptance tests.
For Scan to BIM, pair LOD with QA/QC against registered point clouds and clearly mark measured versus inferred geometry. EU and U.S. teams that write precise matrices get predictable costs and usable models; teams that buy a number get disputes.
Specify LOD with Confidence — Bimzstudio
Bimzstudio helps owners and project teams translate LOD language into deliverable Scan to BIM scopes: category matrices, tolerance targets, and QA/QC checks against point cloud data. Whether you need LOD 300 verified as-builts for renovation coordination or selective higher detail for critical MEP interfaces, we align model development to EU and U.S. project realities—so you pay for decision-grade detail, not inflated labels.
Share your project type and intended model uses, and we will recommend a practical LOD matrix before modeling begins.
