Review and evidence

A review decision belongs to a parent meal order and records the source revision, decision, time, reason, operation key and reviewer. An operation receipt records a guarded action with its expected revision, result state, occurrence time and any external or effect references. Attachments can carry supporting files with a title, evidence type, upload time, visibility and uploader. Together, these records let a supervisor see what was proposed, what was decided and what effect followed.

The records matter most when an outcome is uncertain. A failed receipt should not be treated as an invitation to repeat the action. First compare its operation key, expected revision, linked effects and external reference with the actual records. The finance reviewer can then distinguish a missing local effect from an external action that happened but has not yet been reconciled.

• Independent decision. review decisions keep the reviewer and source revision with the decision and reason.
• Durable outcome. operation receipts retain the action and result state, including failures that still need investigation.
• Supporting file. record attachments hold the actual file and its visibility choice against the order.

A service manager prepares the change or kitchen release. Supervisor decides on the submitted revision and states a reason. Finance Reviewer inspects pending or failed operation outcomes. Admin sets access so shared files do not expose internal evidence outside the intended audience.

Agree which actions need independent review, who can decide them and how a materially changed request receives a new revision. The reviewer should not be the preparer of the same revision. Decide when an attachment is internal or shared and how long the original file is retained. Use a stable operation key for each guarded action so repeat requests can return the known outcome.

Define the evidence needed for a kitchen ticket, cancellation and refund. A reason without the underlying order, revision and supporting record is hard to audit. A final status without persisted effects is equally weak. Reconcile both the local state and any provider reference before closing a receipt as completed.

A service manager submits a revised kitchen ticket after correcting the guest count. Supervisor reads the new revision, reviews the attached evidence and records an approval with a reason. The release action writes an operation receipt. If the receipt remains pending after a timeout, Finance Reviewer checks the ticket, order lines and external reference before retrying. If the expected effect already exists, the team links it and completes the receipt without repeating the work.

A separate cancellation after partial service follows the same principle. Preserve the served line, record the authorized correction and attach the provider refund evidence if money moves. The original decision and operation outcome remain visible for later reconciliation.

• Operation Exceptions — Failed or review-needed actions with the parent order and failure reason.
• Pending Kitchen Release — Submitted ticket revisions waiting for an independent decision.
• Reviewed Kitchen Tickets — Approved, rejected and completed tickets with their decision times.

Read ticket review and release for a submitted decision and receipt reconciliation for failed or pending effects.