Scan-to-BIM explained: from point cloud to as-built model

Scan-to-BIM sounds like one step. It is four, and knowing them is the difference between a model you can build from and a model you argue about.

1. Capture

A Spatialist scans the space with a tripod or mobile scanner, choosing the device by tolerance: a FARO Focus or Leica RTC for structural and MEP work, a NavVis VLX 3 for large floors, a handheld for cores and plant rooms.

2. Registration

Individual scans are aligned into one cloud, checked against control points where the project has a survey grid, and cleaned of people, reflections and noise. The registration report is your evidence of accuracy; ask for it.

3. Modelling

A modeller traces the cloud into Revit or ArchiCAD elements. The brief sets the level of detail: LOD 200 for massing and layouts, LOD 300 for coordination with sizes and locations, LOD 350 where connections matter. Scope also matters: architecture only, or structure and MEP too.

4. Delivery and QA

The model is overlaid on the cloud and deviations are flagged. Good practice is to deliver the cloud alongside the model so the design team can check anything they doubt.

How to write a brief

State the use: fit-out design, MEP coordination, heritage record.
State the LOD and disciplines.
State the tolerance you need and where it matters most.
Say which software and template the model must open in.