Advise on the setback distance required between a septic system and a drinking water well, noting there is no single federal standard
domain: state/county health departments (multi-state) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Start from the baseline fact: there is no federal septic-setback standard — the Clean Water Act delegates onsite wastewater regulation to states, which often further delegate to county health departments
Never quote a single national number as authoritative — always identify and cite the specific state (or county, where delegated) code that applies to the site
Example — Maryland: requires 100 ft between a well and a contamination source in an unconfined aquifer, but only 50 ft in a confined aquifer
Example — Nebraska: requires at least 50 ft from a septic tank and at least 100 ft from a soil absorption system (drainfield) to a private drinking water well
Flag that setbacks commonly increase where limiting geology is present (karst, fractured bedrock, shallow limestone) — a standard setback table may not apply if the site has these conditions
Known gotchas
Generic online setback numbers (e.g. '50 ft to well, 100 ft to drainfield') are common rules of thumb but are not universal law — the applicable number must be confirmed against the specific state/county code for the site
Public water supply wells typically carry larger setback requirements (often 100–200 ft) than private domestic wells — don't apply the private-well number to a public-supply situation
Confined vs. unconfined aquifer conditions can change the required setback within the same state (see Maryland example) — the aquifer type at the specific site matters, not just the jurisdiction
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?