A lighter way to repeat good work

Make recurring work easier to start

A process does not need a heavyweight system. Capture the trigger, keep the useful steps somewhere reusable, and put the next occurrence into a week when it is actually due.

See Cadence for weekly task planning

Keep the boundary clear: Cadence is a task planner, not a recurring-task automation engine. This guide is a manual workflow for work you do more than once.

Decide what makes the work repeatable

Choose a recurring job with a recognisable trigger: month-end invoicing, a Friday client update, a weekly backup review or preparing a regular report. Write down what starts it and what “done” means. If the trigger is vague, the task will appear either too early or after it has become urgent.

Keep a reusable checklist outside the task instance

Write only the steps that are easy to forget or meaningfully reduce errors. A checklist should guide the work, not document every keystroke. Store it where the source material belongs—a notes app, shared procedure or project documentation—then link or refer to it from the task if your setup supports that. Review it after the process changes.

Put the next occurrence where you will see it

When you finish, decide when the next instance is due and capture it deliberately. In Cadence, that means adding a task to the relevant week when you plan it; the app does not automatically recreate tasks on a schedule. For dates that must not be missed, use a calendar or reminder system that can alert you.

Make the queue small enough to trust

Keep a short horizon of upcoming repetitions rather than generating months of placeholder work. If a task is delayed, update its date and note the reason. If the same process repeatedly takes longer than expected, change the estimate or start earlier instead of leaving the queue permanently overloaded.

Review the process, not just the task

After a few repetitions, ask: which step caused rework, what information was missing, and is this still worth doing at the same frequency? A small improvement to the checklist may save more effort than adding more reminders.

For work that slips during the week, read how to roll tasks forward thoughtfully.

A worked example: month-end invoicing

ElementExample
TriggerLast working day of the month
Checklist (kept in a note)Export hours, draft invoices, check expenses, send, log in spreadsheet
Time neededAbout ninety minutes
Task in the week"Month-end invoicing" on the last Friday
Done meansAll invoices sent and logged
Next occurrenceAdded to the last week of next month when you finish

The last row is the whole trick in a planner without recurring tasks: finishing the job includes scheduling the next one. It takes five seconds and means the task is created by someone who has just done it and knows whether the date should move.

Which work deserves a process

Anything else can stay informal. A checklist for a job you do twice a year and never get wrong is clutter.

Where Cadence fits, and where it does not

Cadence is a weekly planner for Mac and iPhone: one board, a column per day, tasks you drag when plans change. It has no timers, projects, tags or recurring tasks, so the method on this page is something you run yourself and place into the week. It costs $19 once for Mac, with no subscription and sync through your own iCloud. More in the weekly planner guide.

Try it this week

  1. Pick the one recurring job that most often catches you out.
  2. Write its trigger and its finished state in one line each.
  3. List the steps in a note the next time you do it, as you go.
  4. Add the next occurrence to the right week before you close the note.

Do this for one job only. If it saves you a scramble next month, add a second.

Questions people ask

Does Cadence have recurring tasks?

No. You add the next occurrence when you finish the current one, which keeps the date under your control.

Where should the checklist live?

In a note, document or text file you can open in seconds. Link or name it in the task. The task is the reminder; the note is the procedure.

What if the job moves every month?

Then the trigger is an event, not a date. Write the trigger into the task name, such as "after the client sends figures", and place it in the week you expect it.

How many processes should I have?

As few as cover the work that hurts when missed. Five to ten is typical for a solo business.