Tag: board document

They approved my client’s £4M budget before she presented a single slide. The presentation was a fifteen-minute formality.

Quick answer: The executive presentation pre-read is the most strategically important document most professionals never learn to write. It’s not your slides emailed early. It’s not a summary of what you’ll say. It’s a separate, purpose-built document with three parts — the Decision Frame, the Evidence Stack, and the Ask — designed to get senior executives aligned on your recommendation before you enter the room. When done right, the meeting itself becomes a confirmation, not a persuasion exercise. Built from 24 years in banking and consulting environments, this is the structure I’ve taught to executives preparing for board meetings, steering committees, and investment approvals. The difference between presenting to an aligned room versus an uninformed room is the difference between getting a decision and getting a “let me think about it.”

The Budget That Got Approved Before She Opened Her Mouth

At Commerzbank, I watched a VP prepare for weeks on a £4M technology modernisation budget. Her slides were immaculate. Forty-two slides covering everything from vendor comparison to implementation timeline. She’d rehearsed the delivery. She’d prepared for questions.

But the week before, she did something most people skip entirely. She sent a two-page pre-read document to the five decision-makers who’d be in the room. Not her slides — a separate document. It laid out the business case in three sections: why now, what the evidence showed, and what she needed them to decide.

By the time she walked into that boardroom, three of the five had already emailed back with variations of “this looks solid.” The CFO had flagged one line item he wanted to discuss. The CTO had already circulated it to his team for technical validation. The meeting itself lasted fifteen minutes. Twelve of those were spent on the CFO’s one concern. The decision was unanimous.

That’s when I understood: the presentation isn’t where decisions get made. The pre-read is. The presentation is where decisions get confirmed.

The Mistake 90% of Presenters Make With Pre-Reads

Most professionals do one of two things with pre-reads: they skip them entirely, or they email their slide deck the night before and call it a pre-read. Both are career-limiting mistakes.

Sending your slides as the pre-read creates two problems at once. First, executives try to read a document that was designed to be presented — and it either has too little text to make sense alone, or too much text because you tried to make it self-explanatory. Second, when you stand up to present those same slides, the room has already seen everything. You’re narrating a document they’ve already skimmed. The energy dies. The questions start on slide two instead of after your recommendation.

Skipping the pre-read is worse. You walk into a room where five executives are hearing your business case for the first time. They’re processing information, forming opinions, and identifying objections simultaneously. No human brain handles that well. The result is almost always “interesting — let me think about it,” which is executive language for “I’m not comfortable deciding without time to process.”

The pre-read solves both problems. It gives executives the thinking time they need so the meeting becomes the decision time you need.

PAA: Should you send your presentation slides before the meeting?
No. Your slides and your pre-read are two different documents serving two different purposes. Slides are visual support for a live presenter — they’re designed to be incomplete without your narration. A pre-read is a self-standing document designed to be complete without you in the room. Sending slides as a pre-read weakens both the document and the presentation. Create a separate two-to-three-page pre-read document using the Decision Frame, Evidence Stack, and Ask structure below.

The 3-Part Board Pre-Read Structure

In twenty-four years of banking, I’ve seen dozens of pre-read formats. The one that consistently produces pre-meeting alignment has three sections — never more. Each section answers a single question that’s running through every executive’s mind before they commit time to your meeting.

The entire document should fit on two pages. Three at the absolute maximum. Anything longer and executives won’t read it — which defeats the entire purpose. I’ve written about the executive summary slide before. The pre-read follows the same principle: compression creates clarity.

Part 1: The Decision Frame (Half a Page)

The Decision Frame answers the question every executive asks before reading anything: “Why am I looking at this, and what do you need from me?”

It has four elements, each one sentence:

The Context: One sentence on why this is on the agenda now. Not the history of the project. Not the background. Just: why now? Example: “Q1 infrastructure costs exceeded forecast by 23%, driven by three unplanned outages in February.”

The Impact: One sentence on what happens if nothing changes. Example: “Without intervention, we project £1.2M in additional unplanned costs by year-end, plus reputational risk from client-facing service disruption.”

The Recommendation: One sentence on what you’re proposing. Lead with the answer, not the analysis. Example: “We recommend a £4M investment in platform modernisation, delivered in two phases over 18 months, with breakeven at month 14.”

The Decision Required: One sentence on exactly what you need from this group. Example: “We are seeking approval to proceed with Phase 1 (£1.8M) and authorisation to begin vendor negotiations by March 15.”

That’s it. Four sentences. Half a page. Every executive in the room now knows what this is about, what the stakes are, and what you’re asking for — before they read another word.

Part 2: The Evidence Stack (1–2 Pages)

The Evidence Stack answers the second question: “Why should I believe this recommendation?”

This is where most people go wrong. They dump every data point they’ve gathered into the pre-read. Executives don’t want to see your working. They want to see the three to five strongest pieces of evidence that support your recommendation — and they want to see them in descending order of weight.

PAA: How long should a board pre-read be?
Two pages is ideal. Three is the maximum. Research on executive reading behaviour consistently shows that documents over three pages see completion rates drop below 40%. Your pre-read should take no more than five minutes to read. If an executive needs more detail, put it in appendices or reference it in your presentation deck — but the core pre-read must be scannable in under five minutes.

Structure the Evidence Stack as three to five numbered points, each with a headline and two to three sentences of support. Example:

1. Cost trajectory is accelerating. Infrastructure maintenance costs have grown 18% year-over-year for three consecutive years. The current platform requires 340 engineering hours per month in reactive maintenance alone.

2. Client impact is measurable. Three client-facing outages in Q1 resulted in two formal complaints and one at-risk account review. The NPS score for affected clients dropped 12 points.

3. Comparable investment shows 2.1x return. The Singapore office completed a similar modernisation in 2024, reducing maintenance costs by 62% and eliminating client-facing outages for 14 consecutive months.

Each point is verifiable. Each point supports the recommendation. Each point can be challenged in the meeting — and you should want that, because you’ll be prepared for exactly those challenges.

Part 3: The Ask (3 Sentences)

The Ask closes the pre-read with surgical precision. Three sentences, no more.

Sentence 1 — The specific decision: “We are requesting approval for £1.8M Phase 1 investment.”

Sentence 2 — The timeline: “Vendor selection begins March 15 if approved; Phase 1 delivery completes by September 30.”

Sentence 3 — The meeting purpose: “Thursday’s session is scheduled for 30 minutes to address questions and confirm the go/no-go decision.”

That third sentence is the one most people miss — and it’s the most important. It tells every executive in advance that they’re expected to make a decision in the meeting. No “let me think about it.” No “circle back next quarter.” The pre-read has given them the thinking time. The meeting is for deciding.

I’ve written about pre-meeting executive alignment — the conversations that happen alongside the pre-read. The document and the conversations work together. The pre-read gives executives the substance. The pre-meeting conversations give you the intelligence on where resistance lives.

When to Send It (And to Whom)

Timing matters more than most people realise. Send the pre-read too early and it gets buried. Send it too late and executives don’t read it.

The optimal window is five to seven business days before the meeting. This gives executives enough time to read it during one of their review blocks, form an initial position, and — critically — have informal conversations with other attendees about it before the meeting.

Those informal conversations are where alignment actually happens. When the CFO reads your pre-read on Monday and mentions it to the COO over coffee on Wednesday, they’ve already begun forming a collective view. By Thursday’s meeting, the room has a shared baseline. Your job in the presentation shifts from “convince five individuals” to “confirm what the group has already been discussing.”

Who receives the pre-read: Every decision-maker who’ll be in the room, plus their chiefs of staff or executive assistants (who control what gets read). Do not send it to observers, note-takers, or people attending for information only. The pre-read is for decision-makers. Everyone else gets context from the presentation itself.

PAA: What goes in an executive pre-read?
Three sections only: a Decision Frame (why this is on the agenda, what you recommend, and what decision you need), an Evidence Stack (three to five numbered pieces of evidence supporting the recommendation), and the Ask (the specific decision, timeline, and meeting purpose). The total document should be two pages maximum. Detailed data, appendices, and supporting analysis belong in the presentation deck or in supplementary documents — not in the pre-read.

Why Your Slides Are Not a Pre-Read

This is the hill I will die on. I watched a managing director at PwC send a 38-slide deck as a pre-read before a partner meeting. The partners received it on Monday. By Wednesday, two had emailed back with detailed objections to slides 14 and 27. By Thursday’s meeting, the first twenty minutes were spent relitigating points that should have been addressed in the pre-read’s Evidence Stack — not discovered by scrolling through presentation slides.

Slides are designed for visual support during live narration. They use headlines, not paragraphs. They show charts, not arguments. They make no sense without a presenter standing next to them. When you send slides as a pre-read, you’re asking executives to guess what you’re going to say about each slide — and their guesses will be wrong.

A pre-read is a narrative document. Full sentences. Complete arguments. No visual dependencies. An executive should be able to read it at their desk, understand your recommendation, evaluate your evidence, and know what you need from them — without ever seeing a slide.

The slides and the pre-read work together, but they are not the same document. The pre-read builds alignment. The slides confirm it visually. I’ve written about board presentation best practices — the pre-read is what makes those best practices actually work, because the room arrives aligned.

Your next step: Before your next high-stakes presentation, open a blank document and write the four sentences of your Decision Frame. Context, Impact, Recommendation, Decision Required. Send that half-page to your key decision-maker five days before the meeting and ask: “Does this capture the right framing?” Their response will tell you exactly where the resistance lives — before you build a single slide.