Scan-to-BIM Workflow Guide: Step by Step (2026)

This guide walks through the five phases, the target LOD, accuracy requirements and available production workflows. With ATIS.cloud, share the survey with your project team, then prepare drawings and models in ATIS.cad or continue modeling in your CAD/BIM software.

Before phase 1: lock the modeling brief

Before anyone scans or models, the team must agree on the zones to capture, target objects, attributes, coordinates, tolerances, LOD or LOI requirements, file deliverables and acceptance method. This brief prevents a technically accurate survey from becoming an unusable BIM delivery.

Need the concept before the execution details? Read the Scan-to-BIM definition. Need a map of the wider topic and its specialist guides? Open the Scan-to-BIM resource hub.

The 5 phases of a scan-to-BIM project

The consensus across industry guides (Matterport, NavVis, Autodesk) is a five-phase pipeline. Skipping or rushing any phase shows up later as rework, missed clashes, or a model your structural engineer cannot trust.

Phase 1. Planning and scope

Before any scanner leaves the office, you negotiate the deliverable. The two key parameters: Level of Accuracy (LOA, how much real-world tolerance the points have) and Level of Development (LOD, how detailed the BIM model needs to be). The USIBD publishes an LOA standard; the BIM Forum / AIA publish the LOD standard.

• Renovation: target LOD 200 to LOD 300, LOA 20 to LOA 30 (5 to 15 mm).
• Facility management twin: can stop at LOD 200.
• Fabrication-ready MEP twin: needs LOD 400.
• Get this wrong: you either over-deliver (and lose money) or under-deliver (and get the call from the architect three weeks later).

Planning also covers the survey control: do you tie scans to a project grid, a national geodetic reference, or a local arbitrary origin? It covers logistics: access times, occupied zones, dust, vibrations, scaffolding. It covers the scanner choice (static for accuracy, mobile or handheld for speed, drone for facades and roofs). And it covers the registration strategy: targets versus targetless cloud-to-cloud registration.

Phase 2. Field scanning

On site, the operator positions the scanner at predefined stations. For static terrestrial scanning, expect 30 to 50 percent overlap between stations so software can later align them. Each station produces a panoramic scan in a few minutes (static terrestrial scanners from FARO, Leica, Trimble and Riegl are all in this family).

Mobile mapping with NavVis or FARO Orbis trades a bit of accuracy for an order-of-magnitude speed gain. Matterport sits at the bottom of the accuracy ladder but covers a small house in an afternoon. All the scanner brands that ATIS.cloud handles natively (FARO, Leica, NavVis, Riegl, Trimble, Viametris, Matterport, etc.) cover the bulk of professional scanning hardware.

Phase 3. Data processing and registration

Back at the office, individual scan stations are aligned ("registered") into a single coordinate system. Industry guides report a target of under 2 mm registration error on a well-planned static project. Manufacturer-side processing software from FARO, Leica, Trimble and NavVis does most of the work, with cloud-to-cloud registration assisted by AI or targets.

• Noise removal: filter out ghost points caused by moving objects or atmospheric interference.
• Vegetation filtering: drop tree foliage and grass that hide built surfaces.
• Classification: separate ground from building from clutter.
• Export: usually E57 for portability, RCP/RCS for downstream Revit work, LAS/LAZ for survey workflows.

Phase 4. Quality assurance

QA is the phase most teams skimp on, and the phase that distinguishes a clean deliverable from a costly mess. Check three things.

1. Registration accuracy: target under 2 mm on static projects, look at the per-station error report.
2. Coverage gaps: overlay the cloud on a floor plan and look for blind zones.
3. Control point alignment: verify that the cloud lines up with surveyed reference points.

Phase 5. Deliverables and BIM modeling

Separate the source survey from the required deliverables: 2D drawings, a BIM model or both. In ATIS.cad, Scan-to-Plan prepares drawings and Scan-to-BIM proposes building objects. The modeler checks each suggestion, adjusts or rejects it, then adds missing elements. External BIM software remains another route, particularly when the specification requires particular objects or native file formats.

The 2D drawings prepared in ATIS.cad export as PDF, DWG or DXF. For a BIM model, IFC export carries building objects after review. Check levels, openings and 3D consistency before handover, then open the result in an IFC viewer. For specialized equipment or services, check that the tool and deliverable cover the requirement; wall detection does not imply support for those objects. ATIS.cad is in early access until the end of November 2026, on request and activated by the team. This is separate from the ATIS.cloud trial.

LOD levels: choosing the right target

Level of Development (LOD) defines how complete a BIM model element is. The AIA defines LOD 100, 200, 300, 400, 500; the BIM Forum added LOD 350 for trade coordination. Here is what each level means, with the typical scan-to-BIM use case.

Accuracy: what to expect, what to demand

Static terrestrial laser scanners (FARO, Leica, Trimble, Riegl) deliver point accuracy in the millimeter range under good conditions, per manufacturer specifications and Wikipedia references on 3D scanning. Mobile mapping systems (NavVis, FARO Orbis) typically deliver centimeter-range accuracy. Photogrammetry from drones can match laser scanning on textured outdoor surfaces but degrades on smooth or reflective surfaces.

Two metrics matter on a scan-to-BIM project. Point accuracy: the deviation of each scanned point from the real surface. Registration accuracy: how cleanly all scan stations align. Industry guides target under 2 mm registration error on a careful static project. Real-world projects often see 3 to 5 mm. That ceiling cascades into the model: a BIM element cannot be more accurate than the cloud it traces.

File formats in the pipeline

• E57: open ASTM standard (E2807). The default exchange format. Use it whenever you ship a cloud across two organizations or two software stacks.
• LAS / LAZ: open ASPRS standards. The reference for outdoor and aerial LiDAR. LAZ is a lossless compression of LAS, typically yielding files several times smaller.
• RCS / RCP: Autodesk Recap native formats, the canonical input for Revit. ATIS.cloud reads and writes them without an Autodesk license, which is unusual.
• LGSx: proprietary Leica Hexagon format. The Hexagon ecosystem is migrating progressively from the "Leica" name to "Hexagon".
• IFC: open buildingSMART format for the BIM model output. The non-negotiable exchange standard for the model itself, not the cloud.

For a deeper look at file formats and the IFC standard, see our guides on IFC files and point clouds.

Tools the modeler actually uses

A scan-to-BIM stack mixes capture-side software (scanner vendors), processing software, modeling software, and diffusion software. Here is how the main tools split across the four roles.

From a shared survey to deliverables with ATIS.cad

ATIS.cloud lets teams view, share and compare surveys in the browser. ATIS.cad is the CAD/BIM authoring product: it includes Scan-to-Plan for editable 2D floor plans and Scan-to-BIM for proposing building objects from a point cloud. Accept, adjust or reject the suggestions, then complete the work before delivering PDF, DWG or DXF drawings, or an IFC model. ATIS.cad is in early access until the end of November 2026, on request and activated by the team. This is separate from the ATIS.cloud trial.

• Every scanner brand natively: FARO, Leica, NavVis, Riegl, Trimble, Viametris, Matterport, etc.
• Formats on every plan: E57, LAS, LAZ.
• Proprietary formats on all plans: RCS, RCP, LGSx.
• Closing the loop: the IFC from the BIM model can be loaded back into ATIS.cloud and compared against the cloud, where the as-built validation happens.

See our BIM managers use case and BIM features overview for more.

Six mistakes that ruin scan-to-BIM projects

1. Skipping the planning phase. No agreed LOD, no agreed LOA, no agreed coordinate system. Every downstream phase pays for it.
2. Under-scanning. Not enough stations, not enough overlap, no targets. Registration error blows up.
3. Over-modeling. Building a LOD 400 model when the client paid for LOD 200. You lose money and the client cannot tell the difference.
4. Ignoring QA. Shipping a cloud without checking registration error and coverage gaps. The architect calls back in week three.
5. Working in silos. The scanner team, the modeler, the client never see the cloud together. Issues surface late.
6. Stranding the cloud. The 80 GB scan sits on one disk, nobody downstream can open it. The asset is invisible to the project.

FAQ