Claude Cowork workflow for chiefs of staff and EAs — pre-read brief before, structured recap with actions after, running actions tracker across meetings.
TL;DR. Before a recurring meeting, pull together the brief — agenda, status updates, decisions needed, pre-reads. After, turn notes into a structured recap with actions and owners. 1–2 hours per recurring meeting per week saved. The single biggest lever is the running actions tracker, not the per-meeting recap.
Before a recurring meeting, assemble the pre-read brief. After, produce a structured recap with decisions and actions, and append to a running actions tracker across meetings.
Chief of Staff, EAs supporting executives, function heads running their own staff meetings.
inbox/)#/inbox/updates-[date]/output/)#prep-[meeting]-[date].docx — pre-read briefrecap-[meeting]-[date].docx — decisions and actionsactions-tracker.xlsx — running list of open actions across meetingsFor the [meeting] on [date]:
Read /inbox/last-meeting-notes.docx and everything in /inbox/updates-[date].
Produce /output/prep-[meeting]-[date].docx covering:
- Agenda (from /CLAUDE.md/agenda-template)
- Status one-paragraph per workstream
- Decisions needed (with the option set for each)
- Open actions from last meeting and their status
After the meeting, I will paste raw notes into /inbox/notes-[date].md.
Then produce /output/recap-[meeting]-[date].docx and append actions
to /output/actions-tracker.xlsx.
1–2 hours per recurring meeting per week.
meeting-prep skill keyed on a calendar event.The single biggest lever is the actions tracker. A meeting-by-meeting Word recap is fine; a running Excel of every action across meetings is what executives quietly love. After three months the tracker becomes the artifact people refer back to, and the recaps become disposable.
Book a 30-minute call. We'll ask where you are, what your team needs, and which systems Cowork should touch.