Review and evidence

A submitted kitchen ticket needs an independent decision on its revision. Review decisions record the reviewer, source revision, decision, time, reason and operation key against the meal order. That lets the team tell whether an approval belongs to the work currently being released. If the ticket changes after submission, the earlier decision should remain connected to the earlier revision.

Operation receipts show the outcome of guarded work. Their action, operation key, expected revision, result state and time let a reviewer distinguish a completed action from one that is pending, failed or needs review. External and effect references can connect the receipt to provider activity and local records. Attachments hold supporting files with a title, evidence type, upload time, visibility and uploader.

• Decision before release. Kitchen Supervisor reviews the submitted ticket revision and records the reason for approval, rejection or return.
• Receipt after the attempt. A guarded action keeps its operation key and result, including a failure that needs investigation.
• Evidence stays attached. Supporting files remain linked to the parent order and carry a visibility choice.

Set who can review each ticket and who checks corrections to accepted or executed scope. A reviewer should be independent of the person who prepared the work. Agree which evidence types should accompany a release, correction, refund or reconciliation. Check whether a file should be Internal or Shared before it is attached; the choice affects who should see the supporting material.

Define the handling rule for a pending or failed operation. The first step is to read the receipt and its linked effects. If external execution may already have occurred, repeating the action can create a duplicate. Finance Reviewer and Order Manager should compare the order revision, quantities and external reference before any retry or compensating action is authorized.

Kitchen Operator submits a ticket for an accepted order. Kitchen Supervisor reads the submitted revision and attached support, then records an approval with a reason. The release receipt identifies the same operation key and expected revision. If the receipt remains pending, staff examine its effect references before moving the ticket to Completed.

For a second case, consider a refund requested after some portions were served. Order Manager checks the remaining scope and Finance Reviewer checks provider evidence. A reviewer records the reason for any compensating decision. If a receipt says Failed while the provider shows a refund event, the team reconciles the two records instead of issuing another refund. The original decision, receipt and provider identity remain readable afterward.

• Operation Exceptions — Failed and review-needed operation receipts with their causes and linked orders.
• Pending Kitchen Release — Submitted tickets waiting for an independent decision.
• Pending Operation Receipts — Actions whose final effects still need confirmation.

Follow kitchen preparation and release and exception reconciliation.