Kitchen tickets

Line tickets carry a parent stop order and their own status and revision. The ticket may include a table code, sent time, guest count and delivery reference. Kitchen Lead submits the current version for review; Shift Supervisor checks the values against supporting evidence and records an independent decision. The decision names the source revision, result, time, reason and reviewer. A ticket returned or rejected for correction does not become kitchen release merely because it was submitted.

A successful release uses the approved revision. The operation completes only when its effects are persisted. This protects the team from a ticket that appears approved while the underlying release failed. An operation receipt retains the key, expected revision and result, giving the supervisor a way to investigate an uncertain outcome. The ticket and its parent order stay linked through the review.

• Submission. The kitchen sends the current ticket revision with the order context that needs review.
• Independent decision. Shift Supervisor records approval, rejection or return with a reason.
• Release. Kitchen Lead works from the approved revision and checks the recorded operation outcome.

Agree which supporting evidence is expected for the table code, sent time, guest count and delivery reference in your shift. Name the supervisor who can make the release decision when the kitchen lead is preparing the ticket. Decide how a returned ticket is corrected and resubmitted without overwriting its earlier decision. Rehearse an old revision arriving after the supervisor has reviewed a newer one.

For a busy stop, a ticket is submitted for several guests. The supervisor compares the ticket’s parent order and supporting details, then approves the specific revision. Kitchen Lead releases it and checks that the operation receipt reports completed effects. If the release returns a failed result, the team opens the underlying receipt from the shift exceptions rather than simply pressing release again.

Submit a valid ticket and confirm an independent reviewer can approve it. Submit a ticket with an inconsistent delivery reference and confirm the reviewer can return it with a reason. Try releasing an outdated revision and confirm it is not treated as the approved scope. Repeat a successful release and confirm the same operation result is returned. Check the ticket’s completed state only after the release effect is persisted.

• Pending Line Release — Give the supervisor submitted tickets and their current review context.
• Recent Review Decisions — Review decisions by revision, reason and reviewer.
• Operation Exceptions — Open a failed release receipt from the shift queue.

Review ticket release and resolve an exception.