When should a recurring task count as done?
by•
In many products, a recurring task looks complete as soon as it is created or scheduled. But that can hide the real question: did someone actually see it and act on it?
I have found that “scheduled” and “handled” are very different states, especially when work repeats every day or week.
How do you show that difference in your product without making the workflow feel heavy?
5 views
Replies
Wynn, scheduled versus handled is the exact distinction that caused problems for me. A dismiss with no reason attached looks identical to an alert nobody has looked at yet, so the unreviewed queue quietly fills with noise disguised as progress. What ended up working was requiring a reason on override instead of on completion, since asking for a reason on every routine task just makes people stop marking anything at all. Curious if you are solving this for a single user's task list or for something that multiple people need to trust at once.