They need to be accurate, concise, strategic, and prepared quickly enough not to consume the entire week preceding the board meeting.
Here is a repeatable process for producing a board-ready operations review in under two hours.
The Template First
The biggest time saving comes from having a fixed template. Every board operations review covers the same five areas in the same order: strategic objective progress, delivery status, capacity and resourcing, financial status, and risks and priorities for the next quarter. Board members understand the template after one or two cycles and can absorb information more efficiently when the structure is consistent.
Build the template once. Reuse it every quarter.
Data Automation Second
The data that feeds the review should be as automated as possible. Delivery status should come from the project management system, not manual survey. Budget vs actuals should come from the finance system. Capacity utilisation should come from the resourcing tool.
If you’re spending thirty minutes per metric gathering data manually, that’s a process design problem, not a reporting problem.
The Two-Hour Process
Hour 1: Pull the automated data for each section of the template. Identify the three to five most significant points in each section — the things that need board awareness, not the full data set. Write one to two sentences per point.
Hour 2: Assemble into the board format. Add context and narrative for the strategic objective section — this is where judgement matters, not just data. Review for consistency — does the capacity status align with the delivery status? Does the risk section connect to the financial section?
Output: a five to eight-page board pack, accurate, concise, and ready for distribution.
What Boards Actually Want
Boards want three things from an operations review: confidence that management has clear visibility of the business, transparency about what’s not working and what’s being done about it, and a clear view of the next quarter’s priorities and risks.
They don’t want every metric. They don’t want detailed project status. They want the story — told with evidence, with honesty, and without spin. The COO’s job is to tell that story with enough data to be credible and enough judgement to be useful.
