In complex projects, EPCM is often described as a coordination function.
In practice, it is something more specific — and more consequential.
EPCM is where accountability is either defined or quietly diluted. Where the link between what is done and who carries the consequence of how it was done is either preserved or gradually weakened.
That link, not the activity it connects, is what determines project stability.
How dilution happens — and why it is invisible until it isn’t
Accountability does not typically dilute through a single decision. It dilutes incrementally, through a sequence of adjustments that each appear reasonable, each appear necessary, and each appear temporary.
A scope boundary shifts slightly — not because anyone decided to change it, but because the situation required flexibility and the formal process would have slowed things down.
A decision is implemented before it is formally anchored — because the intent was clear in the room, and waiting for written confirmation felt unnecessary given the pace of the project.
A risk migrates from its original contractual owner — not through negotiation, but through absorption. One party manages the consequence to keep progress moving, and the formal allocation of that risk is never revisited.
None of these feel significant in isolation. The project continues. Progress is reported. Interfaces appear managed.
But something has changed.
Not in execution. In position.
The intersection that defines EPCM
EPCM operates at a specific intersection: between what is done, and who carries the consequence of how it was done.
When that intersection is managed explicitly — when roles are defined, decisions are anchored, and risks are held by the parties contractually positioned to carry them — EPCM creates stability. The project can absorb pressure because its accountability structure is intact.
When that intersection is managed informally, the accountability structure degrades in a specific pattern.
First, individual decisions become slightly unclear in ownership. Then, the pattern of unclear decisions becomes the norm — expected, accommodated, no longer flagged. Then, when a consequence surfaces — a claim, a delay, a cost overrun — the question of who carries it has no clean answer.
The position that should have been protected was left open at the moment when it could still have been closed.
What this means in practice
In EPCM, the discipline of accountability is not a compliance function. It is not about process for its own sake.
It is about preserving the conditions under which the project can remain stable — not just in normal operation, but under the stress that complex projects always eventually create.
Because alignment that depends on informal understanding holds in calm conditions. It is structure that holds under pressure.
And structure, in EPCM, is accountability made explicit — before it needs to be.
This article is part of ACC Trust Insights and explores accountability structures in EPCM environments — examining how responsibility is defined, how it dilutes, and what the consequences of that dilution are for project stability and commercial position.
ACC Trust Insights is the knowledge centre for Commercial & Contract Governance, Project Delivery and Risk Management in complex projects. Each article draws on practice in construction, infrastructure and energy environments.
office@acctrust.ro