Custom Software for Environmental Remediation Tracking and Audit Reports
Who builds it, what it has to do in 2026, and when custom wins over SaaS
Phoenix Consultants Group builds custom software for environmental remediation tracking, chain of custody, and audit reports across EPA Superfund, CERCLA, RCRA, and state DEP programs. PCG has been engineering remediation systems since 1995, including Superfund soil tracking, ground water monitoring, and EPA Title V air quality platforms used by Fortune 100 refineries and federal cleanup operations.
What does environmental remediation tracking software need to do in 2026?
The regulatory floor for remediation operators moved in 2025 and 2026, and most off-the-shelf platforms have not caught up. A remediation tracking system built today has to cover four things that were not standard requirements three years ago.
First, PFAS as Superfund hazardous substances. EPA designated PFOA and PFOS as hazardous substances under CERCLA in a final rule effective July 8, 2024.1 The agency confirmed in September 2025 that it will retain the designation and is developing a Section 102(a) Framework Rule for future PFAS hazardous substance designations.2 What this means operationally: previously closed sites can be reopened, new sites enter the National Priorities List with a broader contaminant scope, and chain of custody documentation now has to track substances that were not on the regulated list when most legacy systems were designed.
Second, the 2026 Five-Year Review cycle. EPA opened the 2026 review cycle on eight Superfund sites this year.3 Five-Year Reviews are not new, but the documentation expectation has tightened. A review now expects continuous performance data from the operator, not a binder produced the week before the EPA team arrives. A remediation tracking system that does not produce that record automatically becomes the bottleneck of the review.
Third, the new TSCA section 6(g) TCE exemption requirements took effect February 17, 2026, affecting labs that support remediation analysis.4 Workflow integration between the operator and the lab is no longer optional.
Fourth, the PFAS reporting rule under TSCA opens for submission on January 31, 2027, or 60 days after the rule is finalized, whichever comes first.5 Waste management and remediation services (NAICS code 562) are covered. An operator that does not know which of their historical projects are reportable is behind the curve already.
Off-the-shelf EHS platforms address these regulations in their roadmaps. Custom software addresses them in the operator's actual workflow.
Why off-the-shelf EHS platforms fail mid-size remediation firms
There are good SaaS platforms in this category. Matidor handles environmental site assessment and project tracking with a strong map interface, particularly for consultancies running 20-plus concurrent assessments across multiple sites. EVX Software was built specifically for environmental and engineering consultancies, with billing and time tracking baked in. EnFlection from Trihydro is the most regulation-specific of the four, supporting CERCLA, RCRA, NPDES, and Class VI carbon capture workflows out of the box. ERA Environmental rounds out the category. The vendor has been in environmental software since 1995, the same year PCG was founded.
These platforms work well when the operator's process matches the platform's design. They fail in three predictable ways when the operator's process is the differentiator.
Reporting templates miss the regulator
A state DEP reviewer in New Jersey accepts a different format than an EPA Region 9 program officer in California. Multi-jurisdiction firms end up exporting from the SaaS platform and reformatting in Excel before submission.
Instrument and lab integrations are missing
Custom remediation work uses specific lab LIMS systems and field sampling instruments. SaaS platforms support the top integrations. They do not support the one your operation has used for fifteen years.
No source code, no data ownership
When the SaaS vendor pivots its roadmap, sunsets a feature, or raises pricing, the operator has no recourse other than to migrate the data again. For records tied to twenty-year regulatory audits, that risk is material.
PCG has migrated operators away from SaaS platforms comparable to the four named above. In every case the trigger was the same. The operation grew past what the platform was designed to do. The cost of working around the platform exceeded the cost of building a system that fit.
When custom software wins over SaaS for remediation tracking
Custom does not win every project. A small environmental services firm with one office, one state regulator, and a standard workflow should buy a SaaS platform. That is the right answer.
Custom wins in three specific situations.
Multi-jurisdiction reporting where no SaaS template fits. Remediation operators working across three or more state DEP programs plus federal EPA oversight produce reports in formats that no platform can template-match. Building the reports in custom software once produces correct output every time. Building them by exporting and reformatting from SaaS produces a quarterly fire drill.
Integration with instrumentation or lab systems that the operator depends on. When the field data comes from specific sampling equipment and the lab data comes from a specific LIMS, the integration layer is the whole project. Custom software builds that layer once. SaaS asks the operator to change tools.
Source code ownership for long-cycle regulatory audits. Superfund and other long-cycle cleanup programs run over decades. The software supporting a twenty-year remediation needs to outlive any SaaS vendor's business decisions.
PCG delivers source code ownership to every client as a contractual term, not a marketing claim. For remediation systems that have to support decade-long regulatory audits, that ownership is non-negotiable. When the vendor relationship ends, the operator still owns the system.
What PCG has actually built for environmental operators
Four projects from the PCG case study library illustrate the pattern across remediation, monitoring, regulatory permitting, and chemical handling.
Source-to-destination chain of custody for every soil unit. Forward projection on remaining contaminated volumes. Regulatory output aligned with EPA Superfund program officers.
Time-series data across monitored wells. Anomaly detection on threshold exceedances. Multi-site monitoring with state environmental agency reporting.
Tens of thousands of emissions calculations for a Clean Air Act permit application. Worst-case and best-case modeling. Complete audit trail. Permit approved.
Multi-client chemical production and shipping. Chain of custody from production through delivery. OSHA HazCom 2012 / GHS regulatory alignment from one architecture.
Detailed case studies are available for each project. Superfund Soil Remediation. Ground Water Monitoring. EPA Title V Air Quality.
The pattern across these projects is consistent. PCG did not arrive with a product. PCG arrived with engineers who learned the regulatory framework, the operational workflow, and the existing data structure before any code was written.
What to ask a custom software developer before signing
Do they do a diagnostic before quoting? Any developer who quotes a timeline or a price before understanding the data, the regulatory exposure, and the existing workflow is guessing. A serious custom development firm runs a diagnostic engagement first and produces a written scope document. PCG offers this diagnostic at no cost, because the diagnostic is how a real engagement should start.
Do they hand over source code? If the contract does not specify source code delivery, the operator is renting software. For remediation tracking that has to outlive the developer relationship, ownership is non-negotiable.
Have they built for the regulatory framework the operator works under? Building for EPA Superfund is different from building for state DEP. Building for OSHA HazCom is different from building for USDA APHIS. The right developer can name the specific frameworks in their delivered work, not in generic marketing copy.
Do they support post-deployment when regulations change? Regulations change. CERCLA scope changed in 2024 with the PFAS hazardous designation. The 2026 PFAS Destruction and Disposal Interim Guidance from EPA shifted from triennial updates to annual updates.6 A custom remediation system needs a support relationship that handles those changes within weeks, not quarters.
Will the operator's actual user talk to the developer's actual engineer? Operators have been burned by sales engineers who promised one thing and delivery teams who built another. The right answer is that the same person who scopes the project is involved through delivery.
Are they willing to walk away if custom is the wrong answer? A custom development firm that recommends SaaS when SaaS is the right answer is a custom development firm worth hiring. PCG turns down projects that should not be custom. That is not a weakness, it is a filter.
Which path fits your remediation operation?
Full Custom Development if
Your regulatory exposure or operational scale needs software built around your process.
- Active EPA Superfund or CERCLA cleanup with chain-of-custody requirements
- Multi-jurisdiction reporting across three or more state DEP programs
- Specific lab LIMS or field instrumentation that no SaaS supports
- Decade-long regulatory audit cycles requiring source code ownership
- Fortune 100 / Fortune 500 facility with non-standard data architecture
FireFlight Accelerated Custom if
You need a tailored system fast and your workflow is close to a known pattern.
- Mid-size environmental consultancy with standard remediation workflow
- Compliance tracking across permits, certifications, and audit deadlines
- Need scheduling, dispatching, document tracking from day one
- Field-to-office task handoff with low-connectivity tablet support
- Want custom output without starting engineering from a blank page
The free diagnostic consultation tells you which path fits your situation.
A note on FireFlight, PCG's faster path to a custom system
For operators who need a tailored system but cannot wait the timeline a fully custom build requires, PCG offers FireFlight: a faster path to a custom system, built on PCG's engineering foundation and configured to the operator's specific workflow.7 FireFlight is not off-the-shelf. It is custom delivery accelerated by reusable modules PCG has built over thirty years of project work. It applies when the operator's process is close enough to a known pattern that the engineering does not have to start from a blank page.
For Superfund operators, multi-jurisdiction environmental consultancies, and EHS-driven industrial operations with unique regulatory exposure, the answer is usually full custom development. The diagnostic engagement determines which path fits.
Start with a free diagnostic consultation.
PCG will map your current remediation tracking workflow, assess your regulatory exposure, and tell you whether custom development, FireFlight accelerated build, or a SaaS platform is the right answer. No commitment required.
Frequently Asked Questions
At minimum, a 2026 remediation tracking system supports EPA Superfund and CERCLA reporting, RCRA hazardous waste documentation, state DEP environmental compliance, and the new PFAS reporting framework opening in 2027. Operators in specific industries also need OSHA HazCom 2012 / GHS alignment for chemical handling, NPDES discharge permits, and applicable state-level air and water quality programs.
Yes. PCG has built source-to-destination chain of custody systems for active EPA Superfund cleanups, tracking contaminated soil from excavation through transport, treatment, and final disposal. The system produces the regulatory output that EPA Superfund program officers expect during oversight.
SaaS platforms are designed for the operator's process to match the platform. Custom software is designed for the platform to match the operator's process. SaaS wins for small, standard operations. Custom wins when the operator has multi-jurisdiction reporting, specific instrumentation integrations, or a regulatory audit cycle that runs longer than any SaaS vendor's product roadmap.
The client owns the source code. PCG delivers source code ownership as a contractual term, not as a marketing claim. This is non-negotiable for remediation systems that need to support decade-long regulatory audits.
Project length depends on the complexity of the operation, the number of regulatory frameworks the system has to satisfy, and the state of the existing data. A small operation tracking a single Superfund site with a documented spreadsheet workflow is a different project than a multi-site environmental services firm with twenty years of historical data across three state DEP jurisdictions. PCG starts every project with a free diagnostic consultation that establishes the scope before any development quote is given. The written scope document, not a guess, is what determines the timeline.
Yes. PCG provides ongoing support relationships with environmental operators where regulatory changes are part of the operating environment. When CERCLA scope expanded in 2024 to include PFOA and PFOS, when EPA shifted the PFAS Destruction and Disposal Interim Guidance to annual updates in 2026, PCG-built systems were updated to match. The support model is part of the engagement, not an upsell.
1 U.S. Environmental Protection Agency, Designation of Perfluorooctanoic Acid (PFOA) and Perfluorooctanesulfonic Acid (PFOS) as CERCLA Hazardous Substances, final rule effective July 8, 2024. epa.gov/superfund/designation-perfluorooctanoic-acid-pfoa-and-perfluorooctanesulfonic-acid-pfos-cercla
2 U.S. Environmental Protection Agency announcement, September 17, 2025, retaining PFOA and PFOS CERCLA designation and developing Section 102(a) Framework Rule. Reported by Babst Calland, September 2025.
3 STL.News, EPA to Reexamine Eight Superfund Sites in 2026 to Ensure Cleanups Still Protect Communities, February 2026.
4 Lab Manager, EPA Delays Trichloroethylene (TCE) Exemption Requirements to 2026, November 2025.
5 New Jersey Business and Industry Association, EPA Changes Submission Date on Proposed PFAS Reporting Rule, April 2026.
6 U.S. Environmental Protection Agency, 2026 Interim Guidance on the Destruction and Disposal of PFAS, April 2026.
7 Phoenix Consultants Group, FireFlight Project Overview, phxconsultants.com/fireflight-project/, accessed May 2026.
This article is informational and reflects regulatory information current as of May 2026. It is not legal, regulatory, or compliance advice for any specific operation. Operators with active EPA Superfund, CERCLA, RCRA, state DEP, or related obligations should consult their regulatory counsel and the relevant agency directly for guidance on their specific situation. Phoenix Consultants Group founded 1995.