The typical scan-to-BIM QA checklist verifies that files are named correctly, views are set up properly, and the model opens without errors. Those are file management checks, not quality checks. They tell you nothing about whether the model accurately represents the physical conditions captured in the point cloud.
An effective QA/QC process validates the accuracy chain from raw scan data through registration, processing, modeling, and final delivery. Each stage introduces potential errors, and each requires specific validation steps.
Quality control starts at the scanner. Before leaving the site, verify scan completeness by reviewing coverage in the field software. Identify gaps where additional stations are needed and capture them while the site is still accessible. Returning to a construction site for supplemental scans adds cost and schedule delay that proper field QC prevents.
Check scan quality metrics including point density at critical areas, noise levels, and target acquisition quality. Scans captured during active construction may contain excessive moving objects that create ghost geometry in the point cloud. Flag these stations for cleaning during processing.
Registration is the foundation of everything downstream. A poorly registered dataset produces a model that looks correct in isolation but does not match real-world coordinates. The consequences show up in the field when prefabricated assemblies do not fit or new systems collide with existing conditions.
Verify registration accuracy against known control points. Compare registered scan positions against survey coordinates. Check bundle adjustment reports for outlier stations that may have shifted during optimization. Any station with residuals exceeding your project tolerance should be investigated and potentially re-registered.
For multi-day scan projects, verify alignment between acquisition sessions. Thermal expansion, settlement, and coordinate system inconsistencies between sessions create systematic errors that propagate through the entire model.
Processed point clouds should be free of noise, moving objects, and artifacts that could mislead modelers. Verify that cleaning operations removed scaffolding, temporary equipment, and personnel without deleting legitimate building geometry.
Check classification accuracy if automated classification was used. Misclassified elements, such as pipes labeled as structural members, create errors that cascade through the modeling process. Spot-check classified data against the raw point cloud to verify algorithmic accuracy.
This is where most QA processes fail. Verifying that a model looks correct on screen is not quality control. Effective model QC requires systematic comparison between the modeled geometry and the source point cloud.
Section cuts through the model overlaid on the point cloud reveal deviations. Check at regular intervals, not just at locations the modeler chose for their own reference. Random sampling catches errors that targeted checks miss because modelers naturally verify their own work at the locations they found challenging.
Measure critical dimensions in the model and compare them against the point cloud. Pipe diameters, duct cross-sections, structural member depths, and clearance dimensions should all fall within project tolerances. Document any deviations and track them through resolution.
The final QC stage verifies that the deliverable package is complete and usable. Model files should open cleanly in the target software version. Linked files should resolve correctly. Coordinate systems should match the project standards. Exported formats should maintain geometric fidelity.
This is also where you verify that scope boundaries were respected. Elements that were explicitly excluded from the modeling scope should not appear in the model. Elements that were required should all be present and at the specified LOD.
An effective scan-to-BIM QA checklist is not a single document. It is a series of stage-gates, each with specific pass/fail criteria tied to project tolerances. Teams that treat QA as a final-step activity miss the compounding effect of early-stage errors. Teams that embed QC at every stage catch problems when they are cheap to fix.