Exceptions and corrections

An approval can need attention because its due date has passed, its delegation expiry needs review or its execution result is unresolved. Approval Coordinator inspects the request and gives the follow-up a named person and due date. The action remains connected to the original request, making the reason for the work visible when someone opens it later.

A correction has a separate purpose. When an executed revision must change, the correction workflow preserves the prior revision and publishes a successor. It increments the request revision, records the successor operation and returns the request to review. The team can review the changed business case while retaining the history of the earlier action.

• Due work. Compare open requests with their recorded SLA due date and delegation expiry. Approval Coordinator decides who needs to investigate and records the resulting follow-up assignment.
• Action ownership. Use open actions and actions in progress to distinguish work awaiting attention from work someone has started. Record the resolution and completion time when the follow-up is Completed; keep Cancelled separate.
• Revision continuity. Inspect the successor operation with its prior and new revision references. State history retains the correction transition, allowing the reviewer to understand why the request is back in review.

Agree the team’s daily review of overdue approvals and expired delegation. Decide who may assign follow-up actions and what the assignee must record before closing them. A completed follow-up should explain the resolution of its own question. It should not be used as a substitute for inspecting the underlying request or execution result.

Define when the correction workflow is appropriate and who coordinates it. Bring an example of a changed amount after an executed request. Agree how the team reviews the successor revision and how any downstream business adjustment will be handled through its owning system. Preserve the earlier operation evidence when preparing that correction.

An approved request was executed using a quotation that later needed correction. Request Owner explains the discrepancy to Approval Coordinator. The coordinator invokes the correction workflow for the executed revision, then inspects the new request revision and its return to review. The successor operation carries the prior revision as its input and the new revision as its output.

Evidence Reviewer checks the corrected material and records the applicable review. Approver then has a changed request to consider. Execution Operator uses the earlier receipts when investigating the consequence in a connected destination. This gives each person a clear piece of the correction without losing the original decision.

In a separate rehearsal, use a request still under review whose due date has passed. Assign a follow-up to the person who can answer the outstanding question. Mark that action in progress and record the resolution when it is complete. Ask the coordinator to show that the request still has its own approval state and that the action’s completion did not invent a business decision.

• My open follow-up actions — Follow assigned questions and inspect their recorded resolution.
• Approval SLA watch — Find submitted requests or requests still under review whose due date has arrived.
• Request transition history — Trace changes with their request revision, actor and reason.

Correction and follow-up covers the successor revision. Evidence to decision describes the renewed review.