How to Present Audit Results Your Board Will Actually Read

Here's a question. When was the last time a board member read your entire board pack cover to cover?

If you're honest, the answer is probably never. And that's not because your board doesn't care. It's because most board packs are 40, 50, sometimes 60 pages of dense tables, narrative reports, and appendices that nobody asked for. Board members are busy people. Many are volunteers. They've got about 90 minutes before the meeting to prepare, and they're going to skim.

So the question isn't how to write a better 50-page report. It's how to write a 10-page one that actually gets read and acted on.

Lead With the Summary, Not the Data

Page one should be a RAG summary. One page. Red, amber, green across your key dimensions. No paragraphs, no caveats, just the picture. A board member should be able to glance at this page for 30 seconds and know where the school stands.

Most heads do the opposite. They build up to conclusions, burying the headline on page 23. Academic training is partly to blame. We're taught to show our working. Boards don't want your working. They want your answer.

The Top 3 Rule

After the RAG summary, present exactly three priorities. Not five. Not seven. Three.

Why three? Because that's what people remember. And because if everything is a priority, nothing is. Your board needs to walk out of the meeting knowing what three things need attention this term. Each priority gets half a page: what the issue is, why it matters, and what you're recommending.

This forces you to make choices. You might have eight things that need attention. Fine. Pick the three most urgent, put them front and centre, and list the others in a "watching brief" section at the back. The board will thank you for it.

Structure by Dimension, Not by Data Source

A common mistake: organising your report by where the data came from. "Financial report. HR report. Admissions report. Facilities report." This makes sense to the person who compiled it but not to the person reading it.

Better: organise by dimension. Financial health. Operational efficiency. Governance quality. Enrolment and market position. Educational outcomes. Each section pulls from multiple data sources but tells one story. This is how IRIS5 structures its output, and there's a reason for it. Boards think in terms of institutional health, not departmental silos.

Use Visuals That Earn Their Space

A radar chart showing your school's performance across five dimensions tells the story faster than two pages of text. A trend line showing three years of enrolment data is worth more than a table of numbers. Use them.

But be selective. Every chart should answer a specific question. "How are we performing across dimensions?" That's a radar chart. "Is our financial position improving or declining?" That's a trend line. "Where do we sit against benchmarks?" That's a bar chart with a reference line.

What you don't need: pie charts (almost never useful), decorative graphics, or any chart that requires a paragraph of explanation to understand. If you have to explain the chart, it's not doing its job.

The 10-Page Maximum

Here's a structure that works:

1. Page 1: RAG summary across all dimensions
2. Pages 2-3: Top 3 priorities with recommendations
3. Pages 4-8: One page per dimension with key data and trends
4. Page 9: Watching brief (issues not yet critical but worth monitoring)
5. Page 10: Board action items (specific decisions needed, with deadlines)

That's it. If a governor wants more detail on a specific area, they can ask for it. But the core report stays at 10 pages. Supporting appendices can exist. They just don't go in the main pack.

The "Board Action Required" Section

This is the single most important improvement you can make. Every board report should end with a clear list of items that require a board decision. Not "for information." Not "for discussion." Actual decisions.

Format them like this: "The board is asked to approve/note/decide [specific thing] by [specific date]." No ambiguity. No room for the meeting to end with everyone nodding but nobody committing to anything.

Board meetings where three hours are spent discussing data and zero decisions are made are a report problem, not a board problem. If you do not tell governors what you need from them, they will default to asking more questions.

The Cardinal Sin: Data Without Recommendations

Presenting data without a recommendation is the fastest way to lose your board's attention. "Our staff cost ratio is 72%" means nothing on its own. "Our staff cost ratio is 72%, which is within the healthy range but has increased from 68% over three years. We recommend a staffing review before the next budget cycle." That's useful.

Every data point should answer: so what? And: what do you want us to do about it?

Governors are not typically education specialists. Many are accountants, lawyers, or business owners accustomed to executive summaries, clear asks, and efficient meetings. Give them that, and they will engage properly. Give them a 50-page report and they will zone out by page 4.