Laser scan site capture report template
A point cloud arrives with a delivery report that should tell the modeller everything the data cannot: where the scanner stood, how the setups were registered, what accuracy the registration achieved, and which rooms or plant were inaccessible on the day. When that report is thin, the model gets built over holes nobody mentioned. SurveyThanks records the capture setup by setup, so the delivery report is written from what actually happened on site.
Built for scanning firms running teams of roughly 3–50 inspectors.
Sample Point cloud delivery report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Point cloud delivery report
Capture and registration summary
- Site
- Fictional Water Treatment Plant, pump hall
- Capture dates
- 14–15 October 2026
- Delivered
- Registered point cloud, scan position plan
| Item | Recorded | Status |
|---|---|---|
| Scan setups | 64 setups across 3 levels | Status: Pass |
| Registration | Target-based, 18 targets | Status: Pass |
| Mezzanine valve room | Locked — not captured | Status: Not captured |
| Pump 3 | Running during capture; vibration noise in data | Status: Caution |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the point cloud delivery report where your template puts it.
Per setup
- Setup number
- Area / room
- Resolution setting
- Photo of position
Registration
- Method (target, cloud-to-cloud)
- Targets and control used
- Registration result
Coverage
- Areas not captured with reason
- Moving equipment or people in scene
- Reflective or dark surfaces noted
How the point cloud delivery report gets built
Capture it once, offline
Your firm builds the laser scan site capture form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your marks, stations and monitoring points
Enter marks, stations and monitoring points once, as a register. Every one of your observations, rounds and movement readings then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The point cloud delivery report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a point cloud delivery report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The movement summary reports 4 mm at PM3; the round’s readings put it at 11 mm.
Checks a surveying framework usually carries
- Control, datum and epoch are stated for every deliverable
- Quoted tolerances match the project specification being reported against
- Every mark named in the text exists in the register
- Assumptions and sources of error are recorded rather than assumed
Questions
- Can the report list every area that was not captured?
- Yes. Coverage gaps are their own repeatable rows with a reason, and the template prints them as a schedule so the modeller sees every hole before they start.
- Do we upload point clouds to SurveyThanks?
- No. The cloud is delivered through your usual channel. SurveyThanks holds the capture record and produces the delivery report that accompanies it.
- Can a two-day capture be one report?
- Yes. Setups from both days sit in the same job, so the report covers the whole capture with each setup still dated.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other surveying work we cover
- Aerial mapping missionsMapping deliverable report
- As-built verification surveysAs-built report
- Bathymetric survey runsBathymetry report
- Boundary survey field notesSurvey plan evidence
- Construction set-out recordsSet-out verification report
- Contour and detail surveysDetail survey report
- Deformation monitoring roundsMovement monitoring report
- GPR survey recordsGPR survey report
Other disciplines
Rebuild your point cloud delivery report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.