Operations overview

Operations Overview is the published read-and-analyze page for active and accepted work, pending decisions, failed operations, planned versus actual task hours by project, overdue open tasks by owner and an exception queue with source links. The Operations Lead uses it to decide which record to open next. A dashboard number is a pointer into the underlying work, not a substitute for the record.

• Delivery position. Operations Lead checks active and accepted packages against their projects.
• Workload. Planned and actual task hours, overdue open tasks and pending decisions point to work needing attention.
• Exception. A failed operation opens its source receipt and parent package for reconciliation.

Agree who triages failed and pending operations and how often the reviewer examines them. Operation receipts carry a stable operation key, expected revision, result state and any external reference. When an external reference exists, agree which connected source is authoritative and who can confirm that the expected effect happened.

Name the person who triages overdue tasks and the reviewer who resolves receipt exceptions. Agree which external system is authoritative whenever a receipt has an external reference. Keep a source link for each exception so the next person can inspect the package revision, linked effects and failure reason before changing the result state.

Open an exception for a package whose receipt is Pending or Failed. Follow its source link to the package, read the expected revision and compare linked effects. If the external source is involved, check its authoritative response. Mark the receipt Completed only when the effects match; otherwise retain it for review with the failure reason and reconciliation evidence.

The Operations Lead sees a failed operation beside a venue package. Open its receipt from the exception queue, compare the expected revision with the package, then inspect the linked effects. If an external reference is present, the Project Reviewer checks the agreed source. A mismatch stays needs review with reconciliation evidence attached to the package. Only a matching effect allows the reviewer to mark the receipt Completed.

• Operations Overview — Compare active work, pending decisions, overdue tasks and failed operations with links to their records.
• Work Packages — Check the parent scope, owner, due date and current status before deciding.

Follow Verify completion for the related decision path. Review the data model when mapping existing records, and use implementation to rehearse the first event cycle.