Configuring Reversion Steps and Reapproval Settings
As an administrator, setting up reversion steps and reapproval requirements in Weissr Capex Management ensures that your project approval processes align with organizational policies and workflows. This guide explains how to configure these settings effectively to maintain structured project reviews and approvals.
How to Define Reversion Steps
Reversion steps can be configured for approval route steps with a status that includes a move back action. By default, a project will revert to the immediately preceding step. To enable reversion to earlier steps, you must specify which steps are available for reversion and decide whether reapprovals are required for the reverted steps and subsequent ones.
Configuring Reversion Steps
Access the Approval Route Settings
Navigate to Capex Management → Approval Routes.
Expand the desired approval route to view its steps.
Open Reversion Step Settings
Click the context menu (three dots) next to the step you want to configure.
Select Reversion Steps from the dropdown menu.
Specify Steps for Move Back
Select the prior steps to which the project can be reverted, ensuring the selection aligns with the project’s structure and expected review paths.
If multiple steps are selected, the decision-maker moving the project back must choose the specific step to which the project should be reverted.
Set Reapproval Requirements
By default, reapproval will be required for the selected step and all subsequent steps.
If not all subsequent steps require reapproval, uncheck the Require Reapproval option for the unnecessary steps.
Step Reversion Limitations
Reversion steps can only be configured within the same project category or phase to maintain consistency in the project lifecycle.
For example, projects in the Execution Phase cannot be moved back to the Decision Phase but can revert to earlier steps within the Execution Phase if configured. However, an exception exists: it is permitted to move a project from the Post-Completion Phase back to the Execution Phase, provided the reversion is initiated from the immediate preceding step. To reopen the Execution Phase during this reversion, the "Move Back" status must have the Next State set to Monitoring.
What Happens When a Project is Moved Back
When a project is moved back to a previous step, several changes occur to reflect the updated status:
Visual Indicators: All prior steps in the approval route will display an arrow to indicate that the project has been moved back. This ensures that stakeholders can easily track the project's path and understand its current position in the workflow.
Reopened Step: The step to which the project has been moved back becomes active and open for new approvals. This step will be treated as the current stage, requiring a decision-maker to take appropriate action.
Reapprovals: The reapproval process depends on settings configured by administrators:
Single Step Reapproval: If settings specify that only the destination step requires reapproval, the project resumes from that step once it is approved.
Full Subsequent Reapprovals: If configured to require reapproval for all subsequent steps, every step following the moved-back step must be reapproved. This ensures that the entire route segment is reviewed and validated before the project progresses.
Updated Workflow Status: The workflow’s overall status reflects the move, indicating that the project is back in the earlier step for further review or modification.
Notifications and Communication: Notifications are sent to inform relevant stakeholders of the move, ensuring that everyone involved is aware of the project’s new status and any required follow-up actions.
