Stormwater Data Management: From Laboratory Results to Validated Data

ESdat Environmental Data Management Software
Published: 16 November 2026

Stormwater data management connects laboratory results with the information needed to interpret them: sample identities, monitoring locations, analytical methods, detection limits, quality-control records, and review decisions.

Receiving a laboratory result is only the beginning. Before that result can support environmental analysis or reporting, a project team needs to establish what it represents, whether it meets the project's quality requirements, and what limitations affect its use.

Environmental data management software such as ESdat can support this process by keeping analytical results and their supporting information together. A stormwater Quality Assurance Project Plan prepared by Herrera Environmental Consultants for the City of Tacoma provides a detailed example. It specifies ESdat for managing most analytical laboratory data and describes electronic data deliverables, initial checks, review status, corrective action, and data qualification. [1]

For environmental consultants, monitoring teams and data managers, the practical lesson is straightforward: importing results and accepting them for use are separate steps.

Key takeaways

  • A successful import does not establish data validity. Laboratory results still need review against project requirements.

  • Electronic data deliverables support structured processing. Sample identifiers, methods, units, limits and quality information must remain interpretable.

  • ESdat has a documented role in stormwater laboratory data management. The Washington QAPP describes it as the projects chemistry database.

  • Approval status and qualifiers communicate different information. A result can complete review while retaining an estimated-value qualification.

  • Non-detects must remain identifiable. They should retain their associated limits and must not be confused with measured zeros.

  • Professional judgement remains essential. Software supports review; qualified personnel determine whether information is suitable for its intended use.

Why stormwater laboratory results need context

A concentration alone does not explain the condition of a waterway or drainage catchment.

To interpret a result, a reviewer may need to know:

  • Where and when the sample was collected.

  • Whether it was a grab sample or a composite sample.

  • Which environmental matrix was analysed.

  • Which analytical method and units apply.

  • Whether the substance was detected.

  • What reporting limit and qualifiers accompany the result.

  • Whether relevant quality-control information supports its use.

These details matter when comparing monitoring events, investigating unexpected concentrations, or preparing a dataset for statistical analysis.

A useful stormwater database should preserve those relationships throughout the workflow. The information needed to interpret a result should remain available when it is exported, mapped, or reported.

A documented ESdat workflow in a stormwater QAPP

The May 2025 Quality Assurance Project Plan: Stormwater Contaminants of Emerging Concern in Western Washington specifies how laboratory data will be managed.

Section 10 identifies ESdat as the consultant's online chemistry database. It describes a central repository spanning soil, groundwater, surface water, stormwater, gas, and other environmental matrices. This describes the repository's scope; it does not mean the study sampled every listed matrix.

Laboratory partners send electronic data deliverables to a designated email address. The plan then describes initial acceptance checks, an unapproved status, detailed quality review, corrective action where necessary, and approval for use. [1, section 10.1]

This is evidence of a specified workflow. The QAPP alone does not demonstrate completed implementation or quantify improvements attributable to the software.

What is a laboratory electronic data deliverable?

An electronic data deliverable, or EDD, is a structured electronic file supplied for processing or import.

The Washington QAPP requires laboratory results, including quality-control results, in Excel or comma-separated value format. Final laboratory reports are also required as PDFs. [1, sections 10.210.3]

These files serve complementary purposes. A laboratory report preserves the laboratory's presentation and commentary. A structured delivery enables records to be processed without repeatedly transcribing results from report pages.

However, an Excel or CSV file is not automatically a suitable EDD. Its structure and contents must meet the receiving project's requirements.

Agree on delivery requirements before sampling

For a new monitoring program, define the laboratory delivery requirements early.

The specification should address sample naming, parameter identifiers, units, methods, reporting conventions, qualifiers, and quality-control records. It should also explain how amended results will be delivered.

A useful acceptance test is to process a representative laboratory package before routine monitoring begins. Include detections, non-detects, and quality-control information so the test covers more than straightforward concentration values.

From incoming results to reviewed data

A practical laboratory data workflow has five stages:

Receive the EDD -> check the delivery -> identify provisional results -> review quality -> record the use decision

Each stage has a different purpose.

1. Receive and preserve the delivery

Keep the original laboratory files identifiable and retrievable.

Record the laboratory, delivery date, report reference, and relevant sampling event. Preserve the connection between the structured results and the accompanying report.

This provides a reference point if questions arise during review or a corrected package arrives later.

2. Check sample identities and requested work

Before accepting results into routine use, reconcile the delivery with the expected samples and analyses.

Check for unexpected identifiers, omitted samples, missing analyses, and methods that differ from the requested work. Investigate discrepancies rather than silently changing records to make them fit.

These checks establish whether the package corresponds to the work the project intended to receive.

3. Make review status visible

Newly available results should be distinguishable from results that have completed the required assessment.

Status may be represented differently between organizations, but users should understand which records remain provisional. Define whether those records can appear in internal reports, exports or dashboards.

Visibility helps prevent early access from being mistaken for acceptance.

4. Assess analytical quality

Review the relevant laboratory and field quality information against the project's requirements.

Depending on the monitoring program, this may include:

  • Sample preservation and holding times.

  • Method and field blanks.

  • Duplicate results.

  • Spike recoveries.

  • Laboratory control samples.

  • Reporting limits.

  • Sampling and analytical deviations.

The assessment should establish what any identified issue means for the affected results.

ITRC guidance distinguishes verification, validation and data usability assessment, helping teams separate conformity checks from decisions about intended use. [2]

5. Record the decision and its limitations

A review should produce an understandable outcome.

Record whether the results can be used, whether qualifications apply and whether further action is required. Keep the rationale accessible to future analysts.

The goal is a dataset that another qualified person can interpret without reconstructing the review from scattered emails.

Verification, validation, and approval are different

These terms are related, but they answer different questions.

Verification examines whether records are complete, correct, and consistent with specified requirements.

Validation evaluates quality findings in relation to the intended use of the data.

Approval records completion of an organization's prescribed review and decision process.

Usability assessment considers whether the available information can support the project's objectives.

A structurally correct delivery can contain results with analytical limitations. A reviewed result can be usable for one purpose while unsuitable for another.

The workflow should make these distinctions clear. A single valid field can conceal important differences unless its meaning is carefully defined. [2]

Why data qualifiers must stay attached to results

A qualifier communicates a condition affecting interpretation.

The Washington QAPP defines the following project codes:

  • J: An estimated result.

  • R: A rejected result associated with major analytical quality problems.

  • U: A result below the detection and/or reporting limit.

  • UJ: A result below the reporting limit that also carries an estimated qualification.

The plan allows estimated results to be considered for evaluation while excluding rejected results. [1, Table 15 and section 10.1]

For other projects, check the applicable definitions before applying familiar-looking codes.

Approval does not remove uncertainty

Review status and qualifiers should remain separate.

Status explains where a record sits in the workflow. A qualifier explains a condition affecting the result.

For example, an estimated concentration may complete review and be accepted for a defined analysis. Its estimated status should remain visible in subsequent outputs.

When exporting data, check that qualifiers survive the handover. A concentration copied without its qualification can communicate more certainty than the reviewed record supports.

Preserve non-detects and their reporting limits

A non-detect is not a measured concentration of zero.

Consider a detected concentration of 5 ng/L and a non-detect reported at a limit of 5 ng/L. The shared number does not make those observations equivalent.

For data-management purposes, retain:

  • The reported value or applicable limit.

  • Detection status.

  • Relevant qualifiers.

  • Analytical method and units.

Choose statistical treatment separately, based on the analysis objective and dataset characteristics. Guidance on environmental data evaluation recognizes the importance of analytical limits and qualifiers when interpreting results. [3]

Also distinguish not analyzed from analyzed and not detected. That distinction becomes particularly important when analytical suites change between monitoring events.

ESdat within a wider environmental information workflow

The Washington plan assigns different information streams to different tools. Continuous monitoring records are handled in Aquarius, most laboratory chemistry data in ESdat, and statistical analysis in R. Specialist high-resolution mass spectrometry outputs have separate storage arrangements. [1, sections 10 and 13.3]

The wider lesson is to define responsibilities and handovers clearly.

For any monitoring program, establish:

  • Where original records are retained.

  • Where reviewed analytical results are maintained.

  • Which system records qualifications and use decisions.

  • How data reach statistical or spatial tools.

  • Who checks outputs after transfer.

  • How updated results replace or supersede earlier information.

A coherent workflow can involve several applications. Its reliability depends on clear ownership, preserved context and reproducible transfer rules.

What to look for in stormwater data management software

Evaluate ESdat or another platform by following representative data through the proposed workflow.

Laboratory intake

Can the system receive the required delivery formats while preserving links to laboratory reports?

Sample and location identity

Can users reconcile delivered records with expected samples and monitoring locations? How are ambiguous identifiers handled?

Analytical context

Are units, methods, limits, detection status, and qualifiers retained through import and export?

Quality review

Can reviewers access the supporting information needed to assess results? Can decisions and limitations be recorded?

Status and permissions

Can provisional information be distinguished from reviewed data? Are responsibilities for editing and approval clear?

Amendments and traceability

Can a corrected delivery be processed while preserving the information needed to understand what changed?

Reuse and reporting

Can users export a documented dataset that remains interpretable outside the application?

These are evaluation questions, not claims that every system implements the same controls. Ask for demonstrations using realistic data, including a correction and a qualified result.

Preparing data for analysis and reporting

Before generating tables, charts, maps or dashboards, define the dataset selection rules.

Document the included sampling events, parameters, review statuses and treatment of qualified results. Record the extraction date and dataset version.

For each output, ask:

  • Can the selection be reproduced?

  • Are units and reporting conventions clear?

  • Are non-detects distinguishable from detections?

  • Have relevant qualifications been preserved?

  • Could a reader mistake provisional information for reviewed findings?

These checks help maintain consistency between the environmental database and the information presented to decision-makers.

For the broader governance context, see How Governments Use Environmental Data Management Systems to Improve Monitoring, Compliance and Public Trust.

Frequently asked questions

What is stormwater data management?

It is the organized handling of stormwater sampling information, analytical results, monitoring records and quality assessments so they remain interpretable through review, analysis and reporting.

How does ESdat support stormwater laboratory data management?

The Washington QAPP specifies ESdat as the chemistry database within a workflow covering EDD receipt, review status, quality assessment, and approval. That provides a documented project example of its role. [1]

Does importing an EDD mean the data are validated?

No. Structural acceptance and scientific suitability are separate questions. Results need the assessment required by the project's quality procedures. [2]

Can a reviewed result still carry a qualifier?

Yes. Completing review does not remove a limitation. A qualified result may be usable for a defined purpose while retaining information about uncertainty.

Why retain both PDF reports and structured data?

They serve different purposes. The report preserves the laboratory's presentation and commentary; structured records support processing and analysis. Keeping them linked supports traceability.

Why are non-detects different from zeros?

A non-detect reflects the applicable analytical conditions and limits. It does not establish that the actual concentration is zero. [3]

Can spreadsheets be part of the workflow?

Yes. The Washington QAPP allows Excel-format EDDs. File format alone, however, does not establish how review, corrections, and qualifications are controlled. [1]

Does software replace professional review?

No. Software can organize records and support checks, but qualified personnel must assess limitations and determine suitability for the intended use.

Glossary

Approval status: A record of progress through an organization's review and acceptance workflow.

Chain of custody: Documentation recording sample identification, handling and transfer.

Data usability: Suitability of information for a defined purpose, considering quality and limitations.

EDD: Electronic data deliverable; a structured electronic delivery of results and associated information.

Environmental matrix: The material sampled, such as water, soil, or sediment.

ESdat: Environmental data management software identified as the chemistry database in the Washington stormwater QAPP.

Holding time: The specified period allowed before a relevant sample preparation or analytical step.

Non-detect: A result not reported as detected under the applicable analytical conditions.

QA/QC: Quality assurance and quality control; planned processes and checks used to manage and assess quality.

QAPP: Quality Assurance Project Plan; a document defining project methods, responsibilities and quality procedures.

Qualifier: A code communicating a condition or limitation affecting a result.

Reporting limit: A threshold applied when reporting an analytical result under specified arrangements.

Validation: Assessment of data quality in relation to intended use.

Verification: Assessment of completeness, correctness, and conformity with specified requirements.

References

  1. Herrera Environmental Consultants, Inc. May 2025. Quality Assurance Project Plan: Stormwater Contaminants of Emerging Concern in Western Washington. Prepared for the City of Tacoma. Relevant sections include Data Management Procedures, printed pages 8688; Data Verification, pages 9094; and Data Quality (Usability) Assessment, pages 9597. Table 15 defines project qualifiers.

  2. Interstate Technology & Regulatory Council. Analytical Data Quality Review: Verification, Validation, and Usability. Guidance on environmental analytical data review and fitness for use.

  3. Interstate Technology & Regulatory Council. Risk Assessment: Data Evaluation. Guidance discussing analytical data, limits, qualifiers and interpretation.

Categories

Data Management

Keywords

ESdat, Environmental Data Management, Stormwater