Recurring work and shared timers

Plenty of work comes back every week. Recording it once and letting it repeat means it stops living in your memory, which is the least reliable place you could keep it.

Managing a repeat

A repeating task is controlled through Edit recurring, Pause recurring, Resume recurring and Remove recurring. Pause is the one people forget. When a routine stops for a month because a project is on hold, pause it rather than deleting it or letting overdue copies pile up. Resume when the work comes back and the pattern is still there.

There is an option to carry unfinished subtasks to the next occurrence. This suits real routines where a leftover item genuinely still needs doing. Leave it off for checks that either happened this week or did not, otherwise every occurrence inherits the backlog of the one before it.

This one, or all of them

When you change or delete a repeating task you are asked whether it applies to this occurrence or the whole series. Read that question properly. Moving a single week's meeting is one occurrence. Changing the day it happens from now on is the series. Choosing the wrong one is quietly annoying to everybody else on the task.

Timers with other people

Where the option is offered you can Start for me only or Start for everyone, and later Stop mine only or Stop for everyone. Starting for everyone suits a genuinely shared session such as a workshop. It also means each person's hours are recorded, so the cost of that meeting shows up honestly.

Three things worth knowing. A timer can count down as well as up, and can be extended if you need longer. Only one timer runs at a time across everything, so starting a new one ends the old one. And completing a task stops its timer automatically, so you do not need to remember both.

Time entries can lock once the due date of a task has passed, so tidy up your hours before then rather than after.