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 job.
How It Works
Step-level due dates are determined by rules configured for each job and step—specifically, the number of days allowed for a step to be in review.
For example:
| Step | Name | Step Due Date Days |
| 1 | Coordinator Pre-Review | +1 Day |
| 2 | MLR Review & Approval | +3 Days |
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.
| Scenario | Initiator Submits |
Coordinator Pre-Review Due Date (+1 Day) |
MLR Review & Approval Due Date (+3 Days) |
| Standard Path | March 30 | March 31 | April 3 |
| Path When Overdue | March 30 | April 1 (Actual) | April 4 |
| Path When Early | March 30 | March 30 (Actual) | April 2 |
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 job 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).
Comments
0 comments
Please sign in to leave a comment.