Board prep from six weeks of meetings
The board meets on Thursday. The pack is due Monday. Between now and the last meeting there are six weeks in which perhaps forty conversations happened, four of which changed something the board will care about, and you cannot reliably name which four.
So the weekend goes on reconstruction. You scroll a channel, open a calendar, and ask two people what was actually agreed in that Thursday session in August. The pack that comes out of it is written backwards from what you can still prove, which is not the same as what happened.
Board prep is retrieval, not writing
A pack is an argument with evidence attached. Here is what changed, here is what it means, here is the decision we need from you. The writing part of that is two hours on a good day. Everything else is evidence: dates, numbers, the commitment you made last time, and what the customer actually said rather than the version that has been retold four times since.
The place prep fails is rarely the pack itself. It is the follow-up question. A director asks when you decided to hold the second sales hire, and the honest answer is that it was somewhere in August, it was tied to something about pipeline, and you would need to check. Ten seconds of that costs more than a whole thin slide, because it tells the room that the pack is a story rather than a record.
A quarter usually has three or four threads running through it and not more: the hiring plan, the renewal that decides the year, the thing that broke in July and what you did about it. Prep is finding those threads and following each one end to end. Everything else is detail that belongs in an appendix nobody opens.
The five questions a pack answers
Before you go looking for anything, be clear about what you are looking for. A pack that answers these five is a pack that survives the meeting.
- What changed since the last board meeting, stated as changes, not activity.
- What you said you would do last time, and whether you did it.
- Which number moved, by how much, and what you believe caused it.
- The decision you actually need from the board, written as a question they can answer.
- The risk you would rather name yourself than have found.
Notice that four of the five are about the past, and the past is the part you cannot write from memory. That is the retrieval problem, and it is the part a record solves.
The fifth is the one people get wrong in a different way. A pack that asks the board to "discuss the hiring plan" has not asked them anything. A pack that asks whether to hold the second sales hire until the renewal closes, and says which way you lean and why, gets you a decision in the meeting rather than a fourth conversation about it in December.
Six weeks, in one afternoon
The routine below assumes the meetings that mattered were recorded and turned into notes as they happened. Meeting Notes gives each one a transcript, a summary sized to the meeting, and the decisions and action items pulled out with owners against them, which is the raw material the afternoon works from.
From the record to the pack
- Start from the last packOpen what you sent the board six weeks ago and list every commitment in it. That list is your agenda for the afternoon: each line needs a current status and, where it slipped, a reason with a date on it.
- Ask one thread at a timeIn Ask Ona, ask across the six weeks about one thread only: what was decided about the hiring plan since the start of August. Then ask the next thread. A question that covers three threads returns a paragraph that covers none of them well.
- Split decided from discussedHalf of what comes back will be deliberation, not decision. A board pack reports decisions. Move everything else to a private list called "still open", which is usually where your risk section comes from.
- Trace every number to where it was saidEach answer names the meeting it came from. Open the ones behind a figure, a date or a commitment and read the line. This is the step that makes the follow-up question survivable, and it is the one people skip.
- Write the page you least want to be asked aboutDraft the risk section first, while the record is still open in front of you. Written last, it becomes a paragraph of reassurance. Written first, it is the part of the pack the board will trust.
It helps to know in advance where each kind of answer actually lives, because some of them are not in a meeting at all and looking for them there wastes the afternoon.
| The question in the room | Where prep usually looks | Where the answer really is |
|---|---|---|
| When did you decide that? | Someone's memory of a Thursday | The meeting where it was said, with the date attached |
| What did the customer actually ask for? | A summary of a summary | The account call, in their own words |
| Why did that number move? | A chart with no cause under it | Your finance system for the figure, the meeting for the reason |
| What happened to the thing you promised us? | A slide that quietly omits it | Last quarter's pack, checked line by line against the record |
| Who owns this now? | An assumption | The action item, with the name that was agreed in the room |
The third row is the one worth dwelling on. A record of meetings tells you what people believed and said about a number. It does not produce the number. Keep those two jobs separate and the pack gets more honest, not less.
Making the next one shorter
Everything above is recoverable work. The version that scales is not doing it in one afternoon at all. Set a single Routine that runs once a week across the threads the board cares about and reports what moved, what was decided, and what is still waiting on somebody. Six weeks, six briefs, two minutes each.
By the Monday the pack is due you are editing six short documents instead of excavating forty meetings. Teams that run this way tend to find the pack gets shorter as well as faster, because the weekly brief keeps catching the activity that felt important on the day and turned out not to matter.
I used to lose the weekend before every board meeting to reconstructing a quarter. Now the reconstruction is a morning, and the hours it frees go into the part the board actually came for, which is what we intend to do next.
Dana R., Chief Operating Officer, B2B software company
The hour after the board meeting
Prep gets all the attention, and the more valuable hour is the one immediately afterwards. A board meeting produces asks: a number they want broken out differently, a risk they want a plan for, a question they will return to next time. Those arrive in passing, half of them in the ten minutes at the end when the agenda is finished, and they are the first thing lost.
Whether the meeting itself should be recorded is a governance question and not yours alone to answer. Minutes have a formal status, the chair owns them, and a board that has not agreed to a recording should not be recorded. What you can always do is sit down straight afterwards, on your own or with one colleague, and talk through what the board asked for while it is still accurate. Record that debrief, and every ask becomes an action item with a name against it before the day ends.
Do that twice and the next pack starts to write itself, because the list of commitments you open with in step one is a list somebody actually captured rather than one you are inferring from your own slides.
What the pack still costs you
None of this removes the hard part. Deciding what the board needs to hear, and in what order, is judgement, and judgement is the job you are paid for. A record makes the evidence cheap. It has nothing to say about which two of your five problems belong on the first page.
Nor should it write the prose. A pack in your own voice, with your own view in it, reads differently from a pack assembled out of summaries, and a board can tell the difference within a page. Use the record for the dates and the direct quotes and write the argument yourself. The Ona for business leaders page covers where else this shows up in a leadership week.
What this will not do for you
Ona holds meetings you recorded. It does not hold the one-to-one you had walking to the car park, the call you took on a train with no signal, or the conversation you deliberately chose not to record. Some of the most consequential conversations a leader has belong in that last category, and a pack that reads as complete when it is not is worse than one with a gap you have flagged.
It also does not produce numbers. Revenue, runway, churn and headcount come from the systems that hold them, and the pack should cite those systems. What the record adds is the sentence next to the number: who raised it, what they attributed it to, and whether anyone in the room disagreed at the time.
And this playbook assumes six weeks of history behind it. Start recording the week before a board meeting and you have a week, which will not carry a pack. Plan the first pack the way you always have, and treat the six weeks after it as the ones you are actually building for.
In the fortnight before
The shape is the same and the window is longer, which makes the weekly brief more important rather than less. Six months of meetings is not an afternoon of retrieval.
Run a monthly rollup alongside the weekly one, and keep last time's commitments somewhere you will see them, because a six-month gap is long enough to forget you made them.
Personnel matters, anything with legal advice in it, and conversations where someone has asked you not to: leave them out, and do not treat that as a gap to apologise for.
If something from one of those has to reach the board, write it yourself, in your own words, and say where it came from.
That depends on where the meeting lives. A meeting in a shared workspace is visible to that workspace; one in your own account is not.
Decide that before you start recording board-adjacent conversations rather than afterwards, because moving the line later is awkward for everyone involved.
Prepare the next one from the record
Record the meetings that move the threads your board cares about, then build the pack from what was said, not from what you can recall.