Loading
Because it lives on a calendar reminder belonging to one person. They go on leave, it does not happen, and nobody notices until the client asks — or two people do it because neither knew.
A recurring task is a template with a schedule: the same work, owner and estimate, generated each period rather than remembered.
The schedule generates the task on its date with the owner and estimate already set. It appears in capacity like any other work, because it consumes real hours.
A monthly client report is due on the first working day. It generates three days ahead, sits in the owner's queue, and reassigns to the cover named on the schedule if they are on leave.
It will not close itself because the date passed. An uncompleted recurrence stays open and visible, which is the point of tracking it.
Generated tasks feed capacity, timesheets and — if billable — the invoice, so routine work is costed rather than absorbed.
It flags rather than silently stacking duplicates.
Yes, and it respects the holiday calendar in Nest.
Yes, on a date or after a count, keeping the history.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.