How stronger field-level decision making improves safety on water infrastructure projects
Editor's note: The following article deals with ensuring safety on a job site. As such, WaterWorld editor's agreed to not edit the article in any way per the contributor agreement. The original article appears as it was submitted below.
There is no margin for error on water and wastewater jobsites, where crews are working inside live systems that carry immediate safety exposures and, if disrupted, can impact public health.
Electrical tie-ins and process cutovers put personnel in direct contact with energized equipment, pressurized lines and active flow. Isolation has to hold, sequencing has to line up, and multiple teams have to move in sync. When processes or systems break, conditions escalate quickly and the time to respond is limited.
At that point, stronger field-level decision making is what keeps the jobsite controlled when the work moves outside an expected sequence.
The teams who are trusted and empowered to act in those moments are the ones who prevent small issues from turning into safety incidents.
Why maintenance of plant operations (MOPO) plans don’t carry the work
Most teams treat the MOPO plan as the end-all. The sequence is locked in, contingencies are built out, and the expectation is that once the plan is set, execution will follow it.
Yet even with contingencies in place, MOPOs are not all-encompassing. They guide execution, but they do not carry it through every condition crews will face in the field.
At critical moments, the plan gives way to judgment. Conditions shift, variables stack, and decisions move from what was defined on paper to what is happening in real time. That transition places weight directly on the field team, requiring calls that were never fully defined within the plan itself, such as:
- Adjusting sequencing when field conditions no longer support the planned tie-in or shutdown approach
- Determining whether to proceed or stop when isolation is incomplete or system performance is uncertain
- Managing access, staging and safe movement through active process areas as conditions tighten
- Modifying execution in real time when unexpected system or field conditions surface during active work
A MOPO plan sets direction, but it does not make the decision when the work moves outside of it. That moment belongs to the field, and how it is handled determines whether the job stays controlled or starts to drift.
Define decision ownership before work begins
Having a plan on paper is foundational, but crews should enter the work with the authority to act on the contingencies defined within it. When that authority sits too far from the field, response time stretches, snowballing a small deviation into something much harder to recover from.
The breakdown usually shows up in one of two ways. In some cases, people carry full responsibility for the outcome but still have to push decisions upward, which creates hesitation at the moment the work needs to move. In others, authority is pushed down without clear limits, leaving too much open to interpretation once conditions shift. Both scenarios introduce risk to the jobsite, just in different forms.
Strong field-level decision making comes from defining ownership before the work begins. That means being explicit about who holds the call in the field, whether that sits with the foreman adjusting sequencing at the crew level, the superintendent holding or advancing work during a tie-in, or the operations lead making the call when system conditions begin to shift.
It also means defining the edges of that authority. Teams should know what decisions fall within their control, what does not and when escalation is required.
Build intentional escalation paths
“Call me if something comes up” sounds workable until the moment it’s needed. The person you’re counting on might be in a meeting, offsite or completely unreachable. The work does not pause while you track them down, and the system does not stabilize on its own.
That’s why escalation has to be built with the same discipline as the rest of the work, reflecting how jobs actually run, not how they look on an organizational chart. When something breaks outside the expected path, the response should already be in motion, not something the team is piecing together under pressure.
At a minimum, that structure should answer a few non-negotiable questions:
- Who already knows this work is happening before it starts?
- Who has the authority to step in when the field reaches its limit?
- How is that person contacted in real time, and not after the fact?
- Who takes over if the first call does not go through?
The people on the receiving end of that escalation should not be catching up in the moment. They should already understand the scope, the pressure points and where things are most likely to shift once execution begins.
Ensure the plan Is owned, not handed down
Ever heard the phrase “people support what they help create”?
Water and wastewater projects bring together owners, design engineers, operations, and construction teams, each with a different view of how the work should play out beyond the blueprint. What’s surprising is that even with that level of involvement, it’s not uncommon for the final MOPO plan to be pushed to the field as a finished product, with the expectation that it will hold as written.
But without field input, the plan misses how the work will actually unfold, and those gaps tend to surface during execution when there is less room to adjust and more at stake.
Instead, once developed, the plan should go through a true “shakedown” process, where frontline leaders, foremen, and craft review it days or weeks ahead of execution, actively looking for gaps, weak points, and pressure areas in how the work is expected to come together. Crews should be encouraged to challenge the plan, identify risks, and refine contingencies based on real conditions and experience.
By the time work begins, the plan should carry the fingerprints of the teams executing it in order for their sense of ownership to drive more controlled execution in the field.
Safety lives where planning meets accountability
Field-level decision making is not about handing crews full responsibility for jobsite safety and stepping back. Lean too far one way and everything is expected to be solved in the plan; lean too far the other and it becomes sink or swim in the field.
The work holds in the middle, where the plan is thought through and the people executing it are trusted with the responsibility and authority to act when conditions change.