Lake and Reservoir Source-Water Protection, Monitoring, and Utility Handoff 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 system identity, contamination, tap-safety, utility-action, authorization, or effectiveness conclusion implied

Stable record IDNot started

Full-record documentation0 of 36 required fields documented

Independent lake source water protection v1 states

immediate_concern_state
supplying_system_identity_state
authority_handoff_state
water_evidence_class_state
security_access_state
assessment_version_state
protection_area_delineation_state
hydrologic_intake_model_state
potential_source_inventory_state
observed_condition_state
susceptibility_state
public_data_provenance_state
monitoring_design_state
sampling_authorization_state
custody_laboratory_state
source_result_validation_state
utility_operational_decision_state
primacy_public_health_status_state
protection_authorization_state
implementation_maintenance_state
effectiveness_state
public_release_correction_state

Immediate concern, supplying-system identity, source/raw/finished/tap evidence, security, assessment, delineation, susceptibility, public-data provenance, monitoring, sampling, custody, validation, utility operations, primacy/public-health status, authorization, implementation, maintenance, effectiveness, and public correction remain separate attributable decisions.

Safety and authority boundary

This record does not determine tap safety; identify a contaminant, exposure, health risk, violation, source, cause, or culpability; issue or lift an advisory; authorize access, sampling, containment, cleanup, construction, intake operation, treatment change, customer action, or public release; or replace a utility emergency-response plan. Source, raw, treated, finished, distribution, and tap evidence remain separate. Observation-only, existing-data-only, no-sample, monitoring-only, and no-action branches are valid. Potential source is not release; proximity is not hydrologic connection; susceptibility is not contamination; portal silence is not absence or compliance; a non-detect is not absence; ambient criteria are not MCLs; CWA impairment is not an SDWA violation; funding, design, permit application, and plan are not authorization; implementation is not effectiveness. Current utility, primacy, Tribal, environmental, public-health, emergency, landowner, laboratory, safety, security, privacy, access, and public-communication authority controls. Generalize or suppress precise intake, infrastructure, customer, response, and access details in public exports.

LakeTech Learning Center · Field record

Lake and Reservoir Source-Water Protection, Monitoring, and Utility Handoff Record

Template ID: lake-reservoir-source-water-protection-and-utility-handoff-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: MORE EVIDENCE: no system identity, contamination, tap-safety, utility-action, authorization, or effectiveness conclusion implied
Reviewer attestation: Not recorded
Source guide: lake-reservoir-source-water-protection-and-contamination-preparedness-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 concern, system, and authority

Protect people first. Preserve an observation-only, existing-data-only, no-sample, or emergency/utility handoff without converting the record into tap-safety advice, intake operations, or authority action.

Core record

Stable record ID · requiredNot recordedProgram, event, utility, or parent record IDNot recordedRecord date · requiredNot recordedCompleted by and role · requiredNot recordedSensitive data class: personal.Lake or reservoir, generalized location, source use, jurisdictions, access status, and protected infrastructure class · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Immediate concern and emergency-routing state · requiredNot recordedObservable condition, exposure or service concern, safety action, utility/emergency recipient, case ID, direction, time with offset, and paused scopeNot recordedSensitive data class: incident sensitive.Supplying-system identity state · requiredNot recordedSensitive data class: operational.System name and ID, intake purpose, utility or owner, service scope, current source, access date, operating-status limitation, and correction history · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Utility and responsible-authority handoff state · requiredNot recordedCurrent utility, primacy, Tribal, environmental, public-health, emergency, landowner, laboratory, and public-communication owners; sources, dates, channels, cases, instructions, and open handoffs · requiredNot recordedSensitive data class: operational.

2. Classify water evidence, security, and assessment version

Source, raw, treated, finished, distribution, and tap-water records are not interchangeable. Protect precise intake, infrastructure, customer, response, and access information.

Core record

Source-to-tap water-evidence class state · requiredNot recordedSensitive data class: incident sensitive.Evidence IDs, water state, exact source/time/method, collection or record owner, intended use, limits, and prohibited source-to-tap inferences · requiredNot recordedSensitive data class: incident sensitive.Security, privacy, and access state · requiredNot recordedClassification owner, exact restricted fields, authorized users, access basis, retention, public generalization, review date, and incident/security route · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Source-water assessment version state · requiredNot recordedAssessment title, publisher, version, publication and access dates, supplying system and source scope, methods, limitations, protected annexes, updates, and supersession · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.

3. Delineation, hydrology, potential sources, observation, and susceptibility

Potential source, mapped facility, proximity, hydrologic pathway, observed release, detection, susceptibility, causation, violation, and culpability remain separate evidence states.

Core record

Protection-area delineation state · requiredNot recordedBoundary version, method, source, intake and tributary scope, included/excluded areas, jurisdiction, uncertainty, reviewer, and security classificationNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Hydrologic and intake-zone model state · requiredNot recordedLake, tributary, watershed, flow, mixing, depth, operating-state, intake-zone, travel-time, seasonal/event assumptions, calibration, sensitivity, uncertainty, and reviewerNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Potential contaminant-source inventory state · requiredNot recordedCategory, record/source ID, map and non-map evidence, current-operation status, owner/contact restrictions, location generalization, pathway hypothesis, data gaps, corrections, and prohibited inferenceNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Observed release or condition evidence state · requiredNot recordedDate/time/offset, generalized location, observable descriptors, weather/hydrology, photos, method/effort, observer, authority case, uncertainty, and correctionsNot recordedSensitive data class: incident sensitive.Source-pathway-receptor susceptibility state · requiredNot recordedSource, pathway, receptor/intake, controls, consequence, scoring/ranking method, evidence, unknowns, sensitivity analysis, decision owner, prohibited inferences, and review date · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.

4. Public-data provenance, monitoring, sampling authority, custody, and validation

Existing-data-only and no-sample branches are valid. A design, QAPP, monitoring plan, grant, access request, or permit application does not itself authorize sampling.

Core record

Public-data provenance state · requiredNot recordedPortal/publisher, dataset and record IDs, query, filters, coordinates/generalization, date range, units/method, qualifiers, access date, duplicates, gaps, version, and permitted useNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Source-water monitoring-design state · requiredNot recordedDecision, target groups/indicators, baseline/sentinel/event/tributary/lake/intake roles, stations, depths, timing, operating states, methods, limits, QA, security, handoffs, and prohibited inferences · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Sampling authorization and safety state · requiredNot recordedDecision owner, access, utility/landowner/Tribal/agency permission, safety plan, team qualification, method, locations, material, dates, restrictions, waste/decontamination, and stop criteriaNot recordedSensitive data class: operational.Custody and laboratory-receipt state · requiredNot recordedSample IDs, collector, method, containers, preservation, seals, transfers, times/offsets, conditions, laboratory, receipt, requested methods/fractions/units/limits, deviations, and dispositionNot recordedSensitive data class: operational.Source-water result-validation state · requiredNot recordedResult IDs, water-evidence class, laboratory/method/fraction/unit, reporting limits, blanks/QC, qualifiers, validation owner/date, comparison source, uncertainty, permitted use, and prohibited tap-safety inferenceNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.

5. Utility, primacy/public-health, protection authorization, and implementation

LakeTech does not operate an intake, direct treatment, or issue customer advice. Funding, design, recommendation, application, permit, and authorization remain distinct from implementation and maintenance.

Core record

Utility operational-decision state · requiredNot recordedResponsible utility owner, decision category without exposing vulnerabilities, evidence considered, exact scope/time, authority basis, limitations, linked notice, revision, and closureNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Primacy-agency and public-health status state · requiredNot recordedIssuer, authority and notice/determination ID, scope, effective time, evidence basis, customer direction source, limitations, revision, withdrawal, and correction contactNot recordedSensitive data class: health sensitive. Restrict household-associated results, exposure or illness details, and health-authority case references.Protection-alternative and authorization state · requiredNot recordedObjectives, alternatives including no action, eligibility, feasibility, uncertainty, adverse effects, funding/procurement, access, design, permits, exact authorization, owner, conditions, dates, and stop criteria · requiredNot recordedSensitive data class: operational.Implementation, operation, and maintenance state · requiredNot recordedAuthorization link, implementer, exact scope/time, as-designed/as-built evidence, acceptance, deviations, operation, inspection, maintenance, lifecycle resources, failure, adverse effects, and corrective actionNot recordedSensitive data class: operational.

6. Effectiveness, secure public release, correction, and revision

Implementation and one favorable season are not effectiveness. Public statements must be attributable to the responsible utility or authority, security-screened, bounded, versioned, and correctable.

Core record

Protection-effectiveness evidence state · requiredNot recordedMechanism, implementation fidelity, maintenance, source/pathway/service/resilience endpoints, baseline/comparator, timing, detectability, confounders, adverse effects, uncertainty, reviewer, and next decision · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Public release, correction, and revision state · requiredNot recordedIssuer/owner, audience, generalized location, water-evidence class, status and action scope, excluded infrastructure/customer/response details, version, effective time, limitations, correction contact, supersession, and next review · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Qualified reviewer attestation: role, organization, evidence reviewed, bounded conclusions, limitations, conflicts, and dateNot recordedSensitive data class: personal.