Cited to the page
Every value in a report names the document and page it came from. Findings that can't be verified are delivered flagged, not delivered confident. A claim you can check beats a claim you have to trust.
STA 0+00 · About
Method
A sounding is a measurement of depth — the surveyor's lead line, the geotechnical probe, the marked depths on every navigation chart. The name describes the product's method: useful design input is rarely on the surface of the record. It's in a drainage calculation bound into a staff report, an as-built elevation three modifications back, a conservation easement recorded against a parcel nobody mentioned. What you don't sound is what you hit.
Every value in a report names the document and page it came from. Findings that can't be verified are delivered flagged, not delivered confident. A claim you can check beats a claim you have to trust.
When the record is thin, ambiguous, or the district's index is having a bad day, the report says so in plain language. No fabricated zeros, no silent gaps — an honest "couldn't verify" outranks a confident guess.
Permit letters summarize; the engineering file underneath carries the design record. The pipeline reads to the file's depth — staff reports, calculations, as-builts — and says what it indexed without parsing, because an unstated limit is a trap.
Everything comes from the districts' own published records, queried at run time and dated in the report. We don't sit between you and the source — we hand you the source, organized.
If you want to pressure-test the product, the best way is also the simplest: send a study area your team already researched by hand, and grade us against what you found. The scope screen will price it in one pass.
STA 2+50 · Start
Draw or upload a boundary. See the intersecting district records and a firm price. Free, no account, no meeting.
Scope a siteAlready researched the site by hand? Send it. A side-by-side time and finding check is the best product test.