Review and operations

A review decision links to an event, reviewer, source revision and reason. The decision may approve, reject or return the event scope. It is separate from the event’s current status, so an organizer can see which version a person considered. Attachments provide supporting evidence with an internal or shared visibility setting and a named uploader. The review trail stays connected to the event even when a later correction changes the current plan.

Guarded actions produce operation receipts with an operation key, action, expected revision and result state. The receipt may also hold external and effect references or a failure reason. Reconciliation reads these receipts and the linked local effects, then checks an authoritative external source when an external reference exists. An operation becomes completed only when the expected effects match. A discrepancy becomes needs review; the team investigates the specific difference before closing the case.

• Human decision. The reviewer and reason belong to the source revision that was judged.
• Supporting file. An attachment has a title, evidence type, uploader and visibility scope.
• Operation receipt. A stable key records the attempted action and whether its effects completed or need attention.

Decide which changes need a fresh independent review and which staff can see shared versus internal files. Give reviewers a clear reason convention for approval, rejection and return. Choose who investigates receipts in a failed or needs-review state. Connect authoritative sources where external references are used, and define the handoff to the event owner when evidence is incomplete.

Submit an event budget, attach the supporting file and have a separate reviewer record an approval with a reason. Then change the event’s revision and check that the earlier decision remains attached to its original version. Trigger a guarded reservation with an expected revision that no longer matches; inspect the receipt and its failure reason. For a receipt with an external reference, compare the local effects with the provider response. If they differ, keep the case in review and retain the original action history.

• Receipt exceptions — Failed actions and mismatches with action, expected revision and reason.
• Review decision log — Named reviewers, decisions and source revisions.
• Events awaiting approval — Event plans at the review point.

See budget submission and review, event approval and operation reconciliation.