How to Set Up Recurring Tasks in Claude

The difference between fast and gone

Lesson two made your conversations start informed. That is faster. This lesson is about something better than faster, which is work that happens without you being the one who starts it.

There is a whole category of small jobs you do on the same day every week. The Monday priorities list. The Friday summary for your manager. The month end nudge to three people who always need nudging. None of them are hard. Each costs ten minutes plus the mental overhead of remembering, and remembering is the expensive part.

A scheduled task removes the remembering. You define the work once, say when it should run, and it arrives.

Where to find it

Claude can run work on a schedule. The place you set that up has moved around over time, and availability can differ by plan and by whether you are on a computer or a phone, so the honest instruction is to look for anything offering to repeat, schedule or run a task at a set time, near where you would normally start a conversation or manage a workspace.

What makes a good scheduled task

Three things, and a task that fails any of them will annoy you within a fortnight.

It is clearly defined. You can write down exactly what should come back, in what shape, without using the word roughly. If you cannot describe the output, an automated version will produce something different every week and you will stop reading it.

It needs little judgement. The task should not depend on something only today's you knows. Summarise these notes into decisions and actions is low judgement. Decide which client to prioritise is not, because the answer changes with information that lives in your head and your inbox.

It is useful even when imperfect. This is the one people underrate. A scheduled summary that is eighty percent right and lands on your screen at eight on Monday morning beats a perfect one you never get round to writing. If eighty percent is dangerous rather than merely imperfect, the task belongs in the next lesson's do not automate list.

Three you can set up this week

Start with these. They are deliberately dull, which is why they survive.

Run every Monday morning.
Using the attached tracker and my notes, give me my week opener.
DUE THIS WEEK: item, owner, day. Dates exactly as written in the source.
SLIPPED: anything past its date, with how many days late.
NOTHING HEARD: anything with no update for 14 days or more.
ONE THING TO DECIDE: the single item most likely to block others this week.
Bullet points only. Under 200 words. No encouragement, no summary paragraph.
If a date is missing write NO DATE. Never estimate one.

Run every Friday afternoon.
Turn this week's notes into a short update I can edit and send to my manager.
Four sections, one line each item: DONE, MOVED BUT NOT FINISHED, BLOCKED,
NEED FROM SOMEONE ELSE.
Under 180 words. Plain sentences, no adjectives, no padding.
End with a line beginning CHECK THIS: listing anything you were unsure about.
Do not send anything anywhere. Just draft it for me.

Run on the first working day of each month.
From the attached list of outstanding items, produce a chase list.
For each item overdue by more than 7 days: who owes it, what it is,
how long overdue, and a two line message I could send.
Order by how overdue, most overdue first.
If nothing is overdue, reply with the single line NOTHING OVERDUE and stop.
Draft only. I will send them myself.

Notice the last line in two of those. Draft, do not send. A scheduled task that produces something for you to read is low risk. A scheduled task that acts on the world without a human in between is a different animal entirely, and lesson five is where we deal with it.

Start with one

One scheduled task, running for a month, teaches you more than five set up in an afternoon. You will learn what you actually read, what wording you keep fixing, and what you quietly ignore. Then you improve that one and add the next.