More Sharing Options
Key Points
Scan-to-BIM Quality Assurance: Confidence in Your Model
A useful Scan-to-BIM handoff gives your team a model it can review and use with confidence. Check that the agreed elements are included, the coordinates align, and the modeled geometry meets the specified tolerance against the registered point cloud. Record corrections and unresolved areas before the model moves into design or coordination.
Our Approach
How we help your team
Your team needs a model it can use with confidence and a clear explanation of how it was checked. We agree the areas, elements, coordinates and tolerances with you before production, so the review supports your design and coordination needs.
We turn those requirements into a defined modeling scope and review plan. Our team checks modeled geometry against the registered point cloud, records coverage gaps and confirms delivery formats. You receive files prepared for the agreed use, with limitations and outstanding items clearly identified.
Part 1 of 7
Set the acceptance basis before reviewing geometry
Begin by defining the model elements in scope: disciplines, areas, included categories, minimum feature sizes, required properties and intended uses. State how sloping, bowed or irregular existing surfaces should be represented. A nominal wall modeled as a plane and a detailed representation of its measured deformation support different decisions and require different checks.
BIMForum’s Level of Development (LOD) framework describes model content and reliability. State geometric tolerance separately: how far may the modeled surface differ from the agreed reference, and how will that difference be checked? USIBD’s Level of Accuracy (LOA) framework can help define those requirements. Record the adopted document version, measurement method and reviewer so everyone uses the same acceptance criteria.
Part 2 of 7
Establish a trustworthy reference and coordinate relationship
Record the point cloud revision, capture date, units and coordinate basis. Review the registration and coverage information before using the cloud as the comparison reference. A model that follows a misaligned cloud can appear internally consistent while still being unsuitable for coordination with other project data.
Verify shared reference locations across the model and cloud before judging local deviations. Check translations, rotations, elevations and unit conversions, and preserve the agreed transformation. Autodesk documents that RCP projects can contain origin adjustments that affect their placement relative to RCS files. Avoid manually nudging each reviewed area into agreement: that can conceal a coordinate problem affecting the whole deliverable.
Part 3 of 7
Review critical interfaces and representative areas
Agree which interfaces need individual checks and which repetitive areas may use a documented sampling plan. A connection face, opening, equipment footprint or pipe tie-in can deserve more attention than a broad wall used only for general space planning. Select samples across floors, orientations and element types so the review is not concentrated in the easiest area.
Use plans, elevations and cross-sections as well as three-dimensional views. Confirm that each section contains enough scan data to identify the surface being checked. Record the locations reviewed and the areas outside the sample. A model can look close to the cloud overall and still have a misplaced opening or connection that matters to the next trade.
Part 4 of 7
Read model-to-cloud deviation maps with their settings
A deviation map helps your team locate differences between the modeled geometry and the reference point cloud. Read it alongside the comparison settings and measured values. A green area only indicates that the displayed values fall within the selected color band; it does not confirm that every required element is present or that an unscanned area has been verified.
Document the reference, comparison direction, units, color scale, clipping and exclusions alongside the result. Separate permanent surfaces from people, stored materials and other out-of-scope returns. Also inspect modeled geometry for unsupported additions: a cloud-to-model check by itself may not expose a modeled object where no reference points exist. Do not interpret missing scan coverage as zero deviation.
Part 5 of 7
Classify discrepancies before assigning corrections
Separate an out-of-tolerance modeled surface from a missing required element, an incorrect category or property, and an area that cannot be verified. Each needs a different response. A gap caused by inaccessible field coverage may require additional investigation; drawing the missing geometry from assumption does not close the evidence gap.
If the entire cloud and model appear offset, investigate coordinates before issuing dozens of modeling corrections. If only one fitting differs, examine that element and its supporting observations. Record whether a condition is accepted, requires correction, awaits clarification or remains excluded, with the responsible party identified. Avoid treating an unexplained color on a screenshot as a complete issue description.
Part 6 of 7
Create a deviation report that someone can reproduce
This example follows one wall from observation to correction. It assumes the reference cloud is suitable and the project requires the modeled wall face to stay within 10 mm of that reference. The 14 mm observation exceeds that example limit by 4 mm. The values are illustrative; use your project’s agreed tolerance and measurement method for an actual review.
Scroll horizontally to see all columns
| Report field | Example entry |
|---|---|
| Location and element | Level 2, grid B/4; modeled wall W-204 |
| Evidence and versions | Registered cloud C03; model M02; saved section S-07 |
| Requirement | Wall face deviation no greater than 10 mm under the agreed check |
| Observation | 14 mm face offset in the inspected section |
| Classification | Outside the example limit by 4 mm; local modeling discrepancy |
| Action and status | Model author to investigate and correct; open pending recheck |
| Closure evidence | Revised model identifier, repeated measurement, reviewer and date |
Part 7 of 7
Close the review with a usable handoff
Recheck corrected elements against the same reference and acceptance method, then inspect nearby dependent geometry when a change could affect it. Keep the original issue and its resolution linked to the revised model. Where uncertainty or a borderline result affects the decision, apply the agreed decision rule or seek better evidence before closing the item.
Finally, open the delivered files in the agreed application version and verify links, coordinates, categories, required properties and exclusions. Supply the acceptance record with unresolved items clearly identified. Model acceptance confirms the agreed deliverable scope; it is separate from design approval, construction compliance and authorization to fabricate or install equipment.
- Retain the accepted model and point cloud revision identifiers.
- Record reviewed areas, exceptions and responsibility for outstanding actions.
- Confirm the intended uses and any limits on downstream reliance.
Good model QA leaves the next team with clear answers: what was checked, which requirements were met and what still needs attention. Agree those checks with us before production so the model, review record and file delivery support the way your team will use the information.
Frequently asked questions
Related technical guides
More Sharing Options
Plan Your Project
Start with a clear Scan-to-BIM scope.
Tell us what your team needs to design or coordinate. We’ll help define the model contents, tolerances, review requirements and delivery formats before production.
Discuss your Scan-to-BIM project Explore our Scan-to-BIM services