Define what stale means locally
A task reviewed yesterday may still be blocked, while a quiet long-running task may be proceeding normally. Choose review expectations according to the work, not a universal age cutoff. Record the next review point and the reason for waiting. Do not use an aging dashboard as an automatic judgment about a person’s effort.
Ask the smallest useful question
Check whether the next action still exists, whether its owner is current and whether the blocking condition changed. If the task no longer belongs in the project, identify who can decide to pause, cancel or move it. Silence from an absent colleague does not answer those questions.
A fictional review set
Of ten old items, three are legitimately waiting on a scheduled event, two have completed evidence not yet recorded, and five lack a next action. Those are three different repairs. Closing all ten would improve the apparent completion rate while making the underlying record less truthful. Update each item according to actual evidence.
Keep the review bounded
Work through a small relevant set and record the decisions. If the same ambiguity recurs, repair the state definition or ownership process. Do not expand into employee monitoring or collect private communications to explain every quiet period. The goal is a usable next-action record, not surveillance or an invented productivity metric.
Choose a truthful outcome
Each reviewed item should end with an evidence-based next action: continue waiting until a named event, record verified completion, obtain an owner’s decision, or retain an explicit unresolved gap. If the review cannot establish which applies, keep uncertainty visible. Do not reward a lower open-task count independently of record accuracy. Sample the changed items with the receiver so the cleanup actually improves understanding rather than merely producing a more attractive summary.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Nifty task, subtask and milestone dependencies — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01
- Nifty recurring tasks — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01