Shoreline, Littoral, and Fish-Habitat Assessment and Authority Handoff Record

Review overdue

This artifact passed its 2026-10-15 evidence or scheduled review date and is excluded from search-engine discovery until it is reassessed.

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 dispositionSTOP WORK: field safety prerequisite unresolved

Stable record IDNot started

Full-record documentation0 of 100 required fields documented

Independent shoreline habitat v1 states

field Safety: not assessed
survey: not started
assemblage Confidence: not started
condition Comparison: not evaluated
causal Attribution: not evaluated
regulatory Status: not evaluated
restoration: not evaluated
implementation: not started
effectiveness: not evaluated
public Communication: not authorized

Survey, assemblage confidence, condition comparison, cause, regulatory status, restoration authorization, implementation, effectiveness, and publication remain separate attributable decisions.

Safety and authority boundary

This record does not authorize private access, boating, wading, ice work, electrofishing, netting, trapping, fish handling, specimen take or transport, disturbance of rare or protected species or spawning, nursery, or refuge habitat, cultural-resource investigation or disturbance, stocking or harvest, a shoreline buffer or setback, grading, fill, dredging, shoreline armoring, structure placement, vegetation removal or planting, treatment, construction, or public notice. Current approved plans, landowners, Tribes and THPO or SHPO processes, wildlife and water authorities, permits and consultations, and trained personnel control the work. Observation does not prove habitat use, cause, impairment, absence, population size, restoration eligibility, authorization, implementation, effectiveness, or public-release authority.

LakeTech Learning Center · Field record

Shoreline, Littoral, and Fish-Habitat Assessment and Authority Handoff Record

Template ID: shoreline-littoral-and-fish-habitat-assessment-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: STOP WORK: field safety prerequisite unresolved
Reviewer attestation: Not recorded
Source guide: shoreline-littoral-habitat-assessment

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 and survey event

Use stable project, event, plan, jurisdiction, and role IDs. Protect site geometry and do not place private access credentials in this record.

Core record

Record ID · requiredNot recordedGenerated when you start a browser record; preserved on export and import.Sensitive data class: operational.Project or parent record IDNot recordedSensitive data class: operational.Completed by and role · requiredNot recordedSensitive data class: personal.Survey event ID · requiredNot recordedSensitive data class: operational.Waterbody, shoreline reaches, littoral station set, and bounded study area · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Survey purpose, decision question, intended use, and audience · requiredNot recordedGoverning QAPP, SAP, SOP, work order, and map version references · requiredNot recordedSensitive data class: operational.Federal, Tribal, state, territorial, local, land, water, fisheries, and historic-resource authority references · requiredNot recordedSensitive data class: operational.Survey start local date and time · requiredNot recordedSurvey end local date and timeNot recordedSurvey UTC offset (for example -07:00) · requiredNot recordedSurvey-team role IDs and task scopes; keep names in protected personnel records · requiredNot recordedSensitive data class: operational.Responsible data-release owner and roleNot recordedSensitive data class: personal.

2. Safety, access, protected resources, and biosecurity

Stop work or remain observation-only when a safety, access, handling, protected-resource, or cultural-resource condition is unresolved. Permission for one activity does not authorize another.

Core record

Current site- and task-specific safety plan reviewed · requiredNot recordedWeather, lightning, launch, shoreline, and access conditions acceptable · requiredNot recordedBoat, wading, ice, PFD, rescue, and competent-person requirements satisfied · requiredNot recordedElectrofishing, netting, trapping, hooks, sharps, entanglement, and fish-handling hazards controlled for the planned scope · requiredNot recordedHAB, spill, sewage, contaminant, wildlife, unstable-bank, and other water-contact hazards controlled · requiredNot recordedSensitive data class: personal.Communications, float plan, check-in, emergency, and authority contacts ready · requiredNot recordedSafety-gate evidence, limitations, competent roles, and stop-work criteria · requiredNot recordedSensitive data class: incident sensitive.Landowner or controlling-entity access state · requiredNot recordedAccess authority, area, dates, exclusions, and referenceNot recordedSensitive data class: operational.Protected landowner or access-contact record reference; do not enter an address, key, or access codeNot recordedSensitive data class: personal.Rare or protected species review state · requiredNot recordedOfficial species list, consultation, permit, avoidance, or authority referenceNot recordedSensitive data class: operational.Spawning, nursery, refuge, migration, and seasonal habitat review state · requiredNot recordedSensitive-habitat locations, timing windows, avoidance controls, and authority referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Archaeological, historic, Tribal, and culturally significant resource review state · requiredNot recordedTHPO, SHPO, Tribal, agency, confidentiality, consultation, and avoidance referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Decontamination, invasive-organism, pathogen, and between-site biosecurity controls ready · requiredNot recordedBiosecurity plan, equipment zones, waste route, and completion record referenceNot recordedSensitive data class: operational.Fish-capture authorization state · requiredNot recordedApproved fish method, collection permits, gear authorization, trained roles, handling limits, and scope referenceNot recordedSensitive data class: operational.Incident, mortality, exposure, suspected violation, or emergency authority handoffNot recordedSensitive data class: incident sensitive.

3. Survey design and reference frame

Freeze the target population, frame, units, stage datum, methods, effort, and nonresponse rules before interpretation. No gear, effort, depth, station count, or reference design is universal.

Core record

Controlled survey design ID, version, objectives, and analysis plan · requiredNot recordedSensitive data class: operational.Controlled survey design approved for this event · requiredNot recordedTarget population, shoreline and littoral extent, season, strata, receptors, and inference boundary · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Versioned shoreline, littoral, riparian, bathymetric, access, exclusion, and station-frame geometryNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Segment, station, transect, plot, or data-record selection and replacement rule · requiredNot recordedPlanned and actual segment, station, unit, and coordinate identities controlled · requiredNot recordedPlanned eligible segment or station count from the approved design · requiredNot recordedOperational shoreline, ordinary or normal high-water reference, current water edge, and survey-band definitions · requiredNot recordedWater level, stage, vertical datum, source, time, and uncertainty reference · requiredNot recordedSensitive data class: operational.Project-specific littoral boundary, light or depth basis, habitat zones, and limitations; no fixed width implied · requiredNot recordedSeason, phenology, hydrology, inflow, water-level operation, weather, ice, and recent-event context · requiredNot recordedSurvey method class · requiredNot recordedMethod, gear or sensor, settings, calibration, spatial and temporal effort, observers, detection rule, and source · requiredNot recordedObservational, subsample, segment, station, taxon, and reporting units and denominator · requiredNot recordedReference or comparison frame and method comparability resolved for any planned condition comparison · requiredNot recordedReference, benchmark, historical, model, or comparison source and selection ruleNot recordedPredeclared completeness, coverage, effort, taxonomic, positional, and evidence acceptance rules · requiredNot recordedInaccessible, unsafe, dry, deep, obstructed, denied-access, and other nonresponse disposition rules · requiredNot recordedRevisit, confirmation, seasonal, and non-detection inference rules · requiredNot recorded

4. Bounded shoreline, littoral, habitat, and fish observations

Record raw and classified observations with their method, effort, scale, location, time, life stage, and limitations. A habitat feature is not proof that a fish used it.

Core record

Segment and station rows: IDs, planned/actual coordinates, datum, accuracy, access, time with offset, depth, stage, method, effort, and no-sample status · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Substrate, bank, slope, drawdown, depth, woody material, boulder, ledge, vegetation, cover, and structural-observation rows · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Shoreline and riparian land cover, erosion, modification, runoff, access, use, and disturbance observations without causal or condition scoring · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Littoral cover and habitat-structure observations with controlled classes, method, scale, and visibility limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Fish detections and non-detections: observation ID, provisional taxon, rank, life stage, count or class, behavior, method, effort, and evidence · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Authorized capture and handling rows: gear event, effort, taxa, life stage, count, condition, measurements, release or custody, permits, and exceptionsNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Direct, indirect, inferred, or absent habitat-use evidence by taxon, life stage, feature, place, time, method, and limitation · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Potential or observed spawning, nursery, refuge, migration, and seasonal-use evidence and authority controls · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Photo or video IDs, station, direction, scale, time, raw-file hash or reference, photographer role, and release restriction · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Unsurveyed, invalid, inaccessible, unsafe, permission-limited, or method-limited units and denominator treatment · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Access, safety, weather, water-level, method, effort, handling, mortality, biosecurity, protected-resource, cultural-resource, and identity deviations · requiredNot recordedSensitive data class: incident sensitive.Survey completion state · requiredNot recordedSurvey conclusion scope: frame, eligible and completed units, dates, methods, effort, exclusions, deviations, and inference limits · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Detection and non-detection statements with exact taxon or group, area, time, method, effort, and limitations · requiredNot recordedSurvey attestation: name, role, date, event IDs, completion state, scope, and deviations reviewed (not identity-verified) · requiredNot recordedSensitive data class: personal.

5. Assemblage and taxonomic confidence

Keep provisional field names, confirmed determinations, life stages, observation effort, and assemblage inference separate. A detection or CPUE value is not a population estimate, stocking recommendation, or harvest recommendation.

Core record

Observation-to-determination rows: field name, accepted name, rank, authority, evidence, determiner role, date, confidence, and unresolved alternatives · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Taxonomic and assemblage confidence state · requiredNot recordedAssemblage conclusion scope: taxa, rank, life stages, frame, methods, effort, detections, non-detections, exclusions, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Current keys, collections, databases, nomenclatural authorities, and jurisdictional taxon sources · requiredNot recordedSensitive data class: operational.Qualified determination, voucher, image set, genetic result, specimen accession, or authority review referenceNot recordedSensitive data class: operational.Egg, larval, juvenile, adult, spawning-condition, or other life-stage evidence and confidence by observation · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Approved method and effort standardization, selectivity, catchability, detectability, and comparability referenceNot recordedSensitive data class: operational.Approved comparable-method CPUE or index rows with effort unit, scope, uncertainty, and explicit no-population-inference limitationNot recordedSensitive data class: operational.Unresolved taxa, hybrids, life stages, image or specimen limits, gear selectivity, detectability, and assemblage uncertainty · requiredNot recordedOriginal and revised identifications, reviewer, date, evidence, affected observation IDs, products, and notification status · requiredNot recordedSensitive data class: operational.Assemblage reviewer attestation: name, role, date, taxonomic and assemblage scope, evidence, and limitations (not identity-verified) · requiredNot recordedSensitive data class: personal.

6. Condition and reference comparison

Compare only commensurate observations and cited reference evidence. Preserve descriptive observations when a defensible comparison is unavailable; do not invent a universal score, class boundary, buffer, setback, or restoration target.

Core record

Condition and reference-comparison state · requiredNot recordedCited reference-site, historical, modeled, ecoregional, authority, or benchmark source, version, selection basis, and date · requiredNot recordedSensitive data class: operational.Comparison design, metric definitions, units, methods, stage, season, spatial support, uncertainty, and analysis reference · requiredNot recordedSensitive data class: operational.Raw observation, derived metric, method, calculation, source field, unit, eligible denominator, and version crosswalk · requiredNot recordedSensitive data class: operational.Method, effort, gear, taxonomy, season, hydrology, stage, access, scale, historical, and reference-selection limitations · requiredNot recordedCondition-comparison scope: shoreline reaches, littoral zones, taxa or assemblage, metrics, dates, reference, exclusions, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Metric-level observations and cited comparison results without an unsourced composite condition score · requiredNot recordedSensitive data class: operational.Uncertainty, conflicting indicators, insufficient comparability, alternative interpretations, and retained descriptive evidence · requiredNot recordedNext reference, repeat, method-alignment, analysis, or reviewer evidence needed and owner · requiredNot recordedSensitive data class: incident sensitive.

7. Causal attribution and regulatory status

A condition comparison does not identify cause, and neither condition nor cause determines impairment. Only the controlling jurisdiction and reporting cycle establish regulatory status.

Core record

Named causal hypotheses, mechanisms, affected receptors, spatial and temporal predictions, and evidence that could weaken each · requiredNot recordedAlternative causes, confounders, co-stressors, historical changes, management actions, and discriminating evidence evaluated · requiredNot recordedCausal-attribution state · requiredNot recordedCausal analysis, weight-of-evidence, model, experiment, source analysis, or qualified-review referenceNot recordedSensitive data class: operational.Causal conclusion scope: stressor, mechanism, receptor, area, dates, evidence, alternatives, uncertainty, and exclusions · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Causal reviewer attestation: name, role, date, method, alternatives, scope, and limitations (not identity-verified)Not recordedSensitive data class: personal.Controlling assessment-unit ID and waterbody or segment nameNot recordedSensitive data class: operational.Controlling state, authorized Tribe, territory, or EPA jurisdiction; reporting cycle; designated use; parameter; and decision scope · requiredNot recordedSensitive data class: operational.Regulatory impairment state · requiredNot recordedControlling authority decision, Integrated Report, EPA action, ATTAINS record, or case referenceNot recordedSensitive data class: operational.Authority source version, reporting cycle, approval status, retrieval date, and supersession statusNot recordedSensitive data class: operational.Authority-confirmed status scope: unit, use, parameter or cause, category, cycle, decision, exclusions, and limitations · requiredNot recordedSensitive data class: operational.Conflicting, proposed, delisted, superseded, locally tracked, or discovery-only records; explicitly record none · requiredNot recorded

8. Restoration eligibility and authorization

Define the bounded problem and compare no action, protection, and restoration categories. Eligibility, funding, landowner agreement, consultation, permits, technical design, and authorization remain separate controls.

Core record

Bounded restoration problem, affected receptors and uses, evidence, uncertainty, and decision owner · requiredNot recordedProject-specific objectives, measurable target and adverse endpoints, time and area scope, uncertainty, and decision rules from the approved plan · requiredNot recordedNo action, protection, access or use management, revegetation, bioengineering, hydrologic, in-water, and other authority-reviewed alternatives with rejection reasons · requiredNot recordedRare species, spawning, nursery, refuge, migration, wetlands, native vegetation, water use, cultural resources, private access, and neighboring-property avoidance · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Restoration method class · requiredNot recordedRestoration eligibility and authorization state · requiredNot recordedRestoration decision scope: objective, area, method class, alternatives, design basis, exclusions, restrictions, authorization, and affected event IDs · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Controlling authorization, conditions, effective and expiration dates, issuing authority, and case referenceNot recordedSensitive data class: operational.Approved restoration design, drawings, specifications, monitoring plan, and version referenceNot recordedSensitive data class: operational.Water, fill, navigation, floodplain, wetlands, fisheries, protected-species, cultural-resource, local, and other permit or consultation referencesNot recordedSensitive data class: operational.Landowner agreement, property scope, access, maintenance, liability, and term referenceNot recordedSensitive data class: operational.Tribal, THPO, SHPO, agency, confidentiality, identification, effects, and resolution referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Official species list, consultation, take or handling permit, conservation measures, timing, and scope referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Responsible restoration decision owner, role, authority, and decision date · requiredNot recordedSensitive data class: personal.

9. Implementation and effectiveness validation

Record authorized design, actual work, deviations, implementation fidelity, ecological response, and adverse outcomes as separate attributable events.

Core record

Implementation state · requiredNot recordedImplementation scope: authorization, action, area, method, dates, exclusions, restrictions, and affected event IDs · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Scheduled and completed work, inspection, construction, planting, placement, access, and compliance event referencesNot recordedSensitive data class: operational.Approved-design to as-built or as-performed geometry, quantities, materials, species, method, and version crosswalk referencesNot recordedSensitive data class: operational.Safety, weather, access, resource, design, material, equipment, contractor, permit, non-target, spill, exposure, mortality, and stop-work deviationsNot recordedSensitive data class: incident sensitive.Controlled effectiveness design, endpoints, baseline and comparison logic, schedule, uncertainty, adverse outcomes, and decision owner · requiredNot recordedSensitive data class: operational.Baseline, reference, untreated comparison, prior survey, model, or counterfactual evidence and limitations · requiredNot recordedSensitive data class: operational.Effectiveness validation state · requiredNot recordedEffectiveness decision scope: endpoint, area, habitat, taxon or assemblage, dates, evidence, exclusions, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Qualified reviewer decision, analysis package, data version, and conclusion referenceNot recordedSensitive data class: operational.Rare, native, spawning, nursery, refuge, fish-health, water-quality, erosion, neighboring-property, cultural, access, downstream, or other adverse findingsNot recordedSensitive data class: incident sensitive.Next monitoring, validation, maintenance, corrective action, consultation, or decision and due date · requiredNot recordedImplementation attestation: name, role, date, event IDs, and authorization basis reviewed (not identity-verified)Not recordedSensitive data class: personal.Effectiveness reviewer attestation: name, role, date, scope, evidence, and limitations (not identity-verified)Not recordedSensitive data class: personal.

10. Public communication and handoff

Release only an attributable, versioned, bounded product. Generalize or restrict rare-species, spawning, nursery, refuge, cultural-resource, private-access, and structure locations as the responsible authorities require.

Core record

Public communication state · requiredNot recordedResponsible communication authority and decision referenceNot recordedSensitive data class: personal.Public product scope: area generalization, dates, survey, assemblage, condition, cause, regulatory, restoration, implementation, effectiveness, and limitationsNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Published, corrected, withdrawn, or superseded product and version referenceNot recordedSensitive data class: operational.Required uncertainty, non-detection, habitat-use, causal, jurisdiction, impairment, authorization, effectiveness, and location limitations · requiredNot recordedSensitive-location release decision · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Unresolved access, safety, survey, taxonomy, condition, cause, regulatory, authorization, implementation, effects, publication, correction, and owner items; explicitly record none · requiredNot recordedNext responsible role, action, evidence needed, and due date · requiredNot recordedSensitive data class: personal.Reviewer attestation: name, role, date, all decision states and evidence reviewed, scope, and limitations (not identity-verified) · requiredNot recordedSensitive data class: personal.