Most executives use Claude the same way they use a search engine: ask a question, get an answer, close the tab. That is leaving the most useful part of the tool completely untouched.
Claude’s Scheduled Tasks feature, built into Claude Cowork on the desktop app, lets you describe a recurring task once and have Claude run it automatically on a schedule you set. Daily briefings, inbox triage, meeting prep, competitive monitoring, weekly reviews. All of it, waiting for you when you sit down.
No code. No separate subscription. No new tool to learn. If you are already on a paid Claude plan, you have this right now.
Here is what it actually does, how to set it up in under five minutes, and six specific use cases that make real sense for anyone managing a team or carrying an executive workload.
What Scheduled Tasks Actually Is (And What It Is Not)
A regular Claude conversation is reactive. You show up, type something, get an answer, and the exchange ends there. Scheduled Tasks flips that. You set up a prompt once, attach a cadence to it, and Claude runs it on its own at the time you choose: weekdays at 8:00 AM, every Monday at 9:00 AM, daily, hourly. The output is waiting for you when you next open the app.
According to Anthropic’s official documentation, scheduled tasks have access to the same capabilities as regular Cowork tasks: connected tools, skills, installed plugins, file access, and web search. Each task runs as its own Cowork session.
A few things worth knowing before you start:
- Available on Pro, Max, Team, and Enterprise plans. Not on the free plan.
- Runs through Claude Desktop only. Your computer needs to be awake and the app open. If it is not, Cowork skips the run and catches up once you open the app again.
- Schedule options: hourly, daily, weekly, weekdays only, or manually triggered.
- Tasks use the same rate limits as regular chat. Heavy use on Pro will push against those limits; Max is the better plan for daily automation.
- No cloud execution. No mobile. This is local-only for now.
That computer-awake requirement is the one real constraint. Most executives are not going to leave a laptop running overnight for this. The practical window is weekday mornings, where you can set tasks to fire before you sit down so the output is ready by the time you open the app.
How to Set Up Your First Scheduled Task (Step-by-Step)
Two ways to do this. Both take under five minutes.
Method 1: From the Scheduled Tasks Page
- Download and open Claude Desktop if you have not already. Make sure you are logged in with a paid plan.
- Click Scheduled in the left sidebar. This is the Scheduled Tasks page shown in the screenshot below.
- Click New task in the upper right.
- Fill in: the task name, a description, the prompt (what Claude should do each time it runs), how frequently it should run, and optionally which folder to work in.
- Click Save. The task appears in your list with its next scheduled run time.
Method 2: From Inside Any Cowork Task
- Open Cowork, start a new task, and type your prompt as you normally would.
- Once you see the output you want, type /schedule in the chat input.
- Claude walks you through converting that one-off task into a recurring one, asking you about cadence and timing.
- Confirm when prompted. Done.
Method 2 is better if you are not sure what prompt to use. Run the task once manually, see if the output is what you actually want, then schedule it. Do not schedule a task you have not watched run at least once. At 8 AM there is nobody at the keyboard to course-correct a vague prompt.
The Six Pre-Built Templates (What You See When You First Open Scheduled Tasks)
When you open the Scheduled Tasks page for the first time, Claude shows you six ready-made task templates. These are visible in the image at the top of this post. You do not need to write a prompt from scratch for any of them.
| Template | What It Does | Default Schedule |
|---|---|---|
| Daily briefing | Pulls what needs your attention across calendar, email, and messages | Weekdays at 8:00 AM |
| Inbox triage | Categorizes your inbox and drafts replies for anything urgent | Weekdays at 8:00 AM |
| Meeting prep | A short brief before each meeting covering attendees, context, and agenda | Weekdays at 8:00 AM |
| Weekly review | A Friday summary of what happened this week | Every Friday at 4:00 PM |
| Content ideas | Drafts a few post ideas from the latest news in your industry | Every Monday at 9:00 AM |
| Monitor a topic | Watches for news or mentions of a topic, competitor, or keyword | Daily at 9:00 AM |
Each template is a starting point. You customize the prompt, the cadence, and the tools Claude uses to complete it. Connecting your calendar, email, and Slack through the Claude integrations settings makes most of these meaningfully more useful.
Six Use Cases That Actually Work for Executives
1. The Morning Intelligence Briefing
This is the one that most people set up first, and with good reason. The idea is simple: instead of spending 30 minutes checking email, scanning news, and pulling together what matters before your day starts, Claude does it while you are getting ready.
A prompt that works well:
“Every weekday at 7:30 AM, pull my unread emails from the last 12 hours, summarize the calendar for today with prep notes for each meeting, and give me a 5-bullet news brief on [your industry]. Keep the whole thing under 400 words. Format it so I can read it in two minutes.”
Connect your calendar and email through Claude’s integrations first. The output will be waiting in a dated file in your Cowork folder by the time you sit down.
2. Inbox Triage Before You Touch It
Inbox zero is not a system, it is a fantasy. What actually works is starting the day with someone having already sorted what is urgent from what is noise. Scheduled Tasks can handle that layer.
A practical prompt:
“Every weekday morning at 6:30 AM, scan my inbox. Draft replies for anything straightforward. Flag emails that need my actual judgment with a one-line summary of what they need. Ignore newsletters and promotional mail. Save the triage to a file so I can review it when I open the app.”
This does not send anything. Claude drafts. You review, edit if needed, and send. That review step matters: never set this to send automatically unless you are very confident in how consistently the prompt performs.
3. Meeting Prep That Does Not Require 20 Minutes of Context Gathering
The cognitive overhead of back-to-back meetings is not the meetings themselves. It is the context switching. Who is this person, what did we last discuss, what do I need to cover, what materials should I have read. Most executives spend more time gathering that context than they do actually preparing.
Here’s the thing: this is exactly the kind of multi-step lookup that Claude handles well.
“Every weekday at 7:45 AM, look at my first three meetings of the day. For each one, pull the attendees, any prior email threads with them in the last 30 days, and any relevant files I have shared with them. Give me a one-paragraph brief per meeting. Flag anything I need to decide or prepare before the call.”
The output quality depends heavily on what tools you have connected. Google Calendar, Gmail, and Google Drive connected together is the setup that makes this genuinely useful.
4. Competitive and Topic Monitoring Without the Noise
The Monitor a Topic template is designed for exactly this. You give Claude a company name, a keyword, a competitor, or a market signal, and it checks for developments on a daily or weekly cadence.
What makes this different from a Google Alert: Claude does not just surface mentions. It summarizes them, filters out the irrelevant ones, and tells you what actually changed versus what is just noise.
“Every Monday at 9:00 AM, check for news and developments about [competitor name] and [adjacent market trend] from the past seven days. Summarize only what is materially new. Skip press releases and puff pieces. Give me three to five bullets with source links.”
This is the task that pays off over time. After a few weeks you start spotting patterns you would have missed checking manually.
5. Weekly Review That Actually Gets Done
Most leaders know a Friday review would be valuable. Few actually do it consistently because it requires sitting down, pulling data, and writing something structured at the end of a week when the last thing you want to do is more work.
Scheduled Tasks solves exactly that:
“Every Friday at 4:00 PM, give me a structured weekly review. Pull what meetings I had this week, any action items I sent or received over email, tasks I completed versus carried over, and any key decisions made. Then ask me to add three things I want to carry into next week. Save the output as a dated file.”
The “ask me to add three things” part keeps a human loop in a task that benefits from one. You still write the forward-looking part yourself. Claude handles the backward-looking aggregation.
6. Content and Thought Leadership That Does Not Start from a Blank Page
The Content Ideas template is relevant to anyone who publishes on LinkedIn, runs a newsletter, or is building a professional profile. The blank page problem is real: most people know they should be putting ideas out but the activation energy of starting from nothing stops them.
A prompt that produces genuinely usable material:
“Every Monday at 9:00 AM, read the top 10 news items from [your industry] and [your specific area of expertise]. Suggest three LinkedIn post angles that connect current news to a practical insight. For each one, write the opening two sentences. Make them direct and avoid jargon.”
You are not publishing what Claude writes. You are starting from something instead of nothing, which cuts the time from “I should post something” to actually doing it by about 80 percent for most people.
How to Write a Prompt That Actually Works on a Schedule
A prompt that works fine in a live conversation will fail on a schedule. The reason is simple: there is nobody there to answer a follow-up question or redirect a confusing output. Here is what to get right.
- Run it once before scheduling it. Watch what it produces. Refine the prompt until the output is what you actually want, then schedule it.
- Specify the exact output format. “Under 400 words” and “bullet points with headers” are instructions Claude follows reliably. “A good summary” is not specific enough.
- Tell Claude where to save the output. “Save as a dated file in my Cowork folder” gives you a record to review and compare over time.
- Name the sources explicitly. “Check my Gmail inbox” is better than “check my email.” “Pull from Google Calendar” is better than “look at my schedule.”
- Add a human review step for anything consequential. Drafts are always safer than sends. If a task produces something that goes anywhere outside Claude, you should be reading it first.
Honest Limitations You Should Know
This feature is in active development and there are real constraints that will affect how you use it.
- Computer-awake requirement. Tasks only run when your machine is on and Claude Desktop is open. This makes cloud-synced tools like Google Calendar and Gmail more reliable data sources than local files, because the machine that processed the task is the one that has the file.
- No memory between runs. Each scheduled task starts fresh. Claude does not remember what it produced last Monday when it runs again this Monday. If continuity matters, save outputs to a consistent file and reference it in the prompt explicitly.
- Rate limits apply. Each scheduled task uses message capacity. If you are on Pro and running several daily tasks, you will hit limits. Max is the realistic plan for consistent daily automation.
- No direct action on external platforms. Claude can draft replies and flag items, but it does not have permission to send emails, post to Slack, or update a CRM unless you have specifically connected and authorized those integrations through Cowork’s connector settings.
- Prompt specificity determines output quality. This is not a set-and-forget tool. Spend 20 minutes getting the first task right and you will save hours over the month. Skip that step and you will get inconsistent outputs that erode trust in the whole workflow.
Where to Go From Here
Start with one task. The morning briefing is the right first choice because it delivers value immediately and the failure mode is low-stakes: if the output is not what you wanted, you just did not get a useful brief that day. Nothing broke, nothing went out.
Get that one task right before adding more. Once you have seen a prompt perform well across five or six runs, you know what good looks like and you can replicate it for the next one.
The version of your morning that exists six weeks from now, where three or four recurring tasks are running in the background while you sleep, looks meaningfully different from the version where you open your laptop and start from scratch every day.
That gap is where this tool actually earns its place.
If you are an executive or team leader who has already tried Claude’s Scheduled Tasks, share what prompt you would not give up. It might save someone else two weeks of trial and error.
Sources
- Anthropic Support: Schedule Recurring Tasks in Claude Cowork
- Anthropic: Claude Plans and Pricing
- AI Blew My Mind: Claude Cowork Scheduled Tasks: 6 Ways I Automated My Work on Repeat
- Fast.io: Claude Cowork Review 2026
- Write A Catalyst: Claude Dispatch + Cowork: The Real Way to Use AI as an Executive Assistant
- PostHog: Making Claude Cowork Actually Useful
Leave a comment