Process encyclopedia · field to federated model
Scan-to-BIM workflow: capture, Revit modeling and QA
A professional Scan-to-BIM workflow is a gated production line: plan the capture for the modelling purpose, register with control, freeze a specification, model in disciplined packages, QA against the cloud, then publish through a CDE with clear status.
Phase 0 — Purpose & information requirements
Write the decision the model must support: demolition, new MEP routing, heritage record, digital twin seed, etc. Purpose controls density, LOD, and budget.
Phase 1 — Scan planning
- Targets / control network.
- Access, night shifts, infection control, ATEX zones.
- Expected occlusions and recapture loops.
Phase 2 — Register & package clouds
Deliver regionally cropped clouds for modellers (performance), plus a master archive. Document registration reports.
Phase 3 — Production modelling
Package by floor/zone/discipline. Daily section reviews beat end-loaded QA. Keep issue logs for ambiguities.
Phase 4 — QA, federation, CDE publish
Deviation checks, federate with design models, publish Work In Progress → Shared → Published per ISO 19650-minded CDE states.
Gate reviews that prevent rework
- Gate A — purpose + LOD matrix signed
- Gate B — registration report accepted
- Gate C — sample zone modelled + QA’d before full production
- Gate D — federation with design models
- Gate E — publish package + exclusions log
Issue log hygiene
Ambiguous geometry should become tickets with cloud screenshots, not silent modeller guesses. Clients who refuse to answer tickets inherit the risk — write that into the BEP.
Buyer decision guide
A controlled Scan-to-BIM workflow converts uncertain observations into an accepted information product through explicit gates: intake, data validation, pilot, production, QA, client review and handover. Skipping the pilot or acceptance matrix moves disagreements to the most expensive stage.
Inputs to request before a quote
- Cloud inventory, sample, registration/control information and rights
- Model uses, element list, LOD/LOI and tolerance requirements
- Template, coordinates, naming, software/version and exchange formats
- Decision owners, review dates, issue route and change process
Acceptance framework
Put acceptance criteria into the scope before production. The following checks are a practical starting point and should be adjusted to the project’s risks and intended model use.
| Control | What “good” means | How to verify it |
|---|---|---|
| Gate 1: intake | Inputs can support the requested result; gaps are recorded | Written feasibility and clarification list |
| Gate 2: pilot | Standards and tolerance interpretation are agreed on a sample zone | Accepted pilot plus locked matrix |
| Gate 3: production | Model zones follow controlled ownership and review rhythm | Progress register and internal checks |
| Gate 4: acceptance | Delivery meets matrix and documented exceptions | Receiver test, QA pack and signed/recorded outcome |
Limitations and common procurement errors
Automation can classify, segment or compare data, but it does not remove the need for human judgement about ambiguous surfaces, design intent and acceptable simplification. Programme pressure should change priorities or scope openly rather than suppressing QA evidence.
What the handover should contain
Keep the cloud/model inventory, decision log, pilot record, matrix, issue log, model health report, deviation samples, coordinate statement, assumptions/exclusions and final file register together. This creates a traceable answer when a future user asks why an object was modelled in a particular way.
Primary reference: ISO 19650-1 overview. This studio guide explains procurement and QA application; it does not reproduce or replace a standard, contract or software manual.
Frequently asked questions
Who should own the BEP for Scan-to-BIM?
The appointing party sets information requirements; the lead appointing modeller/scanner joint BEP should define LOD, coordinates, and QA before production.
Need this delivered — not just explained?
Scan to BIM Studios is both an encyclopedia and a delivery studio. If you came here to understand Scan-to-BIM workflow and now need a model, a pilot, or a scoped quote, talk to the same people who write for depth.