Delivery and corrections

A decision is followed by delivery work on the case. The case can retain a delivery reference and completion date. Operation runs identify the case revision and operation key used for an execution. Ordered steps within a run retain action names, input and output references and any external receipt evidence. Execution attempts record when an action was tried, its status and any provider reference or failure reason.

This detail helps the team distinguish a case marked Decided from one with a confirmed delivery. An attempt can be Queued, Running, Succeeded, Failed or Unknown. A run can also need reconciliation. An unknown outcome should lead staff to inspect the external receipt or provider reference before they try to settle the case’s status.

• Run identity. Keep the operation key and source revision with the case so a repeated action can be recognized.
• Step evidence. Read the ordered step trace and external receipt evidence alongside the outcome.
• Named correction. Assign a follow-up action with a due date, status and resolution when work remains.

Agree who confirms delivery and what external reference counts as evidence for each public service. Decide how the team investigates a failed or unknown attempt, and who may retry an action. A later correction should be visible as a successor revision with its own review. If an earlier delivery is superseded, record the compensating follow-up so the team knows what remains to be resolved with the recipient or connected system.

For a representative case, record the approved revision’s operation run. Check its steps in order and compare the final receipt with the provider reference. If a step failed, leave the failure reason available to the person assigned to resolve it. Once the action succeeds, record the case delivery reference and completion date. A subsequent change should explain its relationship to that delivery rather than overwriting the original outcome.

Open Cases and Details on a decided case. Read its operation run, step trace and attempts before using the delivery reference. Then open Failed Runs and Execution Exceptions to make sure the same operation is not unresolved elsewhere. If an attempt is Unknown, ask the assigned person to reconcile the provider result. Record an explicit follow-up rather than treating a repeated click as proof of success.

For a corrected case, compare the earlier source revision, decision and state history with the successor. The reviewer should decide the successor on its own evidence. The operator should see the compensating work in Open Follow-ups and close it with a resolution only after the actual external consequence has been addressed.

• Failed Runs — Case-linked operation runs needing investigation or reconciliation.
• Open Follow-ups — Outstanding corrective work with an owner and due date.
• Execution Exceptions — Failed or unknown attempts with provider references and reasons.

See delivery and follow-up and case history.