Claude Cowork: The AI Meeting Prep Tool for Chiefs of Staff

A chief of staff at a 400-person SaaS company runs the same AI meeting prep tool routine before every external call: ten minutes, one page, every meeting on the calendar. Not just the board-adjacent ones. Not just the ones that felt important enough to justify an hour of digging. Every single one. The principal walks in knowing who they’re talking to, what was said last time, and the two things this conversation needs to land. That consistency is the whole point, and it’s the thing manual prep can never deliver at volume.

Most executives walk into most meetings underprepared. Not from laziness, and not from a discipline problem you can fix with a better calendar habit. It’s arithmetic. A busy principal has fifteen to twenty-five meetings a week. Researching each counterpart and reconstructing each prior thread by hand would eat a full day. So prep gets rationed: the big meetings get an hour, everything else gets a glance at the invite in the hallway.

The chief of staff is usually the one expected to close that gap. And by hand, at scale, you can’t. This is where Claude Cowork changes the math.

Why Meeting Prep Breaks Down at Volume

The friction isn’t writing the brief. It’s the gathering. To prep one meeting properly you have to find the last email thread, skim the notes from the previous call, check what shipped or slipped since then, and remember why this person is on the calendar at all. Multiply that by twenty and the prep itself becomes a job nobody has time for.

Cowork is built for exactly this shape of work. It runs on your desktop and moves across local files, folders, and the apps you already use, pulling together information from multiple sources without you coordinating each step. Anthropic designed it for the time-consuming-but-not-complex tasks that fill a knowledge worker’s day — the assembly, not the judgment. You can read more about how it fits the chief of staff role across the broader Claude Cowork for Chiefs of Staff playbook, where meeting prep is one of four recurring workflows.

The reframe that matters: meeting prep is a synthesis problem, and synthesis is precisely what Cowork is good at. You’re not asking it to decide what to say. You’re asking it to assemble what you already know but don’t have time to pull together fifteen times a week.

The One-Page Brief That Works for Every Meeting

A good meeting brief answers four questions, and only four. Keep it to one page or it stops getting read.

First, who is this. Name, role, company, and one line on why they matter to you right now. Second, what happened last time. The decisions, the open threads, the thing you promised to follow up on. Third, what’s changed since. New numbers, a launch, a personnel move, a press item — anything that shifts the conversation. Fourth, what this meeting needs to accomplish. The two or three outcomes that make it worth holding.

That structure is deliberately boring. Boring is the feature. When the format is identical every time, the principal learns to read it in thirty seconds, and you stop reinventing the layout for each meeting.

Here’s a Cowork session prompt that produces it. The goal is a brief tight enough to read while walking to the room.

You are preparing a one-page meeting brief. Read the attached notes,
emails, and metrics. Produce exactly four sections:

1. WHO — name, role, company, one line on why they matter now
2. LAST TIME — decisions made, open threads, commitments I owe
3. WHAT CHANGED — anything new since we last spoke
4. THIS MEETING — the 2–3 outcomes that make it worth holding

Keep the whole brief under 250 words. Flag anything you're unsure of
rather than guessing.

The “flag anything you’re unsure of” line matters. It keeps the brief honest instead of confidently wrong, which is the failure mode you most want to avoid before a real conversation.

The 10-Minute Session, Step by Step

The ten minutes break down into three moves.

Minute one to five: gather inputs. Drop the relevant files into Cowork — the last meeting notes, the recent email thread, the latest metrics snapshot. Cowork can read across them, so you don’t have to summarize first. If the material already lives in a folder on your desktop, point Cowork at the folder.

Minute six to seven: run the brief prompt above. Cowork drafts the one-pager in well under a minute. Anthropic’s own guidance on writing prompts is the rule here — be specific and explicit about the output you want. The clearer your instruction, the less you’ll fix afterward. Their prompt engineering best practices are worth reading once and then internalizing.

Minute eight to ten: refine. Read the draft, correct anything off, and add the one piece of context only you carry — the politics, the history, the thing that isn’t written down anywhere. This is the part you can’t delegate, and it’s also the part that takes two minutes instead of forty.

Run this enough times and it stops feeling like a task. It becomes the thing you do between meetings without thinking about it, the way you’d glance at a watch.

Loading Context Without Spending an Hour

The trap with any prep tool is that loading context takes longer than the meeting itself. The fix is to stop loading context fresh every time.

Set up a standing place for recurring context. In Claude, a Project holds a large working context — roughly a 500-page book’s worth — and lets you add custom instructions so Claude answers from the perspective of your role and your principal. Anthropic describes this in their write-up on collaborating with Claude on Projects. Load your org chart, your principal’s priorities for the quarter, and the recurring counterparts once. After that, each meeting only needs the new material.

For external people you meet repeatedly — a key customer, a partner, a board member — keep a running file per person. Each prep session appends the latest, so next quarter’s brief starts from everything you already knew rather than a blank page. Cowork reads that file and the new inputs together.

The principle underneath all of this comes straight from Anthropic’s guidance: put your long reference material at the top, then ask your specific question. You can see the product’s full scope on the Claude Cowork page. The less you re-explain, the faster the brief lands.

Where Judgment Stays With You

Cowork handles the assembly. It does not handle the call on what to escalate, what to cut, or what your principal actually needs to walk in believing. That stays with you, and it should.

Three honest limits. First, verify the facts. A brief that confidently misstates last quarter’s number is worse than no brief, so spot-check anything load-bearing against the source. Second, mind confidentiality. Confirm your organization’s data-handling policy before loading board materials, personnel matters, or unannounced financials — many chiefs of staff start with lower-sensitivity meetings and expand once governance is clear. Third, the brief is a draft, not a script. The principal still reads the room.

Used this way, the tool removes the mechanical tax without pretending to do your job. You keep the judgment. You just stop spending your week assembling the raw material for it. Anthropic’s own teams describe similar patterns in their webinar on using Cowork at work — the consistent thread is delegating assembly, never the decision.

Frequently Asked Questions

What is an AI meeting prep tool?

It’s software that pulls together the context for an upcoming meeting — attendee background, prior conversation history, recent changes, and the goals for the conversation — and assembles it into a usable brief. Claude Cowork acts as one by reading your files, notes, and emails and producing a structured one-pager, so you spend your time refining rather than gathering.

How long does meeting prep with Claude Cowork actually take?

About ten minutes once you have a standing session pattern. Most of that time is gathering inputs and adding the context only you carry; Cowork drafts the brief itself in under a minute. The speed comes from not rebuilding the format or re-loading recurring context every time.

Can I trust the brief for confidential or executive meetings?

Treat it as a first draft and verify the facts against their source before relying on them. Confirm your organization’s data-handling policy before loading sensitive material like board documents or unannounced financials. Many chiefs of staff start with lower-sensitivity meetings and move up once the governance is clear.

How is this different from a calendar assistant?

A calendar assistant manages scheduling — finding times, sending invites, avoiding conflicts. An AI meeting prep tool like Cowork produces the substance of the meeting: who you’re talking to, what was decided last time, what changed since, and what this conversation needs to accomplish. They solve different problems and work well together.

Start With Tomorrow’s Calendar

Don’t systematize anything yet. Open tomorrow’s first external meeting, drop the last thread and notes into Cowork, and run the four-section prompt above. One brief, ten minutes, before one meeting.

If it’s useful — and it will be on the meetings you’d otherwise wing — do it again the next day, and let the pattern build from there. When you’re ready to make it a standing part of how you work, the Claude Cowork course walks through the full chief-of-staff session library, meeting prep included.