Questions, answered

Click Get started, then use Proto to configure Approval Management System for your business. Pilot a request type in a participating business unit with a known approval policy, supporting evidence and named decision owners. Rehearse a normal decision and a corrected executed request before expanding.

Request Owner remains responsible for the business case. The assigned Approver decides the eligible step, while Approval Coordinator checks route context and follows up unresolved questions.

Decision entries retain their sequence, step order and outcome against the parent request. The decision-chain workflow records the operation and state history, advances the step order and marks the request Approved with its completion time. Agree the route’s completion rule during setup.

Evidence Reviewer has checked the supporting material and recorded its verification state and verifier. An independent revision review records its own outcome, and Approver makes the business decision using the relevant evidence.

Review open requests against their SLA due date in Approval SLA watch. Approval Coordinator identifies the unresolved question and assigns follow-up with a responsible person and due date.

The request and decision records retain delegation expiry. Review requests whose date has arrived and agree who resolves the assignment. Confirm the eligible approver and applicable policy before the person acts.

The correction workflow retains the prior revision, increments the request revision and records a successor operation with prior and new revision references. It appends the correction history and returns the request to review.

Approval records the business decision. Execution Operator inspects the run and any execution attempts, then checks provider references and receipt evidence for a connected destination. An uncertain result remains a reconciliation task until the evidence supports an outcome.

Approval Operations Overview gives a read-only picture of current request states, SLA watch and recent state transitions. Open the related request or history when you need to inspect an individual case.

Bring stable business unit and people identifiers, request numbers, revisions and the policy context. Include supporting documents and prior decisions, then load operation runs before their steps. Reconcile separate attempts using the request and operation key.