Change requests and the decision log
Propose a change to the agreed plan, see its impact from the schedule, decide it, apply it as one change -- with the decision on record.
Raising a change request
RAID register, Change requests tab, New change request. Say what should change -- extend, shorten or move a task by a number of days, optionally with the tasks that depend on it -- and why, and the cost. The impact is worked out by the schedule as you type: the finish, the milestones that move, the tasks that shift, anyone who ends up over capacity. Save it as a draft or submit it; the project's owners and editors are notified.
Deciding and applying
An owner or editor approves, sends it back for changes, or rejects it, with a reason. Approve & apply applies it straight away: the change is worked out again on the plan as it is then, and applied as one change you can restore in Activity, Changes. Only an approved request can be applied.
Approving or rejecting records a decision in the register (DC-01, DC-02 ...) with the reason, the schedule impact and the cost. Decisions can also be added by hand, with when, by whom, and what they cost. Depentra AI cites decision records when it explains why a date moved.