Environmental Data Management Workflow: Field Collection to Compliance Report

The lab TAT is 10 business days. The compliance report is due in 14. Between the lab delivering the EDD and the consultant delivering the report, six things can go wrong: the EDD arrives in the wrong format, a holding time was exceeded and nobody flagged it, the reporting limit for one analyte is above the applicable MCL, a staff scientist applied the wrong state standard for a recently upgraded site, the PM reviewed the exceedance table before noticing a transposition error in row 47, and the state portal rejects the electronic submission because the location ID doesn’t match the permit. None of these are unusual. The environmental data management workflow from field collection to compliance report has failure points at every handoff, and most of them are invisible until they matter.

This is a step-by-step walkthrough of the full workflow with attention to where errors occur and how to catch them before they become report revisions.

Step 1: Field Sampling—What the Lab Will Need

Field collection produces two outputs that drive everything downstream: the physical samples and the chain of custody documentation. COC errors are among the most common causes of lab result problems. The COC must specify the correct analyte list, correct containers, and correct preservation requirements. A lab that receives the wrong container type for VOC samples will either reject the samples or analyze under protest—either outcome costs time.

For NPDES compliance monitoring, verify the sampling procedure matches permit requirements before going to the field. Permit conditions specify whether grab or composite samples are required, what time windows apply for compositing, and what the minimum sample volume must be. Field staff who haven’t read the current permit are the most common source of sampling protocol violations.

Step 2: Lab Delivery—EDD Format and Timing

Standard turnaround time from most commercial labs is 14 business days for standard methods. Rush TAT is 5–7 business days; priority rush is 24–48 hours with corresponding cost premiums. For reports with regulatory submission deadlines, the lab TAT needs to be factored into the project schedule explicitly—“we’ll get the lab data soon” is not a project schedule.

The lab delivers two components: the EDD (the structured data file, typically CSV or Excel) and the analytical report (PDF). The PDF is the legally defensible record. The EDD is what you actually work with. When the EDD arrives:

• Verify the sample IDs in the EDD match the sample IDs on your COC. Mismatched IDs happen when the lab re-labels samples during accessioning. A result associated with the wrong sample ID produces a wrong location assignment in the exceedance table.
• Verify the analyte list is complete. Missing analytes in the EDD are usually a reporting error, not an analytical failure—but you need to identify them before the comparison step, not after.
• Note any late flag codes on the PDF report (samples where holding time was exceeded). Results with holding time violations carry an H qualifier and are typically flagged as rejected (R) or estimated (J) during data validation. If a holding time-violated result exceeds a standard, you need to address that in the compliance narrative.

Step 3: QA/QC Review Before Comparison

QA/QC review is not the same as data comparison. This step checks whether the data is usable before you run any comparisons. Four checks every staff scientist should do before running exceedances:

Check the QC sample results. Every sample batch includes lab-generated QC samples: method blanks, matrix spikes, and lab duplicates. The lab analytical report includes the QC summary. Method blank contamination above the reporting limit means analytes detected at or below the blank level are suspect. Matrix spike recoveries outside of the 70–130% window (or the tighter thresholds specified in some state methods) mean the analytical result is qualified.

Check the field blank and trip blank results. For VOC work, trip blanks travel with the samples to check for cross-contamination during transport. A trip blank result above the MDL means any VOC detections in the sample batch are qualified or potentially rejected.

Check the duplicate precision. Field or lab duplicate results are reported as relative percent difference (RPD). Common RPD criteria are 20% for organics and 35% for inorganics, though project-specific DQOs may be tighter. Results from samples with high RPD duplicates are usually J-flagged.

Verify detection limits against applicable standards. This is the most commonly missed QA step. For every non-detect result, compare the reporting limit (RL) to the applicable standard. If the RL is above the standard—for example, a RL of 1.0 µg/L for a compound with an MCL of 0.5 µg/L—compliance cannot be confirmed. The report must flag this explicitly. This is not an exceedance; it is a detection limit inadequacy, and it requires a different narrative response than an actual exceedance.

Step 4: Standards Selection—The Most Consequential Step

Applying the wrong standard is the highest-consequence error in the compliance workflow. The applicable standard depends on the project type (drinking water, discharge, site cleanup), the jurisdiction (federal vs. state, and which state), and the specific permit or program. The hierarchy:

• NPDES permits: Permit-specific effluent limits control. Where the permit doesn’t specify a limit for an analyte, the Clean Water Act water quality-based standards apply. Do not use MCLs as surrogate discharge limits without confirming that interpretation with your permit writer or regulatory contact.
• Drinking water compliance: Federal MCLs apply as the floor. If the state has adopted a more stringent standard for any analyte—New Jersey’s arsenic MCL is 5 µg/L vs. the federal 10 µg/L, California’s perchlorate MCL is 6 µg/L—use the state standard. Always apply the most stringent applicable standard.
• Site cleanup and groundwater monitoring: Site-specific cleanup standards from a consent order or permit control where they exist. Where they don’t exist, EPA Regional Screening Levels (RSLs) provide risk-based screening values, updated semi-annually. State-specific cleanup criteria (NJ SRS, MA MCP Method 1, CA ESLs) apply in their respective jurisdictions.

On projects that involve multiple site areas under different programs—an NPDES outfall within the boundary of a RCRA post-closure site, for example—document the standard applied to each analyte at each location. A result above the RSL but below the RCRA closure standard may require different action depending on which program governs that monitoring location.

Step 5: Screening Comparison and Exceedance Table

The screening comparison is the step the compliance report is built around: compare every analytical result against the applicable standard and produce a table showing the subset that exceeded.

For small data sets (50–200 results, 1–2 locations), this is manageable in Excel with careful VLOOKUP construction. The failure mode is when the analyst forgets to check for updated state standards since the last sampling event, when a new analyte was added to the permit and wasn’t added to the lookup table, or when a copy-paste error shifts the standard values by a row. For larger data sets, the manual comparison doesn’t scale.

The exceedance table output needs to include, at minimum: location ID, sampling date, analyte, result value and units, data qualifier, applicable standard with citation, and whether the result exceeds. Any result where the RL exceeds the standard should appear as a separate row with a “detection limit inadequacy” designation, not as a non-exceedance.

Qualified results (J-flagged) that exceed the standard should be listed in the exceedance table with the qualifier noted and addressed in the narrative. Whether a J-flag result triggers the same regulatory response as an unqualified exceedance depends on the specific permit and regulatory program—don’t make that determination in the table without confirming it in the text.

Step 6: Compliance Narrative and Report Delivery

The compliance narrative interprets the exceedance table for a regulatory reviewer who will read the report once and needs to understand what was sampled, what exceeded, and what the consultant recommends. Structure:

1. Monitoring event summary: what was sampled, when, by whom, under what permit conditions
2. Laboratory QA/QC summary: any QC failures or qualified results and their implications
3. Exceedance findings: what exceeded, at what location, relative to what standard
4. Detection limit adequacy: any analytes where the RL exceeded the standard and compliance cannot be confirmed
5. Recommended actions: confirmation sampling, permit exceedance notification, no further action—with the specific permit condition that triggers each

For NPDES exceedances, the 24-hour oral notification and 5-day written follow-up requirements under 40 CFR 122.41(l)(6) apply to exceedances of permit limits. The compliance report is not a substitute for those notifications—they are separate obligations with separate deadlines. See the post on NPDES exceedance reporting timelines for the specific notification triggers.

For electronic submission, verify the regulatory portal format requirements before generating the submission file. NetDMR requires specific data field mappings; GeoTracker requires ESI-format XML. A submission that fails portal validation at 4pm on the deadline day requires a phone call to the agency, not a data management system improvement.

The post on managing compliance deadlines across multiple permits covers the calendar and tracking infrastructure for firms managing multiple simultaneous permit obligations—the tracking problem is separate from the data management problem and requires a separate solution.