Direct Answer
How to Plan Laser Scan Registration Before Fieldwork
Plan registration by deciding how adjacent scans will share stable evidence, how the network will close loops, where targets or survey control are required, which coordinate system applies and how the field team will identify weak coverage before leaving. The plan should include recovery paths for repetitive geometry, moving environments and inaccessible transitions.
Work backward from the deliverable and acceptance method
A registration plan for visual background data is different from one supporting fabrication, survey coordinates or deformation analysis. Define the relevant surfaces, coordinate basis, deliverable and acceptance checks first. Those decisions determine whether cloud-to-cloud geometry is enough or the project needs targets, control and independent checkpoints.
Identify the tightest areas and most consequential tie-ins. They may deserve shorter station spacing, additional viewpoints or a direct controlled relationship even when the rest of the site can use a simpler pattern.
Plan stable, distinctive overlap
Adjacent stations need common stable evidence. Flat empty corridors, identical structural bays, moving conveyors, vegetation and reflective surfaces can make automatic alignment ambiguous. Include corners, columns, equipment or distributed targets that constrain translation and rotation in three dimensions.
Overlap should not be one narrow doorway sliver when another station can provide a stronger relationship. Plan both the path through the site and cross-links between nearby paths.
Use targets where they add information
Spheres and checkerboards can create identifiable references across scans and can connect to survey control. Place them at varied heights and directions, within appropriate range and incidence, and where they can be observed from enough stations. Avoid a cluster of nearly coplanar targets that gives poor geometric leverage.
Targets should be stable, uniquely identified and documented. A mislabeled control target can damage an otherwise strong registration, so field photographs and a target schedule are valuable.
Design loops and cross-links
A loop returns the network to previously observed geometry through an independent path. Differences at closure can expose accumulated drift. Cross-links between floors, corridors or exterior paths strengthen the network and reduce dependence on a single bridge station.
Large or phased sites may use clusters that are registered internally and connected through controlled transitions. Plan those transitions explicitly; do not assume two independently captured zones will align because they share a building name.
Separate control from independent checks
Control observations establish or constrain the project coordinates. Independent checkpoints are withheld from the adjustment and used to compare the finished registration. Document units, axis order, point IDs, datum and the expected relationship to civil, plant or BIM coordinates.
Coordinate responsibility should be clear. If another surveyor establishes control, agree on delivery format and verification before field capture begins.
Build field review into the capture sequence
Use Stream, on-site SCENE registration or another supported field workflow to review station placement, connections and visible coverage while access remains available. FARO notes that inadequate overlap is a common cause of on-site registration failure. A failed connection is a field problem to investigate, not merely an office inconvenience.
Review critical rooms and transitions before dismantling targets or leaving a controlled area. Add recovery stations when the network shows a weak or ambiguous link.
Keep notes that make office processing reproducible
Use consistent scan names, cluster names and target IDs. Record skipped stations, moved objects, access limits, control observations, weather and any field correction. Photographs of target placement and a marked route help the processor understand relationships that may not be obvious from point data alone.
The field plan should return with actual conditions marked. Registration quality improves when field context survives the handoff to the person reviewing the project in SCENE.
Registration quality begins before the first scan: plan distinctive overlap, redundancy, control, checkpoints and field recovery around the intended deliverable.
Frequently asked questions
Primary sources and standards
Technical claims in this guide were checked against the following manufacturer documentation, standards bodies and software documentation.