A one-off task saves an afternoon. A scheduled one saves it every week

The part nobody asks about

When I show a group Claude taking a whole job off someone's desk, say a folder of invoices turned into a finished summary, that's when people lean in. Almost nobody asks what happens next month, when the same invoices show up again.

If the answer is that someone opens a new conversation and explains it all from scratch, you saved one afternoon. Make it a scheduled task and you save that afternoon every time the work comes round. For a finance team that produces the same reports every week, the second saving is the one worth caring about.

Setting one up

You don't need a special mode for this. You set it up in any conversation.

1. Describe the task and how often it should run. "Every Monday at 9, go through what moved in the pipeline last week and write it up the way we always do."
2. Answer the questions Claude asks back.
3. Review what Claude put together and change anything that's off.
4. Click Schedule.

From then on the task lives under Scheduled in the sidebar. It runs in the cloud, not on your laptop. There is one catch. A task that works with files on your computer needs Claude Desktop open when it runs. If you'd rather not keep track of that, point the task at apps Claude is connected to instead of a local folder.

Three I'd start with

The Monday pipeline brief

Every Monday morning, a short write-up of what moved and what slipped, in the format your team already uses. Anthropic's own example goes further. One conversation produces a pipeline report plus five matching slides, and then it gets scheduled to run every Monday.

The daily hand-off report

At the end of each day, what's still open, who's waiting on whom, and the first thing tomorrow's shift needs to know. Any team where work changes hands at a fixed hour gets a lot out of this one.

The weekly spend snapshot

Once a week, where the money went compared with last week, with anything unusual at the top. If the numbers sit in a spreadsheet on your computer, the Desktop rule above applies.

Write the brief as if you won't be there

Because you won't be. A scheduled task runs while you're in a meeting or asleep, and nobody is watching to catch a vague instruction as it happens. Say what you want to end up with, what format it should come in, and which files, links or apps Claude should work from.

Then start with tasks that produce something for you to read. A report that lands every Monday is easy to check. A task that sends messages, spends money or changes important files on its own schedule is one to keep a close eye on. Let a report-only task prove itself over a few good Mondays before you hand over anything with more at stake.