Most project reporting systems have the same fundamental design assumption.
Information flows upward.
The Discipline Lead feeds the Construction Manager. The CM feeds the Project Manager. The PM feeds the Project Director. Each layer receives a version of what the layer below it chose to pass on.
The assumption built into that design is that everyone needs the same information — just at different levels of detail.
That assumption is wrong. And it's part of why execution drifts.
A Discipline Lead doesn't need portfolio RAG status. He needs to know, three to seven days out, whether his materials are on site, his drawings are current, and his predecessor work pack is trending toward ready — so he can commit his crew without standing them down on Monday morning.
A Construction Manager doesn't need the same depth on any single discipline. He needs to see across all of them simultaneously — what is ready, what is drifting, and critically, what cascade risk a constraint in one discipline creates for the three disciplines that follow it.
A Project Manager needs control over what goes to field and when. Override authority. Constraint visibility at a level where commercial decisions can be made with full context.
A Project Director needs exceptions, portfolio exposure, and the ability to drill straight through to source data at any layer, any time, without waiting for a report or requesting a breakdown from the team below.
These are not the same job. They are not the same decisions. They should not be the same view.
The problem on most projects isn't that information is unavailable.
It's that the wrong people are looking at the wrong slice of it, at the wrong time, assembled from the wrong sources.
A system designed around how decisions actually get made — with each role seeing exactly what they need and nothing they don't — doesn't just improve reporting. It changes the quality of the decisions themselves.
