What happens to tasks when a contract is rejected and returns to a previous stage?

What happens to tasks when a contract is rejected and returns to a previous stage?

• A. Tasks are archived with no action.
• B. Tasks are reassigned to address corrections and stakeholders are notified.
• C. Tasks disappear from the system.
• D. Tasks automatically become approved.

Answer: (B)

When a contract is rejected, the workflow rolls back to the previous stage and requires corrective action. The tasks tied to that stage are reassigned to the person responsible for making the corrections, and the relevant stakeholders are notified so they know revisions are needed and can track progress. This setup preserves accountability and visibility, ensuring the contract can be updated and resubmitted properly. Archiving, letting tasks disappear, or auto-approving would skip or erase the necessary review and correction steps, which isn’t how a rejected contract should be handled.

When a contract is rejected, the workflow rolls back to the previous stage and requires corrective action. The tasks tied to that stage are reassigned to the person responsible for making the corrections, and the relevant stakeholders are notified so they know revisions are needed and can track progress. This setup preserves accountability and visibility, ensuring the contract can be updated and resubmitted properly. Archiving, letting tasks disappear, or auto-approving would skip or erase the necessary review and correction steps, which isn’t how a rejected contract should be handled.