Lake Water-Quality Sampling Plan Worksheet

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: 2027-01-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 dispositionDocumentation incomplete: reviewer follow-up required

Stable record IDNot started

Full-record documentation0 of 15 required fields documented

Safety and authority boundary

This planning worksheet is not a substitute for a required QAPP, SAP, SOP, permit, current laboratory instructions, agency approval, or project hazard analysis. It cannot authorize boating, preservative handling, or entry into suspected HAB, spill, sewage, flood, or unsafe-ice conditions.

LakeTech Learning Center · Field record

Lake Water-Quality Sampling Plan Worksheet

Template ID: lake-sampling-plan-worksheet
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: Documentation incomplete: reviewer follow-up required
Reviewer attestation: Not recorded
Source guide: sampling-plan

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.

1. Plan control and governance

A field-ready plan needs current method, safety, custody, decision, and approval ownership, not only a list of analytes.

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 recordedPlan version, effective date, and next reviewNot recordedQAPP, SAP, SOP, permit, grant, or funder references and versionsNot recorded

2. Decision and data-quality objectives

Do not prefill a generic healthy range. Every threshold requires its source and exact applicability.

Core record

Problem, management question, intended decision/action, and decision owner · requiredNot recordedData users, target zone/time, designated uses/receptors, and use class (education, screening, trend, regulatory) · requiredNot recordedDecision-rule IDs: parameter, comparison, value/unit/duration/fraction/method, source/jurisdiction/use, confirmation, authority/actionNot recordedPrecision, bias, representativeness, completeness, comparability, sensitivity/range targets, rationale, assessment, owner, corrective actionNot recorded

3. Conceptual model, stations, depths, and schedule

State what each station and depth represents, and what it misses.

Core record

Sources, stressors, pathways, receptors, outcomes, alternative hypotheses, basin structure, inflows/outlets, variability · requiredNot recordedStation rows: ID/name/type, purpose, coordinates/datum, representative area, depth/stage, access, hazards, replacement rule · requiredNot recordedDepth rows by station: matrix/zone, exact depth or adaptive rule, reference/bottom offset, sample type/method, replicate, rationale · requiredNot recordedSchedule rows: station/depth group, season/frequency/time, measurable event trigger, mobilization, missed-event rule, team, lab calendar · requiredNot recorded

4. Methods, instruments, laboratory, and QA/QC

Confirm bottle, fraction, filtration, preservation, holding, shipping, and reporting details with the selected lab before mobilizing.

Core record

Parameter/method rows: analyte/matrix/fraction, method/version, unit/range/reporting limit, bottle/filtration/preservation/holding/shipping, accreditation, lab confirmation date · requiredNot recordedInstrument rows: asset/model/serial/sensor, project acceptance, calibration/verification, standards/expiry, frequency, maintenance, clock/settingsNot recordedSensitive data class: operational.QC rows: type, purpose, frequency, acceptance/source, calculation, review owner, corrective action · requiredNot recordedSample IDs, labels, seals, custody transfers, cooler targets, accession/rejection, tracking, retention/disposal · requiredNot recorded

5. Data, roles, safety, and readiness

Missing is different from not applicable; every N/A needs a reason.

Core record

Raw storage/backup, naming/timezone/units, dictionaries, flags/transitions, qualifiers, nondetect rule, corrections, validation/release/retention · requiredNot recordedRACI and backups for safety, field lead, calibration, custody, lab, validation, decision, and public communication · requiredNot recordedHazard-analysis ID, weather/boat/ice/HAB/spill/electrical/preservative controls, check-in, emergency contacts, stop-work authority, training/PPE · requiredNot recordedUnresolved blockers, approvals/signatures, attachment inventory, revision/change summary, superseded-copy handling · requiredNot recorded