Chat with us, powered by LiveChat
Geotech Bid Intelligence

Data-source guide

Public Boring Logs for Pre-Bid Risk

Public boring logs can turn a blank bid screen into a source-backed risk conversation when they are tied to geometry, distance, and limitations.

Mapped boring and well context for geotech bid intelligence

A useful page explains how boring evidence changes a bid question without claiming to be licensed engineering design.

From records to bid questions

The report should connect each public boring or well record to a specific estimating question: rock, water, dewatering, spoil, or sparse evidence.

Engineering boundary

The output is a pre-bid intelligence memo, not a geotechnical report or design recommendation.

Source appendix

Evidence inputs

Public boring logs

Public evidence

Shows nearby subsurface observations that may affect estimating.

Limitation: Public archives can be sparse, stale, or hard to align with the current work.

Nearby wells

DrillerDB evidence

Adds depth, water, and lithology context around the site.

Limitation: Nearby wells do not replace project-specific borings.

Report logic

What the page should teach

  • Flag sparse evidence within the review radius.
  • Show evidence conflicts instead of hiding them.
  • Route high-uncertainty calls to senior review.

Human-review boundary

  • The screen does not replace licensed engineering design.
  • The screen does not replace a geotechnical report.
  • Final pricing and method decisions require qualified review.
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.