How this site is reviewed, updated, and kept inside planning-tool boundaries.

This page explains how SepticPath turns public rules, file paths, and official-source context into homeowner-facing planning guidance without pretending to be permit software or engineering design.

What we prefer as evidence

Official state, county, district, or delegated authority sources come first whenever they are available and readable enough to support a homeowner-facing explanation.

Rules, forms, manuals, and official local office directories are preferred for workflow claims.
Public cost anchors are used only as broad planning context, not as permit truth.
When sources conflict or stay vague, the page should widen uncertainty instead of inventing precision.

How pages are reviewed

Published pages are expected to carry source references, reviewed-against copy, and a last-reviewed date tied to the workflow described on the page.

State guides are reviewed against official state-level or delegated local sources.
State intent pages are reviewed against the sources tied to that exact workflow and state.
FAQ, CTA, and internal links are written to move the user toward the next real file, office, or estimate step.

What we deliberately avoid

The product is intentionally conservative where local file context, site conditions, or delegated authority rules could change the answer.

We do not present outputs as engineered design recommendations.
We do not present outputs as permit approval or code-compliance decisions.
We do not narrow cost or scope ranges aggressively when source coverage is weak.

Important note

Trust the source trail

Use the pages as planning guidance, then confirm the local file, reviewing office, and site conditions before relying on a quote or design decision.

Open the main estimator