Lake Sample to Result: Collection, Custody, Laboratory, Validation, and Release
Carry a lake-water sample from a decision-linked plan through crew readiness, collection, processing, custody, laboratory receipt, result reconciliation, validation, and attributable release without collapsing those states.
- For
- Lake and watershed managers, monitoring coordinators, field crews, laboratory liaisons, consultants, utilities, municipalities, community programs, data reviewers, and release authorities
- Field stops
- 9
- Reading + practice
- About 300 minutes
- Review status
- Controlled preview
Finish with a field-ready draft, not a badge.
A controlled sample package whose collection, custody, laboratory receipt, validation, and release histories remain separately attributable, reviewable, and bounded to the named use.
Bring the current QAPP or project plan, SAP and SOP versions, hazard controls, station/depth design, receiving-laboratory instructions and contract, controlled analyte-method-container matrix, field and laboratory roles, and intended-use decision rules.
Field route
Use an authored handoff; this is not an automatic recommendation or approval.
Open Lake Decision Packet Carry the packet into the complete custody, validation, authority, and release workflow.
Open Water-Quality Data Validation and Release Checklist Document attributable states in Water-Quality Data Validation and Release Checklist before leaving Lake Sample to Result: Collection, Custody, Laboratory, Validation, and Release.
Open Lake Water Sample Collection, Handling, and Custody Record Document attributable states in Lake Water Sample Collection, Handling, and Custody Record before leaving Lake Sample to Result: Collection, Custody, Laboratory, Validation, and Release.
Shared route boundary
Does not interpret, compare, convert, threshold, rank, diagnose, establish cause, recommend monitoring or treatment, determine safety or compliance, authenticate identity, make an authority decision, or authorize action.
Loading local progress…
Decide · 30 minutes Design the decision-linked sample program
Trace the intended decision backward through analyte, fraction, station, depth, timing, method, field and laboratory QC, custody, acceptance, review, and ownership.
Field exerciseBuild one controlled row for each requested result, naming the represented water mass, exact intended use, method package, evidence requirements, decision owner, and what the result cannot represent.
CheckpointCould another trained team identify every required method, sample, QC record, handoff, review, and authority decision without inventing a value?
Practice · 32 minutes Document task-specific crew readiness
Observe the exact collection, labeling, processing, contamination-control, preservation, custody, and exception-escalation task scope without implying credentialing.
Field exerciseRun a return demonstration with one labeling mismatch, one processing deviation, and one stop-work condition; preserve prompts, limits, retraining needs, and reassessment triggers.
CheckpointAre observed proficiency, field authorization, supervision, and future task scope represented as different decisions?
Measure · 24 minutes Match equipment and kits to the controlled method
Select samplers, contact materials, containers, filters, preservatives, coolers, and custody supplies from the exact matrix and receiving-laboratory instructions.
Field exerciseReconcile a practice kit against one controlled method matrix, recording item, treatment, lot, expiry, count, analyte compatibility, hazard control, and replacement action.
CheckpointDoes every item have a method-defined purpose, and would a substituted bottle, tube, filter, or reagent trigger controlled review?
Measure · 38 minutes Collect, process, and transfer without losing identity
Preserve representativeness, exact station/depth/time, contamination controls, sample identity, processing actions, cooling evidence, exceptions, and custody continuity.
Field exerciseWrite and execute a tabletop sequence for one surface grab, one depth-specific sample, one project-required blank, and one duplicate, including every label, clock, processing, evidence, and handoff transition.
CheckpointCan the receiving laboratory reconstruct what each container represents, what touched it, what changed it, when each step occurred, and where every deviation was recorded?
Document · 45 minutes Build the sample lifecycle record
Keep safety, collection completion, custody continuity, laboratory receipt, validation, and release as six independent states with evidence and affected scope.
Field exerciseComplete an anonymized event with a controlled open custody state, a later partial laboratory acceptance, a qualified named-use validation, and no public-release authorization.
CheckpointDo later receipt or validation decisions preserve, not overwrite, the earlier collection, custody, exception, and affected-scope history?
Document · 40 minutes Reconcile laboratory receipt, results, and amendments
Coordinate receipt and accession, resolve exceptions, reconcile reports and electronic rows, retain qualifiers and QC context, and preserve original and amended deliverables.
Field exerciseCrosswalk field sample IDs, container IDs, accession IDs, requested analyses, reported result IDs, units, qualifiers, limits, batch QC, narrative findings, and amendment lineage for a practice package.
CheckpointAre receipt, acceptance, analytical reporting, accreditation, verification, validation, release, and amendment represented as distinct attributable states?
Decide · 34 minutes Validate fitness for the named use
Verify completeness, evaluate method and QC evidence, preserve qualifiers and censoring, bound affected records, and issue a named-use validation decision.
Field exerciseReview a package containing a blank finding, a duplicate difference, a receipt exception, a qualified laboratory result, and one superseded deliverable without silently deleting any record.
CheckpointDoes the validation decision state the exact data version, named use, affected scope, limitations, open findings, reviewer, and next action?
Document · 36 minutes Record release as a separate authority decision
Connect a completed validation package to an attributable release authority, approved product, scope, user-facing limitations, revision history, and withdrawal path.
Field exerciseCreate one held release and one named-use release from the same validated package, then supersede the second while preserving the original public product and authority references.
CheckpointCan a user distinguish validated data from the exact version and scope that an authority allowed to be published or used?
Practice · 24 minutes Assign safe community and partner roles
Match observation, collection, custody, laboratory coordination, validation, and communication tasks to trained roles and responsible authorities.
Field exerciseClassify each task in the sample lifecycle as community-observable, supervised field work, laboratory-controlled, qualified-review, or authority-only, then assign backups and escalation triggers.
CheckpointCould staff turnover or a volunteer handoff occur without transferring laboratory, validation, public-health, or release authority accidentally?