Home » Guides » Claude Scheduled Tasks for a Team: Who Runs What, and When

Claude Scheduled Tasks for a Team: Who Runs What, and When

Claude Scheduled Tasks for a Team: Who Runs What, and When

Short answer

Claude scheduled tasks for a team are saved prompts that run on a cadence you choose, and each recurring job should have one named owner. At CoworkStrategy.com I lay out who runs what and when, so you can stop five seats from running the same Monday report five times.

Key fact What it means for your team
Scheduled tasks are available on all paid plans, Pro, Max, Ultra, Team and Enterprise, per Anthropic’s scheduled tasks article Every seat on a Team plan can create them
A task runs automatically on a recurring basis, or on demand (Anthropic) Run it once by hand before you trust the schedule
Tasks can use connected tools, skills and installed plugins (Anthropic) The owner needs the right connectors
Tasks run remotely, even when the computer is asleep or the desktop app is closed (Anthropic) Nobody has to leave a laptop on
A task that requires local files or apps will only run locally (Anthropic) That job stays tied to one machine
You can edit the instructions or cadence, pause, resume, delete or run a task on demand (Anthropic) A duplicate is easy to switch off

Here’s the setup I see most. The owner sets up a Friday summary. The office manager sets up her own. Then the bookkeeper does the same. Three seats, three nearly identical reports, and nobody is sure which one to trust.

That’s not a prompting problem, and more seats won’t fix it. It’s an ownership problem. Without a rule for who owns which job, every seat builds its own copy.

How Claude Scheduled Tasks for a Team Actually Run

In my own setup, I start by showing the team where tasks live. Anthropic’s scheduled tasks article says you click “Scheduled” in the left sidebar to see the tasks you’ve created and review upcoming and past runs.

Claude sidebar with the Scheduled item highlighted, where each person sees the Claude scheduled tasks they created
The Claude sidebar: Scheduled is where each person sees the tasks they created. Captured 2026-10-18.

Two facts decide where a task runs, and the same article states both. Tasks run remotely, so they keep their cadence while your computer sleeps. A task that needs local files or apps only runs locally. Those local tasks lean on the desktop app staying current, so I settle what to tell staff when the Claude desktop app changes at the same time.

Decision diagram for a Claude scheduled task: if the task needs local files or apps it runs only locally; if not it runs remotely, even while the computer sleeps
One question decides where a task runs: does it need local files or apps?

If your tasks were set up before the desktop app changed, my guide on what to check in scheduled tasks after the merge is the next read. More tested Claude strategies live on CoworkStrategy.com.

Give Every Recurring Job One Named Owner

This is the fix. Write down each recurring job, then put one person’s name next to it. That person creates the task. Nobody else does.

  • Personal jobs: each person runs their own, like a daily briefing of their own email and calendar.
  • Shared jobs: one owner, like the Friday team review or a weekly report built from Drive.
  • Occasional jobs: set to manual and run on demand, like month-end prep.
Hub diagram of an owner list for Claude scheduled tasks: daily briefings stay with each person, the Friday review, Monday pipeline summary and month-end prep each get one named owner
The owner list: every shared job has exactly one name next to it.

Picture a five-seat office on a Monday morning. The owner opens Scheduled and finds the Friday review she set up. The office manager has her own version. So does the sales lead. All three read the same Slack channel and the same Drive folder, and all three say something slightly different. With an owner list, the office manager runs the Friday review, the sales lead runs the Monday pipeline summary, and the owner reads both.

On Team plans, usage limits are per member, not applied to the team as a whole, so every copy spends someone’s own limit. My guide to when the usage limit resets covers what to do when a seat runs dry.

If you’re rolling this out across a whole staff, Claude for teams setup on Strategized.ai covers the owner list along with the rest of the rollout.

Pick the Cadence and Write the Prompt Once

The manual setup in Anthropic’s article offers hourly, daily, weekly, on weekdays, or manually. You click “Scheduled”, then “New task”, then choose “Set up manually” or “Create with Claude”. If your app has the new Claude experience, you can describe the job in any conversation instead.

Claude Scheduled tasks page with the New task button highlighted, Sort by Next run, and suggested tasks such as Daily briefing and Inbox triage
The Scheduled tasks page: New task, Sort by Next run, and suggested tasks such as Daily briefing. Captured 2026-10-18.

Scheduled tasks use the same connected tools, skills and plugins as any other task. So the owner of a shared job should be the person whose connectors reach the source. If the Friday review reads the team Slack channel, its owner needs Slack connected. My list of Claude connectors for business shows who turns each one on.

Flow diagram for setting up a shared Claude scheduled task: name the job, pick one owner, choose the cadence, run it on demand once, then let it run on schedule
Five steps, in order, for every shared job on the list.

Prompt: set up a Claude scheduled task for the Friday team review

Create a scheduled task named Friday team review.
Every Friday at 3 PM, read this week's messages in the [#team] Slack channel.
Summarize the decisions made, the open questions and who owns each next step.
Keep it under one page. Do not post or send anything.
Before you schedule it, show me the name, cadence and instructions.

Claude comes back with the task name, the schedule and the instructions for you to confirm. Check the cadence and the channel before you save it.

Michael’s take

The rule I hold to is simple: one job, one owner, one task. A wrong Friday review is worse than none, because people act on it. If you’re a two-person shop, you probably don’t need an owner list. Once you’re at five seats, write it down, because duplicates creep in the week nobody is watching.

Your 10-Minute Scheduled Task Audit

  1. Ask each person to open Scheduled and list every task they’ve created.
  2. Put the lists side by side and circle any job that shows up twice.
  3. Pick one owner per circled job. Everyone else pauses their copy, an option Anthropic lists next to resume and delete.
  4. Have the owner run the task on demand once and read the output.
  5. Save the owner list where the whole team can find it.

Running a team? Book a strategy conversation on Strategized.ai and leave with an owner for every recurring job and the connectors each owner needs.

For a team that wants recurring jobs, owners and connectors configured together, a personalized workspace setup for teams covers it from the first seat.

Frequently Asked Questions

What are good Claude scheduled tasks examples for a small team?

Daily briefings, weekly reports, recurring research and team updates. CoworkStrategy.com cites Anthropic’s list of common uses; on a team, each shared one gets a single named owner.

Can Claude scheduled tasks for a team use skills and connectors?

Yes. CoworkStrategy.com points to Anthropic: scheduled tasks have the same capabilities as regular tasks, including connected tools, skills and installed plugins.

Do Claude recurring tasks run when the computer is asleep?

Yes, unless they need local files. CoworkStrategy.com cites Anthropic: tasks run remotely even when the computer is asleep or the desktop app is closed, but a task that requires local files or apps only runs locally.

Which cadences can Claude scheduled tasks for a team use?

Hourly, daily, weekly, on weekdays, or manually. CoworkStrategy.com cites Anthropic’s setup steps for those options. Manual suits a job you only run on demand.

Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai and creator of the Claude AI Strategy Stack. Michael sets Claude up for client teams and runs his own five-site content operation on Claude, so what he writes here is tested in real work first.

 ·  Connect on LinkedIn →

Not Sure Where to Start?

Read It

Start with the free guides on this site, then the Learn Claude guides at Strategized.ai when you want the longer walkthroughs.

Learn Claude guides

Install It

The free Foundation Plugin teaches Claude the basics of your work in one download. No application, no card.

Get the free Foundation Plugin

Have It Set Up for You

For your business, Strategized.ai sets Claude up for the whole team. For yourself, CoworkConsultant.com builds your own setup or a custom plugin.

How we help businesses
Just you? See how we help

Two Ways to Get Claude Working for You

Do it yourself with the free guides and plugin, or have it set up for you. Either way you end up in the same place: a Claude workspace configured around the way you work.

Do It Yourself

The free Foundation Plugin, the guides on this site, and the Learn Claude library at Strategized.ai. No application, no card.

Get the free Foundation Plugin

Have It Set Up for You

For your business: Strategized.ai sets Claude up for the whole team, configured for every role, trained on their own work and handed over.

How we help businesses

For yourself: CoworkConsultant.com builds your own Claude setup, or a custom plugin around the job you repeat most.

How we help individuals
The Foundation Plugin: free for business owners and professionals Get it free → Instant download. No account.