Watershed Nutrient Source-Control Planning and Verification Record

Controlled preview

Internal technical review is complete. Independent review is pending, so this artifact remains available for review but is excluded from search-engine discovery. Next review: 2026-10-15.

Browser-local record boundary

Field values are not uploaded by this form. Standard page analytics may record this page visit, not entered values. Nothing is autosaved: download a completed-record CSV or print before leaving. Downloads may contain personal, precise-location, conservation-sensitive, incident-sensitive, restricted-infrastructure, or health-sensitive information; use approved storage and sharing. Do not publish restricted locations, private assets, household or health records, or conservation-sensitive evidence unless each controlling authority and owner has approved the exact scope and precision.

Computed record state

blank

Operational dispositionMORE EVIDENCE: no source-control action, authorization, or effectiveness conclusion implied

Stable record IDNot started

Full-record documentation0 of 36 required fields documented

Independent watershed source control v1 states

immediate_hazard_handoff_state
authority_and_use_state
watershed_boundary_state
phosphorus_basis_state
monitoring_data_validation_state
phosphorus_budget_state
budget_residual_state
source_inventory_state
source_contribution_state
model_applicability_state
critical_source_area_state
site_verification_state
landowner_tribal_privacy_state
alternatives_comparison_state
design_and_authorization_state
implementation_fidelity_state
operation_maintenance_state
effectiveness_design_state
target_and_adverse_response_state
adaptive_decision_state

Budget terms, source hypotheses, model applicability, critical-source screening, site verification, alternatives, design, authorization, as-built implementation, maintenance, delivered-load response, lake response, adverse effects, and public release remain separate attributable decisions.

Safety and authority boundary

This planning record does not diagnose an urgent bloom, sewage release, spill, exposure, septic failure, or other incident; identify a polluter; establish culpability, liability, compliance, impairment, a TMDL, allocation, permit duty, or property-level contribution; authorize access, monitoring, excavation, grading, infiltration, shore work, vegetation removal or planting, septic work, stormwater work, agricultural work, pesticide use, treatment, construction, or spending; or prove safety, recovery, source reduction, lake response, or effectiveness. High lake phosphorus, chlorophyll, a bloom, trophic state, land use, one sample, a non-detect, a visual observation, PLET, SPARROW, another model, a critical-source-area screen, an installed practice, or a modeled reduction cannot establish those conclusions alone. No universal buffer width, setback, pumping interval, fertilizer rate, storm size, practice efficiency, cost, or load-reduction percentage is supplied. Current local, Tribal, state, and federal authority; owner consent; current state NRCS Field Office Technical Guide where applicable; qualified site design; permits, certifications, zoning, labels, utilities, protected and cultural resources, health procedures, and professional septic requirements control. Do not publish modeled parcel or owner blame. Keep source, mobilization, delivery, external load, internal flux, sediment inventory, storage change, outflow, retention, model expectation, implementation, maintenance, delivered-load response, lake response, and adverse effects separate. No action and protection are valid alternatives. External source control does not guarantee an immediate lake response or prevent a future bloom.

LakeTech Learning Center · Field record

Watershed Nutrient Source-Control Planning and Verification Record

Template ID: watershed-nutrient-source-control-plan-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: MORE EVIDENCE: no source-control action, authorization, or effectiveness conclusion implied
Reviewer attestation: Not recorded
Source guide: watershed-nutrient-source-control-and-shoreland-action-program

Start a browser record to enter values and create a stable ID. You can still print this blank form.

Record view Guided workflow view Full record

Guided view follows recorded workflow branches and preserves evidence from branches you later change. Full view and print always include every field.

Record sections

1. Record control, immediate hazards, authority, and objective

Escalate active HAB, sewage, spill, exposure, or other urgent conditions through the responsible current authority. This planning record never replaces that response.

Core record

Stable record ID · requiredNot recordedProject, watershed-plan, or parent record IDNot recordedCompleted by and role · requiredNot recordedSensitive data class: personal.Record date · requiredNot recordedImmediate-hazard handoff state · requiredNot recordedAuthority, case, direction, date, and scope reference; do not include health detailsNot recordedSensitive data class: incident sensitive.Authority, designated-use, and controlling-plan state · requiredNot recordedResponsible authorities, jurisdiction, designated uses, current plan or TMDL, decision owner, question, and date · requiredNot recordedSensitive data class: operational.

2. Lake, watershed, period, and phosphorus basis

Freeze one control volume, contributing-area interpretation, analysis period, flow convention, phosphorus form, reporting basis, and mass unit before adding terms.

Core record

Watershed and lake control-volume boundary state · requiredNot recordedVersioned lake, surface watershed, groundwater contributing-area, inlet, outlet, direct-drainage, and exclusion boundary reference · requiredNot recordedSensitive data class: precise location.Exact analysis date range or event period and hydrologic context · requiredNot recordedPhosphorus form, fraction, basis, unit, and time convention state · requiredNot recordedAnalyte, fraction, as-P or other basis, units, time basis, flow convention, conversion references, and comparability limits · requiredNot recorded

3. Monitoring evidence and phosphorus budget

Keep concentration, load, yield, land input, generated load, delivered load, external input, internal flux, storage change, retention, and outflow distinct. Do not force closure.

Core record

Monitoring-data validation state · requiredNot recordedStations, periods, concentration and discharge methods, event coverage, validation package, qualifiers, missingness, and use decision · requiredNot recordedSensitive data class: operational.Phosphorus-budget state · requiredNot recordedBudget rows: stable term ID, pathway, input/output/storage/internal class, value or range, unit, period, method, evidence class, version, uncertainty, and overlap group · requiredNot recordedSensitive data class: operational.Budget residual and closure state · requiredNot recordedResidual, uncertainty, sensitivity, missing-term, overlap, and non-closure record · requiredNot recorded

4. Source inventory, contribution evidence, and model register

A source inventory is a hypothesis inventory. Land use, lake concentration, one sample, a non-detect, or a model output does not prove delivery or property-level responsibility.

Core record

Plausible-source inventory state · requiredNot recordedSource rows: source/pathway ID, external/internal class, location-release class, source evidence, mobilization evidence, connection/delivery evidence, known overlap, confidence, and gap · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Source-contribution state · requiredNot recordedAttributable source, mobilization, transport, delivery, comparison, uncertainty, and qualified-review evidenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Model applicability and lineage state · requiredNot recordedModel register: model and version, input vintage, calibration domain, spatial and temporal scale, scenario or observation status, assumptions, uncertainty, owner, and evidence reference · requiredNot recordedSensitive data class: operational.

5. Critical-source-area screening, site verification, and privacy

Critical-source-area status is a planning hypothesis about source, mobilization, and delivery. It is never a finding of culpability, liability, compliance, or parcel-scale truth.

Core record

Critical-source-area planning state · requiredNot recordedObjective, source x mobilization x delivery logic, data lineage, cutoff rationale, sensitivity, scale, ranked areas, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Consent-based site and records verification state · requiredNot recordedConsent, qualified role, noninvasive observations, records, targeted monitoring, dates, deviations, and bounded findingsNot recordedSensitive data class: precise location.Landowner, Tribal governance, producer confidentiality, and privacy state · requiredNot recordedOwnership/consent, Tribal governance, consultation, confidentiality, sensitive-location handling, generalization, release owner, and authority reference · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.

6. Alternatives, local design, and authorization

Compare no action and protection with source prevention, capture, in-transit, edge-of-field, shoreland, stormwater, septic, agricultural, and receiving-water categories. Eligibility, design, permit, and authorization remain separate.

Core record

Alternatives-comparison state · requiredNot recordedAlternatives matrix: mechanism, site/evidence fit, no-action/protection, expected range and basis, uncertainty, adverse effects, equity, O&M, cost basis, owner, authorization path, and rejection reason · requiredNot recordedSensitive data class: operational.Qualified design and authorization state · requiredNot recordedSite investigation, qualified designer, current state NRCS FOTG or other applicable local design basis, utilities, protected/cultural resources, and adverse-effects reviewNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Owner, Tribal, local, state, federal, permit, certification, zoning, label, consultation, authorization, conditions, dates, and exact scopeNot recordedSensitive data class: operational.

7. As-designed, as-built, implementation, and operation/maintenance

A selected or authorized practice is not an installed practice. An installed practice is not a maintained practice or an effective practice.

Core record

Implementation-fidelity state · requiredNot recordedAs-designed version, contracts, materials, dates, as-built record, inspections, deviations, acceptance, responsible roles, and photo/document IDsNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Operation and maintenance state · requiredNot recordedO&M plan/version, owner, inspections, maintenance events, condition, failures, corrective actions, funding, and next due dateNot recordedSensitive data class: operational.

8. Preregistered effectiveness, findings, adaptation, and correction lineage

Keep model expectations, implementation, mechanism response, delivered-load response, lake response, and adverse outcomes as separate attributable states. Lag and confounding remain visible.

Core record

Effectiveness-design state · requiredNot recordedPreregistered theory of change, implementation/mechanism/load/lake/adverse endpoints, baseline/comparator, flow/event context, minimum detectable change or power limits, lag, confounders, methods, rules, and reviewerNot recordedSensitive data class: operational.Target and adverse response state · requiredNot recordedValidated findings by endpoint, evidence version, uncertainty, comparison, implementation state, lag, confounders, adverse findings, qualified reviewer, date, and exact scopeNot recordedSensitive data class: operational.Adaptive-decision state · requiredNot recordedResponsible decision owner, evidence reviewed, decision, rationale, uncertainty, next evidence/action, due date, amendment, correction, and supersession references · requiredNot recordedSensitive data class: operational.Approved generalized public scope or no-public-release decision; exclude parcel/owner blame and protected dataNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Qualified reviewer attestation: role, date, reviewed evidence, bounded conclusions, limitations, and conflictsNot recordedSensitive data class: personal.