Scan-to-BIM Hub: Workflow, LOD, Software & Tools 2026

Scan-to-BIM in one paragraph

Scan-to-BIM is the process of turning a real building into a BIM model. A 3D laser scanner or a mobile mapping rig captures millions of points, those points are assembled into a unified point cloud, and a BIM modeler uses that cloud as a reference to build walls, slabs, beams, pipes and ducts in software like Autodesk Revit or Graphisoft ArchiCAD. The output is what the AEC industry calls an "as-built" model: a digital twin that matches what is actually on site, not what the original drawings claimed thirty years ago. The Wikipedia entry on Building Information Modeling describes the broader BIM concept (ISO 19650-1:2018) and notes that scan-to-BIM and as-built modeling are the standard way to bring existing facilities into a BIM workflow.

If you need the deeper definition first, see our companion article What is Scan to BIM, which walks through the as-built concept end to end. This hub focuses on the orchestration: tools, roles, deliverables, LOD.

The five phases of a Scan-to-BIM project

A Scan-to-BIM project breaks into five phases. Each phase has its own software, its own role, and its own failure modes. Most published workflows align on the same sequence: planning, field scanning, data processing, quality assurance, and deliverable production. Skipping a phase, or letting one team start before the previous one finishes, is the number one source of rework.

Phase 1: Planning and scoping

The planning phase is where you decide three things: which zones to scan, at what point density, and at what LOD(s) the BIM model should be delivered (a project does not require a single LOD). Getting this wrong costs an order of magnitude more than getting it right. The LOD target in particular drives the whole pricing of the modeling phase, and we cover it in detail below.

Phase 2: Field scanning

On site, a surveyor walks the building with a stationary scanner (Leica RTC360, FARO Focus, Trimble X-series) or a mobile mapping system (NavVis VLX, Leica BLK2GO, FARO Orbis). Stationary scanners give the best accuracy but require setup at each position. Mobile scanners trade a small accuracy loss for ten times faster acquisition. ATIS.cloud is compatible with every scanner brand so the choice of capture hardware does not lock the rest of the workflow.

Phase 3: Registration and processing

Several individual scans are needed to cover a building. Registration software aligns these scans into a single coherent point cloud. The output is typically an E57, LAS, LAZ, RCS, RCP or LGSx file ready to be consumed downstream. Industry-standard tools split along hardware ecosystems:

• Leica Cyclone REGISTER 360, the reference for Leica scanners.
• FARO SCENE, the historical companion of FARO Focus.
• Autodesk ReCap Pro, the vendor-neutral option that also handles RCS / RCP exports.
• Trimble RealWorks, the natural choice in a Trimble ecosystem.

Phase 4: Sharing and quality assurance

Once the cloud is registered, it has to travel to three or four other teams: the BIM modelers, the architect, the MEP engineer, and often the client who paid for the survey. This is historically where projects bog down. Sending a 50 GB file over WeTransfer is painful, asking each recipient to install Cyclone or ReCap is unrealistic, and email cannot carry the annotations and markups that drive the QA loop. A web-based platform like ATIS.cloud lets every stakeholder open the cloud in a browser, take measurements, leave notes, and validate completeness without installing anything.

Phase 5: BIM modeling and deliverables

The modeler imports the validated point cloud into Revit, ArchiCAD or AutoCAD and traces walls, slabs, beams, columns, openings, MEP elements and structural members. The output is an as-built BIM model, usually delivered in the authoring tool native format plus an IFC export for vendor neutral exchange. IFC is the buildingSMART open standard, recognized as ISO 16739, and it is the safe long-term archive format for any BIM deliverable.

If you are new to IFC, read our IFC file guide and our online IFC viewer overview for context.

LOD: the decision that sets project cost

LOD stands for Level of Development (sometimes Level of Detail). It is the BIMForum / AIA specification that tells the modeler how much information to put into each model element. Six levels exist: LOD 100, 200, 300, 350, 400 and 500. The full definitions, sourced from BIMForum, are summarized below.

• LOD 100, conceptual: element shown as a symbol or generic mass to signify it exists.
• LOD 200, approximate geometry: generic system with approximate quantity, size, shape, location and orientation.
• LOD 300, precise geometry: specific system, object or assembly with exact dimensions and position. The standard target for as-built renovation work.
• LOD 350, precise geometry with connections: LOD 300 plus the interfaces between systems (flanges, hangers, supports). Reserved for congested MEP zones.
• LOD 400, fabrication ready: includes detailing, fabrication, assembly and installation information. Used for prefabrication and shop drawings.
• LOD 500, field verified as-built: element verified on site, suitable for facility management and long-term operations.

In practice, most renovation projects specify LOD 300 as the baseline. Industry guides consistently cite LOD 300 as precise enough for architectural drawings and general coordination, while LOD 350 is reserved for MEP-heavy areas requiring clash detection. Moving the whole model from LOD 300 to LOD 350 increases modeling cost by roughly 30 to 40 percent because the modeler has to draw individual hangers, brackets and clearances. A hybrid strategy (LOD 300 globally, LOD 350 only where clashes are likely) aligns budget with actual risk.

Software landscape: who does what

Scan-to-BIM is never one piece of software. It is at least three layers stacked on top of each other: registration, sharing and review, and BIM authoring. Confusing the layers is what leads teams to buy a Revit license for someone who just needs to take a measurement.

Sharing and review layer

This is the layer where ATIS.cloud sits. Once the cloud is registered, the BIM manager uploads it once, then invites architects, engineers, clients and subcontractors to open it in a browser. They can pan, rotate, take measurements, drop annotations, compare a scan against an IFC model, and export markups. No desktop install, no GPU requirement, no per-seat license for the people who only consume.

• Capacity: up to 1 TB per file on all plans, up to 5 TB of total workspace.
• Open formats on every plan: E57, LAS, LAZ.
• Proprietary formats on all plans: RCS, RCP, LGSx.
• IFC model overlay supported on Advance and Enterprise plans.

BIM authoring layer

This is where the as-built model gets drawn. Autodesk Revit is the dominant authoring tool worldwide, often paired with ReCap Pro for point cloud import. Graphisoft ArchiCAD is the main alternative, particularly strong in Europe and architecture-led practices. AutoCAD remains widely used for 2D drawings extracted from the cloud, and AllPlan is common in structural engineering. ATIS.cloud ships a Revit plugin on the Advance and Enterprise plans, an AutoCAD plugin on Enterprise, and an AllPlan plugin on Enterprise, so the cloud-hosted point cloud can be referenced directly inside the authoring tool without a separate download.

Deliverables: what comes out of a Scan-to-BIM project

A Scan-to-BIM contract typically produces five deliverables. They cover the raw geometry, the parametric model, the exchange format and the QA artifacts. Each one targets a specific downstream use and tool.

ATIS.cloud supports BCF creation, PDF export of BCF, orthophoto export and cropped exports on its Advance and Enterprise plans, which closes the loop on the QA deliverable directly from the browser.

Who does what on a Scan-to-BIM team

A Scan-to-BIM team is rarely a single company. Even small projects pull in three or four distinct roles, each with its own software stack. Knowing exactly who is responsible for what (and which tool they actually need) is what keeps license costs down and accountability sharp.

The friction surface is between the four upstream roles and everyone downstream. The first four need direct access to the cloud; the rest only need to look at it, take a measurement, drop a comment. Paying for desktop registration software for each downstream stakeholder is wasteful. A web hub that grants per-project access without seat licenses fixes this asymmetry. That is the operating model ATIS.cloud is built for.

ATIS.cloud as the central Scan-to-BIM hub

Concretely, the workflow with ATIS.cloud at the center looks like this. The registration technician finishes the unified cloud in Cyclone, ReCap, SCENE or RealWorks and exports to E57, LAS, RCS or LGSx. They upload the file once to ATIS.cloud (up to 1 TB per file on all plans, up to 5 TB of total workspace). The BIM manager invites the modeler, the architect, the engineer and the client. Everyone opens the project in a browser, on any device, no install required. The modeler can keep working in Revit thanks to the ATIS.cloud Revit plugin on Advance and Enterprise. The architect drops markups directly in the web app 3D. The client validates the survey scope without ever opening a 50 GB file on their laptop.

• Hardware-agnostic: compatible with every scanner brand (FARO, Leica, NavVis, Riegl, Trimble, Viametris, Matterport, etc.).
• Sovereignty options across 22+ countries, useful for sensitive infrastructure or data-localization rules.
• IFC support on Advance and Enterprise, so the scan and the BIM model can live in the same project view.
• Revit, AutoCAD and AllPlan plugins available depending on plan, so authoring tools reach the cloud-hosted point cloud directly.

Comparing a Scan-to-BIM project with and without a hub

Without a hub, the unified point cloud gets duplicated. A copy goes to the modeler over WeTransfer, another copy goes to the architect, another to the engineer, the client gets a screen-recorded video because they cannot open the file at all. Annotations live in PDFs that go around by email. Versions diverge. By month two of a six-month project, nobody knows which copy of the cloud is the latest.

With a hub, the cloud lives in one place. Permissions are per project, per role. Annotations are in the same 3D view as the geometry. Updating the cloud (a missed zone re-scanned, a re-registration with better targets) updates it for everyone at once. The modeler still uses Revit, the technician still uses ReCap, but the shared reference is unique.

If you want the pricing logic before testing, see our plans page. If you want to read more on the underlying data structure, our point cloud primer explains formats and how they shape downstream workflows.

Common mistakes in Scan-to-BIM projects

• No written LOD specification per zone. Modeling cost ends up arbitrary and disputes follow.
• Single uniform LOD across the whole building. Pay LOD 350 everywhere instead of using a hybrid strategy.
• Scanner choice driven by the modeling tool. The two layers should be decoupled: scan with what fits the site, model with what fits the team.
• Cloud delivered as a single ZIP over a transfer service. No versioning, no audit trail, no shared annotations.
• BIM modeler installs the registration software just to view the cloud. Wrong tool for the job, wrong license cost.
• Client cannot open the deliverable on their laptop. The project closes with a deliverable nobody on the owner side can actually inspect.

Next steps

If your team is moving into Scan-to-BIM and you want to remove the bottleneck around point cloud distribution, the fastest path is to open a project on ATIS.cloud and run one survey through it end to end. The plans page details what each tier includes, the features page lists the IFC, Revit plugin and BCF support per plan, and our use cases show how surveyors, BIM managers and large groups have built their hub. The 14-day free trial requires no credit card and no commitment.

FAQ