Separate a date edit from agreement
Changing a due date records a new value. It does not establish that another team accepted the change or that resources became available. Note why the date changed and which commitments it may affect. Avoid overwriting the only explanation of the previous plan if that history is needed to understand the work.
Inspect the cascade
Nifty documents that due-date changes can cascade through linked tasks and subtasks. After a change, inspect the relevant chain and any commitments outside it, such as a meeting or another team’s delivery. A cascade can keep relative dates aligned while still creating an unrealistic overall plan.
A fictional consequence
An input task moves two days later. Two dependent tasks move with it, but a weekly review meeting does not. The receiving owner should raise the mismatch rather than treating all displayed dates as agreed. Options may include changing the meeting, reducing the review scope or obtaining an earlier partial input; each needs the appropriate decision.
Do not repair with silent edits
If two records disagree, identify which one controls the commitment and who can resolve the conflict. Record that answer before updating other copies. Do not run repeated date changes until the board looks tidy. The useful outcome is an understandable plan with acknowledged exceptions, not uniform dates across every surface.
Keep the original comparison
For a meaningful change, retain the earlier target, revised target, reason and affected task references in the approved record. Compare the revised chain with external commitments rather than checking only whether all dates moved by the same amount. A two-day cascade can be technically consistent and operationally impossible. If acceptance is still pending, label it pending and name the reviewer. Do not report the new schedule as confirmed merely because the application saved it.
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