Regulatory water submissions — drinking-water programs, PFAS reporting under EPA Method 1633, NPDES discharge data — all share a baseline set of chain-of-custody fields. Miss one and the submission gets bounced back, sometimes with downstream reporting penalties. This guide lays out the minimum required data elements, where state programs add their own, and how a configurable LIMS keeps the COC form clean from collection through final reporting.
Short answer: a defensible water-program COC captures sample identity (unique ID, matrix, location and GPS), collection metadata (collector name, date and time, temperature, preservative), custody transfers (every handoff with signature and timestamp), the method and analyte list, and the lab's accreditation context. State programs add specifics — bottle types, hold times, certified-lab IDs, sample-type codes — on top of that baseline.
The baseline COC fields every water submission needs
Regardless of program, water labs and environmental contract labs need these elements on the COC at the time of submission.
- Sample identity — unique sample ID, project ID, matrix (drinking water, surface water, groundwater, wastewater, soil leachate), and location identifier with GPS where applicable.
- Collection metadata — collector name and credentials, collection date and time, container type, preservative used (e.g., HNO3, NaOH, Trizma for PFAS), and field-measured temperature.
- Custody transfers — every handoff between collector, transporter, and receiving lab, each with signature, printed name, organization, date, and time.
- Analytical scope — list of methods requested (e.g., EPA 537.1, EPA 533, EPA Method 1633 for PFAS), reporting limits, and target analytes.
- Lab and accreditation context — receiving lab's NELAP, TNI, or state-specific accreditation reference applicable to the requested methods.
- Hold-time and condition checks — temperature on receipt, container integrity, hold-time check, and any deviations.
If any of these are blank or inconsistent across the bottle label, the COC form, and the LIMS intake record, the submission is at risk.
Where PFAS reporting raises the bar
PFAS submissions under EPA Method 1633 (and the related Methods 533 and 537.1 for drinking water) demand extra COC discipline because field contamination risk is unusually high.
Practical additions you'll see required or strongly preferred:
- Documented use of PFAS-free sampling equipment and containers, captured as a field on the COC.
- Field blank, equipment blank, and trip blank IDs, linked to the sample IDs they correspond to.
- Collector attestation that no PFAS-containing materials (Teflon tape, certain waterproof clothing, fluorinated lubricants) were used during sampling.
- Matrix-specific preservation notes — for example, Trizma for aqueous matrices in Method 1633.
State programs frequently overlay their own PFAS reporting templates on top of EPA's. Check the program's data dictionary before each submission cycle.
Common rejection causes in state regulatory submissions
Submissions get bounced for a small set of recurring reasons. Most are preventable at intake.
Inconsistent identifiers across artifacts. The bottle label says SW-2026-0412-03 and the COC says SW-2026-0412-3. The state portal flags the mismatch.
Missing or implausible timestamps. A collection time later than the receipt time, or a hold-time interval that exceeds the method's allowance.
Custody gaps. A transporter row with no signature, or a receiving lab acknowledgment with no time stamp.
Method-analyte mismatch. Reporting a PFAS analyte not on the certified method scope for that lab.
Temperature out of range. Receipt temperature above the method's allowed maximum, with no deviation note explaining what happened.
How a configurable LIMS keeps the COC defensible
A configurable LIMS doesn't replace your SOP — it enforces it consistently. The capabilities that matter for a clean regulatory submission:
- Sample IDs and barcodes generated once and printed onto the bottle label, the COC, and the worksheet, so all three artifacts always match.
- Chain-of-custody, sample-tracking, and lot-genealogy building blocks that capture each handoff with user authentication and timestamp — in conjunction with the lab's validated SOPs.
- Configurable intake forms by program — different required fields for drinking-water, PFAS, NPDES, or state-specific templates — so analysts can't accidentally skip a mandatory element.
- Result-locking, deviation-management, and corrective-action-tracking so out-of-range receipts and hold-time exceedances are surfaced and resolved before the data leaves the lab.
- Audit-trail and chain-of-custody outputs that map cleanly to state submission portals, reducing the manual remap step that often introduces errors.
Confident provides these building blocks for environmental labs and water programs working under NELAP, TNI, or state-specific accreditation, in conjunction with the lab's validated methods.
Aliquot genealogy and sample-retention policy
A defensible water or PFAS submission has to trace every aliquot back to its parent sample and prove the retention policy was followed. When one field sample is split into separate aliquots — metals on one, PFAS on another, anions on a third — each aliquot needs its own ID that still resolves to the original collection record, preservative, and custody chain.
Aliquot genealogy is the parent-child record linking each split, sub-sample, and dilution back to the sample it came from. It matters because a state reviewer auditing a PFAS result will ask which aliquot was analyzed, when it was prepared, what preservative it carried, and how long it was held before extraction. If the genealogy is implicit — tracked in an analyst's notebook rather than the system — that question turns into a scramble.
Retention policy is the companion record: how long each matrix and aliquot must be kept after reporting, when disposal is authorized, and who signed off. EPA Method 1633 and most state drinking-water programs set minimum sample-hold and record-retention windows, and mixing those up is a common finding.
- Parent-to-aliquot links — every split, dilution, and re-extraction resolves to the original sample ID, preservative, and collection metadata.
- Preparation timestamps — extraction and prep times captured against each aliquot so hold-time compliance is provable, not estimated.
- Retention clocks per matrix — disposal-eligible dates calculated from receipt, with disposal requiring an authenticated sign-off.
- Re-test traceability — when a result is challenged, the exact aliquot, its genealogy, and its retention status are recoverable in one pull.
Confident provides chain-of-custody, sample-tracking, and lot-genealogy building blocks that capture aliquot parent-child links and retention clocks against each sample, in conjunction with the lab's validated SOPs. That keeps the genealogy and retention record queryable at audit time instead of reconstructed from memory.
A practical pre-submission checklist
Before pushing a batch to a state portal, walk this five-line check:
- Every sample ID matches across bottle label, COC, intake form, and result record.
- Every custody transfer has a signature, name, organization, date, and time.
- Receipt temperature, container integrity, and hold-time fields are all populated — not blank.
- Method codes on the COC match the lab's certified scope on file with the state program.
- Field blanks and trip blanks (for PFAS) are linked to their parent samples in the LIMS.
If any line is unclear, fix it before submission. Bouncebacks cost more than the extra 15 minutes of QC.
Frequently asked questions
What is the minimum COC field set for a state drinking-water submission?
Sample ID, matrix, collection date and time, collector identity, preservative, container type, receipt temperature, hold-time check, custody-transfer signatures, and the certified method list. State programs may add their own required fields — always check the current data dictionary.
What COC fields are PFAS-specific?
Confirmation of PFAS-free sampling materials, field, equipment, and trip blank IDs linked to parent samples, matrix-specific preservatives (such as Trizma for aqueous matrices), and collector attestation that no fluorinated materials were used during sampling.
How does a LIMS prevent COC submission errors?
By generating consistent sample IDs across bottle, COC, and worksheet; by enforcing program-specific required fields at intake; by recording every custody transfer with authenticated timestamps; and by surfacing out-of-range receipt conditions before results are reported.
What is aliquot genealogy and why do auditors care?
Aliquot genealogy is the parent-child record linking every split, dilution, and re-extraction back to its original sample, preservative, and custody chain. Auditors use it to confirm which aliquot produced a reported result and that hold times were met — which is hard to prove if those links live only in an analyst's notebook.
How long do water and PFAS labs have to retain samples and records?
Retention windows are set by the program — EPA Method 1633, the Safe Drinking Water Act, and state-specific rules each define minimum sample-hold and record-retention periods. Track the clock per matrix from receipt, and require an authenticated sign-off before disposal so the retention record stays defensible.
What's the most common reason a state portal rejects a submission?
Identifier inconsistency across the bottle label, the COC, and the result record — usually a typo or a hand-edited number. Auto-generated IDs eliminate this category of error.
Do I need separate COC templates for different programs?
Yes. Drinking-water (SDWA), PFAS (Method 1633), NPDES discharge, and state-specific programs each have their own required field sets. A configurable LIMS keeps separate intake templates per program rather than forcing one universal form.
Ready to see how Confident handles regulatory COC submissions?
Confident LIMS supports environmental, agriculture, and food and beverage labs that need defensible chain-of-custody records, aliquot genealogy and retention tracking, and clean state-portal exports — in conjunction with the lab's validated SOPs. To see how the platform handles your water, PFAS, or NPDES reporting workflows, Get Demo.
