Three objects, not one checkbox
The rule says when work should recur. The occurrence identifies the particular run. Completion records what happened to that run. If these are blurred, a new task can make overdue work disappear from attention or an old completion can be mistaken for this week’s result. Use a period label or stable occurrence reference that the receiving person can explain.
Check the trigger
Nifty documents recurrence based on date, status or completion. Those choices answer different needs. A monthly review tied to a calendar date is not the same as a maintenance task that repeats after the last one finishes. Decide which behavior the work requires before configuring it, and check the actual preview or a harmless test occurrence.
A fictional weekly review
The September 28 review remains unfinished when October 5 arrives. The next occurrence must not imply the earlier review happened. Keep the outstanding action visible and decide whether both reviews are needed, whether one can supersede another, and who may make that decision. Do not silently delete or mark the old one complete to clean the board.
Handover includes the rule owner
Give the cover person the rule’s purpose, trigger and end condition, plus where changes are authorized. A recurring automation can continue creating work after a project has paused. Review it when ownership changes. This site explains the distinction; it does not connect to an account or enable, edit or stop any automation.
Give each occurrence an identity
Name the period or event beside the task reference: equipment review, week 40, rather than equipment review alone. Record whether the next occurrence is allowed to exist while the previous one remains open. A date-triggered routine and a completion-triggered routine answer different operational needs. Test the selected behavior with harmless examples before applying it broadly. A recurring rule cannot decide whether unfinished work should be combined, cancelled or carried into another period.
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 recurring tasks — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01