What directors actually need to see in board reports

Sponsored content by Clew, a connected risk and assurance platform linking objectives, risk, and board-level decisions.

Boards receive thick packs of reports each quarter. Risk reports. Compliance updates. Strategy progress. Performance dashboards. Each is produced by a different function, in a different format, often telling a different story. Directors are then expected to assemble these pieces into a single view of how the organisation is performing against what it set out to achieve.

That assembly happens, if it happens at all, in directors’ heads during the meeting. It is a significant ask, and most board packs do not make it easy.

The gap between activity and position

A useful test for any board report is this: after reading it, can a director quickly say what has changed since the last meeting, where exposure is rising or falling, and where the board is being asked to challenge or decide?

Many reports cannot answer those three questions. They describe activity. They confirm that functions are operating. They document progress against plans. What they rarely do is tell the board where the organisation actually stands.

The opening page is often where this becomes most visible. If it is a summary of everything underneath it, the director knows the function is busy. If it is a judgement on the current position, the director knows where to focus.

Reporting structured by function, not by question

The deeper issue is that most board reporting is structured by function rather than by question. Strategy lives in one document. Risk lives in another. Compliance lives in a third. Audit findings live in a fourth. Performance metrics live in a fifth.

Directors are left to trace, on their own, how a strategic objective connects to the risks that threaten it, the controls that manage those risks, and the indicators that tell the organisation whether things are working. The thread between intent and outcome is rarely visible on a single page.

This matters because governance is about lines of sight. A board that can trace a strategic objective forward to its current confidence level is a board that can govern it. A board that cannot trace that connection can only note it.

What good looks like

A board report that helps directors govern tends to share a few characteristics:

• It is anchored to objectives. Every material item ties back to something the organisation has committed to deliver.
• It shows direction, not just position. A heatmap that never moves invites the conclusion that nothing is moving.
• It distinguishes between what management is managing and what the board is being asked to decide.
• It is honest about what has changed since the last meeting, including what got worse.
• It tells the director where to focus before they have read past the opening page.

The harder discipline

Most boards do not need more information. They need better-connected information. That usually means removing content from the pack rather than adding it. Less is more. Detailed registers, methodology notes, compliance calendars, and full action logs belong one level down, available on request rather than presented by default.

Every page kept for safety is a page that steals attention from the pages that matter. The question worth asking before the next board meeting is not whether the report is comprehensive. It is whether a director, after sixty seconds, would know what the board is being asked to do.

This perspective is drawn from work at Clew with risk and assurance teams across sectors.