How to Write a Checklist for Recurring Work Tasks
It is the last working day of the month and you are sending invoices again. You know how to do it. You have done it thirty times.

It is the last working day of the month and you are sending invoices again. You know how to do it. You have done it thirty times. And yet you still forget to attach the timesheet for one client, chase the purchase order number for another, and only remember the late fee clause after the emails have gone. The job takes ninety minutes when it should take forty, mostly because you spend the time reconstructing steps from memory.
Recurring work feels like it should get easier with repetition, and some of it does. But tasks you do monthly or quarterly sit in an awkward gap: too infrequent to become automatic, too familiar to feel like they need instructions. That gap is where a written checklist pays for itself many times over, provided you build it in a way you will actually keep using.
Why memory fails on monthly and quarterly tasks
Daily tasks become habits because you repeat them before the details fade. Brushing your teeth, opening the same three tools at the start of the day, the commute. A job done once a month gets about twelve repetitions a year, and the gap between each is long enough for small steps to drop out.
The steps that disappear are rarely the main ones. Nobody forgets to send the invoice. People forget the edge cases: the client who needs a separate VAT line, the report that must go to a second address, the backup that only matters if the first export fails. Those are the steps that cause rework, awkward follow up emails and, occasionally, real money lost.
There is also a confidence trap. Because the task feels familiar, you start it with the attitude of an expert and skip the brief pause where you would normally ask what you might be missing. Familiarity hides gaps.
The common advice to automate everything first
A popular line in productivity writing says that if you do something more than twice, you should automate it. Write the script, build the Zapier flow, set up the template. I have tried this approach for years, and I think it is often the wrong first step.
Automation works well when the process is stable and you understand every branch. Most recurring work is not like that at the beginning. It changes a little each cycle: a new client, a different form, a deadline that moves. If you automate a process you have never written down, you encode your current mistakes and add a layer that is harder to inspect when something breaks.
A checklist is the cheaper experiment. It costs ten minutes to write, it shows you which steps are truly fixed and which vary, and after three or four cycles you will know exactly which parts are worth automating. In my experience that turns out to be fewer than you would guess, maybe a third of the steps. The rest need a human to look at them anyway.
How to write a checklist that survives the next cycle
The best time to write one is while you are doing the task, not afterwards. Open a blank note before you start and record each step as you take it. Keep the wording short and specific enough that a tired version of you could follow it without thinking.
- Write the trigger at the top. State when the checklist runs and what kicks it off, for example "Last working day of the month, after timesheets are approved." This stops the classic failure of starting too early and redoing half the work.
- List inputs before actions. Before any step that sends, submits or files something, list what you need in hand: the approved timesheet, the PO number, last month's figures. Gathering inputs first is where most of the time savings come from.
- Use verbs and specific objects. "Export March sales CSV from Shopify" beats "Get sales data." If a step lives in a particular tool, name the tool and the menu path.
- Mark the exceptions inline. Put the client specific quirk right next to the step it affects, not in a notes section at the bottom. "Send invoice. Client B: cc their accounts address."
- Add one verification step at the end. Something like "Check sent folder: one email per client, each with two attachments." A single check catches most errors before anyone else sees them.
- Record the date and duration when you finish. A line like "Done 31 Oct, 45 min" helps you notice when the task is creeping longer, and gives you a realistic estimate for planning next month.
Keep it under about fifteen lines. A checklist that runs to three pages turns into a manual, and manuals get skimmed. If a step needs lots of explanation, link to a separate note and keep the checklist line short.
Where to keep them so you actually use them
Location matters more than format. A checklist you have to hunt for is one you will skip. I keep mine in the same place the recurring task appears in my calendar or task manager, attached directly to the event or repeating to do item. When the reminder fires, the list is one click away.
Some people prefer a single "checklists" folder in their notes app with one file per process. That works if you also put a link in the calendar event. The failure mode I see most often is a beautiful folder of checklists that nobody opens because the reminder does not point to it.
For work done with a team, a shared document is fine, but give each checklist one clear owner who updates it. Shared lists without an owner tend to drift out of date within a couple of months, and then people stop trusting them.
Keeping the checklist honest
The checklist is not finished after the first cycle. Each time you run it, change one thing. Add the step you nearly forgot. Cut the step you no longer need. Reword the line that confused you. This takes a minute and it is the reason the list stays useful a year later.
After four or five cycles, read through the whole thing and look for the steps that never vary and take the most time. Those are your automation candidates. Now you can build that template or script with confidence, because you know exactly what it needs to do.
A small bonus: once a checklist exists, you can hand the task to someone else during holidays or sick days. That alone has saved me more stress than any productivity app. It pairs well with a workday shutdown ritual, since the end of the day is a natural moment to add a line you learned.
If you want somewhere to start this week, pick the one recurring task that annoyed you most last month. Write its checklist during the next run. Then tick it off in your done list so you can see the time it took shrinking cycle by cycle.
FAQ
What is the difference between a checklist and a process document?
A checklist is a short list of steps you follow while doing the task. A process document explains the why and the background. Most recurring tasks need only the checklist.
How many items should a work checklist have?
Usually between five and fifteen. Fewer than five rarely needs writing down. More than fifteen suggests the task should be split into two checklists.
Should I use a checklist app or a notes app?
Either works. What matters is that the checklist opens directly from the reminder for the task, so you never need to search for it.
When should I automate a recurring task instead?
Once the checklist has stayed the same for several cycles and a few steps take most of the time. Automate those steps and keep the rest on the list.
More in Productivity
Productivity
Workday Shutdown Ritual That Stops Work Following You Home
You close the laptop at six, make dinner, and halfway through the washing up you remember the invoice you meant to chase.
Productivity
Ivy Lee Method and How Six Tasks a Day Keep You Focused
You end the day with a to-do list of 23 items, a vague sense of having been busy, and no idea which of those items actually...
Productivity
Eat the Frog Method and When Doing Hard Tasks First Works
You know which task you should do first today, and you have already opened your inbox twice to avoid it.