Course contents
Scheduled Tasks and Automations
Recurring reports, one-time reminders, and event-triggered automations — proven manually, then scheduled.
Scheduling is where Work stops being a tool you use and starts being a system that runs. Four trigger types: one-time ("in 6 hours"), recurring ("every Monday 8am"), event-based ("when her reply arrives"), and continuous monitoring. The iron rule from the Cowork course applies identically here: never schedule an unproven task.
The official build of a weekly metrics report — the same recipe as this walkthrough.
Prove the report manually
Run your recurring report once, on demand, and review it hard.
promptCompile my weekly metrics report: pull last week's numbers from the metrics sheet in Drive, compare to the prior week, chart the trend, and flag anything that moved more than 10%. One page.VerifyThe on-demand version is correct and formatted the way you want it every week.Schedule the recurring run
Add the cadence — from a cloud surface (web or mobile), which matters for reasons the Cloud vs Local lesson covers.
promptRun this every Monday at 8:00 AM and notify me when it's ready.VerifyThe task appears in your scheduled tasks list.Build a conditional follow-up
The pattern that impresses everyone: promise + deadline insurance. Riley's version — draft the reply, then create a one-time automation that sends a follow-up in 6 hours if he hasn't delivered.
promptStarting tomorrow at 9:00 AM, check hourly for Emily's response. As soon as she replies, add her answer to the project doc in Notion and email me a summary.VerifyOne notification when the condition fires — not hourly noise.Audit your automations monthly
Scheduled tasks consume usage allowance every run and drift as data sources change. Once a month, list them, kill the stale ones, and re-verify the important ones.
VerifyYou can name every automation you're running and why it still earns its slot.