Before the visit:
Pre-clear access:
Confirm site access, inductions, and escorts in advance.
Arrange for keys / access cards and ensure doors are unlocked or can be propped open where allowed.
Plan scan segments and loop closures:
Define logical segments (per floor, wing, or building).
Plan loop closure paths on a floor plan beforehand.
Prepare control points:
Decide in advance where a control point is needed and how it will be measured.
Install or mark control points before the scanning day if possible.
On the day:
Minimize starts and stops:
Avoid unnecessary pauses while scanning.
Group short interruptions together where possible (e.g. housekeeping, quick checks) between scan segments.
Standardize procedures:
Use a checklist for each scan segment (control point captured, start/stop points, loop closure path, panorama strategy).
Optimize panoramas:
Take panoramas strategically, not at every step.
Consider modes or workflows that allow faster panorama acquisition when available.
Use multiple devices smartly:
Split areas cleanly between operators to avoid overlap.
Share a consistent control framework and naming convention.
After the visit:
Review performance data:
Track realized m²/day (ft²/day) and m²/hour (ft²/hour) across projects.
Feed this back into your planning assumptions for future jobs.
Accuracy vs. speed trade‑off
Higher speed is not always better if it compromises:
Loop closure quality
Coverage completeness (e.g. missing rooms or occluded areas)
Alignment to control / coordinate systems
For high‑accuracy or highly regulated projects, you may:
Accept lower m²/hour (ft²/hour)
Invest more time in control points, redundant passes, and quality validation.
This should be explicit in your project planning and client communication.