LOD is frequently used as shorthand for model detail, but a number alone is not a complete scope. Scan-to-BIM teams must define which systems are modelled, the dimensional tolerance, level of information, inaccessible areas, file version, coordinates and acceptance process.
Measured reality also has limits. A scanner records visible surfaces from each station. Ceilings, shafts, operating equipment and restricted spaces may remain occluded. The model should distinguish measured geometry, interpreted geometry and client-supplied information.
LOD 200: approximate systems for planning
LOD 200 commonly represents elements with approximate size, shape, location or orientation. It can support feasibility, early coordination and broad existing-condition context when detailed fabrication or asset decisions are not required.
For Scan to BIM, the team still needs to agree which walls, slabs, roofs, openings, major services or equipment are included. Approximate does not mean uncontrolled; coordinates, levels and source coverage must remain documented.
LOD 300: defined geometry for coordination
LOD 300 is often selected for renovation, design coordination and measured as-built models because modelled elements have defined size, shape, location and orientation within the agreed tolerance. Architectural, structural and MEP scopes may have different inclusion rules.
A point cloud contains more surface detail than a practical BIM. Modellers interpret planes, edges and systems and should not model noise as reality. Acceptance zones and sample checks help confirm the model answers the intended design question.
LOD 400: fabrication intent needs more than a scan
LOD 400 is associated with fabrication, assembly or installation-level detail. Existing-condition scanning alone does not reveal hidden construction, manufacturer data or fabrication logic. Reaching this level generally requires approved design and fabrication information in addition to measured surfaces.
Calling every dense point cloud an LOD 400 model is misleading. The contract should identify which elements, parameters and fabrication relationships genuinely need that definition and which remain measured context.
Write an acceptance-ready Scan-to-BIM scope
Specify disciplines, element list, model uses, units, project origin, levels, tolerances, Revit/IFC version, naming, families, information fields, exclusions and sample acceptance checks. Include a coverage register for inaccessible or occluded areas.
SurveyCopter combines terrestrial LiDAR, registered point clouds, model production and deviation evidence across India. The delivery can include E57, RCP/RCS, LAS/LAZ, RVT, IFC, drawings and a documented assumptions register.
- Coordinate and level strategy
- Capture coverage and registration report
- Discipline/element matrix
- LOD, LOI and tolerance by element
- Native and exchange formats
- Model QA and acceptance sampling
Frequently asked questions
Is LOD 300 always accurate to the same tolerance?
No. LOD describes model development, not a universal millimetre tolerance. The project must specify and verify dimensional acceptance separately.
Can a laser scanner see inside walls?
No. Standard terrestrial LiDAR records visible surfaces. Hidden construction requires other evidence, opening-up or client information.
What files are delivered for Scan to BIM?
Common files include E57, RCP/RCS, LAS/LAZ, RVT, IFC, DWG and PDF, subject to the agreed workflow.
Need a method built around your project?
Share the location, required decision, accuracy and timeline. SurveyCopter will define the appropriate aerial, ground, processing and delivery workflow.
Explore Scan to BIM services in India ↗Technical guidance is provided for general information. Project methods, accuracy, permissions and engineering decisions must be established for the specific site and applicable requirements.