Kitchen release

The ticket begins in draft. Kitchen Lead checks the parent order and its current revision before submitting it. Table and delivery details must agree with the supporting evidence for the service arrangement. Submission freezes the revision presented to Kitchen Supervisor. A rejected ticket stays out of release; Kitchen Lead can correct the details and submit a new revision. An approved one can proceed to execution. Completion follows the persisted effects of release rather than the click that requested it.

Consider an accepted order for a dining room table that is later switched to a delivery destination. The ticket’s table and delivery reference deserve a fresh check against the order and its service location. Kitchen Supervisor should see which revision was submitted and make a decision about that revision. The prior decision remains available if the team submits a corrected ticket.

• Ticket status. Draft, submitted, approved, rejected and completed positions distinguish preparation from an executed release.
• Submitted revision. The ticket revision and parent order define the scope that Kitchen Supervisor reviews.
• Decision evidence. Decision time and the independent review record connect the decision to the actual ticket.

Decide which details are required for dining room, takeaway and delivery work. Agree how table codes are checked, when the ticket is considered sent and who can decide a disputed guest count. Kitchen Supervisor should be different from the person who prepared the release request. Set the review practice for changed order lines so the supervisor can compare the ticket with the latest accepted order.

The team should define when an approved ticket is sent to the kitchen and how it confirms the resulting effects. If a send outcome is uncertain, the operations team should inspect the receipt and linked effects before trying again. This keeps a repeated request from producing a second kitchen release for the same scope.

Start with an accepted order and prepare a ticket with a table code, sent time and guest count. Submit it, then have Kitchen Supervisor compare those details with the order and supporting evidence. Record approval and check that the same revision reaches preparation. Next, change the ticket and repeat the review; the earlier decision should still describe the earlier submitted revision. Finally, rehearse a rejected ticket and ensure it never appears as completed kitchen work.

• Pending Kitchen Release — Submitted tickets ready for Kitchen Supervisor’s decision.
• Kitchen Ticket Decisions — Tickets in an approved, rejected or completed state, with decision time visible.
• Open Meal Orders — Parent orders that give the kitchen the current service context.

The kitchen release process carries the review into execution. Use preparation and service to follow the approved work through actual portions and service.