Most owner reports describe the past accurately and answer no question you actually have. Yours should be interrogable: every figure traceable to a document, and the project itself able to answer a question in plain language.
Illustrative engagement telemetry — live engagements display from the actual record.
A monthly report describes drift that is already weeks old and half-hardened. That cadence has nothing to do with how quickly projects change and everything to do with how a labour-based practice organises its billing: a team assembles a document, the document takes a fortnight, and the reporting period is set to the interval the team can sustain. Owners inherit the interval and call it governance.
The deeper problem is that the report cannot be questioned. A figure appears; behind it is a spreadsheet nobody outside the team has seen, assembled from claims the same team sampled. Ask where the number came from and the answer is a person's recollection. That is not a governance instrument. It is an opinion with a cover page, and it asks the owner to trust the author instead of the evidence.
So the questions that actually matter go unasked, because everyone knows they cannot be answered inside the meeting. What does a two-month delay on the steel package do to the opening date? What did we actually agree with the façade contractor about testing? Which decisions are sitting with me right now? Every one of those answers exists in the project's documents. None of them is reachable.
A narrative a board can act on. Cost, schedule, risk, and design status in language that supports a decision, with a recommendation attached to each item that needs one — and every figure in it resolving to the documents it came from.
Forecasts, not extrapolations. The anticipated final cost and the forecast completion date are computed from the live commitments and the programme logic, and they move when the record moves rather than when the reporting cycle comes round.
Scenarios on demand. The consequence of a specific event, computed rather than estimated: what a delay to one package does to opening and outturn, with the assumptions visible.
A standing decision log. Every recommendation, approval, and deferral recorded with its date and its reasoning — which is both a governance instrument during delivery and, later, part of the evidential record.
And because the whole record is indexed and connected, the project can be asked a question directly — in plain language, with the answer grounded in the documents rather than in somebody's memory of them.
Every figure in it resolves to the documents it came from. A cost position traces to the invoices and variations behind it; a progress figure traces to the verified quantities. A report you cannot open up is an opinion with a cover page, and it asks you to trust the author rather than the evidence.
The real consequence of a specific event, from the live record rather than from judgment in a corridor. What a two-month delay to a steel package does to the opening date and the outturn cost, computed against the programme logic and the current commitments — so the question is answered in the meeting rather than taken away.
Yes, and it is the capability owners tend not to believe until they use it. Because every document is indexed and connected, a question like “what did we agree with the façade contractor about performance testing” returns an answer grounded in the actual correspondence, with citations to the documents it came from.