top of page
Environmental Risk Assessment Review: What Matters

Environmental Risk Assessment Review: What Matters

core-env
Sep 24
6 min read

A property can appear straightforward until a sampling result, historic aerial photograph, or regulatory file changes the decision. An environmental risk assessment review is the point where environmental data must become a clear business position: proceed, investigate further, adjust the deal, control the risk during construction, or develop a path to closure. For buyers, lenders, developers, insurers, and counsel, the quality of that review often matters more than the volume of material collected.

The objective is not to eliminate every uncertainty. Environmental work rarely offers that option at the beginning of a project. The objective is to identify material exposure, distinguish it from manageable uncertainty, and define actions that are technically defensible, commercially proportionate, and aligned with the applicable regulatory framework.

What an Environmental Risk Assessment Review Should Answer

A useful review does more than restate conclusions from a Phase I Environmental Site Assessment, Phase II investigation, remediation report, or consultant memorandum. It tests whether the available record supports the decision being made.

For a commercial acquisition, that may mean determining whether a recognized environmental condition has been adequately investigated and whether remaining uncertainty should affect pricing, indemnities, escrow, or post-closing obligations. For a redevelopment project, the focus may shift to soil handling, dewatering, vapor intrusion, utility installation, worker protection, and schedule risk. For an operating industrial facility, the central issue may be whether known impacts are stable, migrating, reportable, or likely to trigger corrective action.

The review should answer several connected questions: What is known about releases or potential releases? What pathways could create human health, ecological, regulatory, or financial exposure? What data gaps remain? Are prior conclusions still reliable given site conditions and planned use? What is the practical cost and timeline of addressing the risk?

Those answers require judgment. A report may identify petroleum-impacted soil but provide little basis for assessing groundwater conditions. Another may show groundwater impacts but lack enough well coverage to establish whether the plume is stable or leaving the property. Neither issue automatically stops a transaction. Each does, however, affect the terms, investigations, and risk controls needed to proceed responsibly.

Start With the Decision, Not the Document Stack

Environmental files often accumulate over decades. A review can include historical environmental reports, regulatory correspondence, laboratory data, boring logs, groundwater monitoring records, permits, spill reports, site plans, and construction documents. Reading each document in isolation can produce a technically accurate chronology without answering the client’s actual question.

The review should begin by defining the decision and deadline. Is a lender evaluating collateral risk? Is a purchaser seeking liability protection? Is a developer planning excavation within 60 days? Is counsel assessing the strength of a claim or allocation of responsibility? The scope, level of certainty, and recommended next step should follow from that context.

A transaction-sensitive review may focus on liability pathways, cleanup obligations, and unresolved conditions that could impair value. A pre-construction review needs a tighter focus on subsurface conditions within planned work areas, disposal characterization, dewatering requirements, and contractor controls. A regulatory strategy review may prioritize the conceptual site model, agency expectations, and the evidence needed to support closure.

Speed matters, but a fast review should not become a superficial one. The most efficient work targets the issues that can materially alter cost, schedule, liability, or regulatory posture. That is different from summarizing every environmental event ever documented at a property.

Evaluate the Conceptual Site Model

The conceptual site model is the working explanation of how a release may have occurred, where contaminants are located, how they move, and who or what could be exposed. It is the foundation of a sound environmental risk assessment review, even when it is not labeled as such in the existing reports.

A credible model considers the source area, contaminant type, media affected, migration pathways, receptors, and current or future land use. For example, a former dry cleaner may raise concerns about chlorinated solvents in soil gas and groundwater, while a former fueling operation may require attention to petroleum hydrocarbons, groundwater impacts, and utility corridor migration. The site history changes the investigation strategy.

Hydrogeologic conditions can be decisive. Groundwater depth, flow direction, permeability, seasonal variation, nearby surface water, drainage features, and the presence of preferential pathways all influence whether impacts are likely to remain localized. A single groundwater sample rarely resolves those questions. Conversely, extensive monitoring data may still be inadequate if well locations do not test the most plausible downgradient direction.

The review should also challenge assumptions tied to future use. A condition that is manageable for an industrial property may require additional evaluation for residential redevelopment, childcare use, or a project with enclosed occupied spaces. Vapor intrusion, soil exposure, and groundwater use assumptions can change materially when the development plan changes.

Data Quality Is a Business Issue

Laboratory results do not speak for themselves. Detection limits, sampling methods, sample locations, analytical suites, quality-control documentation, and the age of the data affect how much confidence can be placed in a conclusion. Older reports may have been prepared under standards or cleanup criteria that have since changed.

This does not mean every historic dataset must be recreated. It means the reviewer should identify whether the dataset is fit for its intended purpose. If a major financing or construction decision depends on it, uncertainty should be explicit rather than buried in an appendix.

Separate Regulatory Status From Actual Risk

A common mistake is treating regulatory silence, a closed file, or the absence of a listed case as proof that no risk remains. Regulatory status is relevant, but it is not the entire analysis. Files can be closed based on land-use restrictions, limited scope, agency priorities, or information available at the time. Some historic releases may never have entered a formal cleanup program.

The reverse is also true. An open case does not necessarily mean a site is unsuitable for acquisition, development, or lending. It may indicate that the responsible party is actively addressing a defined condition under an approved work plan. The key question is whether the regulatory path is understood, adequately funded, and compatible with the project schedule.

A review should identify applicable federal, state, and local considerations without overpromising an outcome. In Texas, Delaware, and throughout the Delmarva Peninsula, program requirements, agency practices, and cleanup expectations can vary by jurisdiction and site setting. Local knowledge helps translate technical findings into a practical strategy rather than a generic recommendation for more investigation.

Convert Findings Into Actionable Risk Controls

The value of the review lies in what happens next. Recommendations should be prioritized by decision impact, not simply listed in the order issues appeared in the files.

For some projects, the appropriate action is targeted delineation before closing or before finalizing a purchase agreement. For others, a limited soil management plan, vapor mitigation design allowance, environmental escrow, or access agreement may be a more proportionate response. Where conditions are well characterized, the focus may be on advancing a remedial strategy and documenting progress toward regulatory closure.

Cost estimates deserve careful treatment. A low initial estimate can be misleading if it excludes offsite disposal, groundwater treatment, extended monitoring, agency coordination, engineering controls, or construction delays. At the same time, broad contingency figures without a defined technical basis can unnecessarily impair a transaction. A defensible range should explain what is included, what could change it, and what additional information would narrow the uncertainty.

Contractual protections should align with the technical record. Environmental indemnities, escrows, representations, insurance, and access rights can allocate financial risk, but they do not make contamination disappear or guarantee that a remedy can be completed on schedule. Technical strategy and deal strategy need to be developed together.

When a Second Review Is Worth the Time

An independent review is especially valuable when an environmental conclusion will support a high-consequence decision, when prior work is dated or incomplete, or when the consultant’s scope was limited by a prior client’s objectives. It can also help when technical findings and business expectations do not match - for example, when a supposedly minor condition carries a large construction contingency, or when a reassuring report does not explain obvious data gaps.

Senior-level review can be most useful at these inflection points because it brings experience to the interpretation, not just the collection, of data. The task is to identify the shortest credible path to the information and controls a project actually needs.

A disciplined environmental risk assessment review gives decision-makers a clearer basis for acting under uncertainty. Before capital is committed or ground is broken, ask whether the environmental record explains the risk well enough to support the decision in front of you. If it does not, the next investigation should be focused, purposeful, and tied directly to the outcome the project requires.

 
 
 

Comments


bottom of page