Shift the workflow due dates when a form is sent back and resubmitted

Current State

When a form is sent back for revision and then resubmitted, the workflow starts its next round carrying the due dates from the first round. Those dates have usually passed by then, so the new round begins overdue. The reviewer's to-do arrives red on their home page, the form reads as late in the tool's table, and no reminder email goes out either, because the reminder points are in the past as well.

The only way to correct it is to open Edit Assignees and change each step's due date by hand, on every form, every time one comes back.

Desired State

When a form starts a new round of review, its workflow due dates move forward with it, so the round starts with dates that are actually ahead of it.

The original ask was to shift the whole workflow out by a week on resubmit. Other options worth weighing:

• re-apply the original interval from the resubmit date
• carry the per-step durations from the template
• prompt whoever is resubmitting with the proposed dates so they can adjust before sending
• move only the steps that have not responded yet, and leave a manually set date alone

Benefits

Coordinators stop re-dating every step by hand on each revision, which is most of the manual work on a submittal that goes around more than once. Reviewers get a due date that means something and a reminder that actually fires, instead of an item that is red the moment it lands. Overdue counts on the tool tables start reflecting real lateness rather than leftovers from an earlier round.

Requested by: Forrest Hughes