CHAPTERS
- 0:05 – 0:35
Setting up Claude Cowork for recurring meeting prep
The video shifts from a simple demo to a realistic workflow: preparing for a major customer call. You’re shown how connecting calendar, Slack, and email lets Claude gather context quickly for a specific meeting.
- •Moves from a self-contained task to real-world meeting preparation
- •Connects key tools: calendar, Slack, and email
- •Points Claude to a meeting notes folder as the destination/template source
- •Uses a concrete example: “today’s call with Acme Corp at 1 PM”
- 0:35 – 1:05
Delegating a multi-step meeting prep plan (calendar, research, Slack, notes, agenda)
You instruct Claude with a detailed set of steps and a formatting constraint based on existing docs. Claude turns the request into an explicit plan and begins executing the task list in order.
- •Claude searches the calendar to find the correct meeting
- •Researches attendees/who you’re meeting with
- •Checks Slack for recent account threads
- •Reviews previous meeting notes
- •Creates an agenda that follows the folder’s existing template/format
- 1:05 – 1:36
Mid-task updates: adding email context without restarting
While Claude is already working, you realize another source matters and ask it to check email too. Cowork adjusts the in-flight plan rather than forcing you to stop and regenerate.
- •Adds a new requirement mid-execution: check email for additional context
- •Highlights difference from typical chat workflows (no restart needed)
- •Claude pivots and continues the task seamlessly
- 1:36 – 1:51
Reviewing the output: agenda doc plus decision guidance
Claude finishes by sharing a completed agenda and surfacing strategic guidance for the meeting. It also saves the agenda to your working folder for easy review and ownership.
- •Delivers a completed agenda document
- •Calls out decisions to push for during the meeting
- •Highlights your biggest win to lead with
- •Flags watch-outs to monitor
- •Saves the full agenda to the working folder
- 1:51 – 2:06
Template fidelity: matching headings, structure, and formatting
The video emphasizes that Claude didn’t just generate content—it mirrored the team’s established doc style. It pulled structured information from multiple sources and set you up to capture actions during the call.
- •Matches existing agenda format and headings
- •Uses consistent bullet hierarchy and structure
- •Pulls attendees from the calendar
- •Incorporates context from Slack and email
- •Includes a blank action items section for live note-taking
- 2:06 – 2:21
Iterating after review: adding missing pricing context from Slack
After you spot a gap, you direct Claude to include a specific pricing update from a recent Slack thread. Claude finds the thread and integrates the details into the brief.
- •User identifies missing context (recent pricing conversation)
- •Claude locates last Tuesday’s Slack thread
- •Updates the prep brief by folding in the pricing update
- •Demonstrates fast post-generation iteration
- 2:21 – 2:36
Clear handoff: Claude does the legwork, you own the final document
The workflow closes the loop with a handoff model: Claude prepares and drafts, but you retain final control. You can edit via Claude or directly, depending on preference.
- •You can make final edits through Claude or manually
- •Positions Claude as a prep assistant, not the final owner
- •Emphasizes user control over the final output
- 2:36 – 2:52
Scheduling autonomous work: hourly Drive change monitoring and summaries
The video transitions to scheduled tasks that run while you focus elsewhere. An example shows monitoring a shared Drive folder, summarizing document changes, and saving daily updates grouped by client.
- •Creates a scheduled workflow instead of a one-off task
- •Checks a shared Drive folder for added/modified docs
- •Captures who made changes and what’s new
- •Groups summaries by client
- •Saves the result into a Daily Updates folder
- 2:52 – 3:08
Reviewing and adjusting the scheduled-task prompt and cadence
Before scheduling, Claude drafts the task instructions for your approval. You can edit the cadence and wording, then accept to create the automation.
- •Claude proposes a draft prompt for the scheduled task
- •User reviews before anything is finalized
- •Cadence can be changed (hourly, daily, weekdays, manual)
- •Accepting the proposal creates the scheduled task
- 3:08 – 3:38
How scheduled runs work: sessions, freshness, and the Scheduled page
Once created, the task appears in the Scheduled page and runs automatically while the desktop app is open. Each run uses fresh context so summaries reflect the latest state of files and connected tools.
- •Scheduled tasks appear in the left-sidebar Scheduled page
- •Runs automatically while the Claude desktop app is open
- •Each run is a separate Cowork session with fresh context
- •Always operates on the latest files/tool state
- 3:38
Operational requirements: app open, computer awake, and delayed-run behavior
The video clarifies reliability details: tasks require your computer to be awake and the desktop app to remain open. If a run is missed due to sleep/closure, Cowork executes it upon return and flags the delay.
- •Computer must be awake for scheduled cadence to be met
- •Claude desktop app must stay open
- •If a task is due while asleep/closed, it runs when you’re back
- •Cowork notifies you that the run was delayed
Managing scheduled tasks and closing takeaway: legwork on your terms
You can audit and control automations from the Scheduled page—review runs, edit instructions, change cadence, or run on demand. The conclusion frames Cowork as flexible: steer live tasks or rely on schedules to protect your attention.
- •Review past runs from the Scheduled page
- •Edit task instructions and change cadence anytime
- •Trigger tasks on demand
- •Scheduled tasks can use any configured connectors
- •Cowork supports both interactive steering and autonomous execution
