Information reviewed: 16 November 2026
Registration brings separate scans into a common spatial relationship. Quality assurance asks whether the resulting dataset is suitable for its intended use. A cloud can look convincing on screen while containing local misalignment, drift or missing coverage. When commissioning point-cloud surveys, ask for an agreed checking approach rather than relying on a single software score.

Registration methods solve different problems
Cloud-to-cloud registration matches overlapping surface geometry. Target-based registration uses identifiable targets or features. Survey control can connect the observations to an agreed reference. These approaches may be combined; the appropriate method depends on the building, overlap, access and project requirement.
A long corridor with repetitive geometry can pose a different registration problem from a small room with distinctive features. A multi-floor building needs reliable connections between levels, not just good alignment within each room. The capture plan should anticipate these issues before the team leaves site.
A residual is not the whole accuracy story
A registration residual describes fit within the registration solution. An independent check tests observations that were not used to establish that solution. Both can be useful, but they should not be presented as the same evidence.
Ask what the reported statistic measures, how many observations it represents and where those observations are located. An overall average can conceal a local problem at a stair, façade or distant wing. For design-critical areas, the location of a discrepancy matters as much as the headline number.
A practical six-stage review
| Stage | Review question | Useful evidence |
|---|---|---|
| Brief | What accuracy, coverage and outputs are required? | Agreed scope and acceptance criteria |
| Capture | Are connections and critical viewpoints sufficient? | Coverage record and access notes |
| Registration | Are scans consistently aligned? | Registration summary and local inspections |
| Independent checking | Does the dataset satisfy the agreed requirement? | Check observations and their locations |
| Extraction or modelling | Does the output represent the cloud appropriately? | Selected comparisons and review comments |
| Handover | Can another team use and interpret it? | File register, reference information and limitations |
This is a recommended commissioning framework, not a claim that an identical report is automatically included in every MS365 appointment. Agree the evidence needed and include it in the scope.

Coordinates and levels must be named
A local project grid can be suitable for a building survey if it is documented and consistently used. A project requiring a connection to mapping or other survey datasets may need a national reference. Do not describe a cloud as “georeferenced” without stating what that means.
Ordnance Survey’s OSTN15 and OSGM15 resources support transformations between GNSS-derived references, the British National Grid and relevant height datums. A GNSS ellipsoidal height is not simply interchangeable with a site level. Ask the surveyor to document the horizontal and vertical reference, units and any transformation used.
For combined building and topographical survey work, agree the common reference before either dataset is produced. Retrofitting alignment from a few guessed points can undermine otherwise useful information.
Check the places most likely to cause design trouble
Inspect slices through floor connections, stairs, façades and repeated structural grids. Look for double surfaces, abrupt offsets or geometry that changes unexpectedly between neighbouring scans. Also inspect the relevant openings and interfaces at an appropriate scale.
Then check the derived output. A model may intentionally simplify an irregular surface, but the rule should be known. A drawing can omit an overhead feature even when the cloud contains it. Our Scan to BIM service and CAD extraction service should be scoped around the information the design team needs.
Handover questions that prevent rework
- Which areas were inaccessible, obscured or excluded?
- Are checks reported in the same reference as the deliverable?
- Which geometry is observed, inferred or deliberately simplified?
- Are cloud dependencies and coordinate instructions included?
- Who reviews a discrepancy, and which revision supersedes the earlier issue?
Use the DWG/DXF Viewer for convenient drawing review and the deliverables checklist for file acceptance. Keep the review tied to named files and revisions so that comments can be resolved reliably.

Frequently asked questions
Does zero visible misalignment prove accuracy?
No. Screen appearance depends on scale, rendering and viewpoint. It does not replace the agreed measurement checks.
Is a national grid always necessary?
No. The reference should fit the project and any datasets it must coordinate with. A documented local system may be appropriate.
Can I request a QA report with my cloud?
Yes—define the required evidence at quotation stage. Send the intended use and acceptance requirements so that checking and reporting can be included in the scope.
References and review date
References checked on 16 November 2026. Requirements can change; confirm the applicable edition and project-specific requirements when appointing the team.

