Retiring Expertise, Lingering Risk: Capturing Field Judgment Before the Crew Changes
The environmental field has a retirement problem that is easy to measure and hard to solve. Experienced scientists, remediation supervisors, and compliance managers are leaving the workforce, and they are taking with them something that rarely appears in a standard operating procedure: judgment. A junior geologist can learn a sampling method from a manual. Learning why a particular PFAS sampling location was moved, why a regulator was comfortable with one line of evidence but not another, or why a crew stopped excavation before reaching a predicted boundary requires something slower and more deliberate.
That gap matters more in 2026 because PFAS work is still evolving. Methods change, regulatory expectations vary across states, and site histories are often incomplete. The people who have spent decades interpreting those conditions are the same people now approaching retirement. Firms that treat knowledge transfer as an exit-interview formality will discover the loss later, when a project hits a decision point and no one can explain the reasoning behind the original approach.
The knowledge that leaves first is judgment
Most organizations are good at capturing procedures. They are less good at capturing thresholds, exceptions, and the stories behind them. A decision log can help. For each significant field or regulatory decision, record the date, the decision, the alternatives considered, the data available at the time, the people consulted, and the rationale. The log should not be a polished narrative written after the fact. It should be a working record that captures uncertainty.
For PFAS projects, decision logs are especially useful around sampling design, analytical method selection, treatment-train choices, and communication with regulators. A log that says moved monitoring well from A to B is nearly useless. A log that says moved well because the original location intersected a utility corridor and the alternate location preserved upgradient coverage preserves the reasoning.
Pair people before the retirement date is fixed
Paired shadowing is more effective when it starts early. Pair a senior field lead with a junior staff member for a full project cycle, not a single site visit. The junior person should observe not only fieldwork but also client calls, agency meetings, and internal debates. The senior person should narrate decisions in real time and allow the junior person to lead portions of the work while still in the room.
Reverse mentoring belongs in the same program. Early-career staff often understand new data tools, remote sensing, and electronic chain-of-custody systems better than senior staff. A transfer program that runs only one way misses the chance to build mutual credibility.
Cross-vendor training is an underused lever
Environmental projects are delivered by networks of consultants, laboratories, drillers, and remediation contractors. Knowledge often sits at the seams between organizations. EPVA members can convene short, scenario-based sessions in which a laboratory specialist explains how a sampling plan affects data usability, a remediation contractor explains constructability constraints, and a consultant explains regulatory expectations. These sessions should be recorded and summarized, but the main value is the conversation.
Cross-vendor training also reduces key-person risk. If a client's longtime consultant retires, the laboratory and drilling contractor may still hold useful project history. A simple annual project-history review, attended by the prime vendor and its subcontractors, can surface details that no single organization's file contains.
Document judgment calls, not just outcomes
Many closeout documents record what was built, not why. A better practice is to add a short judgment-call appendix to project closeout. It can list the three to five decisions that most shaped the project, the information available, the alternatives rejected, and what the team would do differently. This appendix becomes a training artifact and a risk-management record.
For compliance roles, capture regulatory negotiation history. Which agency staff were involved, what concerns were raised, what commitments were made, and which interpretations were accepted? These details are often held informally by one person. When that person leaves, the organization may retain the permit but lose the context needed to defend it.
Measure transfer, not attendance
A knowledge-transfer program that measures completion of an exit form will not tell leadership whether capability remains. Measure instead how many key roles have a named backup; how many critical decisions have a documented rationale; whether a junior employee can lead a mock agency meeting; and whether project teams can answer questions about an inherited site without calling a retiree. These indicators are imperfect, but they are more useful than counting training hours.
The association's view
EPVA's perspective is that knowledge transfer is a risk-management function, not a human-resources formality. Firms and vendors that treat it as such will protect project continuity, reduce costly rework, and preserve the professional standards that clients rely on. The retirement wave is already here. The question for 2026 is whether organizations will capture judgment while the people who hold it are still available to explain it.
