Scan-to-BIM is the process of turning raw 3D laser-scan data into an intelligent, parametric BIM model — usually in Autodesk Revit — that designers, contractors, and owners can actually use to make decisions. The scan answers 'what is there?' The BIM model answers 'what do we do about it?'
The plain-English definition
A 3D laser scanner captures the physical world as a point cloud — a dense, color-mapped collection of millions of measured XYZ coordinates. By itself, a point cloud is fantastic for visualizing existing conditions, but it is not something a designer can detail, an estimator can quantify, or a fabricator can build from.
Scan-to-BIM is the modeling step that converts that cloud into the elements people actually work with: walls, floors, columns, beams, ductwork, piping, conduit, equipment, and so on. The output is a Revit model that lives inside the team's normal design and coordination workflow — not a side artifact.
How the workflow runs end-to-end
A typical Scan-to-BIM engagement runs in five stages. The first three live in the field; the last two live in the office.
- Site walk and scope. Identify what areas to capture, what disciplines to model, and what level of detail (LOD) is required.
- Field capture. Crews scan with terrestrial (Leica RTC360, FARO Focus) or mobile (NavVis VLX, Leica BLK ARC) scanners, with target control where accuracy demands it.
- Registration. Individual scans are stitched into a single coordinated cloud in Cyclone REGISTER 360 or equivalent, with an accuracy report.
- Modeling. Discipline modelers build inside Revit against the cloud — architectural, structural, and MEP elements at the agreed LOD.
- QA and deviation. The model is checked against the cloud and delivered with a color-mapped deviation report so accuracy is provable, not promised.
Why LOD is the single most important decision
LOD — Level of Development — defines how much geometric and informational fidelity the model carries. LOD 200 is generic shapes in roughly the right size and location. LOD 350 is fabrication-aware geometry with connections. LOD 500 is verified-installed reality.
Most Scan-to-BIM disasters trace back to a vague LOD agreement at scoping. Get specific: 'LOD 300 architectural and structural, LOD 350 mechanical and piping, LOD 200 ceilings and finishes.' That single line determines how long modeling takes, what it costs, and whether the deliverable is useful.
What you actually receive
- Native Revit (.rvt) models per discipline at the agreed LOD
- A federated Navisworks (.nwd / .nwc) coordination model
- IFC exports for openBIM workflows
- A linked point cloud (.rcp) packaged with the model
- A color-mapped deviation report (model-vs-cloud) with element-level tolerances
- BIM execution plan (BEP) compliance checklist signed off at handover
When Scan-to-BIM is worth it
Scan-to-BIM pays back fastest when existing conditions matter and field surprises are expensive. That covers more projects than most teams realize.
- Renovations and tenant fit-outs where drawings of record are stale or wrong
- MEP retrofits and prefabrication-driven coordination
- Mission-critical facilities — data centers, semiconductor fabs, hospitals
- Historic and adaptive-reuse projects where invasive measurement is not an option
- Owner digital-twin and as-built archive programs