Steering Committee and Executive Reporting

Most program status reports are written for the person preparing them, not for the committee reading them. They contain the right information in the wrong order, bury the risks that matter in a list of thirty items, present RAG ratings that do not reflect the actual state of the program, and require the committee to work hard to understand what decision or action is required of them.

Steering committees that cannot read their own program reports accurately cannot provide effective governance. The consequence is that escalations arrive late, decisions are made without adequate information, and the committee is surprised by problems that were visible in the data months earlier.

Good executive reporting is a craft. It requires an understanding of what the audience needs to know, a clear view of what the program's actual state is, and the discipline to present that clearly even when the news is not good.

Reporting engagements cover the full design of the reporting framework - the structure of the status report, the risk register format, the escalation threshold definitions, and the meeting pack structure. This includes working with the delivery team to understand what information they actually have, and building reporting that can be sustained by the team without constant external support.

For programs in recovery, reporting design often includes a committee reset - a structured briefing to the committee that resets expectations, establishes what accurate reporting will look like going forward, and creates the conditions for honest escalation.