Every task system meets the same question sooner or later: what do I do with recurring tasks? The invoices at the start of the month. The furnace filter every spring. Taxes, trip preparation, the month-end close.
Most apps answer with a button: repeat daily, weekly, monthly. It feels like relief, and it is often the start of a pile that grows by itself. GTD answers differently. It first asks what kind of repetition it is. A meeting that happens every Tuesday is a different thing from a filter that needs changing roughly every six months, and both are different from a twelve-step routine you run the same way every month.
Why automation builds a pile
An automatic repeat creates the next occurrence as soon as its date arrives. Whether you finished the last one doesn't matter.
As long as everything runs smoothly, you don't notice. Then comes a full week, a vacation, the flu. "Water the plants" still comes every day, "write the weekly report" still comes every Friday, "sort the filing" still comes on the first of the month. Depending on the app, you now see several entries side by side, or one with a date long gone. Either way, your list has grown without you deciding anything.
That is the real damage. A list is only worth as much as your trust that everything on it is a real commitment. A pile the system stacks up for you wears that trust down. You start reading past entries because you know half of them are only there "again". From then on, you also read past the ones that matter. There is more on why date-driven lists fail this way in Why task apps fail.
Automation promises to take the remembering off your hands. In practice it trades remembering for cleaning up. Instead of deciding once when something is due again, you click away whatever has collected, week after week.
Without automation, the same vacation looks different. Each recurring task exists exactly once: the next occurrence. If it waits, it stays one entry and doesn't become seven. When you are back, you do it, and then you decide when it is due next. Your list grows only when you let it.
Four kinds of recurring tasks
Almost everything that comes back fits one of four groups. Each has its own place in GTD.
Tied to a day. The Monday team meeting, training on Tuesday at 7 pm, birthdays. These go on the calendar.
Due again from a date on. Sending invoices, changing the filter, comparing insurance before it renews. No fixed appointment, but a point from which it is time. These go into the tickler file.
Made of several steps. The month-end close, the packing list, onboarding a new client. These go on a checklist.
A habit. Reading, exercise, going to bed earlier. These, unlike what many expect, don't belong in the task system at all.
Tied to a day: the calendar
David Allen calls the calendar the hard landscape of your day. It holds only what really happens on that day or at that time. For recurring appointments, every calendar has repetition built in, and that is where it belongs: an appointment happens whether you tick it off or not.
In tingdo, your calendar stays your calendar. If you want to see your scheduled tasks next to your appointments, subscribe to the Calendar Feed. Then both sit in one view, in the calendar you open anyway.
Due again on a date: the tickler file
A tickler file is a set of 43 folders: 31 for the days of the month and 12 for the months. Anything you want to see again on a certain day goes into the matching folder. Each morning you empty the folder for that day, and whatever is inside becomes a task again. It is one of the quietest ideas in Getting Things Done and one of the most useful.
The idea matters more than the folders: something is safely kept and still out of sight until it counts. You don't have to read past the insurance renewal every week when it only matters in November. That is also the answer to the question people ask most about the tickler file system, how it differs from a calendar. The calendar holds what happens at a time. The tickler holds what should come back from a day on.
A physical or a digital tickler file works the same way; only the folders change. In tingdo, Scheduled does exactly this job. A task with a date stays out of your next actions and joins them on its day. Until then you can see it in Scheduled, in order, whenever you want to look at what's coming.
For recurring tasks that means: there is exactly one occurrence at a time, the next one.
- Create the next occurrence as a task and give it a date, in the next bar or later in the editor.
- Until that day, the task waits in Scheduled, not in your next actions.
- On its day, it joins your next actions, next to everything else you can do right now.
- When you finish it, create the next occurrence with the date that fits now. Or reopen the finished task and give it the new date.
This is what it looks like in Scheduled:
Scheduled
- Send October invoices Date: November 2
- Compare car insurance before it renews Date: November 10
- Replace the furnace filter Date: March 15
The last step takes a few seconds, and it is on purpose. The moment you finish something is the moment you know best when it is due again. You changed the filter three weeks later than planned? Then the next date counts from today, not from the old plan. And sometimes you notice that something doesn't need to come back at all. Then you don't create a new one.
Made of several steps: checklists as reference material
Some recurring tasks are not a single step but a routine. The month-end close has ten points, trip preparation twenty. Allen recommends checklists for routine tasks like these, for a simple reason: what you do the same way every time shouldn't need thinking through every time.
Those steps don't belong on your lists as separate tasks. Ten entries that reappear every month turn your next actions into a wall. A checklist is knowledge, not work: it tells you how something is done.
In tingdo, such a checklist is a note in Reference, the place for what you look up rather than do.
- You capture it as a note with the
*prefix in the next bar, the one input for search, capture and navigation. - Notes support Markdown. You write the steps as a checklist and tick them off right in the note as you go. When a step is easier to show than to describe, add a screenshot.
- You file it where it belongs: in a project, or in an area when it serves a standing responsibility instead of one outcome. The month-end close belongs to the Finances area, not to a project that will be done one day.
- The note stays out of your action lists. You find it through the next bar as soon as you type a few letters of its name.
To bring the checklist back at the right time, there are two ways. The shorter one: give the note itself a date. It then waits in Scheduled and shows up in your next actions on its day, exactly like a task. You don't need a separate task for it. The other way: create a task with a date, such as "Do the month-end close with the checklist", and keep the note as pure reference in its area. That fits when one checklist serves several occasions.
This is what a month-end checklist can look like:
Reference · Finances area · Month-end checklist
- Send last month's invoices
- Match open payments against the bank statement
- Upload receipts to the accounting app
- Check whether a quarterly tax payment is due this month
- Review subscriptions: is everything still in use?
When you are through, untick the boxes and give the note its next date. Then it waits quietly in Scheduled until next month.
The real value shows after a few months. Every time you notice a missing step, you add it. The checklist gets better, and you no longer have to carry the routine in your head. It is the part of your system that learns.
One note per area can do something else as well: a short overview of what comes around regularly in that area. "Finances: month-end close, quarterly taxes, tax return in April, insurance renewals in the fall." It is not a list to work through. It is the list you check to see whether each item has a next occurrence waiting in Scheduled.
A habit: not in the task system
Reading ten pages a day, drinking water, putting the phone away in the evening. Good intentions, but not next actions. A next action is a decision you make once. A habit is something you eventually do without deciding.
Daily recurring entries have a quiet side effect on a task list: you tick them off by reflex, or you push them on by reflex. Both teach you to read past your list. And a list you read past loses exactly what it is there for.
Habits are better kept elsewhere: as a fixed block on your calendar, in an app built for habits, or simply in the shape of your day.
The safety net: the review
If you forget to create the next occurrence once, that's fine. That is what the review is for.
The guided weekly review also takes you through Scheduled. Together with a look at your calendar for the coming weeks, you see what's ahead there, and whatever is missing, you add. In the areas review you read the overview you keep for each area and ask: is anything missing here? Does every recurring commitment have a next step waiting?
That is the core of GTD's answer to recurring tasks. Not automation that remembers for you, but a rhythm in which you look regularly.
The trade tingdo makes on purpose
Automation keeps repeating long after your life has changed. The subscription is canceled, the project is over, the rhythm no longer fits, and the task still comes back. That is why tingdo has no automatic repeat.
Creating one occurrence after another is a little extra work. In return, your list holds only what you have really still chosen, and nothing piles up behind your back.
It doesn't suit everyone. If your days are made of many fixed daily routines you want to tick off, an app with built-in repetition may be the better choice. That is an honest trade, not a question of right or wrong.
For everything else that comes back, three places are enough: the calendar for what happens on a day, Scheduled for what is due again from a date on, and Reference for what you do the same way each time. How these places fit into the rest of the method is in the overview of GTD.