What the report proves
The first page should establish the route, nearby well evidence, mapped soils, known data gaps, and the deterministic rules that triggered each risk note.
BoreCast
Sample report
Sample HDD Bore Report
A BoreCast sample report should show an estimator what evidence supports the bore-risk read, what remains uncertain, and what has to be verified before mobilization.
The report format keeps the source appendix, uncertainty, and next actions visible instead of burying them in fine print.
What the estimator can do next
The output should support a route review, contingency conversation, potholing plan, client explanation, or pre-work compliance packet.
Source appendix
Evidence inputs
Nearby well logs
DrillerDB evidenceShows local formation, water, and depth context near the planned bore.
Limitation: Nearby logs are not a substitute for site-specific investigation.
Mapped soils and bedrock context
Public and derived evidenceFrames likely constructability concerns before field verification.
Limitation: Mapped data can be coarse or stale at the jobsite scale.
Route geometry
Customer inputPreserves the bore corridor and report boundary for review.
Limitation: Bad geometry creates bad conclusions, so the input must be confirmed.
Report logic
What the page should teach
- Show comparable wells and their distance bands.
- Separate deterministic findings from model-written explanations.
- Highlight missing evidence as a report output.
Human-review boundary
- 811 locates remain legally required.
- The report does not identify every buried utility or distribution asset.
- Final route, safety, and construction decisions require qualified human review.
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.