Ground penetrating radar survey report app
A GPR report is read by someone about to cut, core or excavate, and what they need is not the radargram — it is where the targets are, how deep they appear, how confident the operator is, and what the radar could not see. Slab conditions, moisture and rebar density all limit what GPR returns. SurveyThanks captures each scan area, target and limitation on site so the report qualifies its findings properly.
Built for locating firms running teams of roughly 3–50 inspectors.
Sample GPR survey report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
GPR survey report
Scan area 2 — Level 1 slab, proposed core locations
- Site
- Fictional Shopping Centre, tenancy 14
- Scan date
- 2 September 2026
- Antenna
- High-frequency concrete antenna
| Target | Position and apparent depth | Status |
|---|---|---|
| Post-tensioned tendon band | Runs N–S, 60–75 mm apparent depth | Status: Avoid |
| Electrical conduit | E–W, 40 mm apparent depth | Status: Avoid |
| Core location C1 | Clear of detected targets | Status: Clear |
| Core location C2 | Shadowed by top mesh — inconclusive | Status: Inconclusive |
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 GPR survey report where your template puts it.
Scan area
- Area ID and location
- Surface type and condition
- Antenna used
- Grid or line spacing
- Photo of marked area
Per target
- Target type
- Orientation
- Apparent depth
- Confidence
Limitations
- Masking reinforcement
- Moisture or surface conditions
- Areas not scanned
Standards the report works to
- AS 5488.1:2019Classification of subsurface utility information (SUI)
- Where GPR locates buried services, the quality level each service is reported at.
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 GPR survey report gets built
Capture it once, offline
Your firm builds the GPR survey record 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 GPR 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 GPR 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 each proposed core or cut have its own clear or avoid result?
- Yes. Proposed locations are rows in a repeatable group with their own result and photo, and the report lists them as a table the builder can act on.
- Does SurveyThanks store or interpret the radargrams?
- No. Interpretation stays with the operator and their GPR software. SurveyThanks records the findings, limitations and photos the client report needs.
- Can the report carry our standard depth disclaimer every time?
- Yes. Fixed wording lives in your Word template, and per-option report text lets a choice like “inconclusive” print a full qualifying sentence.
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
- Utility locating recordsLocate mark-up report
- Volumetric drone surveysVolume report
- 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
Other disciplines
Rebuild your GPR 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.