The working day
A weekly task completed three days late should not become a Thursday task.
But that is what most recurrence does — the next one is counted from when you ticked the last one, so a fortnight of slightly-late completions quietly moves a Monday routine into the middle of the week.
Nobody notices until the routine has stopped working.
Recurrence
The next one is counted from when it was due, not from when you finished.
So a task finished three days late does not drag the whole chain three days later. A weekly review stays a weekly review.
Every copy points at the head of its chain, which is what makes "this is the fourth of these" a question with an answer.
- Applied templates are due at the end of the working day —
Not at midnight. Two templates ship — onboarding a new customer, and following up after a demo — each with its steps offset by days.
- A task due today does not read as overdue at nine in the morning —
The date is normalised to the end of the day. Small, and it is the difference between a list people trust and a list that cries wolf.
- Two separate permissions for giving somebody work —
Creating a task for another person, and moving an existing one, are different rights — because they are different acts.
- Reassigning moves ownership with it —
Rather than leaving a task assigned to one person and owned by another.
Follow-ups
A follow-up remembers what caused it, and how far it has slid.
A follow-up is raised from something — a call, a note, an email, a recording, a person, a deal — and it keeps a pointer back to it. So the question "why am I doing this" is answerable from the row.
Its title comes from the first real line of what you wrote, so the list never shows a blank row.
And the snooze trail is the part worth having. The original due date is stamped on the first snooze and never again, so the record shows the total distance travelled rather than only the most recent push.
- Originally dueraised from a call4 Aug
- Snoozed7 Aug
- Snoozed14 Aug
- Now due29 days past the original2 Sep
- Snoozing is refused on the wrong kind and the wrong state —
Each by name, rather than silently doing nothing.
- Email reminders default on, per follow-up —
With the reasoning stated in the code: a missed follow-up is a lost deal. It can be turned off for a specific one.
- The overdue count is always yours —
The "am I behind" question is about the person asking it, so that tile does not re-scope when a manager changes the view.
›Are there subtasks?
No. The recurrence link is a chain, not a hierarchy. A task that needs breaking down is several tasks.
›Do sequence steps appear here?
Not today — a task step inside a cadence lives in the cadence queue and does not create a task in this list. Worth knowing when deciding where a team's work should live.
›Can a deal's next-step date remind me?
Not currently. The field is on the deal, editable and exported, and nothing surfaces it. Use a follow-up for anything you need to be reminded about.
›Can I report on tasks?
No. The report builder covers deals, accounts, contacts, leads, activities, forecast submissions and sequence enrollments — not tasks or notes.