A concrete scanning report documents what a GPR survey found — rebar depth and spacing, embedded conduits, post-tension cables, voids — so the GC gets a clear "safe to core" or "do not penetrate" answer. A professional report includes site information, scan area details, equipment used, annotated images with mark-out locations, and a summary of findings. If you're scanning concrete and still delivering handwritten notes or verbal clearances, you're leaving money and credibility on the table.

GCs hire concrete scanners for one reason: they need to know what's inside the slab before they cut into it. Your scan might be perfect, but if the report doesn't clearly communicate your findings, you're creating risk for the GC and limiting your own repeat business. A clean, professional report is what separates a $300-per-scan operator from one charging $500+ and staying booked.

What goes in a concrete scanning report

Every GPR scan report should include these sections:

• Header and company information — your company name, logo, contact info, license or certification numbers (if applicable), and the report date.
• Project information — client name (usually the GC), project name, site address, and the name of the on-site contact (superintendent, project manager, or foreman).
• Scan area description — where exactly you scanned. Reference column lines, room numbers, or grid coordinates the GC's team uses. "North wall of Room 204, between column lines A3 and A5" is useful. "The wall" is not.
• Equipment used — GPR unit model (GSSI StructureScan, Proceq GP8000, etc.) and antenna frequency. This matters for liability and for the structural engineer who may review your report.
• Findings — the core of the report. What did you find at each scan location? Rebar depth, spacing, and orientation. Conduit locations and estimated depth. Post-tension cables (this is the big one — hitting a PT cable can be catastrophic). Voids or anomalies. Mark-out locations painted or flagged on the slab.
• Annotated images — photos or GPR screenshots showing scan areas with marked targets. These should be labeled and referenced in the findings section.
• Recommendations — the GC wants a clear answer. For each scan area: safe to core/cut/anchor, do not penetrate (with reason), or requires further investigation (X-ray recommended).
• Limitations and disclaimers — GPR has limitations. It doesn't see through metal decking. Congested rebar can mask deeper targets. State what you scanned, how deep the signal penetrated, and what conditions may have affected results.

Report format: single-page clearance vs full deliverable

Not every scan needs a five-page report. Match the format to the job:

Single-page clearance letter

For simple jobs — one or two penetration locations on a known slab. The GC just needs a signed document saying "scanned this location, no conflicts found to X depth, safe to proceed." Quick to produce, quick to deliver. This is your bread-and-butter for small coring and anchoring jobs.

Full scan report

For larger projects — full-floor surveys, structural investigations, or any job where a structural engineer is involved. Multiple scan areas, detailed findings per area, annotated images, and comprehensive recommendations. These take more time but justify higher pricing ($1,000–$5,000+ depending on scope).

Whichever format you use, deliver it the same day. GCs schedule coring crews based on your clearance. If your report arrives tomorrow, the coring crew was already sent home — and the GC remembers that next time they need a scan.

How to turn scan data into a report the same day

The bottleneck isn't writing — it's the gap between scanning and sitting down at a computer. Here's how to close that gap:

• Capture findings in the field — use a mobile form with pre-built fields for scan area, depth readings, target types, and recommendations. Fill it in while you're still on site and the findings are fresh.
• Photo documentation on the spot — take photos of every scan area, every mark-out, and the GPR screen showing key targets. Timestamp and label them immediately. Don't dump 40 unlabeled photos into a folder and sort them later.
• Generate the PDF from your phone — field service software like Clevra lets you fill in work forms, attach photos, and generate a branded PDF report before you leave the site. Email it to the GC from the parking lot.
• Save report templates — build a standard template once, reuse it for every job. Only the findings, photos, and project details change. The structure, disclaimers, and company info stay the same.

Common mistakes that cost you GC callbacks

• Vague findings — "rebar detected" doesn't help. "Rebar at 2.5 inches depth, 12-inch spacing, running east-west" gives the coring crew what they need.
• No mark-out reference — if you painted marks on the slab but your report doesn't show where they are relative to the building grid, the marks are useless after the next trade walks through and scuffs them.
• Missing PT cable warnings — post-tension cables are the highest-risk finding in concrete scanning. If your report doesn't explicitly flag PT cables and include a do-not-penetrate recommendation for affected areas, you're exposing yourself and the GC to serious liability.
• Delayed delivery — anything more than same-day turnaround on a standard clearance scan is too slow. The GC's project schedule doesn't wait for your report.
• No limitations section — GPR isn't X-ray. It has real limitations (metal decking, congested reinforcement, shallow targets). Stating what you couldn't see is as important as stating what you found — both for accuracy and for liability protection.

FAQ

What is a concrete scanning report?

A concrete scanning report documents the findings of a ground-penetrating radar (GPR) survey of a concrete structure. It identifies the location and depth of rebar, conduits, post-tension cables, and other embedded objects, and provides recommendations on whether it's safe to core, cut, or anchor at the surveyed locations.

How long should a GPR scan report take to write?

A single-page clearance letter should take under 10 minutes if you're capturing data digitally in the field. A full multi-area scan report takes 20–30 minutes. If your reports consistently take over an hour, the problem is your data capture workflow, not the writing.

Do GCs always need a written report?

Yes. Even for simple clearance scans, a written report with your findings and recommendation protects both you and the GC. Verbal clearances offer zero liability protection. If something goes wrong during coring and there's no written report, you have no documentation of what you communicated.

What GPR equipment should I list in the report?

List the GPR unit model and manufacturer (e.g., GSSI StructureScan Mini XT) and the antenna frequency (typically 1600 MHz or 2600 MHz for structural scanning). This information matters for understanding the scan's depth capability and resolution, especially if a structural engineer reviews the report.

Can I use field service software for GPR reports?

Clevra and similar field service platforms let you create custom work forms for concrete scanning — with fields for scan area, depth readings, target types, and recommendations. Photos attach with timestamps, and the report generates as a branded PDF from your phone. It's the fastest path from scan complete to report delivered.