Skip to content

Systems and records

Environmental remediation administrative data: the approval evidence behind each change

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

A remediation project change needs its approval evidence linked to it: the request and reason, the classification that set the approval path (minor, significant or fundamental after a Superfund decision, or a permit modification class), the approving authority's decision, any revised quality plan, and field or lab records showing what was done. Environmental remediation administrative data without that chain records status, not decisions, and cannot train or test an AI system.

Provenance trail

Environmental remediation

This page covers environmental remediation administrative data: the approval evidence behind each change.Illustrative

Key takeaways

  • A remediation change is evidence only when the request, classification, approval and measured outcome are linked.
  • The classification step decides the approval path and is the judgment most change logs fail to record.
  • Each case must be judged against the decision document, permit and quality plan revision in force on the request date.
  • Outcome labels come from confirmation data and later reviews, not from a schedule marking the task complete.
  • Public administrative records and a consultant's internal files carry different confidentiality and privilege screens.

What approval evidence belongs with changes to a remediation project?

Every change needs four linked pieces of evidence: the request and its reason, the classification that decided which approval path applied, the approving authority's decision on that path, and the field or laboratory record showing what was actually done. A change log entry that says excavation expanded, approved is a status, not evidence.

Classification is the step most records skip and the one that matters most. Under federal Superfund rules, a change after the record of decision is minor, significant or fundamental, and each category carries a different document, audience and level of public involvement. Under a hazardous waste permit, the permittee's change falls into a modification class with its own approval steps. A case that does not show which category the team chose, and why, cannot teach or test the judgment.

This page is about administrative records: requests, classifications, approvals, plan revisions and the documents that close them out. It is not engineering or regulatory advice; the right classification for a real site is a call for the project's qualified professionals and the lead agency.

Which records does a remediation change touch?

A single change usually touches records in four places: the regulatory decision file, the quality plan, the contract file and the field data system. The table maps them so a case can be assembled from the systems where each record actually lives.

Assemble by date, not by folder. Put every record about the change on one timeline, from the first field observation that prompted it to the last confirmation result, and note which version of each controlling document was in force at each point. Gaps on that timeline, such as work that started before the approval date, are findings in their own right and belong in the packet rather than being tidied away.

Which records does a remediation change touch?
RecordWhere it usually livesWhat it provesTypical owner
Decision document (ROD or permit)Agency administrative record and project fileThe baseline the change departs fromLead agency or permitting authority
Change request and rationaleProject management system or correspondence fileWhy the change was proposed and by whomProject manager
Classification memo or ESD or amendmentPost-decision file or administrative recordWhich approval path appliedLead agency with the consultant
Permit modification request and responsePermit file and agency correspondenceClass chosen and the agency's actionPermittee and regulator
Revised quality assurance project planDocument control systemSampling and analysis changes were approvedQuality assurance manager
Contractor change orderContract or ERP systemScope and schedule change to the workContracts administrator
Field logs, lab results and as-built recordsField data system such as EQuIS, and lab reportsWhat was done and measuredField lead and data manager
Five-year review or closeout reportAgency record and project fileWhether the changed remedy performedLead agency

Why must the classification call be in the record?

Because the category decides the approval path, a case without it hides the judgment the record is supposed to capture. EPA's guide to Superfund decision documents sorts post-ROD changes into non-significant or minor, significant and fundamental. Minor changes are recorded in the post-decision document file, significant changes in an explanation of significant differences, and fundamental changes in a ROD amendment.

The regulation draws the line by effect. Under 40 CFR 300.435(c)(2), an explanation of significant differences is published when a change significantly alters the remedy's scope, performance or cost without fundamentally altering it, and a ROD amendment is proposed when the change fundamentally alters the remedy's basic features.

Hazardous waste permits use classes instead. Under 40 CFR 270.42, permittee-requested modifications are Class 1, 2 or 3; some Class 1 changes need the Director's prior written approval, and Class 2 and Class 3 requests go through a 60-day public comment period. Quality plans have their own gate: EPA's Quality Assurance Project Plan Standard requires approval before environmental information work begins, and significant changes may need a revised plan approved before work proceeds under the new conditions.

State cleanup, voluntary and brownfield programs set their own change procedures, and a single firm may work under several of them in one year. The packet should therefore name the program and the rule the team applied, rather than assuming the federal categories. A model trained on cases that mix programs without saying so will learn an average approval path that no regulator actually uses.

What fields does a reviewed remediation change packet need?

Each packet is one change, assembled so a model or a reviewer can reach the decision from the starting state and check it against what happened. A domain reviewer with remediation experience confirms the classification and outcome fields before a packet is used. The fields below can be used as a template as is.

  • One change per packet; a request that bundles several changes is split, with a shared reference so they can be read together.
  • Every field cites the record behind it by document identifier and date, so a reviewer can reopen it.
  • The classification field keeps the team's original call even when the agency later changed it, with the correction in the approvals field.
  • Outcome is left blank, and the packet held back, until measured results exist; a scheduled completion date is not an outcome.
  • Reviewer disagreements on classification are recorded, not resolved by vote, and such packets are tagged as contested.
What fields does a reviewed remediation change packet need?
FieldContentLinked evidenceChecked by
Case scopeSite type, program, project phase and the one change coveredProject file indexData preparer
Starting stateDecision document version, permit or QAPP revision in force on the request dateDated copies of each documentData preparer
Change requestWhat changed, why, who proposed it and whenRequest memo or correspondenceData preparer
Operating constraintsProgram rules, schedule commitments, access or seasonal limitsAgreement, order or permit conditionsDomain reviewer
ClassificationCategory or class chosen and the reasoningClassification memo, ESD, amendment or modification requestDomain reviewer
ApprovalsWho approved, under what authority, on what dateAgency letter, signed ESD or permit action, QAPP approval pageDomain reviewer
Documents updatedPlans, contracts and records revised because of the changeRevision history in document controlData preparer
OutcomeWhat was done and measured, and whether it met the changed objectiveField logs, lab results, as-built or review reportDomain reviewer
Real or illustrativeWhether the packet is a real cleared case or constructedRights review recordRights reviewer
Rights and confidentialityClient permission, privilege screen, removed identifiersEngagement terms and review logRights reviewer

How should an illustrative excavation that grew during design be classified and closed?

This case is illustrative; the site, quantities and dates are invented. During remedial design at a former plating facility, delineation sampling shows the soil requiring removal is about 20 percent larger than the volume estimated in the decision document, and two additional metals exceed cleanup levels in one area.

Starting state: the record of decision selected excavation and off-site disposal, and the approved quality plan lists the original analytes. The consultant's change request proposes the larger excavation footprint and adds the two metals to confirmation sampling. The project team classifies the volume change as minor, because the remedy, cleanup levels and disposal method are unchanged, and records it in the post-decision file. The analyte addition is a significant quality plan change, so a revised plan goes to the approving authority before confirmation sampling begins.

Outcome check: confirmation samples from the expanded floor and walls, analyzed for the full analyte list, meet the cleanup levels, and the as-built drawing shows the final footprint. The packet's outcome label comes from those results, not from the project schedule marking the task complete.

  • Counterexample (illustrative): at another site a team logged a change of treatment technology as minor. The agency later required an explanation of significant differences because the change altered how the remedy would perform. The packet for that case keeps both the original classification and the agency's correction, because the disagreement is the lesson.
  • Exception: if the classification depended on a site-specific risk calculation, keep the conclusion and its approval, not the calculation, unless a qualified reviewer can confirm it.

What does a generic change-order example miss about remediation work?

It misses the version in force on the date of the decision. A generic change-order example treats the plan or permit as fixed text, while a remediation change is judged against the decision document, permit condition and quality plan revision that applied when the request was made, and those change over a project's life.

The second constraint is who may approve. A consultant can recommend a classification, but the lead agency or permitting authority decides what the change requires, and some approvals must exist before the work starts. A packet that records the contractor's change order approval but not the regulator's action teaches the wrong authority.

The third is public participation. Significant and fundamental Superfund changes, and higher-class permit modifications, carry notice or comment steps. The packet should show whether those steps happened, because a change made before them is a different case from one made after.

Which records prove the decision, and the outcome years later?

The decision is proven by the document the approval path requires: the post-decision file entry for a minor change, the signed explanation of significant differences or ROD amendment, the agency's action on a permit modification, or the approval page of a revised quality plan. Correspondence that discusses a change without a decision document is context, not proof.

The outcome is proven by measured results, and sometimes only years later. For Superfund sites, 40 CFR 300.810 lists what the administrative record typically contains, including verified sampling data with quality control and chain of custody records, the proposed plan, public comments and responses, and decision documents. When a remedy leaves hazardous substances on site above levels that allow unlimited use and unrestricted exposure, EPA conducts five-year reviews, and later reviews are triggered by the previous report's signature date. Those reviews are often the best outcome evidence a changed remedy ever gets.

What has to be screened before a remediation case leaves the firm?

Screen for client confidentiality, privilege and identifiable people before anything else. Much of a Superfund administrative record is public, but the consultant's own files also hold client communications, draft classifications, cost data and legal strategy that were never meant to leave the engagement.

Separate three questions: whether the firm can access the records, whether privacy rules allow the intended use, and whether the client agreement and the firm's ownership of its work product allow licensing. De-identifying site names and people reduces privacy risk but does not create a licensing right that an engagement letter withheld.

  • Remove or generalize site addresses and parcel identifiers unless the record is already public and the client agrees.
  • Exclude documents prepared at counsel's direction or marked privileged.
  • Drop names of residents, landowners, workers and agency staff from correspondence and field notes.
  • Exclude cost-recovery, enforcement and settlement strategy documents.
  • Confirm laboratory reports can be shared under the lab's and the client's terms.

Can a remediation firm license its change and approval histories?

Remediation consultancies and contractors hold years of change requests, classifications, approvals and outcomes that show how regulated decisions are made in practice. Packaged as reviewed task packets with rights cleared, those histories are a specific, defensible dataset rather than a dump of project files.

A consultancy that licenses such packets through SourceX hands over the rights review, contract, preparation, delivery and payment work. Multi-terabyte project archives are not hosted by SourceX; they stay in the firm's own storage or travel on encrypted drives. The firm learns whether it qualifies from a short company assessment, with no project files uploaded.

Frequently asked questions

What should a remediation change task packet include?

Case scope, the starting documents in force, the change request, operating constraints, the classification and its reasoning, approvals with authority and dates, documents updated, the measured outcome, whether the case is real or illustrative, and the rights screen. Each field should link to the record that supports it.

What is an explanation of significant differences?

It is the Superfund document that records a change which significantly alters a selected remedy's scope, performance or cost without fundamentally altering it. A change that fundamentally alters the remedy's basic features calls for a ROD amendment instead.

Is a contractor change order enough approval evidence?

No. It shows the contract was changed, but the regulatory approval path depends on how the change was classified and what the lead agency or permitting authority decided. A packet needs both, linked.

Are Superfund administrative records public?

Much of the administrative record for a response decision is made available to the public, but privileged documents are generally excluded and the consultant's own project files are not part of it. Those internal files need a client and confidentiality review before any use.

Can an environmental firm license its remediation change histories?

Sometimes. It depends on the engagement terms, privilege, and how much client-identifying detail can be removed while keeping the decision intelligible. Counsel and the client relationship owner should review a sample before any packet is prepared.

Sources

  • EPA's guide to Superfund proposed plans and records of decision (EPA 540-R-98-031) sorts post-ROD changes into non-significant or minor, significant, and fundamental; minor changes are recorded in the post-decision document file, significant ones in an ESD and fundamental ones in a ROD amendment. Source
  • Under 40 CFR 300.435(c)(2), an explanation of significant differences is published when a change significantly alters the selected remedy's scope, performance or cost without fundamentally altering it; a ROD amendment is proposed when the change fundamentally alters its basic features. Source
  • 40 CFR 300.810 lists what the administrative record file for selecting a response action typically contains, including verified sampling data with QA/QC and chain of custody records, the proposed plan, public comments and responses, and decision documents, with an index. Source
  • Under 40 CFR 270.42, RCRA permit modifications fall into Class 1, 2 and 3; some Class 1 changes need the Director's prior written approval, and Class 2 and 3 requests go through a 60-day public comment period. Source
  • EPA's Quality Assurance Project Plan Standard (CIO 2105-S-02.1) requires QAPP approval before environmental information operations begin, and significant changes may need a revised plan approved before work under the changed conditions. Source
  • EPA's five-year review page explains that a statutory review is triggered when a remedial action leaves hazardous substances on site above levels allowing unlimited use and unrestricted exposure, and later reviews are triggered by the previous report's signature date. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies