Readiness check

Will your laser scan be usable or just a pretty cloud?

A laser scan is only worth the effort if it ties to control, hits the accuracy the use needs, and actually gets used to build or verify. A drifting, gap-filled cloud nobody opens again is wasted money. Answer for how your scanning actually runs. The score stays on your device; enter an email only if you want the reality capture checklist sent over.

1. Do you make a scan plan (coverage, overlap, setups, line of sight) before scanning?Yes, a plan that covers the area with overlapWe wing the setupsNo plan, we scan and hope

2. Do the scans tie to the project survey control (the same control as layout and BIM)?Yes, registered to control with targetsCloud-to-cloud only, not to controlNo control reference

3. Is the registration checked so the combined cloud does not drift?Yes, registration error checked and within specWe register but do not check the errorWe do not check registration

4. Is the level of accuracy (LOA) agreed and matched to the use?Yes, a specified LOA for the deliverableWe use the instrument defaultAccuracy is not defined

5. Is the right method used for the job (terrestrial for accuracy, mobile for speed, drone for outside)?Yes, method matched to accuracy and areaOne method for everythingWhatever is on hand

6. Is the coverage complete (no gaps in the areas that matter)?Yes, complete coverage of the scopeSome shadowed gapsBig gaps we discover later

7. Is the cloud turned into something usable (scan-to-BIM model or a QA deliverable)?Yes, a model or QA output people useRaw cloud handed overIt sits on a drive

8. Do you use the scan to verify the as-built against the design (deviation check)?Yes, scan overlaid on the model to catch deviationsRarelyNo as-built verification