42 ft from drainfield to well
The CDC 50-ft siting baseline is not met, so the screen reports a known conflict even before a local rule is entered. A local rule may require more distance, not less.
Transparent methodology
Dakiv is a pre-permit organization tool. It never converts a generic web number into a claim that a property is legally approved.
CDC currently advises locating private wells at least 50 feet from septic tanks and 50 feet from septic leach fields. The calculator checks both measured distances against that 50-ft health-oriented baseline.
If you enter stricter local well minimums, Dakiv compares the tank-to-well and drainfield-to-well distances separately. The local requirements do not replace the CDC context; the result shows both.
For house/foundation, property line, surface water and driveway/traffic clearances, Dakiv does not supply a made-up national minimum. You enter the official local minimum when you know it. A blank rule produces a “verify” status.
Known conflict found means at least one CDC or entered local threshold is not met. Known checks clear — local rules incomplete means no known conflict was found, but at least one measurement or local rule is missing. All entered checks clear means every comparison you supplied is above its screening threshold; it still does not mean the property has a permit.
The decision pack also shows the tightest known clearance margin, unresolved rules or measurements, checklist gaps and a project-specific permit-office question pack.
The tool does not approve soils, determine a seasonal high water table, calculate a legally sufficient drainfield size, establish system technology, interpret easements, certify survey accuracy or grant a variance. These require the applicable program and site-specific professional work.
Sources are reviewed and dated in the source library.
The optional property-intelligence screen uses a transparent Dakiv planning-friction screen. It starts at 100 and subtracts only when a successfully loaded public layer shows a caution signal: poor mapped drainage, hydrologic group D, shallow mapped annual minimum water table, steep mapped slope, more-than-rare mapped flooding, a FEMA Special Flood Hazard Area or an NWI wetland feature inside 150 m.
Missing data never creates a positive bonus. Dakiv reports how many of the three public layers loaded. A numeric planning-friction score appears only if all three static public layers return usable responses; otherwise the score remains unavailable (—) and missing coverage is explicitly marked. The site decision brief then lists mapped cautions, unavailable sources and field/permit questions without certifying buildability. The score is not a perc probability, permit probability, land valuation or engineering opinion.
The live advisory is deliberately separate from the static planning-friction score. It combines the public layers that successfully load: NOAA National Water Model near-surface soil-moisture saturation, recent precipitation from the nearest available National Weather Service observing station, NWS gridded precipitation forecast and selected USDA mapped drainage/water-table context.
The advisory reports LOW, MODERATE, HIGH or UNAVAILABLE environmental pressure, plus a coverage-based confidence label and a short 48-hour trend. Current implementation treats near-surface saturation at 70/80/90%, roughly 72-hour observed rain at 20/40/75 mm and next-48-hour forecast rain at 10/25/50 mm as progressively stronger wet-weather signals. Poor mapped drainage, hydrologic group D and a shallow mapped annual minimum water table can add context when USDA data is available.
Those thresholds are a transparent planning heuristic, not a calibrated septic-failure model. The advisory never claims that a system is failing, predicts a failure probability, measures the drainfield itself or determines whether normal water use is safe. Missing live data lowers coverage/confidence rather than being interpreted as a favorable condition.
Data freshness and response speed: Dakiv serves the mapped soil/flood/wetland screen before separately loading slower weather context. Public USDA, FEMA and FWS map layers can be cached locally for up to 24 hours by exact coordinate, while NOAA/NWS context can be cached for up to 10 minutes. Each source retains its original fetched-at time. Street addresses, full property results and user notes are not placed in the shared cache. The individual API response remains private and no-store. A cold lookup can still depend on agency availability: local edge cache is not a global pre-seeded snapshot.
Septic permit records are fragmented across state and local systems. There is no complete official national septic-permit API, so Dakiv routes users to the responsible authority instead of pretending nearby-permit coverage is complete.
The CDC 50-ft siting baseline is not met, so the screen reports a known conflict even before a local rule is entered. A local rule may require more distance, not less.
The CDC baseline is clear, but Dakiv still reports the local rule as unresolved. “No known conflict” is deliberately different from permit approval.
Dakiv can show a +5 ft planning buffer against the number you supplied. It does not certify that 20 ft is the correct rule for the parcel.
The result can still remain incomplete because soil suitability, vertical separation, system type, repair area and permit history sit outside the distance calculation.
When calculator logic, source interpretation or status wording changes materially, Dakiv updates the reviewed date and the production browser checks that exercise the affected workflow. The goal is to make a result reproducible from the inputs and sources, rather than rely on an unexplained score.