How a Chief of Staff runs board meetings

The board meeting is in nine days. Finance hasn't closed the month, two executives haven't started their sections, and your CEO has just asked you to "tighten the story" in a deck that doesn't exist yet.

That week comes around every cycle at a lot of companies, because board prep has no owner until it's late. Run it as a system and the CEO walks in with no surprises, directors spend the meeting helping, and the follow-ups turn into introductions and hires. This is part of our Chief of Staff toolkit; for the brief you'll write your CEO, see our guide to briefing your principal.

What does a Chief of Staff do for the board?

The Chief of Staff runs the machinery around the board: the meeting calendar, the preparation process, the pre-read, the CEO's preparation, the follow-ups and the updates between meetings. The CEO owns the relationship with each director, the CFO owns the numbers, and counsel or a corporate secretary owns the legal record.

Board work touches everyone and belongs to no one. Every executive writes a section, finance closes the books early, legal drafts resolutions, and without a single owner for the process the CEO becomes the integrator at midnight.

Our Leveling Framework, built from a survey of 200+ Chiefs of Staff, lists board meetings among the recurring meetings a Chief of Staff manages at every level, and "investor updates and critical presentations for my principal" among the typical projects. Direct relationships with investors start to appear at the VP and executive levels.

Who your principal is changes your part. Of the more than 700 postings in our 2026 Pathways Report that name the principal, only 44% say CEO, founder or president. A Chief of Staff to a CFO may own the whole finance section, and one to a CTO may write one slide, so agree your part in your mandate.

Most Chiefs of Staff sit on the CEO's side of the board, and should stay there. I'd stay out of building your own relationships with directors unless the CEO asks, because directors notice when someone other than the CEO is managing them. Some Chiefs of Staff work for the board side directly: Elyse Levine was hired at the University of Southern California as deputy Chief of Staff to the president and Chief of Staff to the chair of the board of trustees. She described on our podcast how the person between them can't be pulled into "don't tell the other one" requests, and spent her first 30 to 60 days learning where she played for each before changing anything.

How far ahead should you start preparing for a board meeting?

Start four weeks out. A board meeting needs locked numbers, sections drafted by several executives, time for the CEO to shape the story, and a pre-read in directors' hands about a week before the meeting, and each of those steps waits on the one before it.

The critical path is almost always the month-end close and the executives' drafts. If finance closes on the 10th and the meeting is on the 14th, no amount of late-night editing will produce a pre-read directors can read in advance, so set the board date against the close calendar first. The plan below assumes a pre-read a week out, our recommendation for most boards.

# Board meeting work-back plan: [meeting date]

Owner: [Chief of Staff] · Approver: [CEO] · Finance lead: [name] · Counsel: [name]

## T-28 days: agenda and owners
- Agree with the CEO the 1 or 2 questions we want the board's help on
- Confirm agenda and timing with the lead director (or their assistant)
- Name an owner and a due date for every pre-read section
- Ask counsel which resolutions and approvals are needed

## T-21 days: drafts start
- Section owners get the template and last meeting's version
- Finance confirms the close date and the metrics list (same as last time)
- Collect open actions from the last meeting and their status

## T-14 days: first drafts in
- All sections drafted; Chief of Staff edits for one voice and one story
- Finance locks numbers; any restatement is flagged now
- CEO writes the opening letter

## T-10 days: CEO review
- 60-minute working session with the CEO on the full draft
- Leadership team walks through the strategic topic together

## T-7 days: pre-read out
- Send the pre-read and resolutions to directors and observers
- Book CEO pre-calls with each director for T-5 to T-2

## T-3 to T-1: CEO preparation
- Question bank by director; one-page brief with numbers to know cold
- Rehearse the strategic topic; the updates are in the pre-read

## Meeting day
- Open session; Chief of Staff tracks actions; closed session as the board decides

## T+2 days: follow-up
- Action list with owners and dates to directors and executives
- Director offers (intros, references, reviews) logged as commitments

## T+7 days: close the loop
- Counsel circulates draft minutes
- Open actions go into the operating rhythm and the next pre-read

# Board meeting work-back plan: Mon, Feb 22

Owner: Chief of Staff · Approver: CEO · Finance lead: VP Finance · Counsel: outside counsel

Board: five directors and one observer · Q4 close: Feb 5

| Step | Date | What | Owner |
| --- | --- | --- | --- |
| T-28 | Jan 25 | Agree the two questions for the board: enterprise pricing and the CFO search | CEO, Chief of Staff |
| T-28 | Jan 25 | Confirm agenda with the lead director's assistant; ask counsel which approvals are needed (option grants, annual budget) | Chief of Staff |
| T-21 | Feb 1 | Section owners get the template and last meeting's version | Chief of Staff |
| T-14 | Feb 8 | All drafts in; Q4 numbers locked; CEO letter drafted | Section owners, VP Finance, CEO |
| T-10 | Feb 12 | 60-minute review of the full draft | CEO, Chief of Staff |
| T-7 | Feb 15 | Pre-read and resolutions to directors; content freeze | Chief of Staff |
| T-5 to T-3 | Feb 17 to 19 | CEO pre-calls with each director | CEO |
| T-3 | Feb 19 | Question bank by director, one-page brief | Chief of Staff |
| T+2 | Feb 24 | Action list to directors and executives | Chief of Staff |
| T+7 | Mar 1 | Draft minutes circulated | Counsel |

## At risk
- Sales section: VP Sales is at a customer event the week of Feb 8, so her draft is due Feb 5. Flagged to the CEO on Jan 25.

Put every date into each owner's calendar the day the board date is set, with the section template attached, and set the whole year's dates at once so the close and holidays get planned around them. When an executive misses the T-14 draft, tell the CEO which section is at risk and what it will cost the meeting; the escalation comes from the plan, which keeps you out of the role of hall monitor.

Ben Darfler, Chief of Staff and Director of Strategy and Operations at Honeycomb, described on our podcast about scaling with structure building work-back time into the calendar so the executives could work through the presentation together before the meeting. A presentation the team built together is one the team can defend together.

Judgment calls on the timeline

When the close can't move and the meeting can't either, send the pre-read on time with flash numbers labeled as preliminary, and send final financials as a one-page supplement. Directors plan their reading around the date you gave them. CEOs often want to change the story at T-3, so agree a content freeze at T-7; anything that changes after it goes into the CEO's opening remarks. And let an executive present live only on the strategic topic, and only if their written section went out with the pre-read.

How the plan changes with the board

The four weeks above suit a venture-backed company with five to seven directors. Scale it to the board you have:

• An early-stage board of three, often two founders and a lead investor, can run on two weeks. The monthly investor update does most of the work, and the meeting can be a two-hour working session.
• A larger board with independent directors and committees needs committee pre-meetings, usually audit and compensation, scheduled inside the work-back, with counsel more involved in the timeline.
• A private-equity-owned company usually has an operating partner who wants a monthly KPI pack in their own format. Build your scorecard to match it, so the board pack reuses it.
• A nonprofit or university board works through the chair's office, which is the seat Elyse Levine described at USC. Expect longer lead times and agree the timeline with the chair's office first.
• A public company adds disclosure rules and a bigger role for counsel. The Chief of Staff's part narrows to the process and the CEO's preparation.

After two or three cycles, the T-14 deadline gets easier and the pre-read starts to grow because writing it got easier. Cut it back every cycle. This week, get the next two board dates and the finance close calendar for those months; if any meeting falls within five working days of a close, raise it with your CEO now.

Should the board get a deck or a written pre-read?

Send a written pre-read memo, with charts in an appendix, for most boards. Directors read it on their own time before the meeting, so the meeting goes to discussion and decisions, and writing it forces the company to state a position on one page.

Slides break one argument into fragments, the presenter fills the gaps out loud, and the meeting turns into a walkthrough of material directors could have read in twenty minutes. A memo has to hold together on the page, and if it doesn't, you find out at T-10 in a working session with your CEO. Jenna Parker, Chief of Staff at Healthie, said on our podcast about her path into the role that her company doesn't make fancy presentations because there isn't time:

Our earlier post on board management makes the same case. Some directors, often investors who sit on many boards, expect slides anyway. If that's your board, I'd send the memo as the pre-read and keep a short deck only for the strategic topic.

Directors need three things from the memo: where the company stands against the plan they approved, what management is worried about, and what management wants from them. Put the asks on the first page, next to the bad news, because those are the two things a director reads first.

# Board pre-read: [meeting date]

## 1. CEO letter (one page)
- The three things the board should know since we last met
- What we want the board's help on in this meeting (1 or 2 questions)
- Lowlights first: what's behind plan, and what we're doing about it

## 2. Scorecard vs plan
- Same 8 to 10 metrics every meeting, actual vs plan vs last quarter
- One line of explanation for every metric off plan (owner named)

## 3. Decisions and asks for the board
- Decisions needed today (with management's recommendation)
- Help wanted: intros, hires, customers, expertise (be specific)

## 4. Strategic topic for discussion
- The question, the options we see, our current view, what would change it
- Pre-read length: 2 to 3 pages max

## 5. Function updates (one half-page each, read-only)
- What moved, what's at risk, what's next quarter

## 6. Status of actions from last meeting
- Each action, owner, done / in progress / dropped (and why)

## 7. Approvals (from counsel)
- Resolutions, option grants, policies

## Appendix
- Financials and forecast, pipeline, hiring plan, charts

Function updates are where length creeps in; cap them at half a page each and push detail to the appendix, because a pre-read past 20 pages before the appendix gets skimmed. I'd put every number that's off plan on page one, in the CEO's own words. Directors forgive bad news. They don't forgive hearing it for the first time in the room, or finding it on page 23.

What should the board meeting agenda look like, and what's your role in the room?

Spend most of the meeting on one or two questions where the company wants the board's help, keep updates to questions on the pre-read, and end with a closed session for directors only. The Chief of Staff usually attends the open session to track actions and timing, then leaves when the board goes into closed session unless the board asks you to stay.

If directors have read the pre-read, the update portion shrinks to the questions they bring, and the time goes to the topic where their experience is worth the most: a pricing change, a hiring plan, a fundraise. Boards that spend two hours on updates and twenty minutes on strategy are paying for advice and getting a recital.

In the room, keep time against the agenda and give the CEO a quiet signal when a block runs long. Write down every action and offer of help as it happens, in the director's exact words, because "I can introduce you to their CFO" turns into nothing if nobody writes it down. Read the actions back before the closed session, then leave without being asked. If the chair wants you to stay and take notes, agree beforehand what you'll write down and who sees it.

The legal record isn't yours. Counsel or a corporate secretary drafts the minutes; your action list is a working document, kept separate from anything that could be read as the official record. Don't record board meetings with a notetaker either: board discussions are on the never-record list in our guide to running leadership meetings.

How do you prepare the CEO and predict the board's questions?

Build a question bank by director, set up short pre-calls between the CEO and each director a few days before the meeting, and give the CEO a one-page brief with the numbers to know cold and a prepared answer to the three hardest questions. The goal is a meeting with no surprises in either direction.

Each director asks from their own seat: the investor who led the last round watches burn and the next raise, the operator asks about hiring and execution, the independent director asks about governance and risk. After two or three meetings you can write down each director's usual questions and how they reacted last time. Keep that file with your notes from mapping stakeholders, and keep anything personal out of it. A surprise in the room tells a director that management either didn't see the problem coming or saw it and didn't say, and either makes every later number harder to trust.

Pre-calls are worth more than another draft of the pre-read. Fifteen minutes between the CEO and each director surfaces objections while there's still time to answer them. Your part is booking the calls, sending the CEO a two-line reminder of what each director cares about, and capturing what they said.

Book fifteen-minute pre-calls between your CEO and each director two to five days before every board meeting, and bring what you hear into the brief.

[SCOTT: how you prepared the Spring CEO for a board meeting, and the question directors asked that you didn't see coming?]

Then write the brief, using the meeting brief from our guide to briefing your principal: the outcome first, then the people, then the risks. For a board meeting, add the numbers the CEO must know without looking (cash, runway, the metric that's off plan and why), the three hardest questions with a short answer for each, and anything from the pre-calls that changes the plan.

A worked example: preparing for a missed quarter

This is a labeled illustration. Revenue came in 14% below plan, mostly because two enterprise deals slipped into next quarter. The pre-read says so on page one, in the CEO's words, with what the company is doing about it.

On the pre-calls, the lead investor asks whether the sales hiring plan still makes sense if the deals slip again. The independent director asks nothing about revenue and a lot about a security incident from the summer. Neither question was in your draft brief.

So the brief changes. The numbers to know cold become cash, runway at the current burn, pipeline coverage for next quarter and the status of the two deals. The three hardest questions become: do we pause sales hiring, what happens to runway if both deals slip again, and what changed after the security incident. You rehearse those answers out loud with the CEO at T-2. In the meeting, revenue takes ten minutes because every director already knew, and the hour goes to the hiring question.

Judgment calls on preparation

Bad news always goes before the meeting, in the pre-read or on a pre-call; which director hears it first is the CEO's call. If your CEO resists pre-calls, start with the two directors most likely to raise something hard and show what came back. When one director dominates every meeting, raise it with the chair on their pre-call, with the agenda times attached. And when a director contacts you directly, answer the factual request, send anything involving judgment back to the CEO, and tell your CEO the same day.

AI is good at the question bank. Give it the pre-read and your notes on each director's interests, and ask it to argue against the plan from each seat. Use a tool approved for confidential company data; I'd use Claude, but you can pick any tool you prefer or your company allows.

You are helping me prepare my CEO for a board meeting. Below are (1) the pre-read we sent to the board and (2) short notes on each director: their background, what they usually ask about, and how they reacted at the last meeting.

Do three things:
1. For each director, list the 3 questions they are most likely to ask about this pre-read, in their voice, and the page or number that would trigger each one.
2. List the 3 hardest questions overall, the ones that would be most uncomfortable to answer in the room, and explain why each is hard.
3. Point out any number, claim or chart in the pre-read that contradicts another one, or that a skeptical director could read differently than we intend.

Be direct. Don't soften the questions, and don't answer them for me.

Pre-read:
[paste]

Director notes (no personal information, roles and interests only):
[paste]

Then sit with the CEO for thirty minutes and rehearse the three hardest answers out loud, because answers that sound fine on paper often fall apart when spoken. Start the question bank this week: for each director, write the two questions they asked at the last meeting and what they were really worried about.

What should happen after the board meeting?

Send the action list to directors and executives within 48 hours, treat every director's offer of help as a commitment with an owner and a date, log the decisions, and feed what the board asked for into the operating rhythm so the next pre-read answers it. The meeting is only as useful as the week after it.

Most of a board's value arrives as small offers made in the room: an introduction to a customer, a reference call on a candidate, a look at the pricing model. A director who offered an introduction on Thursday and hears nothing for three weeks assumes you didn't need it, and stops offering. The CEO sends the note below, and you draft it the same day while the notes are fresh.

Then the open items go where the company already looks every week: management actions into the leadership meeting's action list, director offers into the owner's priorities, and anything the board asked to see into the next pre-read. Decisions and advice go into the decision log described in our guide to context management, and our guide to the operating rhythm covers where the rest lives.

Hold a short debrief with the CEO within two days: what landed, what surprised us, and what we change in the next pre-read. Write the answers at the top of the next work-back plan.

Send the board action list within 48 hours, with an owner and a date next to every offer of help a director made.

How do you write investor updates between board meetings?

Send a short update to your board and investors every month: the same five to eight metrics each time, highlights, lowlights, what the company is deciding, and two or three specific asks. It keeps directors current so board meetings start from shared facts, and it turns every investor on the list into a source of introductions, candidates and advice.

Once the template exists, it takes a couple of hours a month. The pre-read scorecard becomes three monthly updates side by side, investors who hear about a missed quarter in month two aren't shocked in month three, and an ask like "do you know anyone who has hired a head of sales in fintech?" reaches every investor at once. Writing it also forces you to understand the numbers and the risks at the level the CEO does.

Subject: [Company] update, [month year]

## The headline
[Two sentences: the most important thing that happened this month, and how we feel about it.]

## Metrics (same every month)
| Metric | This month | Last month | Plan |
| --- | --- | --- | --- |
| [Revenue or ARR] | | | |
| [Growth metric] | | | |
| [Cash and runway] | | | |
| [Burn] | | | |
| [Headcount] | | | |

## Lowlights
- [What went wrong or is behind, and what we're doing about it]

## Highlights
- [Wins, launches, hires, customers]

## What we're deciding
- [Decision in progress, our current view, when we'll decide]

## Asks
- [Specific ask: intro to X at Y for Z / candidates for role / advice on topic]

Thank you, [CEO name]

Lowlights go before highlights on purpose: investors read updates from many companies, and they trust the ones that lead with the problem. Keep the metrics list identical month to month, even when one looks bad, because a metric that disappears is the first thing an experienced investor notices. Agree a send day with your CEO and keep it.

Drafting from your notes is a good job for AI, as long as the numbers come from finance and you check every one before the CEO sees the draft.

Draft this month's investor update for our CEO to edit and send. Use the structure below exactly: headline (2 sentences), metrics table, lowlights, highlights, what we're deciding, asks.

Rules:
- Use only the numbers I give you. Don't calculate new metrics or fill gaps; mark anything missing as [MISSING].
- Put lowlights before highlights, and give each lowlight one line on what we're doing about it.
- Asks must be specific: who, for what, and why it matters now.
- Plain, direct sentences in the CEO's voice. No superlatives. Under 400 words.

Last month's update (for tone and continuity):
[paste]

This month's metrics from finance:
[paste]

My notes on what happened this month:
[paste]

How can AI help with board prep, and what has to stay out of it?

Use your company's approved AI tools to draft the narrative from your metrics, check the pre-read against the financials, predict questions and draft the follow-up and the monthly update. Keep board materials inside tools approved for confidential data, never put a notetaker in a board meeting, and keep personal notes about directors out of AI tools entirely.

Board prep is already one of the most common places operators use AI. 70% of respondents to the Chief of Staff Network's AI Readiness Diagnostic, 1,200+ senior leaders drawn from Chiefs of Staff and senior operators, have used AI for board decks or executive briefings. I'd use it hardest on the consistency check: does the scorecard on page 3 match the appendix, does the CEO letter promise something the hiring plan can't deliver, which of last meeting's actions isn't mentioned. A pre-read with two different revenue numbers costs the CEO credibility a well-written letter can't buy back.

How candid to be with this board this quarter stays the CEO's call. A board pack holds cash, plans, compensation and sometimes acquisitions, and at a public company much of it is material non-public information. Write these rules into your AI setup before you need them:

• Use only the AI tools your company has approved for confidential data, signed into the company account.
• Never paste a board pack into a personal account or a tool IT hasn't reviewed.
• Don't record or transcribe board meetings with a notetaker; counsel owns the record.
• Keep director notes to roles and interests. Anything personal stays out of writing and out of AI.

If your company hasn't approved any tool for this, start that conversation with IT and counsel; our AI and the Chief of Staff guide covers how to make the case. Then run your last board pack through your approved tool with one instruction: list every number that appears more than once, and flag any that don't match.