Risk before mobilization
The report should identify rock, water, cobble, shallow refusal, or data-sparse conditions early enough to affect the bid review.
BoreCast
Workflow guide
HDD Pre-Bid Risk Report
This guide explains how BoreCast turns route and nearby subsurface evidence into a pre-bid risk memo without pretending to be a final engineering conclusion.
A good pre-bid report changes the estimate conversation before the crew is already committed.
Proof for the office and field
Screenshots, source tables, and report exports give the office and crew a shared reference for what was checked.
Source appendix
Evidence inputs
Bore route
Customer inputConnects risk notes to a real route or crossing.
Limitation: The report is only as accurate as the entered geometry.
Subsurface comparables
DrillerDB evidenceShows logs and depth patterns near the work.
Limitation: Sparse areas should be treated as uncertain, not safe.
Report logic
What the page should teach
- Call out evidence density by distance band.
- Flag route segments where data is missing.
- Suggest review questions for bid closeout.
Human-review boundary
- The report does not replace geotechnical investigation.
- The report does not guarantee drillability.
- Field conditions and utility requirements still govern the work.
Customer signal
Improve this report
Corrections and real project outcomes are the fastest way to make these vertical reports useful. Send the exact signal and we will route it into the product feedback loop.
Missing utility or sourceA source, locate note, or corridor input is missing from the report.Send signal811 boundary issueThe locate, utility, or field-verification boundary is unclear.Send signalBad bore risk explanationThe risk note does not match how an HDD team would explain it.Send signalActual field outcomeYou have field results that could improve the report logic.Send signal
Internal links
Keep the cluster connected
These pages are designed to support the product hub, sample report, and related source guides with clear crawl paths.