Groundwater monitoring software: when Excel stops working for regulatory compliance

Why do Excel groundwater reports stop passing regulator review around year three?

Three years is a pattern, not a hard line. What crosses it is compounding: more wells, more analytes, more frequent sampling, more sites, and rising regulator expectations, all growing at once until the total exceeds what a spreadsheet handles well. The arithmetic is simple. One site at eighty readings a year is manageable. Six sites at roughly 480 readings a year reach about 1,440 readings after three years, and about 2,400 by year five, which is the point where the spreadsheet becomes the bottleneck rather than the tool.

Two things made 2026 push programs past that line faster. Regulators now expect continuous trend visibility under RCRA corrective action, NPDES permits, and state DEP frameworks, not a plot assembled at review time. And PFAS is now firmly inside the Superfund framework: the D.C. Circuit upheld EPA's designation of PFOA and PFOS as CERCLA hazardous substances on August 18, 2026, so monitoring programs are adding PFAS analytes to their wells, which raises the volume and the stakes of every reporting cycle.¹

What are the five failure modes regulators flag most often?

1. Trends are invisible in static data. A pattern only appears once someone plots it by hand, which can happen too late to notify.
2. Exceedance windows close before the pattern surfaces. A quarterly manual review can miss the notification window entirely.
3. Cross-station analysis becomes impractical. Plume movement and treatment degradation span stations, and reconciling them across sheets by hand is too slow to keep up.
4. Audit reconstruction takes days. Historical context has to be reassembled from spreadsheets, lab PDFs, and emails every time a regulator asks.
5. Data-integrity gaps. Missing chain-of-custody entries, inconsistent analyte names, formula drift, and corrupted aggregation cells, which quietly compound the other four.

Regulators penalize the operational consequences of spreadsheets, not the spreadsheets themselves.

How does a missed exceedance window actually happen?

Picture a single reading that looks acceptable on its own. Plotted against the last six months it is trending toward an action level, and it matches a drift at an adjacent well. A spreadsheet hides both facts, because seeing them depends on someone deciding to look. In a common version of this, the reading sits in the file for weeks until the quarterly review, and by then the notification window has moved. Regulators read that gap as reactive monitoring, and the exposure compounds across later submissions rather than resetting each quarter.

What does cross-station trend analysis look like once Excel can no longer support it?

PCG's groundwater monitoring work produced station-by-station and analyte-by-analyte time series, supported anomaly searches, and surfaced coordinated, plume-like patterns on its own rather than waiting for an analyst to find them. The difference between the two approaches is where the work happens.

How does PCG move groundwater data from Excel to a custom database?

PCG runs the transition in four phases, each producing something the business keeps whether or not the next phase proceeds. The scope and schedule of each phase depend on the specific program and are set during the diagnostic, not promised in advance.

1. Discovery and source auditPCG documents every Excel file, lab archive, chain-of-custody form, and regulatory framework in play, and delivers a written audit the business keeps.
2. Schema design and prototype reviewPCG designs the SQL Server schema and the EHS review screens, then builds a prototype for the team to review before production work begins. A correction caught here saves far more rework than one caught after the build.
3. Build and validationPCG builds a .NET 10 application on SQL Server, with recurring staff demos and user-acceptance testing against representative real data.
4. Migration and parallel operationHistorical data moves across with a reconciliation report, and the Excel process and the new system run in parallel until the EHS team signs off.

What about the historical Excel data, lab PDFs, and chain-of-custody forms already accumulated?

Historical readings move into a time-series structure so trends run unbroken across the full record. Lab PDFs are stored as linked source documents, and chain-of-custody forms are kept both as source images and as queryable structured records. The original files stay accessible, and because the migration method is documented before any data moves, the migration itself is auditable. You keep and control the data throughout, in a standard format rather than a closed one.

Can the system align with multiple regulatory frameworks at the same site?

Yes. One site often sits under several regimes at once: RCRA corrective action, CERCLA Superfund, NPDES permits, EPA Title V requirements that intersect groundwater, and state DEP frameworks. Per-site configuration, the analyte lists, thresholds, and reporting requirements, is stored as data rather than written into code, so adding a site or a new threshold does not require new development. The payoff is a single cross-framework dashboard across the whole portfolio. PCG covers the field-data side of this in environmental remediation tracking and the spreadsheet origin of the problem in the Spreadsheet Trap.

Frequently Asked Questions