Operations and exceptions

An operation receipt records a stable operation key, action, expected revision, result state and occurrence time under its work package. External and effect references can be retained when applicable; a failure reason explains a failed or uncertain result. This lets the operations team examine one attempted action without assuming that repeating it is safe.

The Operations Overview brings planned and actual task hours by project, overdue tasks by owner and a paginated exception queue with source links together. It is a place to identify work needing attention, then open the source package, task, inspection or receipt. A dashboard figure should send a manager back to the underlying record before a decision is made.

• Record. A guarded package or inspection action carries a stable key and expected revision into its receipt.
• Investigate. Operations Analyst compares Pending, Failed and needs review receipts with their linked local effects.
• Resolve. Mark a receipt Completed only when the recorded scope, identity, quantity and revision match the effects; retain a specific discrepancy otherwise.

Reconciliation starts with the records already present. It must not execute the external action again merely because the response is uncertain. A later correction should preserve the original receipt and supporting evidence.

Choose who owns the exception queue and how quickly they inspect pending outcomes. Decide which effect references and external references need to be captured for each guarded action. Establish a rule for mismatched revisions and partial effects: the analyst records the discrepancy and sends it to the manager for review. Keep access to sensitive references narrow while allowing the package owner to see the business outcome.

Rehearse a receipt whose expected revision differs from the package’s current revision. The analyst should leave it needing review, document the mismatch and locate the original operation key. Also rehearse a matching receipt that can be completed without rerunning the action.

A package acceptance has a pending receipt after the owner sees the accepted status. Open the package and its decision history, compare the receipt’s key and expected revision with the local effect, and decide whether they match. Use the exception queue to return to the receipt. If the effect is incomplete, retain needs review and a precise failure reason. If it matches, mark the receipt Completed and keep the original action reference.

• Failed and Needs Review — Guarded actions requiring investigation with their reason and parent package.
• Pending Operation Receipts — Outcomes still awaiting reconciliation.
• All Operation Receipts — The durable history of actions and result states.

See reconcile operations and scope correction.