The AI Board Prep Chief of Staff Playbook
It’s the Thursday before the board meeting. The CEO sent you three bullet points at 11pm, the CFO’s numbers won’t be final until tomorrow afternoon, and last quarter’s deck has a structure everyone liked but nobody remembers why. You have a day and a half to turn scattered inputs into a forty-slide story that survives contact with seven directors. This is the moment the ai board prep chief of staff workflow earns its keep: not by deciding what the board should hear, but by collapsing the hours of assembly that stand between you and the decisions only you can make.
Board prep is the highest-stakes recurring deliverable a chief of staff owns. It is also the most assembly-heavy. The work splits cleanly into two piles. One pile is mechanical: pulling metrics from six dashboards, reconciling the version the CFO uses against the version sales reports, rebuilding the narrative scaffolding, and listing the obvious questions. The other pile is judgment: what the quarter means, what to lead with, what to bury, and what the CEO needs to own in the room. Claude Cowork is built to take the first pile off your plate so you can spend your scarce hours on the second.
Separate What Cowork Drafts From What You Decide
Before you open a single tool, draw the line. The most expensive mistake in AI-assisted board prep is letting the model’s fluent draft quietly make decisions that belong to you. A deck reads as confident whether or not the judgment behind it was sound.
Cowork drafts. You decide. Cowork can assemble the revenue waterfall, write the transition sentences between sections, and propose how to characterize a soft quarter. You decide whether “soft” is the right word in front of this board, whether the churn number goes on a headline slide or a footnote, and which risk gets named out loud versus handled in the executive session. Write this division down before you start, because under deadline pressure the line blurs fast.
A practical test: for every slide, ask whether a wrong call would embarrass the CEO or mislead a director. If yes, that slide’s framing is yours and yours alone, no matter how good the draft looks. If no, let Cowork carry it and spot-check.
Compress the Metrics Pull
The metrics pull is where the hours disappear. Numbers live in different systems, defined slightly differently, last refreshed at different times. Reconciling them by hand is the single most tedious part of board prep, and it’s the part most prone to a copy-paste error that surfaces live in the meeting.
This is exactly the kind of multi-step assembly Cowork handles well, the same agentic pattern that powers Claude Code on the engineering side. Point it at your sources, give it the definitions the board expects, and have it produce a reconciled metrics table with the source noted for each figure. The source notation matters more than the table: when a director asks where the number came from, you want the answer in the deck, not in your memory.
Keep the most sensitive figures under manual control. Run the routine numbers through Cowork, then add the board-only financials yourself after a human reconciliation pass. The point is to spend your reconciliation time on the few numbers that carry real risk, not on the forty that don’t.
Build the Narrative Arc, Then Take It Over
A board deck is a story with a spine: here’s where we said we’d be, here’s where we are, here’s what changed, here’s what we’re asking you to weigh in on. Cowork is good at producing that scaffolding from your prior deck and this quarter’s inputs. It will give you a coherent arc faster than you could outline one cold.
But the arc is where judgment lives, so take it over the moment the draft exists. The model will default to a tidy, balanced narrative. Your board may need the opposite: a blunt lead on the one thing that went wrong, or a deliberate de-emphasis of a metric that looks alarming out of context. Rewrite the spine in your own voice, then let Cowork repopulate the supporting slides underneath it.
If you run board prep every quarter, capture the recurring structure once so you don’t rebuild it each time. The same way engineering teams persist project context in a memory file, you can give Cowork a standing brief on your deck’s format, your board’s preferences, and the definitions that never change. Anthropic’s Claude Code memory documentation describes the persistent-context pattern that makes each session start informed rather than cold, and the same instinct applies to a recurring board deliverable.
Anticipate the Questions Before the Room Does
The work that separates a good chief of staff from a great one is walking into the meeting already holding the answer to the question the CEO will get asked. Cowork can read the deck the way a skeptical director would and generate a list of likely questions, including the uncomfortable ones the team talked itself out of including.
Treat that list as a checklist, not an oracle. It will catch the obvious probes: why did the burn rate climb, what’s the pipeline coverage, how does this compare to plan. It will not know that one director always hunts for the assumption buried in the forecast, or that another cares only about hiring velocity. Add those from your own knowledge of the room, then prep the one-line answers with the CEO before the meeting, not during it.
This anticipation step is also a quality check on the deck itself. If a Cowork-generated question has no good answer in your materials, you’ve found a gap to close while you still have time. For a deeper routine on prepping the conversation around a deck, the approach in Claude Cowork meeting prep carries over directly to the board context.
Fit Board Prep Into Your Operating Rhythm
Board prep isn’t a standalone event; it’s the loudest beat in a quarterly rhythm. The chiefs of staff who stay calm the week before are the ones whose weekly planning template already reserves time for incremental deck work, so the Thursday-night scramble becomes a Thursday-afternoon review. Cowork makes incremental prep cheap enough that doing a little each week is finally realistic.
The broader skill is knowing which parts of the chief of staff role to delegate to an agent and which to keep. The same reasoning that governs using Claude Code as a chief of staff governs Cowork: hand off assembly, keep judgment, and never let the tool’s fluency stand in for your decision. For the full set of recurring workflows, the chief of staff Cowork hub collects the routines that compound across a quarter.
You can read more about how Cowork handles this class of multi-step office work on the Claude Cowork product page, and the agentic workflow overview explains the same delegate-the-assembly pattern in a developer setting.
Frequently Asked Questions
What parts of board prep should stay human even with Cowork?
The framing and the judgment calls. Cowork can pull metrics, draft narrative connective tissue, and surface likely questions, but you decide which numbers go in front of the board, how the quarter gets characterized, and what the CEO needs to own personally. Treat Cowork’s output as a complete first draft, never a final one.
How much time does Cowork actually save on a board deck?
Most of the savings come from assembly, not authorship. Pulling metrics from scattered sources, reconciling them, and stitching a coherent narrative arc is where the hours go, and that is exactly what Cowork compresses. The judgment work that matters most takes roughly the same time.
Can Cowork anticipate board questions reliably?
It can generate a strong starting list by reading the same materials a director would. It will not know your specific board’s politics or which director always probes on cash runway. Use its list as a checklist to react to, then add the questions only you would know to expect.
Is it safe to put confidential board metrics through Cowork?
Follow your company’s data handling policy and your legal team’s guidance before putting any board-level financials through any tool. Many teams scope Cowork to a controlled workspace and review what data it can access. When in doubt, keep the most sensitive figures out and add them manually.
Start with your next deck: take last quarter’s structure, hand Cowork the metrics pull and the narrative scaffolding, and reserve your own time entirely for the framing decisions and the question prep. If you want the guided version of this workflow with templates for the metrics table and the question checklist, the Cowork course walks through it end to end.