Change a task scope without losing the original agreement
Assess a requested change, update the right record and recheck the affected work.
Change a task scope without losing the original agreement
Separate a correction from a new requirement. A correction makes the output meet the original agreement; a new requirement changes what must be delivered.
Assess and apply the change
1. Open the task and its project. Read the current description, accepted requirements, dates, estimate and related files. 2. Write the requested change and its effect on effort, dates, dependencies and review. Agree the new scope with the person responsible for the delivery before editing the commitment. 3. Prepare the revised output with a clear version name. Keep the earlier version according to your team’s retention process. 4. Open the existing task. Update Description and any agreed Status & Planning values. Keep unaffected fields unchanged, then select Update Task. 5. If a revised file already exists in Files, use Related Documents → Attach from Vault to link that version and save with Update Task. Keep the version decision clear rather than silently removing useful history. 6. Reopen the task and compare its description, dates, estimate, relationships and filenames with the agreed change. 7. Review the revised output and save the decision in Comments using the send arrow. Update delivery instructions to name the exact accepted versions.
Expected result: the changed requirement, updated task and revised output agree, with any unfinished review or delivery work still visible.
When the workflow itself needs changing
Board-wide definitions live under Config, including Statuses, Priorities, Resolutions and Stages & Rules. Ask the Board administrator to assess affected records before changing them. A Task status is separate from a Project or Sprint status. A terminal-state setting can restrict later movement; renaming Done to Accepted does not supply missing acceptance evidence.
If a save is unclear: reopen the same record before repeating it. Do not create a replacement task or delete a definition to recover an uncertain update.
Continue learning
In this series: Plan and deliver work — guide 15 of 17.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.