On most EPC projects, information doesn't disappear.
It gets filtered.
A Discipline Lead reports an issue.
A Construction Manager condenses it.
A Project Manager summarises it.
A Project Director receives the final version.
Nobody is lying.
Nobody is hiding anything.
But every layer makes decisions about what matters, what can wait, and what deserves attention.
The result is that the person ultimately accountable for the outcome often receives the information long after the point where it could have changed the outcome.
That's why projects are full of surprises that weren't actually surprises.
The warning signs existed.
The constraints were visible.
The risk was known.
Someone, somewhere, was already talking about it.
A delayed material delivery.
A permit still awaiting approval.
A design query sitting unanswered.
A critical activity quietly slipping by a few days.
None of these events are particularly dangerous on their own.
The danger comes when the signal becomes weaker at every reporting layer.
By the time it reaches the project leadership team, the issue has been shortened, summarised, blended together with twenty other issues, and stripped of the context that made it important in the first place.
Most reporting systems were designed to move information upward.
Very few were designed to preserve its original meaning.
And that's where execution starts to drift.
Not because people are incompetent.
Not because people are dishonest.
But because the reporting architecture itself creates distance between decision-makers and the reality of the work.
How many reporting layers exist between your Project Director and the people doing the work?
