BIM Standards
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.
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.
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:
Those slogans create three failure modes:
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:
Without that package, LOD is a label—not a deliverable.
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.
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.
Teams may mix:
These are related but not identical. Cross-walking them poorly creates false equivalence.
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.
Vendors may bid “LOD 400” cheaper by silently excluding categories, simplifying geometry, or skipping QA. Buyers comparing only the number select the wrong partner.
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:
European teams increasingly ask not only “what LOD?” but “what decisions must this information support at this stage?”
U.S. design-build and CM-at-risk projects often reference BIMForum LOD interpretations in BIM Execution Plans:
Across both regions, successful teams use matrices—not one number—and verify deliverables with reviews and, for existing conditions, point-cloud deviation checks.
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.
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.
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.
Meaning: Adjacent element interfaces are developed so disciplines can coordinate connections and penetrations more reliably.
Typical uses: Complex MEP coordination, penetration management, tighter federated model reviews.
Why it matters: Many “clash surprises” happen at interfaces that LOD 300 representations leave ambiguous.
Meaning: Elements are developed in sufficient detail for fabrication and assembly, often by the trade responsible for installing that scope.
Typical uses: Duct manufacture, pipe spooling, steel detailing, prefabricated corridor racks.
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.
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.
Geometry development and alphanumeric information should be specified separately. You can have:
ISO-oriented projects often prefer explicit information need statements over overloaded LOD numbers.
| 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 |
Examples: permit drawings, clash-free corridors, prefabricated racks, stone replacement, asset inventory.
Rows = element categories. Columns = project stages. Cells = LOD / information need / notes.
Explicitly exclude or simplify ceiling tiles, small conduit, furniture, temporary objects, etc., unless required.
For design BIM: coordination readiness reviews.
For Scan to BIM: registration metrics + deviation sampling + completeness checks.
If the matrix changes, commercial terms change. This prevents silent scope erosion.
Model one floor plate or plant room. Review against expectations and adjust rules.
Run clash detection at the LOD you actually modeled for. Do not expect LOD 200 placeholders to behave like LOD 400 spools.
Document what was verified in field, what remains design-only, and what must be updated after changes.
Project: Hospital wing renovation, United States
Owner request (initial): “LOD 400 as-built of the entire wing.”
Reality check:
Revised matrix:
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.
LOD will remain useful shorthand—but the winning teams will specify evidence, not just numbers.
Owners and client-side project managers can protect budget and quality with a short procurement pattern:
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.
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.
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.
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.
Yes. Elements progress through project stages. Track milestone requirements in the BEP and model element table.
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.
Categories, stages, target LOD, information requirements, tolerances, exclusions, responsible party, and acceptance method.
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.
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.
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.
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.
Continue with the related service, or request a scoped proposal if you already have a brief.
Complete Guide to Scan to BIM
Learn Scan to BIM end to end—scanning, registration, modeling, LOD, and QA/QC—for renovation and as-built projects across Europe and the USA.
Point Cloud to Revit Workflow Explained
A production Point Cloud to Revit workflow—from ReCap linking and shared coordinates to modeling, QA, and clash-ready exports for as-built BIM.
Best Point Cloud File Formats
Compare point cloud file formats—E57, LAS/LAZ, RCS/RCP, PTS, and native vendor files—for Scan to BIM exchange, archiving, and Revit workflows.
| documentation links |
Owner-confirmed studies that already list this service — visual delivery evidence, not invented metrics.
1105 Lakewood
A Point Cloud → BIM comparison of 1105 Lakewood. The scan and the BIM model share the same viewpoint so the existing condition can be read against the modeled geometry.
18 Grand Avenue
Residential Scan-to-BIM work for 18 Grand Avenue. Cutaway and plan views compare existing-condition scan data with the BIM model. Exterior stills are shown independently and are not used as a slider pair.
Foyer Soleil – Résidence Les Marronniers
Residential BIM for Foyer Soleil – Résidence Les Marronniers. A plan-view scan overlay can be compared with the BIM layout. Exterior elevations are shown as BIM drawings, not as a point-cloud slider.
Telecom Infrastructure As-Built Modeling
As-built BIM for a building with rooftop telecom equipment. The axonometric pair compares an existing-condition capture with the BIM model of the same volume. Façade stills are shown independently.
Language
