Wastewater Infrastructure is too important to run on outdated Project Controls
- Admin

- Apr 21
- 5 min read
Updated: 4 days ago

There is a particular kind of pressure that comes with managing capital projects for a public water and wastewater utility.
It is not just the pressure of keeping a project on schedule and within budget though that pressure is very real. It is the pressure of knowing that every dollar overspent is a dollar that came from ratepayers. That every month of delay is a month where aging infrastructure stays in service longer than it should. That every claim or dispute that lands on a lawyer's desk is a failure that could have been caught earlier, managed better, or avoided altogether.
I have worked with public agency project teams long enough to know that the problem is rarely a lack of effort or expertise. The engineers are skilled. The project managers are experienced. The intentions are good.
The problem is almost always the same: The project controls framework has not kept pace with the complexity of the program.
For an Utilities Agency managing an ambitious capital improvement program across water recycling, wastewater treatment, and regional infrastructure that gap between program complexity and controls capability is where budgets leak, schedules slip, and claims get born.
The challenges I see repeatedly in Utility Capital Programs
1. Cost reporting that is always looking backwards
On too many utility projects, cost reports tell you what happened last month. By the time the data is compiled, reviewed, and distributed, the project has moved on. Decisions are being made today based on information that is four to six weeks old. This is not a data problem. It is a process and structure problem. When cost control is treated as a reporting function rather than a management function, it loses its value. The report becomes a historical document, not a decision-making tool.
What it should look like: cost forecasting that is updated continuously, with clear cost-to-complete estimates tied to the current schedule, so that project managers can see where they are headed not just where they have been, This can be linked to implementing of Earned Value Management system.
2. Schedules that exist but do not Control
I have seen beautifully built schedules that nobody uses. They are created at the start of a project, baselined, and then quietly abandoned as the project takes on a life of its own. Progress updates become disconnected from the underlying logic. Float disappears without explanation. Milestones slip without formal analysis of cause or impact. A schedule that is not actively maintained and interrogated is not a project controls tool. It is a document. And a document cannot tell you that a six-week delay in a biosolids handling upgrade is going to push your startup commissioning past a regulatory compliance deadline.
For utilities agencies, where projects often intersect with state and regional water quality requirements, an unmaintained schedule is not just a project risk it is a compliance risk.
3. Change management that happens after the damage is done
Change is inevitable on wastewater infrastructure projects. Subsurface conditions, regulatory shifts, supply chain disruptions, design revisions these are not exceptions. They are part of the work. The question is not whether changes will happen. The question is whether your change management process catches them early enough to control their cost and schedule impact, or whether you find out at project closeout when the contractor submits a claim for $2 million in cumulative impact costs that nobody saw coming.
Weak change management processes unclear entitlement thresholds, slow approval workflows, inadequate documentation of owner-directed changes do not prevent claims. They manufacture them.
4. Delay Analysis that starts too late
By the time a formal delay analysis is commissioned on most public agency projects, the project is already in dispute. Records are incomplete. Daily reports are missing. The as-built schedule has to be reconstructed from fragments. Delay analysis should not be something you do when a contractor files a claim. It should be a continuous part of your project controls process tracking actual versus planned progress, documenting delay events as they occur, and maintaining the records that would be needed if a claim ever did materialize.
An agency that manages delay proactively does not just defend itself better in disputes. It avoids most disputes altogether, because the contractor knows the record is being kept and the agency knows what it owns.
5. Fragmented Information across too many systems
On many utility capital programs, schedule data lives in one place, cost data lives in another, risk registers live in a spreadsheet that one person maintains, and field reports are somewhere in an email inbox. Nobody has a complete picture, and assembling one requires hours of manual work.
When information is fragmented, problems hide in the gaps. A cost variance that would be obvious in an integrated dashboard stays invisible until it is too late to course correct. A schedule risk that the field team flagged in a daily report never makes it into the risk register. A change order that was approved verbally never gets properly documented.
What better Project Controls actually looks like?
None of what I have described above requires a complete overhaul of how an agency operates. In my experience, the most effective improvements are targeted, practical, and implemented without disrupting the work that is already in progress.
A living cost forecast, not a static budget tracker. Cost control that compares earned value against actual spend, projects cost-to-complete based on current productivity and remaining scope, and flags variances before they become overruns.
A schedule that is maintained, analyzed, and used. Regular schedule updates with documented logic changes, float analysis, and a clear picture of critical path. Not a snapshot a live management tool.
A change management process with teeth. Clear thresholds for what requires formal documentation, a workflow that moves quickly enough to keep pace with the project, and a contemporaneous record that protects the agency's interests whether or not a claim ever materializes.
Proactive delay event tracking. Recording the cause, responsibility, and schedule impact of delay events as they happen not reconstructing them after the fact. This is the difference between managing delays and litigating them.
Integrated reporting that gives decision-makers a real picture. A dashboard that brings together schedule performance, cost performance, change order status, and risk exposure in one place so that the people who need to make decisions can make them on current information.
A different way to think about Project Controls
Project controls is not a back-office function. It is not the team that produces the monthly report. Done well, it is the early warning system that tells a project manager three months before a milestone that they are in trouble and gives them enough time to do something about it. It is the cost forecasting process that tells a finance director whether the current budget is still realistic. It is the delay documentation process that protects an agency's interests when a contractor's claim lands on the table.
For a public utility with a significant capital program and real accountability to the communities it serves, investing in that capability is not overhead. It is risk management.
Is your Project Controls framework working for you?
If your project reports are telling you what happened last month instead of where you are headed. If your schedule is being updated but not really managed. If change orders are piling up faster than they are being evaluated. If you have a sense that a claim is building somewhere on one of your active projects but you are not sure where.
These are not small problems. They are signals that your controls framework needs attention.
At KARA Consults we work with project owners and public agencies to build project controls frameworks that are practical, right-sized, and actually used by the teams running the work. Cost control, scheduling, delay analysis, and claims support built around your program, not a generic template.
What is the biggest project controls challenge your team is navigating right now? I'd welcome the conversation.
KARA Consults provides construction project controls, project scheduling, cost control, delay analysis, and construction claims services. We work with project owners, contractors, and public agencies across the infrastructure and utilities sector.
.jpg)

Comments