Fish Community and Littoral Habitat Restoration Program

Identify the waterbody and connected system, land and water ownership, responsible federal, Tribal, state, territorial, and local authorities, designated and existing uses, treaty or reserved rights, cultural and subsistence values, target and non-target species or assemblages, relevant life stages, public uses, and protected resources. Translate broad goals such as improve the fishery into a bounded objective with location, receptor, mechanism hypothesis, evidence measure, uncertainty, timeframe, adverse endpoint, decision owner, and communication owner.

Use the state's or authorized Tribe's current water-quality standards and other governing documents rather than a generic aquatic-life label. EPA explains that designated uses, criteria, and antidegradation are distinct parts of water-quality standards. The Meskwaki Nation source is a specific Tribal example showing cultural, fish-consumption, fish-and-aquatic-life, and habitat uses for its waters; its classifications do not govern another Tribe, state, or waterbody.

Sources: [2], [16], [1]

Define the target population or assemblage, sampling frame, habitat and depth coverage, index period or seasonal logic, repeat or trend objective, approved capture or observation methods, identification resolution, animal-care and biosecurity controls, permits, qualified personnel, protected-species procedures, data-quality criteria, and analysis before mobilization. Methods may include authority-approved active or passive capture, visual observation, hydroacoustics, eDNA, telemetry, creel or harvest information, or existing agency records; their detections and denominators are not interchangeable.

USGS fish-community guidance emphasizes permits, protected species, coordination, complementary methods, and expert identification. Minnesota's lake-survey manual is a primary state protocol demonstrating how one jurisdiction standardizes lake fisheries information. Its gear specifications, effort, seasons, comparisons, and management uses are Minnesota program controls, not universal instructions for another project. This guide intentionally supplies none of those operational values.

• Survey purpose, inference population, stations or reaches, habitats, season, life stages, and decision use are explicit
• Capture, handling, marking, anesthesia, tissue, voucher, eDNA, access, navigation, and protected-species permissions are confirmed where applicable
• Gear and observation selectivity, detection probability, avoidance, attraction, size selectivity, habitat access, weather, water level, temperature, and crew effects are recorded
• Individual observations retain event, location, method, effort unit defined by the approved protocol, taxon confidence, disposition, and anomalies
• Counts, catch indices, occupancy, relative abundance, size structure, age, condition, recruitment proxies, and population estimates remain distinct outputs
• Non-detection is bounded to method, effort, place, depth, season, and detection limits rather than promoted to absence
• Historical and partner data are screened for method and taxonomic comparability before trend use

Sources: [7], [12], [5], [1]

Define lake class and comparison context using relevant natural and management controls such as ecoregion, basin origin and morphometry, hydrology, elevation, climate, connectivity, native zoogeography, thermal and oxygen regime, productivity, substrate, shoreline and littoral structure, water-level operation, land use, and documented history. Candidate reference sites or historical periods need screening, comparability evidence, and explicit remaining disturbance.

EPA's lake bioassessment guidance treats reference condition as foundational to biological assessment and biological criteria. A regional reference distribution, state lake class, authority-adopted criterion, historical baseline, least-disturbed comparison, best-attainable condition, and project target are different constructs. Record which one is used, who adopted it, its geographic and temporal domain, method compatibility, uncertainty, and what decision it can support.

Sources: [5], [2], [12]

Use a controlled spatial design that represents the decision area and retains station, reach, plot, polygon, depth, datum, current and reference shoreline, water level, observation method, visibility, access limits, imagery source, and survey time. Characterize riparian vegetation and continuity, bank condition and alteration, runoff pathways, shade, shoreline modification, substrate, sediment deposition or erosion, woody and other cover, aquatic vegetation, littoral slope and depth, refuge, adjacent land use, and connected wetland or tributary features under the approved method.

EPA's National Lakes Assessment field manual provides one national survey design for population-level assessment, and EPA's physical-habitat indicator combines shoreline and shallow-water components. Those definitions and category boundaries should be retained when using that method; they are not universal design specifications or local impairment thresholds. Minnesota's lake-habitat resources similarly illustrate a state program and do not establish requirements elsewhere.

• The assessment frame covers target, comparison, protected, untreated, and potential downstream or adjacent effect areas
• Normal high-water, ordinary high-water, operational shoreline, current water edge, and project datum are not conflated
• Riparian, shoreline, drawdown, littoral, pelagic, tributary, wetland, and groundwater interfaces are represented where relevant
• Structure presence, condition, function, origin, stability, and ownership are separate observations
• Aquatic vegetation evidence links to controlled plant-identification and survey records
• Temperature, dissolved oxygen, clarity, flow, water level, and chemistry are linked by time and depth without being treated as physical structure
• Photographs, remote sensing, maps, and models retain ground verification and inference limits

Sources: [4], [3], [13], [1]

Build a conceptual model from sources through stressors to fish and habitat responses. Candidate pathways may involve altered water level or flow, lost connectivity, temperature or oxygen regime, sediment, nutrients, contaminants, salinity or ionic conditions, pathogens, harvest, stocking history, invasive species, food-web change, shoreline and riparian alteration, littoral vegetation, substrate, refuge, direct disturbance, or interacting stressors. List evidence expected if each candidate is important and evidence that could weaken it.

EPA CADDIS provides a weight-of-evidence approach for causal assessment and cautions against assuming that a biological response identifies its cause. Use site evidence, temporal order, exposure or co-occurrence, mechanistic plausibility, stressor-response information, spatial patterns, experimental or comparison evidence, and evidence inconsistent with each candidate. State residual uncertainty and competing causes. The responsible authority, not the analyst or contractor, determines impairment under applicable law and process.

Sources: [6], [3], [5], [8]

For each focal native species, assemblage function, or protected receptor, document life stages and required functions without assuming one habitat serves all of them. Map spawning, incubation, nursery, feeding, seasonal refuge, overwintering, migration, and recolonization evidence; tributary, outlet, wetland, floodplain, groundwater, and adjacent-lake connections; barriers and partial barriers; water-level and flow operation; thermal and oxygen pathways; entrainment or injury risks; and timing uncertainty.

Treat connectivity as both potential benefit and potential risk. Reconnection can affect invasive species, pathogens, predators, genetics, water levels, sediment, infrastructure, and other protected resources. USFWS describes fish passage as supporting movement needed for food, reproduction, and migration, and emphasizes professional planning, engineering, implementation, and monitoring. A barrier inventory, passability model, or observed fish below a structure does not constitute a design or removal authorization.

• Focal taxa and life stages are confirmed or explicitly provisional
• Movement timing is tied to observed or authoritative evidence rather than a universal calendar window
• Barrier ownership, purpose, condition, operations, safety, and legal constraints are documented
• Upstream and downstream habitat quantity, quality, accessibility, and protected receptors are evaluated
• Invasive-species, disease, genetic, predator, sediment, water-level, and infrastructure consequences are screened
• Passage feasibility, engineering, hydrology, geomorphology, and authorization remain qualified-authority tasks

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

Start with no action, monitoring, protection of intact habitat, and removal or prevention of avoidable stressors. Compare categories at the conceptual level against the documented cause, life-stage need, designated and cultural uses, expected condition, uncertainty, reversibility, feasibility, climate and water-level resilience, maintenance, protected resources, public and landowner effects, permits, monitoring burden, and total lifecycle cost. Record reasons for retaining or rejecting each category.

Potential categories for analysis may include watershed or runoff-source actions; riparian or shoreline-process protection; littoral vegetation, substrate, or structural-habitat work; hydrologic, water-level, wetland, or floodplain processes; connectivity or passage; water-quality and thermal-refuge actions; invasive-species prevention; and fisheries-management actions under the responsible fish authority. Listing a category is not a recommendation. Qualified agencies, fisheries professionals, engineers, Tribes, landowners, and permitting bodies determine whether any site-specific alternative may proceed.

Sources: [8], [9], [6], [12]

Build an authority matrix early: land and water ownership; sovereign jurisdiction; designated uses and antidegradation; treaty or reserved rights; Tribal natural and cultural resources; federal and state listed species and critical habitat; migratory birds, wetlands, navigation, water quality, dam and water-level control, floodplain and local shoreline requirements; fish collection and handling permits; invasive-species controls; archaeology and historic properties; construction, access, easements, utilities, and public safety. Name the responsible decision-maker and current status for each review.

USFWS IPaC can support planning for listed species and critical habitat but does not replace required consultation or authorization. For federal undertakings, ACHP describes Section 106 participation by State or Tribal Historic Preservation Officers, Tribes, Native Hawaiian organizations, local government, applicants, and the public. Do not expose sensitive species, archaeological, sacred, burial, or traditional-use locations in public files; follow the authority's collection, custody, confidentiality, inadvertent-discovery, and stop-work requirements.

Washington's Hydraulic Project Approval process is included only as a state-specific example showing that work in or near water may require agency review and that changed projects may require modification. Its jurisdiction, terminology, timelines, and pathways are not national rules. Similarly, the Meskwaki Nation code governs the waters and uses within its own stated authority and is not portable to another jurisdiction.

• Eligibility, application completeness, consultation, permit issuance, landowner consent, design approval, funding, contracting, and notice are tracked separately
• Action area includes direct, indirect, downstream, staging, access, disposal, and cumulative-effect areas as required
• Protected-resource and cultural reviews use current official records plus authority-directed field work where necessary
• Approved drawings, specifications, methods, timing windows, exclusions, monitoring, reporting, mitigation, stop-work, and amendment controls agree
• The final authorization gate names who may approve work, exact scope, effective dates, prerequisites, open conditions, and revocation or modification path

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

Translate every authorization and design condition into a controlled work package with revision, responsible owner, contractor and subcontractor qualifications, approved area and exclusions, access and staging, utilities and property controls, timing and weather or water-condition gates, safety and emergency plans, species and cultural stop-work procedures, erosion and contamination controls, material provenance and inspection, equipment and decontamination, public notifications, observation or inspection hold points, monitoring, reporting, change authority, and demobilization or stabilization criteria.

Record as-approved and as-implemented evidence separately. Retain dates and times, personnel and roles, drawings and spatial files, survey control and datum, material and equipment records required by the project, pre-work conditions, photographs, inspections, work limits, actual geometry or quantities required by the approved record, weather and water level, turbidity or other construction controls, fish and wildlife observations, incidents, complaints, deviations, stop-work, corrective actions, waste or removed-material disposition, and as-built certification where required.

Sources: [11], [14], [1], [10]

Before implementation, create an endpoint matrix linking each objective and supported causal pathway to implementation, physical-process, habitat, fish-assemblage or population, life-stage, designated-use, non-target, adverse, socioeconomic or access, and compliance evidence. For each endpoint, name the represented population and area, method, baseline, reference or comparison, timing, expected direction, detectable-change requirement, quality criteria, uncertainty, confounders, sensitive-data handling, decision rule source, owner, and possible disposition.

NOAA explicitly separates implementation monitoring (whether a project was executed as designed) from effectiveness monitoring (whether it functions as intended). Apply that separation even when a funding or permit program uses different tier names. A completed shoreline, open passage route, installed feature, planted area, or contractor sign-off is not a fish-community outcome. Fish presence is not recruitment; short-term use is not population benefit; target response is not proof that native, cultural, infrastructure, or downstream receptors were protected.

Sources: [11], [1], [5], [8]

1. 01

   Verify the package

   Reconcile raw fish and habitat evidence, taxonomic review, methods and permits, reference expectations, causal record, authority decisions, approved and as-built files, deviations, monitoring, quality findings, sensitive-resource controls, and data versions. Preserve missing and rejected evidence.

2. 02

   Test implementation and mechanism

   Determine whether work matched authorization and whether the intended physical or ecological mechanism occurred before attributing a fish response. Bound deviations and affected monitoring intervals.

3. 03

   Evaluate target and adverse responses

   Compare preregistered target, non-target, life-stage, designated-use, cultural, access, and adverse endpoints with baseline and reference logic while considering method change, season, hydrology, weather, water level, stocking, harvest, disease, invasive species, and other projects.

4. 04

   Assign a scoped conclusion

   Use a controlled result such as supported improvement, no supported change, adverse effect, mixed response, or inconclusive. State the exact project version, area, period, endpoints, uncertainty, open findings, reviewer, and named use.

5. 05

   Authorize the next decision separately

   Possible dispositions include continue monitoring, protect the result, repair or mitigate under authority, revise the conceptual model, collect missing evidence, close the project, or develop a new alternative for separate review. No outcome authorizes stocking, harvest change, construction, treatment, or a repeated action.

Sources: [11], [6], [1], [8]

Before field work or implementation, communicate the objective, authority, evidence need, methods and limits, access and safety controls, protected and cultural-resource handling, approved scope, public restrictions, schedule uncertainty, complaint and incident path, monitoring, and next update owner. During work, distinguish operational changes, permit or stop-work findings, observations, and confirmed authority decisions. After work, distinguish completion, implementation conformance, provisional monitoring, validated effectiveness, and any authority finding.

Release fish and habitat datasets, maps, reports, and dashboards with project and event IDs; station, reach, polygon, datum and time basis; method and effort definition; gear or observation type; taxonomic confidence; detection and inference limits; reference and comparison basis; stocking and management-history context; quality and review state; sensitive-location suppression; decision and communication authority; intended use; version; and correction path. Do not publish precise protected-species, sacred, archaeological, private-property, or vulnerability information contrary to authority requirements.

When identity, assemblage calculation, geometry, reference set, causal conclusion, impairment status, permit, as-built record, endpoint result, or public interpretation changes, issue a traceable amendment. Name affected records, maps, decisions, and users; notify downstream custodians; preserve the superseded version; and reassess whether prior communication remains valid.

• Observation, identification, assemblage estimate, habitat association, cause, impairment, eligibility, authorization, implementation, effectiveness, and communication are separately labeled
• Maps distinguish surveyed, modeled, unsurveyed, inaccessible, provisional, and sensitive-suppressed areas
• Fish estimates identify the exact sample frame, method, period, effort definition, analysis version, and uncertainty
• Authority statements identify the issuer, jurisdiction, effective date, exact scope, and current official source
• Effectiveness reports include null, adverse, mixed, and inconclusive results and do not report only target gains
• Each release names reviewer, release authority, intended use, limitations, open findings, version, and amendment lineage

Sources: [1], [11], [2], [10]