Infrastructure
When a Water Utility’s Consulting Team Changes, Protect the Project Memory
A leadership change at a major water firm offers a useful reminder that utilities need durable records, not just familiar contacts.

Water infrastructure projects often last longer than the working relationships that launched them. A utility may spend years studying a treatment upgrade, replacing mains or planning for new regulations. During that time, consultants can be promoted, reassigned or replaced. Utility employees and board members can change, too.
Water Finance and Management reported that Stantec has appointed Kari Shively to oversee its North American water business beginning Oct. 1. The report, written by WFM Staff, says Shively has more than 33 years of water-sector experience and has led multidisciplinary teams. The Stantec leadership announcement concerns one company, but it points toward a broader operational question for Midwest utilities: What happens to project knowledge when the people overseeing the work change?
The answer should not depend on somebody remembering an old conversation.
Separate the relationship from the record
Water projects generate formal documents such as contracts, engineering reports, plans, permits and construction specifications. Yet some of the most useful knowledge can remain scattered across meeting notes, email threads and individual recollections.
Why was one pipe route selected over another? Which assumptions were used to estimate future demand? Did operators raise concerns about access to a proposed valve or pump? Was an alternative rejected because of cost, land ownership, maintenance or permitting?
If those answers are not collected in the utility’s files, a personnel transition can reopen decisions that were already examined. That can consume staff time and make it difficult for a governing board to distinguish a genuinely new problem from an old question with a missing answer.
A practical project record should identify the decision, the alternatives considered, the information available at the time and the person or body that approved the choice. It does not need to reproduce every conversation. It needs to preserve the reasoning well enough that someone new can understand it.
Make the utility the keeper of its own history
Consultants commonly provide essential technical capacity, especially for small systems that cannot employ specialists in every field. But the utility remains responsible for operating the finished system. Its records should therefore be complete enough to follow the project without relying on a particular consulting employee’s inbox.
For each active project, the utility can maintain one current index showing the contract, scope, schedule, budget, major decisions, pending questions and responsible contacts. The index should point to the underlying documents rather than trying to replace them.
File names and version dates matter. A folder containing several documents labeled “final” can create uncertainty during construction or permit review. The record should show which version was approved, whether later revisions superseded it and who received the change.
Utilities should also retain the assumptions behind calculations. A capacity recommendation may depend on projected demand, operating hours, source reliability or storage targets. The number alone is less useful than the conditions that produced it.
Use transitions as a checkpoint
When a consulting team changes, the utility can request a short transition meeting focused on unfinished work. The agenda should cover upcoming deadlines, decisions awaiting utility action, agency coordination, construction questions and any risks that have not been resolved.
This is also a good time to verify who can authorize changes. A new project leader may coordinate the work, but contract amendments and additional spending should still follow the utility’s established approval process. Clear authority protects both sides from informal instructions being mistaken for approved work.
Operators belong in the handoff. Engineers may design a facility, but operators will encounter its controls, alarms, sampling points and maintenance spaces every day. Their unresolved questions should appear in the same transition record as schedule and budget issues.
Explain the household boundary clearly
Residents may hear about a utility project and assume it covers every pipe or device associated with their water. Public infrastructure and household equipment are usually separate responsibilities. A utility project may improve a main, treatment plant or public service connection without repairing private plumbing, a water heater or an appliance inside the house.
Utilities can reduce confusion by stating where public responsibility ends and private responsibility begins. Homeowners reviewing their own maintenance plans may separately consider coverage for home systems and appliances, but that decision should not be confused with the scope of a municipal water project.
Leadership changes are ordinary. Lost reasoning does not have to be. A utility that keeps decisions, assumptions and responsibilities in an accessible record can change consultants or project leaders without forcing the community to pay for the same institutional knowledge twice.