Step-Level Due Dates

Starting in R30, Vodori supports workflow Step-Level Due Dates (SLDD). This feature automatically assigns due dates for each individual step in a review process based on your organization’s specific business rules.

By using SLDD, organizations can create a clear distinction between individual reviewer timelines and the overall target completion goal for a workflow.

How It Works

Step-level due dates are determined by rules configured for each workflow and step—specifically, the number of days allowed for a step to be in review.

For example:

Calculation Logic

• Automatic Recalculation: Dates are recalculated with each circulation, removing the need for manual adjustments on the Details screen.
• Calendar Days: Due dates are calculated based on calendar days, not business days.
• Pending Status: Due dates for future steps that have not yet been reached will display as "Pending."
• Completion Dates: Actual completion dates for each step are prominently displayed, providing transparency into the workflow progression.

Target Approval Date vs. Step Due Dates

With this update, the former "Due Date" property may be relabeled to Target Approval Date.

• Step Due Date: The system-calculated deadline for a specific task. These dates are visible in the ‘Add/Edit Assignees’ modal. 
• Target Approval Date: The overall project goal. These two dates function independently; updating the Target Approval Date does not impact individual step due dates. The only exception is if your organization uses Step-Level Due Dates based on Target Approval (not common). The Target Approval Date is visible and managed on the document Details screen.

Important Considerations & Limitations

• No Manual Overrides: There is currently no way to manually override a system-set step-level due date. Exception cases must be managed outside the system-set dates.
• Mid-Review Edits: Selecting "Edit" from the More Actions menu while a workflow is in review ends the current cycle and starts a new circulation. This triggers a restart of the step-level due dates.
• Step vs. Group Level: Due dates are set at the step level. Disparate due dates cannot be assigned to different review groups within the same step.
• Edit Due Date: A coordinator using the "Edit Target Approval" option mid-review does not cause the system to recalculate the step-level due dates. The only exception is if your organization uses Step-Level Due Dates based on Target Approval (not common).

What Happens After an “Amend and…” Vote?

For workflows that calculate Step-Level Due Dates using the Step Start approach, the due date is recalculated when the review process resumes after amendments are completed.

The system provides the newly active step with its full configured number of calendar days. Time that elapsed before the amendment is not deducted from the new review period.

For example, assume a review step is configured for four days:

• The reviewer casts an “Amend and…” vote after two days.
• The workflow moves to Incorporating Feedback while the initiator makes the requested changes.
• When the initiator resubmits the workflow, the applicable review step receives a new due date four calendar days from the time of resubmission—not the two days that remained from the previous review period.

The specific behavior depends on the vote selected:

• Amend & Progress: The workflow advances to the next step after resubmission. The next step receives its full configured review period.
• Amend & Return: The workflow returns to the step where the vote was cast. That step receives a new due date using its full configured review period.
• Amend & Resubmit: A new circulation begins from the first applicable review step. The newly active step receives its full configured review period.

The new due date is calculated when the workflow resumes—not when the reviewer initially casts the amendment vote.

Note: This behavior applies to Step-Level Due Dates calculated using Step Start. Due dates based on the Target Approval Date remain anchored to that date and follow different recalculation rules.