How to Put Your Week on Autopilot with Claude

Most people try to automate a messy week and end up with a faster mess. The order matters. First you decide what actually deserves your time, then you hand the repeating parts to Claude on a schedule. I run my own week this way while shipping apps, and the setup takes one quiet afternoon.

Sort the week before you automate it

A long to-do list looks like a plan. In practice it is a pile of guilt with no order. Before any automation, dump everything into one Claude chat and let it push back on you. The part you cannot do alone is cutting things, so make that the point of the prompt.

Here is everything on my mind this week, unfiltered. Sort it into four groups:
1. Do this week (it matters and has a real deadline)
2. Schedule (it matters, no deadline, so it keeps getting skipped)
3. Hand off or automate (someone or something else could do it)
4. Drop (be honest, most lists have a lot of these)

Rules: no more than 3 items in group 1 per day. For every item in group 4,
give me one line on why it can go. For group 3, say who or what could take it.
Then ask me the one question that would change this sort the most.

My list:

Argue with the result where it is wrong, but let the drop list stand. Everything in group 3 that repeats every week is your automation shortlist.

Pick where each automation runs

Claude has three places to run scheduled work, and choosing the right one saves most of the confusion later.

• Cowork scheduled tasks. In the Cowork tab of the Claude desktop app, type /schedule and describe the task. These run in the cloud, so your computer does not need to be awake. This is the easiest start if you never open a terminal.
• Claude Code routines. A routine is a saved prompt plus a schedule plus the connectors it may use, running on Anthropic's cloud. Create one at claude.ai/code/routines or by typing /schedule inside Claude Code. Routines need a Pro, Max, Team or Enterprise plan and are still in research preview. A routine clones a GitHub repository at the start of each run, so a small private notes repo works well as its home.
• Desktop local tasks. In the desktop app's Code tab, open Routines, choose New routine, then Local. These run on your machine with access to your files, but only while the app is open and the computer is awake.

The rule I use: if the job reads your inbox, calendar or docs, run it in the cloud. If it touches files on your laptop, run it locally. The official comparison is in the scheduling docs.

Connect your tools once

Scheduled work sees your tools through connectors. Connect the ones you actually use, such as Gmail, Google Calendar, Google Drive, Notion or Slack, in your Claude settings. Each asks you to sign in once. After that, every routine and task can use them.

Four routines that pay for themselves

You do not need ten automations. Start with the four below and add more only after they run clean for a week.

Monday plan

It is Monday morning. Read my Google Calendar for this week and the task
doc at [link]. Write a one page plan: the 3 outcomes that would make this
week a success, the meetings that need prep, and any day that is already
overbooked. Flag anything on the calendar that does not serve the 3 outcomes.
Save it as a draft titled "Week plan" and do not send anything.

Daily brief

Build today's brief in under 150 words: my meetings in order with times,
the one task that matters most today and why, and anything waiting on me
from yesterday's email. Save it as a draft titled "Today". If there are
no meetings, say so in one line instead of padding.

Inbox drafts

Read unread email from the last 24 hours. Group it into: needs me today,
needs a reply this week, and no action. For the reply group, write a short
draft reply on each thread in my tone. Never send, archive or delete.
End with a single draft called "Inbox summary" listing all three groups.

Friday review

Compare this week's plan draft with what actually happened on my calendar
and in my sent email. Tell me where the time really went, one thing to stop
doing, and the first task for Monday. Be direct, skip the encouragement.
Save it as a draft titled "Week review".

Swap "draft" for wherever you look first in the morning. A Gmail draft, a Notion page and a Google Doc all work, as long as it is a place you already check.

Guardrails that keep it trustworthy

Automation looks risky because it can act while you sleep. In reality the risk comes from a few specific settings, and you control all of them.

• Drafts only at first. Every prompt above drafts or summarizes. Nothing sends, posts or deletes. Keep it that way until a routine has earned it.
• Trim connectors per routine. A cloud routine includes all your connectors by default and runs without permission prompts. Remove every connector a routine does not need before you save it.
• Web research needs network access. Routines use an allowlisted network by default. Connectors still work, but if a routine must browse the open web, change the environment's network access first.
• Timing is approximate. Runs start a few minutes after the scheduled time on purpose. A local task that missed its slot while your laptop slept runs once when it wakes, so a morning task may land at night. Write prompts that check the date.
• It uses your plan. Routine runs draw from your normal usage and there is a daily cap on runs. You can see both at claude.ai/settings/usage.

Tune the prompt during week one

For the first week, read every result. When something is off, resist the urge to edit the draft by hand. Open the routine and change the prompt, because the prompt is the automation. Every run is saved as a session you can open, so you can see exactly what Claude read and why it wrote what it did.

A good sign you are done tuning: you read the Monday plan and change nothing. That usually takes two or three weeks.

Start this weekend with the sort prompt and one routine, the daily brief. Once it lands where you look every morning for five days in a row, add the Friday review. The full reference for cloud routines is in the routines docs, and the local version is covered in Desktop scheduled tasks.