LOD in Scan to BIM: Differences Between Level of Detail and Project Scope

The rapid evolution of the AEC sector has witnessed various technological developments, accelerating the design and construction process for AEC professionals. Building Information Modeling (BIM) is one such process that involves digital representation of a built form, leading to accurate and seamless results on-site.

As much as it simplifies the designing and construction work, it brings unique challenges to the table with unstructured data and processes that result in cost and time overruns. A clear understanding of how much detail and what geometry level is required significantly impacts the process, saving time and costs.

In the realm of Scan to BIM projects, there’s often a common misconception that Level of Detail (LOD) and Project Scope are one and the same.

However, it’s crucial to recognize that these are two distinct aspects that require separate consideration and clarification. Let’s delve into this topic further to understand the difference and why it matters.

What is the Level of Development (LOD) in Scan to BIM?

Level of development is a set of standards that defines the different stages of project development within BIM and provides the AEC professionals the power to document and describe the BIM content effectively and clearly.

The LOD is an industry standard that helps verify the reliability of information associated with components of the project model.

The LOD requirements also define the measure of service level required to develop the project model. BIM modeling services use LOD to enhance 3D BIM models using a numerical lexicon, facilitating better understanding among stakeholders of all disciplines.

Every project has a reusable checklist to verify various components, and LOD can be integrated into the list by assigning an LOD status attribute to the components on the list. Attaching a LOD status will provide certainty about the quality of information at a given point, enhancing the final project outcome.

How Did the Concept of LOD Start?

The American Institute of Architects (AIA) introduced Levels of Development (LOD 100–500) in E202‑2008, later organizing model content and authorized uses in G202‑2013. The BIMForum then published the LOD Specification to interpret AIA’s definitions with system‑specific examples, and formalized LOD 350 to describe modeled interfaces needed for coordination. The LOD framework defines what model elements can be relied on for at various stages; it does not itself set accuracy tolerances or dictate project phases.

Complete Explanation of LOD 100–500 in BIM

AIA digital practice documents guide defines various Levels of Development for using Revit BIM modeling services as discussed below:

LOD 100 – Conceptual Massing from Scan Data

Concise Definition

LOD 100 represents a conceptual level model where building elements are shown as approximate masses, symbols, or generic forms that communicate overall size, shape, volume, orientation, and location without defining specific systems or components. In a Scan-to-BIM context, this level conveys high-level design intent and spatial understanding rather than construction information. Any quantities, areas, or dimensions derived from LOD 100 elements must be considered approximate and suitable only for early-stage evaluation such as feasibility, planning, or portfolio-level analysis.

Scan to BIM Specifics

In Scan to BIM workflows the point cloud is used primarily as a visual reference to establish the overall building envelope and major volumetric zones such as main blocks, roof profiles, atriums, or core shafts. The objective is not to trace every surface but to capture the dominant geometric form of the structure.

Modeling is performed using simple masses or very basic generic walls, floors, and roofs. There is no effort to define exact wall thicknesses, precise slab edges, openings, façade articulation, or specific system types. Geometry is generalized to communicate scale rather than detail.

Included:

• Overall building footprint
• Building height and general elevation profile
• Floor to floor levels (approximate)
• Roof forms and slopes (conceptual)
• GFA-level accuracy
• Major volumetric zones (e.g., building blocks, towers, podiums, cores)

Excluded:

• Individual doors and windows
• Detailed façade elements
• Structural framing members
• MEP systems
• Interior partitions and finishes
• Penetrations, interfaces, or coordination details
• Fabrication or construction information

Common Use Cases

LOD 100 is primarily used for feasibility studies, master planning, high level area validation and early stakeholder discussions. It is appropriate when a client needs to quickly understand building scale, zoning capacity or redevelopment potential without investing in detailed scanning or modeling. For example, a hospital redevelopment concept may show only major building blocks and space allocations to support early decision-making before moving into schematic or coordination stages.

Scope–Cost Note

LOD 100 represents the lowest modeling effort in Scan to BIM projects and requires minimal scanning density. Coarse laser scans (typically 15–20 mm spacing) are generally sufficient because only overall geometry and envelope forms are derived. Modeling turnaround is fast, resource requirements are limited, and quality control focuses on volumetric accuracy rather than element-level precision. This makes LOD 100 highly cost-effective for early-stage studies.

Note:

• LOD 100 does not support coordination, clash detection, or construction documentation.
• All measurements, areas, and volumes must be treated as approximate.
• It should never be used for procurement, fabrication, or permit-level submissions.
• Upgrading from LOD 100 to higher LODs typically requires additional scanning and substantial re-modeling, as detailed systems are not embedded at this stage.
• Clearly defining that the deliverable is “conceptual massing only” in the project scope prevents unrealistic expectations from stakeholders.

Case Study --> Scan to BIM Modeling with LOD 300 for a UK-based Educational Institute

LOD 200 – Schematic Existing Conditions

Concise Definition

LOD 200 represents schematic-level modeling where building elements are shown as generic systems or assemblies with approximate quantities, size, shape, location, and orientation. In a Scan-to-BIM workflow, this level translates point cloud data into a structured architectural, structural, and MEP framework that communicates spatial relationships and system layout while maintaining generalized geometry. The model supports early design validation, spatial analysis, and preliminary cost planning, with all derived dimensions and quantities considered approximate and suitable for schematic decision-making.

Scan to BIM Specifics

Modelers interpret the point cloud to create generalized walls, slabs, columns, beams, and roof forms that follow the visible geometry. Each element represents its correct system category, while dimensions reflect best-fit alignment to the scan within agreed tolerances suitable for schematic use.

For MEP systems, primary ducts, pipes, cable trays, and major equipment zones are represented as generic components. Routing reflects actual system paths captured in the scan while fittings and detailed transitions remain simplified to maintain schematic clarity.

Included:

• Architectural shell
• Primary structural grid
• Main vertical circulation elements
• Primary MEP runs (ducts, pipes, trays as generic systems)
• Approximate dimensions and quantities
• Basic element classification and system identification
• Overall spatial relationships between discipline

Excluded:

• Precise offsets and micro-deviations from scan data
• Detailed fittings, reducers, and transitions
• Fabrication-level components
• Hangers, supports, bolts, and flanges
• Trade-level connection hardware
• High-precision penetration detailing

Common Use Cases

LOD 200 supports space planning, area calculations, zoning submissions, early-stage cost estimation, and sustainability analysis. Project teams use this level to evaluate layout options, validate structural grids, and understand primary MEP routing within existing buildings. It enables schematic approvals and informed concept development while maintaining efficiency in time and budget.

Scope–Cost Note

LOD 200 requires moderate modeling effort compared to conceptual massing. Medium to coarse laser scan density, typically in the range of 10–20 mm spacing, provides sufficient data to capture general system geometry and spatial relationships. Modeling time increases compared to LOD 100 due to the introduction of categorized building systems, though the process remains efficient for large-area schematic documentation.

Note:

• LOD 200 supports schematic coordination and early clash review at a system level.
• Quantities and dimensions serve planning and estimation purposes.
• Project teams often use LOD 200 as a foundation for progressing into LOD 300 for renovation or coordination phases.
• Clear definition of which systems are included at this level ensures alignment between client expectations and modeling deliverables.
• LOD 300 – Detailed Design / Standard Existing Conditions
• Concise Definition

LOD 300 – Detailed Design / Standard Existing Conditions

Concise Definition

LOD 300 represents a detailed design level model where each element is graphically modeled as a specific system, object, or assembly with accurate quantity, size, shape, location and orientation. In a Scan to BIM workflow this level translates point cloud data into precisely aligned architectural, structural and MEP components that reflect real world geometry within agreed tolerances ±10–20 mm for building projects. Elements are positioned accurately relative to the defined project origin and relevant non-graphic information such as material or system classification may be attached. LOD 300 supports design coordination, construction documentation and reliable quantity extraction.

Scan to BIM Specifics

Modelers align elements directly to the registered point cloud using agreed tolerance standards. Walls, slabs, columns, beams, doors, and windows follow actual measured dimensions, and structural grids reflect the built condition rather than assumed layouts. Each object uses the correct category and family type to maintain BIM integrity.

For MEP systems ducts, pipes, cable trays and major equipment are modeled with accurate cross-sections and routing paths. Geometry reflects true installed positions captured in the scan, enabling dependable system-level coordination and spatial validation across disciplines.

Included:

• Walls with accurate thickness and placement
• Doors and windows with real dimensions and sill/head heights
• Structural beams, columns and slabs with correct profiles
• Major ducts, pipes and cable trays with accurate sizes
• Equipment footprints and primary service zones
• Quantity take-offs suitable for scheduling
• Basic material and system data
• Correct alignment to project coordinates

Excluded:

• Hangers and support rods
• Bolts, welds, and connection hardware
• Fabrication-level detailing
• Trade-specific connection assemblies
• Vendor-specific manufacturing parameters
• Installation sequencing data
• Common Use Cases

LOD 300 serves renovation and extension projects, permit documentation, tender drawings and multidisciplinary coordination. Project teams rely on this level to conduct system level clash detection, validate spatial clearances, and produce construction ready documentation. It has become the standard deliverable for existing conditions modeling because it balances precision, usability, and project cost across most AEC workflows.

Scope–Cost Note

LOD 300 requires higher scan quality and coverage compared to schematic levels. A point density of approximately 5–10 mm spacing typically supports accurate geometry fitting and reliable dimensioning. Modeling time increases significantly compared to LOD 200 because each element must align precisely with scan data and maintain BIM classification standards. Quality assurance processes also become more rigorous to confirm tolerance compliance.

Note:

• LOD 300 establishes the foundation for reliable coordination and documentation.
• Quantity extraction at this level supports procurement planning and cost validation.
• Many Construction projects adopt LOD 300 as the baseline for existing conditions before selectively upgrading complex areas to LOD 350.
• Clear tolerance definition in the project scope ensures alignment between scan accuracy, modeling detailed and stakeholder expectations.

LOD 350 – Coordination-Level Interfaces (Critical Distinction)

Concise Definition

LOD 350 represents a coordination-focused modeling level where elements are modeled as specific systems or assemblies with accurate quantity, size, shape, location, and orientation, including their interfaces with other building systems. This level extends beyond accurate geometry to explicitly define how architectural, structural, and MEP components intersect, connect and influence one another. Model elements include penetrations, openings, offsets and routing conditions necessary to validate constructability. Non-graphic information may be attached to support coordination and geometry aligns to the point cloud within high-precision tolerances suitable for interdisciplinary validation.

What Makes It Different from LOD 300?

LOD 300 establishes accurate geometry and confirms design intent, while LOD 350 models system interfaces and validates constructability. At this level, the model demonstrates how elements physically relate to one another, enabling reliable clash detection and coordinated installation planning.

Scan to BIM Specifics

Modelers use high-resolution point cloud data to define structural openings in slabs and beams, sleeves within walls, framed penetrations, and clearance zones around services. Geometry reflects real intersection conditions observed in the scan, particularly in congested areas.

MEP systems include accurately routed fittings, reducers, take offs and transitions around structural and architectural constraints. Architectural components such as soffits, ceiling bulkheads, recessed zones and service corridors. These are modeled to reflect actual coordination conditions that influence service installation.

Included:

• Trade interfaces between architecture, structure, and MEP
• Structural openings and slab/beam penetrations
• Sleeves and framed wall penetrations
• Coordinated routing in congested zones
• Modeled fittings, reducers, and directional changes
• Clearance validation for ducts, pipes, and trays
• Reliable clash detection geometry
• Interface-aware assemblies suitable for coordination reviews

Excluded:

• Full fabrication hardware and hanger rod detailing
• Bolt patterns and weld-level steel detailing
• Vendor-specific shop drawing components
• Manufacturing constraints and spool-level breakdown
• Installation sequencing logic

Common Use Cases

LOD 350 supports plant room upgrades, hospital MEP rerouting, industrial retrofits and other high risk coordination zones where system congestion demands precise interface modeling. Project teams often apply LOD 300 across general building areas and selectively upgrade mechanical rooms, risers, ceiling plenums and equipment zones to LOD 350 to ensure coordinated installation and constructability validation.

Scope–Cost Note

LOD 350 introduces a substantial increase in modeling effort compared to LOD 300 because teams must define penetrations, offsets, fittings, and system relationships in detail. High-resolution scans, typically around 5 mm spacing or better, support accurate clearance validation and coordination analysis. Comprehensive scan coverage and strong registration accuracy directly influence the reliability of coordination outputs and clash detection results.

Note:

• LOD 350 enables dependable interdisciplinary clash detection and constructability review.
• This level delivers the highest value in mechanically dense or structurally complex areas.
• Many projects adopt a hybrid strategy by applying LOD 350 selectively to critical zones.
• Clear definition of tolerance expectations and coordination deliverables in the project scope ensures alignment between scanning quality and modeling outcomes.

LOD 400 – Fabrication-Ready Existing Conditions

LOD 400 represents fabrication-ready geometry where each model element is developed as a specific system, object, or assembly with precise size, shape, quantity, location, and orientation, including detailing required for fabrication, assembly, and installation. In a Scan-to-BIM context, this level translates high-accuracy point cloud data into constructible models that support shop drawing production and prefabrication workflows. Elements include the detailing necessary for manufacturing and field installation, and non-graphic data such as fabrication codes, piece marks, and installation references may be embedded to support downstream construction processes.

Scan to BIM Specifics

Modelers align geometry to high-resolution point cloud data to define exact routing and tie-in conditions for prefabricated systems. MEP components include detailed fittings, flanges, valves, reducers, and transitions positioned accurately to reflect real-world installation paths.

Structural elements may incorporate connection plates, stiffeners, bolt patterns, and embed locations when the scan and design documentation support derivation. Hanger locations and support conditions are modeled where fabrication or installation planning requires them, ensuring constructible output.

Included:

• Shop-drawing level geometry
• Exact routing suitable for prefabrication
• Detailed fittings, flanges, valves, and reducers
• Bolt patterns and connection plates (where derivable)
• Hanger and support locations when required
• Fabrication parameters and piece mark data
• Installation and assembly metadata
• High-precision tie-in geometry

Excluded:

• Elements outside defined fabrication zones
• Asset management and lifecycle maintenance datasets
• Operational performance tracking data
• Construction-phase temporary works
• Portfolio-wide modeling beyond agreed scope areas

Common Use Cases

LOD 400 supports prefabricated pipe racks, steel retrofits, industrial plant upgrades and high precision tie-ins where components must fit existing conditions accurately during first installation. Contractors and fabrication teams rely on this level to generate shop drawings, produce spools or assemblies off-site, and plan installation sequencing with confidence in geometric accuracy.

Scope–Cost Note

LOD 400 requires dense laser scanning, robust registration accuracy, and strict quality assurance procedures. Projects often target tolerances in the ±5–10 mm range to ensure prefabricated elements align correctly in the field. Modeling effort increases substantially compared to coordination-level models, and teams typically limit LOD 400 to defined tie-in or fabrication zones rather than applying it across entire buildings to maintain cost control.

Note:

• LOD 400 enables direct generation of shop drawings and fabrication outputs.
• High scan quality directly influences fabrication reliability and installation success.
• Teams often apply this level selectively to prefabrication zones while maintaining lower LODs in general areas.
• Clear agreement on tolerance thresholds and fabrication deliverables ensures alignment between scanning, modeling, and construction execution.

Case Study --> CAD to BIM Conversion for a Commercial Project

LOD 500 – Field‑Verified As‑Built (FM‑Ready)

Concise Definition

LOD 500 represents a field-verified, as-built modeling that reflects the actual constructed condition of a facility in terms of size, shape, location, quantity and orientation, enriched with operational and asset information. This level integrates high-accuracy point cloud verification with comprehensive non-graphic data to support facility management, lifecycle planning, and digital twin applications. The emphasis shifts from design intent or fabrication readiness to confirm real world conditions and long term operational reliability.

Scan to BIM Specifics

Project teams perform verification scans during or after construction to confirm that installed systems align with the modeled geometry within strict tolerance thresholds. Model elements are adjusted to reflect final field conditions rather than design assumptions.

In addition to geometric validation, teams attach asset intelligence such as manufacturer details, serial numbers, equipment IDs, and maintenance parameters. The result is a data-rich digital environment that connects spatial accuracy with operational performance tracking.

Included:

• Field-verified as-built geometry
• Accurate placement of architectural, structural, and MEP systems
• Asset tags and equipment identification numbers
• Manufacturer and model information
• Serial numbers and warranty dates
• Maintenance schedules and service intervals
• Lifecycle and performance-related metadata
• Data structures compatible with facility management platforms

Excluded:

• Temporary construction elements
• Demolished or replaced components
• Fabrication process details unrelated to final installed condition
• Design-stage assumptions superseded by field verification
• Incomplete asset data outside agreed information requirements

Common Use Cases

LOD 500 supports digital twin development, facility management operations, lifecycle cost planning, compliance tracking, and long-term asset management. Owners and operators rely on this level to manage hospitals, industrial plants, airports, campuses, and other mission-critical facilities where accurate spatial and asset intelligence improves maintenance efficiency and capital planning decisions.

Scope–Cost Note

LOD 500 requires high-resolution scanning, rigorous registration control, and structured validation workflows to confirm installation accuracy, often within ±2–5 mm depending on project requirements. Costs increase due to multiple site visits, verification cycles, and structured data capture processes. Organizations typically reserve this level for mission-critical assets, high-value facilities, or strategic digital twin initiatives rather than applying it portfolio-wide at full granularity.

Note:

• LOD 500 delivers operational value beyond construction by supporting asset lifecycle management.
• Clear definition of Asset Information Requirements and Employer’s Information Requirements ensures consistent data capture.
• Data governance and standardized naming conventions strengthen integration with CMMS and CAFM systems.
• Continuous update protocols maintain model accuracy throughout the facility’s operational life.

Pro Tip: Reference BIMForum LOD Spec 2024/2025 in contracts for Scan to BIM; hybrid LOD saves 30–50% vs. uniform high LOD.

What is the Scope of Work in Scan to BIM?

Scope of Work is a list composed of activities and obligations stated in a contractual document that every contractor, sub-contractor, supplier, and other site member is compelled to follow.

Be it any building type, all project stakeholders are usually inclined towards defining a clear scope of work with all major project requirements enlisted in detail.

The document includes what are the necessary tasks during project execution and who is responsible for completing them. Each worker is assigned a set of responsibilities and the expected completion time, facilitating a seamless construction process.

The nature of the scope of work varies from project to project and as per the client requirements in a specific project. Sometimes, it only includes a broad work description, and sometimes it provides a complete project description, program of work with expected delivery time, significant milestones, and end products that are supposed to be provided.

An important thing that should be kept in mind is that the Scope of Work is not set in stone, and can be altered if necessary via change orders or partial terminations, as project requirements and necessities can evolve throughout the construction cycle. Projects with no pre-defined scope of work might result in project delays and payment issues with contractors and suppliers.

Elements of Scope of Work

• Elucidates all tasks, activities, obligations, and duties required for a successful project and desired results.
• States the codes and standards expected to be followed in a project, and all special requirements if any.
• Outlines the requirements of the project and objectives of the contract.
• Explains all responsibilities of the contractors
• Discusses the payment schedule and the contract method.

Read More --> Everything You Need to Know About Scan to BIM

Clarifying Expectations

While LOD defines the level of detail within the BIM model, it does not inherently dictate the Project Scope. It’s essential for stakeholders to understand that specifying LOD alone does not provide a comprehensive understanding of the project requirements.

To avoid misunderstandings and ensure project success, it’s imperative to clearly define both LOD and Project Scope separately. This involves open communication, collaboration, and agreement among all parties involved in the project, including clients, designers, contractors, and BIM specialists.

Conclusion

Level of Development refers to a particular level that discusses a single element of the project and Scope of work entails what all elements will be included and not included in the project model. The scope of work outlines the elements included in a model and how these elements are supposed to be developed.

Before deciding on the LOD requirement for a project, it is crucial to identify the use cases of BIM as different use cases might require specific LOD.

The use cases include site utilization planning, architectural programming, cost analysis, design authoring and briefing, facility management, and much more.

The AEC companies can decide on the scope of work and level of development for a project depending on the client’s requirements and the course of the project.