Contour and detail survey report template
An architect commissioning a detail survey needs more than a drawing: they need to know the datum the levels are on, what was and was not picked up, which trees were measured, and that the boundary shown is from title rather than re-established. Those qualifications usually live in a notes box nobody updates. SurveyThanks captures them as fields on site so the report states them correctly for each job.
Built for architects running teams of roughly 3–50 inspectors.
Sample Detail survey report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Detail survey report
Survey notes and limitations
- Site
- 42 Fictional Parade
- Survey date
- 6 August 2026
- Datum
- Levels AHD from PM 5000 (fictional); coordinates on a local grid
| Item | Recorded | Status |
|---|---|---|
| Boundary | Shown from title dimensions, not re-established | Status: Qualified |
| Trees > 300 mm trunk | 7 located with trunk diameter and spread | Status: Pass |
| Neighbouring floor levels | Window sills and ridge of No. 40 picked up | Status: Pass |
| Rear yard of No. 44 | No access — levels not obtained | Status: No access |
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 detail survey report where your template puts it.
Datum and control
- Benchmark or permanent mark used
- Height datum
- Coordinate basis
Features
- Trees (trunk diameter, spread, height, species if known)
- Services visible
- Neighbouring windows, sills and ridge heights
Limitations
- Boundary basis
- Areas not accessed with reason
- Weather and ground cover
Standards the report works to
- AHDAustralian Height Datum
- The height datum the levels are reduced to, stated with the mark they were taken from.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the detail survey report gets built
Capture it once, offline
Your firm builds the contour and detail survey 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 detail survey 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 detail survey 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 stop us forgetting the boundary disclaimer?
- Yes. Boundary basis is a required choice on the form, and the template prints the matching wording, so a title-only boundary is never presented as re-established.
- Can trees be recorded once and reused for the arborist?
- Trees are a repeatable group with their own rows, so the same tree schedule can feed the survey report and any later report that references those trees.
- Can the surveyor note areas they could not access?
- Yes. Each limitation is its own row with a reason, and the report lists them together so the architect sees every gap in one place.
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
- Boundary survey field notesSurvey plan evidence
- Construction set-out recordsSet-out verification report
- Deformation monitoring roundsMovement monitoring report
- GPR survey recordsGPR survey report
- Laser scan site capturesPoint cloud delivery report
- Mine survey pickupsMine survey report
- Strata plan field verificationStrata plan report
- Utility locating recordsLocate mark-up report
Other disciplines
Rebuild your detail survey 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.