Keep each approval tied to its request revision.

1. Submit request

   Capture the business case with its owner, requested amount and supporting material.

   Replace warehouse loading dockAR-88788 · Request Owner

   Submit requestBy Request Owner

2. Resolve route

   Check the request revision and eligible approver order, then retain the route context.

   Replace warehouse loading dockAR-88788 · Approval Coordinator

   Resolve routeBy Approval Coordinator

3. Verify evidence

   Check the supporting document before using it in the business decision.

   Replace warehouse loading dockAR-88788 · Evidence Reviewer

   Verify evidenceBy Evidence Reviewer

4. Approve request

   The eligible Approver records the decision for the current ordered step.

   Replace warehouse loading dockAR-88788 · Approver

   Approve requestBy Approver
   ApprovalApprover checks the assigned step, request revision and evidence before approving the business request.

5. Review execution

   Inspect the run, step evidence and any uncertain destination result.

   Replace warehouse loading dockAR-88788 · Execution Operator

   Review executionBy Execution Operator

6. Correct revision

   Retain the prior executed revision and return the successor request to review.

   Replace warehouse loading dockAR-88788 · Approval Coordinator

   Correct revisionBy Approval Coordinator

Start with Request to review

Roles and permissions

1. 01Request volume by organization

   Where is submitted work coming from, and how is it distributed across current request states?

2. 02Approval turnaround

   How much time elapsed between submission and the recorded completion of approved requests?

3. 03Open SLA exposure

   Which submitted requests or requests still under review have reached their due date, and who is assigned to them?

4. 04Delegation expiry exposure

   Which requests still under review need attention to their recorded delegation expiry?

5. 05Decision outcomes by route

   What outcomes were recorded at each ordered step, grouped by the parent request's route and the recorded route version?

6. 06Evidence verification coverage

   Which requests have supporting documents still awaiting verification?

7. 07Execution exceptions

   Which runs and attempts need investigation, and what step evidence is available?

8. 08Follow-up aging

   Which assigned actions are still open or in progress beyond their due date?

All reports and dashboards

See each stage in detail

1. Agree the first request

   Choose a request type and participating business unit. Name Request Owner, Approval Coordinator and Approver, then define the supporting evidence and any independent review required before the decision.

2. Prepare identity and policy

   Load the business unit and people records, confirm account mapping and configure the effective route. Rehearse the ordered approver selection, delegation expiry handling and SLA due-date meaning with the policy owner.

3. Map existing work

   Preserve request numbers, source identifiers and revisions. Import parent records before decisions and evidence. Load operation runs before their steps, then reconcile separate execution attempts using the original operation context.

4. Rehearse the decision

   Submit a request, resolve its route, verify the evidence and record the eligible decision. Test a changed revision and an ineligible person. Inspect the decision entry and the resulting operation and state history together.

5. Rehearse recovery

   Investigate an uncertain execution result and assign follow-up. Correct an executed request, inspect its successor revision and return it to review. Confirm that earlier evidence remains accessible throughout the correction.

Read the implementation plan