Lake Water Sample Collection, Handling, and Custody 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 dispositionSTOP WORK: field safety or authorization prerequisite unresolved

Stable record IDNot started

Full-record documentation0 of 58 required fields documented

Independent sample workflow v1 states

field Safety: not assessed
collection: not started
custody: not started
lab Receipt: not received
validation: not started
release: not authorized

Laboratory receipt or acceptance never implies validation. Validation never implies public release.

Safety and authority boundary

This record does not authorize sampling, boating, wading, ice travel, or entry into suspected contaminated water. Do not handle chemical preservatives without an approved method, current SDS, training, and PPE. It does not prove representativeness, laboratory acceptance, data validity, regulatory compliance, safety, or public release. Current QAPP, SAP, SOP, laboratory, method, and authority requirements control every decision.

LakeTech Learning Center · Field record

Lake Water Sample Collection, Handling, and Custody Record

Template ID: lake-water-sample-collection-and-custody-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: STOP WORK: field safety or authorization prerequisite unresolved
Reviewer attestation: Not recorded
Source guide: lake-water-sample-collection-handling-and-custody

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 sampling event

Use stable IDs. Keep personal contact details out of exports unless your program requires and protects them. Reference the governing plan and receiving laboratory before mobilizing.

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, station ID/name/type, and representative area · requiredNot recordedSensitive data class: operational.Coordinates, datum, accuracy, and sourceNot recordedSensitive data class: precise location.Sampling event ID and parent plan or work order reference · requiredNot recordedSensitive data class: operational.Collection start local date and time · requiredNot recordedCollection end local date and timeNot recordedCollection UTC offset (for example -07:00) · requiredNot recordedIntended use, decision, audience, and fitness-for-use scope · requiredNot recordedGoverning QAPP, SAP, SOP, permit, method, and laboratory references with versions · requiredNot recordedSensitive data class: operational.Receiving laboratory name, accreditation context, and contract or case reference · requiredNot recordedSensitive data class: operational.Laboratory coordination reference ID or role (not direct contact credentials)Not recordedSensitive data class: operational.

2. Safety and authorization gates

For every gate record Unknown - HOLD, No - HOLD, or Yes. Any No - HOLD or unresolved Unknown - HOLD requires stopping field work until the responsible authority records resolution in safety gate evidence.

Core record

Current approved sampling plan, SAP element, and authority direction on site or accessible · requiredNot recordedWeather, lightning, and shore access conditions acceptable for the planned work · requiredNot recordedBoat, PFD, buddy, wading, and ice controls satisfied as applicable · requiredNot recordedPreservative or reagent handling only under approved method, current SDS, training, and PPE · requiredNot recordedNo entry into suspected HAB, spill, sewage, or contaminated water without authority direction · requiredNot recordedCheck-in, communications, and emergency escalation path confirmed · requiredNot recordedDecontamination, waste handling, and cross-contamination controls understood · requiredNot recordedEvidence IDs, verifier, hold reasons, authority direction, and 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.

3. Method readiness and mobilization

Confirm analyte, matrix, fraction, container, filtration, preservation, holding, shipping, and QC design with the selected laboratory before collection. This form provides no universal container, preservative, temperature, or hold-time values.

Core record

Controlled method matrix reference ID and version · requiredNot recordedSensitive data class: operational.Approved method matrix present and current for this event · requiredNot recordedSensitive data class: operational.Laboratory coordination: confirmation date, case ID, shipping window, and special instructions · requiredNot recordedSensitive data class: operational.Kit and consumable inventory rows: item ID, lot, expiry, count, and reconciliation status · requiredNot recordedSensitive data class: operational.Field kit inventory reconciled against the controlled method matrix · requiredNot recordedSensitive data class: operational.Analyte/method rows: analyte, matrix/fraction, method/version, unit/range, container/filtration/preservation/holding/shipping per controlled matrix · requiredNot recordedSensitive data class: operational.QC design rows: type, purpose, frequency, acceptance source, calculation, and corrective action owner · requiredNot recordedDelivery deadline basis: controlled shipping cutoff, analysis window, and mobilization trigger from governing plan · requiredNot recordedSensitive data class: operational.

4. Station, depth, and collection

Record what was collected, where, when, and under which method. Preserve deviations and field measurements with the sample identity log.

Core record

Station/depth/time rows: station ID, depth or zone, matrix, start/end time with offset, stage, and access notes · requiredNot recordedSensitive data class: precise location.Sample identity rows: field ID, label, matrix/fraction, station, depth/zone, collector role ID, and duplicate or parent link · requiredNot recordedSensitive data class: operational.Sample labels, field log, and plan reconciled without mismatch or duplicate identity · requiredNot recordedSensitive data class: operational.Collection method, equipment, rinse sequence, and representativeness basis per sample group · requiredNot recordedSensitive data class: operational.Represented water mass, zone, or event segment and known limitations · requiredNot recordedSensitive data class: operational.Sample sequence rows: order ID, rationale, contamination-control step, and completed time · requiredNot recordedSensitive data class: operational.Field measurement rows: parameter, time, depth/reference, value, unit, instrument ID, and flag · requiredNot recordedSensitive data class: operational.Collection deviations, missed depths, equipment failures, and authority direction; explicitly record none when applicable · requiredNot recordedSensitive data class: incident sensitive.

5. Field processing, preservation, and QC

Document filtration, preservation, processing times, QC samples, contamination controls, and cooling start under the controlled method. Do not assume universal preservation or temperature targets.

Core record

Field processing completed under the controlled method or documented as not required · requiredNot recordedSensitive data class: operational.Filtration/preservation rows: sample ID, step, equipment, reagent/lot, operator role ID, time with offset, and controlled-method reference; document not required when applicable · requiredNot recordedSensitive data class: operational.Processing time rows: sample ID, step, start/end time with offset, and elapsed basis; document not required when applicable · requiredNot recordedSensitive data class: operational.QC sample rows: QC ID, type, parent sample, station, matrix, collection/processing time, and purpose; document none when the controlled plan requires none · requiredNot recordedSensitive data class: operational.Contamination control rows: blank, duplicate, equipment rinse, glove change, and sequence control evidence · requiredNot recordedCooling start evidence: sample or cooler ID, start time with offset, method reference, and observation basis; document not required when applicable · requiredNot recordedSensitive data class: operational.Cooling and transport condition evidence recorded per controlled plan · requiredNot recordedSensitive data class: operational.Processing deviations, missed QC, preservative issues, and corrective action; explicitly record none when applicable · requiredNot recordedSensitive data class: incident sensitive.

6. Custody and transport

A result is inseparable from sample identity and custody continuity. Record every transfer, seal, cooler package, and shipment tracking reference.

Core record

Custody transfer rows: transfer ID, time with offset, from/to stable role IDs, sample or cooler IDs, seal/condition, evidence reference, and exceptions · requiredNot recordedSensitive data class: operational.Custody continuity documented through each handoff · requiredNot recordedSensitive data class: operational.Cooler and package rows: cooler ID, contents crosswalk, seal ID, condition, and packing method reference · requiredNot recordedSensitive data class: operational.Shipment rows: carrier or hand-delivery method, tracking ID when used, departure/arrival time with offset, and chain-of-custody form reference · requiredNot recordedSensitive data class: operational.Transport deviations: delayed shipment, seal issue, condition outside plan, and authority direction; explicitly record none when applicable · requiredNot recordedSensitive data class: incident sensitive.

7. Laboratory receipt and accession

Record receipt condition, temperature evidence, accepted and rejected containers, accession crosswalk, and exceptions without inferring data validity.

Core record

Laboratory receipt local date and timeNot recordedSensitive data class: operational.Laboratory receipt UTC offsetNot recordedSensitive data class: operational.Accession crosswalk rows: field sample ID, container ID, lab accession ID, matrix/fraction, and match statusNot recordedSensitive data class: operational.Receipt condition rows: container ID, seal, label, volume, turbidity, damage, and narrativeNot recordedSensitive data class: operational.Receipt condition or temperature evidence rows: evidence ID, measurement basis, time, and controlled-method reference; document not required when applicableNot recordedSensitive data class: operational.Accepted and rejected container rows: container ID, disposition, reason code, and authority or lab case referenceNot recordedSensitive data class: operational.Receipt exception log: exception ID, affected IDs, finding, lab narrative, and resolution owner; explicitly record none when applicableNot recordedSensitive data class: incident sensitive.Laboratory notification log: time, organization/role, information provided, direction, and case referenceNot recordedSensitive data class: operational.

8. Result package and validation handoff

Link result packages, laboratory narrative, qualifiers, QC results, and amendment lineage to field and accession IDs. This section does not validate or release data.

Core record

Result package reference ID, deliverable type, and receipt dateNot recordedSensitive data class: operational.Laboratory narrative, case notes, reanalysis, and dilution summaryNot recordedSensitive data class: operational.Result crosswalk rows: accession ID, analyte, reported value, unit, method, analysis date, and field sample linkNot recordedSensitive data class: operational.Method, unit, and qualifier review rows: result ID, qualifier, limit type, detection condition, and review noteNot recordedQC result link rows: QC sample ID, QC type, result ID, acceptance source, and affected sample IDsNot recordedAmendment and version lineage: prior package ID, change cause, affected records, and superseded markersNot recordedSensitive data class: operational.Data validation owner, review procedure reference, and due dateNot recordedSensitive data class: personal.

9. Workflow disposition and attestation

Disposition documents field and custody evidence; it does not validate data, prove compliance, or authorize public release.

Core record

Collection completion state · requiredNot recordedSensitive data class: operational.Collection scope reference: affected sample and container IDs · requiredNot recordedSensitive data class: operational.Custody continuity state · requiredNot recordedSensitive data class: operational.Custody scope reference: affected sample, container, cooler, and transfer IDs · requiredNot recordedSensitive data class: operational.Laboratory receipt state · requiredNot recordedSensitive data class: operational.Laboratory receipt decision or accession referenceNot recordedRequired when a receipt or acceptance state is recorded.Sensitive data class: operational.Laboratory receipt scope reference: accepted, pending, affected, or rejected IDsNot recordedRequired when a receipt or acceptance state is recorded.Sensitive data class: operational.Linked data-validation state · requiredNot recordedSensitive data class: operational.Validation decision referenceNot recordedSensitive data class: operational.Validation scope and named-use referenceNot recordedSensitive data class: operational.Linked public-release state · requiredNot recordedSensitive data class: operational.Release authority and decision referenceNot recordedSensitive data class: personal.Release scope and named-use referenceNot recordedSensitive data class: operational.Public product, dataset, report, or withdrawal referenceNot recordedSensitive data class: operational.Disposition scope: samples, containers, QC, intervals, and restrictions attached · requiredNot recordedSensitive data class: operational.Unresolved items: ID, owner, due date, impact, and evidence link; explicitly record none when applicable · requiredNot recordedNext responsible role, action, and due time · requiredNot recordedSensitive data class: personal.Collection attestation: name, role, date, and statement of collection evidence completed (not identity-verified) · requiredNot recordedBrowser-entered attestation is not identity-verified and does not authenticate collection approval.Sensitive data class: personal.Custody attestation: name, role, date, and statement of custody continuity (not identity-verified) · requiredNot recordedBrowser-entered attestation is not identity-verified and does not authenticate custody approval.Sensitive data class: personal.Reviewer attestation: name, role, date, and basis reviewed (not identity-verified)Not recordedBrowser-entered reviewer details are not identity-verified and do not authenticate validation.Sensitive data class: personal.