Skip to content
Lake and pond expertiseSoftware, monitoring, and consulting
Learning CenterApplications chapterBuild a Watershed Nutrient Source-Control and Shoreland Action Program
Application program · Source control and shoreland

Build a Watershed Nutrient Source-Control and Shoreland Action Program

Turn supported source-and-pathway evidence into locally authorized prevention, repair, conservation, stormwater, wastewater, and shoreland actions with documented design, maintenance, and independent effectiveness evaluation.

For
Watershed and lake managers, Tribes, municipalities, conservation districts, public works, onsite-wastewater and agricultural partners, shoreland organizations, consultants, monitoring teams, funders, and community participants
Reading time
32 minutes
Reviewed
Next review
Direct answer

What to do first

A source-control program starts with governance, a bounded receiving-water objective, supported source-and-pathway evidence, and a theory of change linking each action to an interrupted nutrient pathway. Apply readiness gates before design: evidence, willing and authorized participants, feasibility, applicable permits, funding, maintenance ownership, equity, and a measurement plan. Compare prevention, operational change, inspection or repair, green infrastructure, erosion and runoff controls, agricultural conservation systems, shoreland restoration, monitoring, and no-action alternatives; do not begin with a favorite product. A buffer has no universal width, and a BMP has no universal efficiency. Current state NRCS Field Office Technical Guide criteria, site conditions, qualified design, property rights, local and Tribal requirements, permits, and pesticide labels control where applicable. Pumping a septic tank does not prove the system is protective; wastewater inspection and repair belong with qualified providers and responsible authorities, not DIY exposure. Resolve permit and certification applicability before disturbance, discharge, fill, shoreline work, or pesticide use; EPA guidance is not a substitute for controlling law. Record final design assumptions, approvals, as-built condition, deviations, costs, operation, maintenance, and participation. Implementation completion does not prove water-quality effectiveness. Pre-register comparison, timing, stations, covariates, endpoints, QA/QC, analysis, uncertainty, and decision rules before outcome data. Report measured change, modeled expectation, implementation evidence, and inference separately. A lake's response may be delayed, masked, or limited by weather, groundwater, legacy stores, internal cycling, ecology, and incomplete coverage; external source control does not guarantee a bloom-free lake, and in-lake work does not replace watershed source control.

Use this guide to
  • Establish accountable governance, authority, privacy, participation, and decision records
  • Connect each action to a supported source, delivery pathway, and measurable theory of change
  • Use readiness gates and alternatives analysis before committing to design or construction
  • Apply current local, Tribal, state, federal, NRCS field-office, and label requirements
  • Document as-built fidelity, operation, maintenance, participation, and implementation evidence
  • Pre-register an effectiveness design that separates observed outcomes from modeled expectations
  • Adapt transparently without treating delayed lake response as automatic failure or success
Continue the work

Field route

Use an authored handoff; this is not an automatic recommendation or approval.

Shared route boundary

Does not calculate loads from monitoring inputs, TMDLs, allocations, efficiencies, targets, treatment prescriptions, rankings, causation, or guaranteed reductions.

1. Establish governance, authority, and decision rights

The program needs named owners for evidence, funding, design, authorization, implementation, maintenance, monitoring, privacy, and public communication.

Create a charter identifying the receiving-water objective, geographic scope, current watershed plan or TMDL, participating governments and organizations, Tribal jurisdiction, landowner roles, decision rules, conflict process, records, and accountability. Separate voluntary assistance, grant eligibility, regulatory decisions, and public claims.

Use respectful participation and minimum-necessary data. Do not publish property-level source allegations or assume that one government can authorize work on another jurisdiction's or a private party's land.

Sources: [1], [23]

2. Write a source-pathway-action theory of change

Every proposed action must identify the mass or pathway it is expected to change and the evidence that would test that expectation.

Action logic record
ElementRequired statementDo not substitute
Source and pathwaySupported source, mobilization, connection, periodLand-use label alone
Action mechanismHow the action prevents, retains, treats, repairs, or disconnectsBMP name alone
Implementation endpointAs-built, operated, maintained, and participating conditionInvoice or award alone
Outcome endpointExpected directional change and uncertaintyGuaranteed lake response

Sources: [1], [2]

3. Pass readiness gates before detailed design

A technically plausible action can still be unready because access, authority, maintenance, or evaluation is unresolved.

  • Source and pathway evidence is sufficient for the proposed mechanism
  • Affected landowners, operators, communities, and jurisdictions have a lawful participation path
  • Site reconnaissance supports feasibility without replacing design
  • Permit, certification, consultation, property-right, procurement, and funding pathways are identified
  • Operation, maintenance, inspection, repair, and replacement owners accept their roles
  • Baseline, implementation, and effectiveness evidence can be collected ethically and safely

Sources: [1], [2]

4. Compare prevention and alternatives before selecting projects

A program should compare ways to avoid, reduce, disconnect, retain, treat, repair, or monitor a pathway.

Define the no-action baseline and compare operational prevention, source substitution, inspection or repair, flow reduction, infiltration where appropriate, erosion control, treatment, restoration, acquisition or easement, outreach, policy, and further monitoring. Evaluate effectiveness evidence, site fit, risk, cost, lifecycle effort, equity, co-benefits, adverse effects, reversibility, and uncertainty.

Select systems of complementary practices when one measure cannot control the full source and transport chain. Do not transfer runoff, erosion, flooding, exposure, maintenance burden, or cost to another community or resource.

Sources: [2], [1]

5. Build shoreland actions around runoff, soil, vegetation, and lake access

Shoreland work must fit the site's slope, soils, drainage, wave climate, vegetation, use, and controlling rules.

Begin with runoff disconnection, soil protection, native or locally appropriate vegetation, minimized disturbance, stabilized access, and maintenance. Minnesota DNR and Extension examples illustrate principles, but their dimensions and plant guidance are not universal outside the applicable setting.

Do not prescribe a universal buffer width or assume a planted strip can compensate for concentrated flow, failing infrastructure, unstable banks, or an untreated upslope source. Resolve shoreline, grading, wetland, floodplain, easement, and local approvals before work.

Sources: [16], [17], [18]

6. Put onsite wastewater assessment and repair in qualified hands

Service history, age, or visual condition alone does not establish hydraulic and treatment performance.

Use current health, environmental, and local requirements to identify the responsible authority and qualified provider. Records, inspections, setbacks, soils, groundwater, hydraulic loading, components, maintenance, and receiving-water pathways may all matter. Protect household privacy and communicate findings through authorized channels.

Pumping is maintenance, not proof of treatment performance and not a repair for every failure mode. Never direct residents or volunteers to open, enter, sample, reroute, or repair septic or sewage components themselves.

Sources: [6], [7]

7. Control urban, road, and construction runoff as a connected system

Trace rainfall and snowmelt through impervious areas, drainage, erosion, conveyances, practices, and outfalls.

Prioritize source prevention, housekeeping, fertilizer and organic-material control, erosion prevention, runoff reduction, disconnection, green infrastructure, conveyance repair, treatment, and maintenance according to local conditions. Include roads, parking, municipal operations, development, and construction where evidence supports them.

Construction stormwater requirements and municipal, industrial, or other permits vary by activity and jurisdiction. Resolve applicability with responsible authorities; do not treat a national web page as authorization or a complete local specification.

Sources: [8], [9], [10], [19]

8. Develop agricultural conservation systems through current local technical channels

Agricultural source control depends on operation-specific goals, site evidence, producer participation, and coordinated practices.

Work with producers and qualified conservation professionals to assess nutrient sources, timing, placement, rate, soil and crop conditions, erosion, runoff, drainage, livestock areas, storage, and connected pathways. Protect confidential operational data and distinguish voluntary technical assistance from regulatory functions.

NRCS national Conservation Practice Standards describe purposes and criteria, but implementation must use the current state Field Office Technical Guide and applicable laws, contracts, permits, and professional judgment. Standard 590 is not a universal fertilizer prescription and does not authorize a site plan by itself.

Sources: [11], [12], [13]

9. Select practice systems for the actual pathway

Practice names such as filter strip or riparian buffer do not guarantee performance independent of design and maintenance.

Define the inflow, pollutant form, hydrology, sediment and nutrient mechanism, bypass conditions, capacity, vegetation, pretreatment, outlet, inspection, and failure response. A filter strip and riparian forest buffer serve defined purposes under current criteria; neither has a universal width or efficiency.

Model the expected reduction as a scenario with uncertainty, then preserve it as modeled evidence. Do not report that expectation later as a measured reduction unless the effectiveness design supports that inference.

Sources: [14], [15], [2]

10. Resolve design basis, labels, property rights, and permissions

The controlling design and authorization package is local and activity-specific.

Record current survey and site data, design criteria, responsible designer, calculations, geotechnical or ecological needs, property rights, utilities, access, procurement, safety, permit and certification determinations, consultation, inspection hold points, and approval owners. Confirm requirements again if scope or conditions change.

Section 401 certification, Section 404 authorization, construction stormwater coverage, shoreline or wetland rules, and other approvals may apply depending on facts and jurisdiction. A pesticide label is legally enforceable; the program must not recommend use inconsistent with the current label or applicable law.

Sources: [20], [21], [19], [22]

11. Select transparently and fund the lifecycle

Project selection should show why an alternative fits and who will carry benefits, risks, and recurring work.

Use a documented matrix for pathway fit, evidence, feasibility, lifecycle cost, operation and maintenance, monitoring, co-benefits, adverse effects, climate resilience, participation, accessibility, and distributional impacts. Record who participated, who decided, and how conflicts or new evidence are handled.

Fund inspection, sediment or vegetation management, repairs, replacement, training, recordkeeping, and access, not only construction. A project without a capable maintenance owner is not ready.

Sources: [1], [2]

12. Verify as-built condition, operation, maintenance, and participation

Completion evidence must describe what exists and functions, not merely what was funded or planned.

  • Approved design, revisions, approvals, and georeferenced or otherwise controlled as-built record
  • Materials, dimensions, elevations, vegetation, drainage, connectivity, capacity, and deviations
  • Commissioning, stabilization, initial performance checks, photographs, and inspector acceptance
  • Operation, maintenance, inspection, repair, replacement, training, and record owners
  • Participation, adoption, operational change, access, downtime, bypass, and failure history

Sources: [1], [3]

13. Pre-register effectiveness monitoring before outcome data

A defensible evaluation specifies the inference and analysis before seeing the answer.

Define implementation endpoints and environmental outcomes separately. Before outcome data, register the comparison design, baseline and follow-up periods, stations, event and seasonal coverage, discharge or other covariates, parameters, methods, laboratories, QA/QC, missing-data rules, analysis, uncertainty, confounders, decision thresholds, and publication commitments.

Use designs proportionate to the decision, such as paired, upstream-downstream, before-after, or control-impact approaches when feasible. A trend at one station can be affected by flow, weather, upstream change, legacy stores, sampling, and unrelated actions.

Sources: [3], [4]

14. Separate implementation, modeled expectation, measured outcome, and lake response

Adaptation is strongest when the program does not overclaim what each evidence stream can establish.

Report implementation fidelity, operation, maintenance, participation, modeled reduction, edge-of-practice or pathway outcomes, watershed loads, lake condition, uncertainty, and attribution strength as distinct results. Never relabel a modeled reduction as measured or project completion as effectiveness.

No detected response can reflect inadequate implementation, insufficient coverage, low power, an unsuitable indicator, lag, weather, groundwater, legacy stores, internal cycling, or a wrong conceptual model. It is not automatically failure. Likewise, a favorable change is not automatically caused by the program. Update the model, monitoring, maintenance, coverage, or alternative only through a documented review.

Sources: [3], [1]

Evidence base

Sources and review notes

Educational watershed nutrient-planning guidance only. This material is not a source-attribution, liability, compliance, impairment, permit, engineering-design, septic-system, agricultural nutrient-management, pesticide-use, public-health, or treatment decision. It does not establish a universal phosphorus target, critical-source cutoff, buffer width, setback, pumping interval, fertilizer rate, storm design, BMP efficiency, load reduction, or expected lake response. Current state, territorial, Tribal, federal, watershed, and local authorities; adopted standards and TMDLs; property and access rights; current NRCS state Field Office Technical Guide materials; product labels; qualified professionals; and site-specific evidence control. LakeTech does not identify responsible parties or authorize work.

  1. Handbook for Developing Watershed Plans to Restore and Protect Our WatersU.S. Environmental Protection Agency · agency guidance
  2. Critical Source Area Identification and BMP Selection: Supplement to Watershed Planning HandbookU.S. Environmental Protection Agency · agency guidance
  3. Guidance: Monitoring and Evaluating Nonpoint Source Watershed ProjectsU.S. Environmental Protection Agency · agency guidance
  4. Nonpoint Source Monitoring: TechNOTESU.S. Environmental Protection Agency · reference
  5. Sources and Solutions: WastewaterU.S. Environmental Protection Agency · agency guidance
  6. Septic System Impacts on Water SourcesU.S. Environmental Protection Agency · agency guidance
  7. SepticSmartU.S. Environmental Protection Agency · agency guidance
  8. Sources and Solutions: StormwaterU.S. Environmental Protection Agency · agency guidance
  9. Nonpoint Source: Urban AreasU.S. Environmental Protection Agency · agency guidance
  10. Urbanization and Stormwater RunoffU.S. Environmental Protection Agency · agency guidance
  11. Conservation Practice StandardsUSDA Natural Resources Conservation Service · agency guidance
  12. Field Office Technical GuideUSDA Natural Resources Conservation Service · agency guidance
  13. Nutrient Management (Ac.) (590) Conservation Practice StandardUSDA Natural Resources Conservation Service · agency guidance
  14. Filter Strip (Ac.) (393) Conservation Practice StandardUSDA Natural Resources Conservation Service · agency guidance
  15. Riparian Forest Buffer (Ac.) (391) Conservation Practice StandardUSDA Natural Resources Conservation Service · agency guidance
  16. Restore Your ShoreMinnesota Department of Natural Resources · agency guidance
  17. Shoreline Alterations: Natural Buffers and LakescapingMinnesota Department of Natural Resources · agency guidance
  18. Minimizing Runoff from Shoreland PropertyUniversity of Minnesota Extension · agency guidance
  19. Stormwater Discharges from Construction ActivitiesU.S. Environmental Protection Agency · agency guidance
  20. Overview of CWA Section 401 CertificationU.S. Environmental Protection Agency · agency guidance
  21. Permit Program under CWA Section 404U.S. Environmental Protection Agency · agency guidance
  22. Introduction to Pesticide LabelsU.S. Environmental Protection Agency · agency guidance
  23. Tribal Nonpoint Source ProgramU.S. Environmental Protection Agency · agency guidance