Recreational-Water Sampling 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 dispositionESCALATE: responsible-authority direction required; no advisory or reopening decision implied

Stable record IDNot started

Full-record documentation0 of 48 required fields documented

Safety and authority boundary

No water entry or contact is required to complete this record. Do not collect samples or enter the water when conditions are unsafe or contrary to current authority or laboratory direction. This browser-local record does not identify pathogens, diagnose illness, declare water safe, issue or lift an advisory, reopen a site, authenticate a reviewer, or replace state, Tribal, or local rules, permits, QAPPs, SAPs, SOPs, or laboratory instructions.

LakeTech Learning Center · Field record

Recreational-Water Sampling and Authority Handoff Record

Template ID: recreational-water-sampling-and-authority-handoff-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: ESCALATE: responsible-authority direction required; no advisory or reopening decision implied
Reviewer attestation: Not recorded
Source guide: recreational-water-bacteria-monitoring-and-response

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, site, and authority

Use stable IDs. Keep personal contact details out of exports unless your program requires and protects them. Name the designated use and the authority responsible for advisory decisions.

Core record

Record ID · requiredNot recordedGenerated when you start a browser record; preserved on export and import.Project or parent record IDNot recordedCompleted by and role · requiredNot recordedSensitive data class: personal.Reviewer attestation recorded byNot recordedBrowser-entered reviewer details are not identity-verified and do not authenticate validation.Sensitive data class: personal.Reviewer attestation dateNot recordedWaterbody, beach, swim area, or site name and ID · requiredNot recordedSensitive data class: operational.Designated recreational use (for example primary contact, secondary contact, wading) · requiredNot recordedCounty, state, Tribal, or local jurisdiction · requiredNot recordedResponsible public-health or environmental authority for advisory decisions · requiredNot recordedSensitive data class: operational.Site coordinates, datum, accuracy, and sourceNot recordedSensitive data class: precise location.Access point, hazards, and representative area notesNot recordedSensitive data class: precise location.

2. Current advisory, restriction, and governing references

Record what is officially in effect and the procedure or criterion documents that govern sampling and response. Do not infer or declare a new public status here.

Core record

Current official advisory, restriction, or closure status and effective time · requiredNot recordedSensitive data class: operational.Advisory source reference: issuer, posting ID, URL, sign, or bulletinNot recordedSensitive data class: operational.Authority procedure, response plan, SAP, or SOP references with versions and effective dates · requiredNot recordedSensitive data class: operational.Criterion or BAV references: analyte, statistic, window, method, jurisdiction, and version · requiredNot recordedSensitive data class: operational.Sampling authorization: who directed collection, when, and under which plan elementNot recordedSensitive data class: operational.

3. Immediate safety and advisory gates

For every gate record Unknown, No, or Yes. Any Yes or unresolved Unknown can require stopping field work and contacting the responsible authority before sampling.

Core record

Reported human illness or exposure linked to the site · requiredNot recordedSensitive data class: incident sensitive.Reported pet, livestock, or wildlife illness or exposure · requiredNot recordedSensitive data class: incident sensitive.Active sewage release, spill, or suspected illicit discharge · requiredNot recordedVisible bloom, scum, discoloration, or suspicious surface film from safe distance · requiredNot recordedUnsafe shore, boat, current, lightning, ice, electrical, or entanglement condition · requiredNot recordedUnknown whether a current official advisory or restriction applies · requiredNot recordedEvidence IDs, observations, reporter contact path, authority direction, and hold resolutions for every gate · requiredNot recordedSensitive data class: incident sensitive.Stop-work or do-not-sample direction received and case referenceNot recordedSensitive data class: incident sensitive.

4. Freshwater routine sanitary observations

Record observable conditions from a safe distance. Observations support sampling decisions; they do not establish pathogen presence or absence.

Core record

Observation date and local timeNot recordedObservation UTC offset (for example -07:00)Not recordedWeather, rainfall in last 24-72 hours, and inflow context · requiredNot recordedWater level, stage, current, and turbidity or clarity from safe observation · requiredNot recordedWildlife presence: waterfowl, mammals, fish, strandings, or unusual behavior · requiredNot recordedBather load, beach use, and nearby activity · requiredNot recordedVisible outfalls, storm drains, tributary inflow, or drainage paths · requiredNot recordedSensitive data class: precise location.Odors, sheens, foam, debris, trash, or sewage indicators from safe distance · requiredNot recordedBloom or scum observations: extent, color, location, wind accumulation, and confidence · requiredNot recordedPhoto or video evidence IDs, time, direction, description, and original preserved · requiredNot recordedSensitive data class: operational.

5. Sampling plan and collection event

Collect only under current authority and laboratory direction. Confirm bottle, fraction, preservation, holding, and QC requirements before mobilizing.

Core record

Sampling plan, event ID, and authority approval reference · requiredNot recordedSensitive data class: operational.Station rows: ID/name, purpose, coordinates/datum, depth/zone, access, and replacement rule · requiredNot recordedSensitive data class: precise location.Collection start local date and time · requiredNot recordedCollection end local date and timeNot recordedCollection UTC offset (for example -07:00) · requiredNot recordedDepth, matrix zone, and sampling basis (for example ankle, knee, grab, integrated) · requiredNot recordedAnalyte or indicator, matrix, fraction, and intended decision use · requiredNot recordedSensitive data class: operational.Exact field and laboratory method, version, accreditation, and lab confirmation date · requiredNot recordedSensitive data class: operational.Container, volume, filtration, preservative, holding time, shipping, and temperature targets · requiredNot recordedSensitive data class: operational.Field QC rows: type, frequency, acceptance criteria, result, and corrective action · requiredNot recordedField reading rows: parameter, time, depth/reference, value, unit, instrument, and flag · requiredNot recordedSensitive data class: operational.

6. Sample IDs, custody, cooling, and laboratory receipt

A result is inseparable from sample identity, preservation, custody, and laboratory narrative.

Core record

Sample ID rows: field ID, label, matrix/fraction, station, depth, collection time/offset, collector · requiredNot recordedSensitive data class: operational.Custody rows: transfer time, from/to, seal/condition, signature or attestation, and exceptions · requiredNot recordedSensitive data class: operational.Cooler IDs, ice/packs, target and observed temperature log, and shipment carrier/tracking · requiredNot recordedSensitive data class: operational.Laboratory receipt, accession, rejection, partial acceptance, and narrative with case ID · requiredNot recordedSensitive data class: operational.Broken seal, warm sample, missing label, or other custody exceptions and authority directionNot recordedSensitive data class: incident sensitive.

7. Results, comparison, and authority handoff

Record laboratory results and handoff evidence. Comparison status documents project review; only the responsible authority issues or lifts public advisories.

Core record

Result rows: sample ID, exact analyte, matrix/fraction, and preparation · requiredNot recordedSensitive data class: operational.Analytical method, version, laboratory, analysis date, and accreditation context · requiredNot recordedSensitive data class: operational.Reported value, unit, significant figures, and dilution factor per result · requiredNot recordedQualifier, detection limit type/value/unit, censoring rule, and narrative per result · requiredNot recordedCriterion or BAV source, statistic, window, geomean/n-single rule, and applicability per result · requiredNot recordedSensitive data class: operational.Comparison status per result or decision set · requiredNot recordedComparison detail rows: result ID, criterion ID, statistic computed, window dates, and reviewer notesNot recordedSensitive data class: operational.Notification log: time, organization/person, information provided, direction, case number, next update · requiredNot recordedSensitive data class: incident sensitive.Authority-issued public status reference, posting, and effective time (if issued) · requiredNot recordedSensitive data class: operational.Unresolved QC, custody, missing results, or pending authority decisions · requiredNot recordedNext responsible person, action, review date, and follow-up sampling trigger · requiredNot recordedSensitive data class: personal.Handoff attestation recorded by (not identity-verified)Not recordedBrowser-entered reviewer details are not identity-verified and do not authenticate authority decisions.Sensitive data class: personal.