Lake Sample-to-Laboratory-to-Result Workflow
Manage lake-water samples from laboratory coordination and kit control through collection, custody, cooler delivery, receipt exceptions, result reconciliation, qualification, validation, release, and amendment lineage.
What to do first
A defensible sample result begins before a bottle is ordered and remains controlled after the laboratory reports it. Confirm the decision, exact analyte and fraction, preparation and analytical methods, containers, processing, preservation, holding, delivery, quality controls, reporting limits, deliverables, and acceptance rules with the project and receiving laboratory. Inventory the kit; preserve unique sample identity and custody; document cooler and handoff evidence; reconcile laboratory receipt exceptions immediately; compare every report and electronic row with the field plan and accession; retain units, qualifiers, detection conditions, limits, batch QC, and narrative; and keep field completeness, laboratory acceptance, data validation, public release, and later amendments as separate attributable decisions.
- Coordinate the project and receiving laboratory before kits, labels, couriers, or sampling schedules are committed
- Control the analyte-method-container-preservation-holding matrix without relying on a generic bottle chart
- Preserve sample identity, custody, cooler, delivery, receipt, and exception evidence across every handoff
- Reconcile reports and electronic data deliverables with field, accession, method, batch, qualifier, and narrative records
- Interpret blanks, duplicates, limits, censoring, and laboratory qualifiers only under the applicable project and method rules
- Keep field completeness, laboratory acceptance, validation, release, and public or regulatory decisions distinct
- Retain original and amended deliverables with complete version lineage and downstream impact review
Use the versioned field record.
Use this guide inside a field curriculum.
1. Define ownership and decision states before sampling
A bottle can be field-complete, accepted by a laboratory, analytically reported, and still not be validated or releasable.
Name the project manager, field lead, laboratory liaison, sample custodian, receiving-laboratory contact, data verifier, validator, release authority, and public or regulatory decision owner. Record backups and after-hours contacts where the method, courier window, holding requirement, or decision consequence makes delay material.
Publish a controlled state vocabulary and entry evidence. Do not let received, analyzed, reported, accredited, validated, approved, and released collapse into a single green status. Each transition needs an actor, date and time, evidence, scope, limitations, and any next action.
| State or decision | Question answered | Does not establish |
|---|---|---|
| Field documentation complete | Were required field, identity, processing, custody, and deviation records completed? | Laboratory acceptance, analytical validity, or fitness for use |
| Laboratory received/accessioned | Did the laboratory receive and log the submitted containers and condition? | That every requirement was met or every requested analysis will proceed |
| Laboratory accepted, qualified, or rejected | What receipt or analytical disposition did the laboratory assign? | Project validation, regulatory acceptance, or public release |
| Verified/validated for a named use | Is the package complete, and what limitations affect usability for that decision? | Fitness for every later use or authority to publish |
| Released | Which version may be used or published, by whom, for what purpose? | A guarantee that the conclusion is permanent or universally applicable |
2. Pre-coordinate with the laboratory that will receive the samples
Method capability, logistics, and decision timing must agree before the field event is released.
- Project purpose, intended use, decision timing, matrix, expected range, and required sensitivity communicated
- Laboratory organization, location, project contact, after-hours contact, and receiving hours confirmed
- Preparation and analytical method identifiers and versions accepted for each analyte or target
- Current accreditation or certification scope, when required, checked for organization, location, matrix, analyte, and method
- Bottle kit, field processing, preservative, shipping, holding, custody, and receipt instructions received in controlled form
- Sample count, QC count, volume, schedule, turnaround, rush conditions, and capacity accepted
- Reporting limits, units, qualifiers, case narrative, signed report, electronic deliverable, and data dictionary specified
- Receipt-exception, resampling, reanalysis, subcontracting, amendment, notification, and escalation procedures assigned
- Courier cutoff, weekend/holiday closure, weather contingency, and missed-delivery response confirmed
3. Issue one controlled analyte-method-container-handling matrix
The analyte name alone does not define a sample or its acceptable handling.
Give the matrix a version, effective date, approver, laboratory confirmation date, and change history. Link every bottle and requested result to one row or controlled method package. If the laboratory changes a kit, method, location, reporting limit, preservative, holding instruction, or deliverable, stop and assess the plan rather than silently updating a field cheat sheet.
| Control group | Fields to lock | Evidence source |
|---|---|---|
| Identity and use | Analyte/target, matrix, whole/filtered/dissolved/total or other fraction, intended use, project requirement | Approved project plan and decision rule |
| Method | Field processing, preparation method, analytical method/version, laboratory/location, subcontracting rule | Approved method, contract, and laboratory confirmation |
| Container and volume | Material, treatment, count, minimum volume, headspace, fill, cap, sterilization or cleaning requirement | Exact method and receiving-laboratory instruction |
| Processing and preservation | Homogenization, filtration, filter type/lot, timing, preservative identity/lot/addition, storage and light controls | Exact method, project SOP, hazard plan, and laboratory instruction |
| Time and transport | Holding-time start/end definition, required temperature or condition, shipment mode, delivery deadline, receipt evidence | Applicable method/program requirement and laboratory schedule |
| Quality and reporting | Field QC, laboratory QC, project acceptance criteria, units, limit types, required reporting limit, qualifiers and deliverables | QAPP, analytical method, contract, and electronic-data specification |
4. Receive and inventory the kit before the field day
Kit custody and suitability begin when supplies arrive, not when the first bottle is filled.
Do not substitute a bottle, cap, filter, preservative, cooler configuration, or temperature device because it appears equivalent. Record the question and obtain controlled project and laboratory direction. Preserve the original kit discrepancy and resolution evidence.
- Kit or shipment ID, sender, receiving person, arrival date/time, condition, and controlled instruction version recorded
- Bottle types, sizes, treatments, caps, labels, preservatives, filters, blanks, custody forms, seals, coolers, and shipping materials reconciled with the matrix
- Bottle and preservative lot, expiration, integrity, pre-preserved status, storage, and hazard information recorded when required
- Sterile, analyte-clean, pre-preserved, blank, and ordinary containers remain distinguishable and protected
- Temperature devices or laboratory-supplied temperature blanks identified and conditioned under the laboratory instruction
- Sample IDs, bottle labels, analysis requests, event forms, and custody records cross-checked before packing
- Shortages, damage, leakage, broken seals, expired materials, unexpected substitutions, and excess bottles quarantined or resolved with the laboratory
- Cooler capacity, segregation, absorbent/containment, seal locations, shipping label, courier plan, and backup delivery checked
5. Preserve unique sample identity and custody from collection onward
A plausible analytical value cannot repair an ambiguous or conflicting sample identity.
Preassign stable event and sample IDs under a controlled naming rule. Never reuse an ID after a missed, broken, or canceled sample; retain its status and reason. Link every container to project, event, station, actual location and depth/reference, matrix/fraction, collection start and end time with UTC offset, collector, requested analyses, field-processing record, and parent QC relationship.
At each transfer, record who relinquished and received custody, organizations, date/time and offset, container and cooler count, seal condition and IDs, requested analysis or custody record version, transfer method, and exceptions. A courier tracking scan supplements but does not silently replace the project custody record unless the approved procedure defines that relationship.
- Label and field record agree before the container leaves the collector
- Actual collection details replace planned values without erasing the plan
- Uncollected, insufficient, broken, spilled, resampled, duplicate, blank, and extra samples have explicit states
- Blind QC identity is protected through the controlled crosswalk while custody remains traceable
- Corrections retain original entry, corrected value, reason, actor, date/time, and reviewer
- Every custody gap or conflicting time becomes a visible exception with an owner
6. Build cooler, seal, temperature, and delivery evidence as one record
Cold packs and a tracking number are not complete proof of sample condition or timely delivery.
Close the event inventory
Reconcile sample IDs, bottle counts, analyses, field processing, preservatives, QC, exceptions, custody pages, and laboratory notification before packing. Preserve missing or compromised items rather than deleting them from the request.
Package under the controlled instruction
Apply required segregation, upright placement, containment, absorbent material, protection from breakage or immersion, cooling or other condition control, temperature device placement, and dangerous-goods or preservative handling.
Seal and release custody
Record cooler ID, seal IDs and placement, packed time, packer, condition, custody record, destination, service level, courier or driver, tracking, expected delivery, and laboratory notification.
Monitor and escalate delivery
Track delay, misroute, damage, failed delivery, weather, and weekend or holiday risk against the method-controlled window. Notify the laboratory and project owner while response options still exist; do not alter collection time or holding evidence.
7. Reconcile laboratory receipt and accession exceptions immediately
The laboratory receipt record is a new evidence layer, not a replacement for the field and custody record.
Do not resolve a receipt conflict by choosing whichever timestamp or bottle count makes the sample acceptable. Preserve both records, investigate the source, and document the laboratory and project decisions separately. A laboratory may proceed with analysis while the project keeps usability pending; conversely, a complete field sheet does not compel laboratory acceptance.
- Laboratory, location, accession or work-order ID, receiver, and receipt date/time/offset captured
- Courier/tracking, cooler and seal IDs, seal condition, custody form, and container counts reconciled
- Laboratory temperature method, device or blank ID, observed result, target source, and qualification recorded when applicable
- Bottle identity, material, volume, headspace, preservation, breakage, leakage, contamination, and sample sufficiency exceptions recorded
- Collection-to-receipt and collection-to-preparation/analysis timing assessed under the exact method-controlled definition
- Requested and logged analytes, methods, fractions, turnaround, reporting limits, and subcontracted work compared
- Accepted, accepted with exception, on hold, canceled, rejected, resample, or other laboratory disposition retained per sample/analysis
- Project notification, laboratory contact, time, direction, corrective action, and unresolved impact recorded
8. Reconcile the signed report, case narrative, and electronic data deliverable
A PDF total and an EDD row count can agree while identities, methods, units, or qualifiers conflict.
Freeze the original package before importing, renaming fields, converting units, deduplicating rows, or calculating summaries. Store normalized and derived data separately with source field, original value and unit, transformation rule/version, actor, and date.
- Project, laboratory, location, accession, report ID, report status, issue date, and deliverable version identified
- Client sample ID, laboratory sample ID, parent/child and QC relationships, collection and receipt records cross-walked
- Requested versus reported analytes, matrix/fraction, preparation and analytical methods, dates, laboratory and subcontractor reconciled
- Result, unit, detection condition, qualifier, limit types and values, dilution, basis, significant digits, and comments retained as delivered
- Batch, method QC, field QC, narrative exception, reanalysis, re-extraction, rerun, confirmation, and canceled analysis linked to affected results
- EDD schema/data dictionary, row counts, unique keys, required fields, encodings, time zones, controlled vocabularies, and referential integrity checked
- Signed report, narrative, EDD, attachments, transmittal, and checksum or preservation evidence stored together
- Every discrepancy opened as a finding; no PDF or EDD is silently declared authoritative without the contract and laboratory response
9. Preserve units, qualifiers, detection conditions, and limits without manufacturing certainty
A nondetect is a method-defined censored observation, not zero and not a license to invent a substitute value.
If an approved analysis estimates censored values or converts units, place that output in a derived layer with method, assumptions, varying limits, source IDs, code or formula version, uncertainty and sensitivity analysis where required. Keep the delivered observation unchanged.
| Element | Preserve | Do not infer |
|---|---|---|
| Reported result | Original value, unit, basis, significant digits, dilution, and laboratory field name | Interchangeability with another unit, fraction, basis, or method |
| Detection condition | Detected, not detected, present below a stated quantitation/reporting level, or exact delivered vocabulary | Zero concentration or absence from the waterbody |
| Detection/reporting limits | Limit type, value, unit, basis, sample-specific status, and source | That MDL, LOD, LOQ, RL, MRL, and project quantitation limits are synonyms |
| Laboratory qualifier | Original code, dictionary/version, narrative, and affected result | One universal meaning for a code used by another laboratory or program |
| Project validation qualifier | Separate decision, reason, reviewer, date, intended-use scope, and link to laboratory evidence | Permission to overwrite or remove the laboratory qualifier |
10. Interpret blanks, duplicates, and batch QC within their exact design
A QC result is evidence about a defined pathway or process; it is not a universal verdict on every sample.
Apply the QAPP and method-defined frequency, acceptance criteria, calculations, affected-result logic, corrective action, and review authority. Preserve adverse and acceptable QC alike. Do not delete an unusual environmental result merely because it differs from a duplicate, and do not average duplicates unless the approved analysis plan defines that operation.
| QC evidence | Question it can inform | Boundary to preserve |
|---|---|---|
| Field, equipment, trip, filter, reagent, or other blank | Whether contamination may have entered through the pathway represented by that blank | Blank types are not interchangeable; one blank does not locate the source or automatically correct results |
| Field duplicate or replicate | Combined variability from the environment, collection, processing, transport, and analysis represented by the design | It is not a pure measure of laboratory precision or proof the site is homogeneous |
| Laboratory duplicate or subsample | Analytical or subsampling precision under the laboratory method | It does not evaluate station selection, field collection, or transport variability |
| Spike, surrogate, control sample, calibration or continuing check | Method-specific recovery, bias, calibration, or process control for the associated batch/results | Apply exact method/project limits and affected-result rules; do not borrow a universal acceptance band |
| Matrix interference, dilution, reanalysis, or narrative finding | Whether sample-specific conditions altered sensitivity or confidence | A plausible rerun does not erase the original analysis or reason for repeating it |
11. Keep laboratory disposition, validation, and release decisions separate
The same result may be reportable by the laboratory, qualified by the project, and unusable for one decision but adequate for another.
Verify completeness and conformance
Check required field, custody, receipt, method, report, EDD, narrative, QC, qualifier, and contract elements. Record missing, conflicting, or late evidence without silently repairing the package.
Retain laboratory decisions
Preserve accepted, qualified, rejected, canceled, on-hold, rerun, or amended states and laboratory reasons per sample and analysis. Do not replace them with a project label.
Validate for the intended use
Apply project requirements and qualified judgment to assign accepted, qualified, rejected, or pending-for-use with affected records, reason, reviewer, date, limitations, and corrective action.
Assess the decision dataset
Evaluate completeness, representativeness, sensitivity, precision/bias evidence, censoring, deviations, assumptions, and uncertainty against the stated decision, not an abstract label of good data.
Release through named authority
Issue a versioned package with included and excluded records, intended use, dictionary, limitations, unresolved findings, approval, archive, correction contact, and superseded-version handling.
12. Preserve amendments, version lineage, and downstream impact
An amended report should create a more visible history, not make the prior evidence disappear.
Do not overwrite an EDD in place, rename an amended PDF to the original filename, or update a dashboard without retaining the prior release and change record. State what changed, why, which conclusions or decisions were affected, and which products or recipients were updated.
- Original report, EDD, narrative, transmittal, and archive identifiers retained unchanged
- Amended report and EDD have distinct version, issue date, status, laboratory reason, and supersedes relationship
- Changed and unchanged sample/result rows identified, including method, unit, limit, qualifier, narrative, or identity changes
- Laboratory contact, project receiver, receipt time, investigation, and unresolved questions recorded
- Verification and validation findings reopened for affected records and intended uses
- Released datasets, calculations, charts, dashboards, reports, submissions, decisions, and known users assessed for impact
- Corrected release receives a new version, approval, revision note, archive, and user notification appropriate to consequence
- Root cause, corrective/preventive action, owner, due date, verification, and similar-package review recorded when warranted
Sources and review notes
Educational sample-management and data-quality guidance only. This guide does not select or approve a laboratory, method, container, preservative, filtration step, storage condition, holding time, reporting limit, quality-control limit, data qualifier, regulatory submission, public-health conclusion, or release decision. Apply the current project QAPP, SAP, SOP, permit or program requirements, receiving laboratory instructions and contract, approved analytical method, hazard controls, and responsible-authority requirements. Laboratory accreditation or certification is scope-specific and does not by itself establish that a particular sample, batch, result, dataset, or use is acceptable.
- National Field Manual, Chapter A1: Preparations for Water SamplingU.S. Geological Survey · field protocol
- National Field Manual, Chapter A4: Collection of Water SamplesU.S. Geological Survey · field protocol
- National Field Manual, Chapter A5: Processing of Water SamplesU.S. Geological Survey · field protocol
- Quality Assurance Project Plan StandardU.S. Environmental Protection Agency · agency guidance
- Memorandum for Reissue of Guidance on Environmental Data Verification and Data Validation (QA/G-8)U.S. Environmental Protection Agency · agency guidance
- Guidance for Data Quality AssessmentU.S. Environmental Protection Agency · agency guidance
- WQX User Guidance: Detection Limits Best PracticesU.S. Environmental Protection Agency · agency guidance
- Water Quality Data Upload (WQX)U.S. Environmental Protection Agency · agency guidance
- Clean Water Act Analytical MethodsU.S. Environmental Protection Agency · agency guidance
- Procedures for Identifying and Documenting Revisions to USGS Water DataU.S. Geological Survey · agency guidance