One ask, not twelve charts
Most board packs fail because they are written for the operators who live in the numbers. A director does not have time to reconstruct a decision from twelve slides.
Write as if the reader will give you two minutes. If the first page does not name the decision, they will skip to the appendix.
The vote belongs on page one
Start with what changed in the language the board already uses. Then say whether that change is good, bad, or mixed.
A usable opening usually includes:
- The decision requested
- The number that moved
- Why it moved
- What happens if we wait
- Who owns the follow-up
- The date to review again
- What is still unknown
If the first paragraph cannot be forwarded as written, it is not a board summary yet. It is still a briefing for the people who already know the story.
Name the driver, not the channel
After the opening, explain the cause in one paragraph. Channel detail can wait for the appendix. The board needs the driver, not the dashboard.
Then name the ask. Approve spend. Pause a program. Hire. Delay. A pack without a decision is a recap, not a board paper.
Keep supporting numbers in the document, not as the document. Charts belong after the story is clear.
The appendix is not the paper
If a director missed the working session, they still need the same three answers. Write as if they will vote without you in the room.
- The risk they should not ignore
- The option already on the table
- The work already done
- What changed since last meeting
- What the team now recommends
Skip the task dump. The paper has to survive a director who only reads page one.
When final results will take time, separate what you know now from what you will know later, and name the date to review.
Write as if they will vote without you
A concise board summary helps directors act. It may include the period, the change, the cause, the risk, and the ask.
Write it so it can be shared with people who were not in the data. That is the whole job.
The pre-read test
Have a teammate comment before it goes out. Ask whether the opening can be forwarded, and whether the ask is actually a decision.
Useful questions include:
- Can a director forward the first paragraph?
- Is the ask a real decision?
- Did we hide a risk in a footnote?
- What would we cut if this page had to be one slide?
- What is still unknown?
- Who should speak if the room pushes back?
Create space for honest comments without immediately defending the pack. Capture the specific cuts and the specific risks.
Pack versus working notes
The version you send should read like a paper for the room. The internal draft can keep the extra charts, the caveats, and the unfinished questions.
Lock the send version before the meeting, then document lessons that should change the next pack.
Assign ownership for those changes. A lesson that stays in meeting notes rarely changes the next board cycle.
Same paper. New cycle.
Directors learn the map. If page one is always the vote, they stop hunting through slides for the ask.
Lock the pack days before, not the night before. Owners move. Details disappear. The room still expects a vote.
Agree on what stays in the room and what can be forwarded before the pack leaves your desk.
Approve, pause, hire, or wait
End with one decision. Approve, pause, hire, or wait. Then name who comes back with the answer.
Put these next to the vote:
- Cost in the language the board already uses
- What happens if they wait until next quarter
- Who comes back with the answer
- The date the room should see it again
- What stays in the appendix, not on page one
Some rooms need a vote this meeting. Others need a dated follow-up. The recommendation should match how that board actually decides.
Materials before the meeting
When a follow-up is needed, connect it to the outcome you just named. Do not wait until the next crisis to reopen the paper.
Put cost, timing, and ownership next to the vote. A board that has to infer those from an appendix will spend the hour on the appendix.
Give the room enough time to decide without burying the ask in a long appendix.
Counsel the paper
The pack should leave with a named owner and a dated return. Without that, even a clear vote disappears into the minutes.
Schedule the next check-in around a real event: a launch, a budget cycle, a risk date. A relevant follow-up is more useful than a generic update.
Directors learn the map
Send the paper before the meeting. A director who sees the vote for the first time in the room is already behind.
Use the follow-up to review what moved, answer remaining questions, and name any required change. That shows continued ownership without turning every paper into an open-ended update.
Record the vote
Archive superseded drafts, confirm the final version of the pack, close open questions, and record the decision in writing.
Record what was approved. The next cycle should open with last quarter's vote, not a fresh pile of charts.
The paper is the meeting
A board pack is not an administrative dump. Done well, it becomes the bridge between the numbers, a clearer ask, and a decision the room can stand behind.
Teams that write the decision first spend less time defending slides and more time answering the one question the board actually asked.