Kitchen release

Give the kitchen a reviewed ticket tied to the current meal order. Kitchen Lead submits a ticket linked to the meal order and organization. The ticket holds its own revision and sent time; its table code and guest count can inform the handoff without creating a table assignment. Kitchen Supervisor decides the submitted revision and records a separate decision with reviewer, reason and time.

For a lunch order, the kitchen lead submits a ticket with its parent order, organization, revision and sent time. The supervisor reads the current lines and recipe context. They approve the submitted revision with a reason, or reject it so the lead can correct the scope. The decision record names the reviewer and keeps the source revision.

• Working scope. Kitchen Lead checks the parent order and its meal lines before submitting the ticket revision.
• Decision point. Kitchen Supervisor compares the submitted revision with current order scope and records Approve, Reject or Return.
• Evidence. kitchen tickets records status and revision; review decisions records the source revision, reviewer, decision and reason.

Agree who may submit a ticket and who may decide it. Keep the supervisor separate from the preparer for the same revision. Decide how table codes and guest counts are entered when they matter to kitchen handoff. The kitchen should use the approved scope, with later changes routed through a new revision and decision.

Write down the policy in the team’s operating procedure before the first service cycle. Give each role the access it needs for its step and rehearse denied access as well as the successful path. The organization and location on the order should match the staff and service work involved.

Rehearse a submitted ticket whose linked order has changed after submission. The supervisor should see the mismatch before approval. Record a rejection with a reason, correct the ticket and submit a new revision. Then record an approval by a different person and check the decision time. Do not treat submission itself as permission to prepare.

Have Kitchen Lead reopen the ticket after the decision and confirm the approved revision still matches the work to prepare. If it changed, submit a new revision rather than reusing the old decision.

• Pending Kitchen Release — Find submitted tickets awaiting a supervisor decision.
• Tickets Requiring Decision — Focus the same submitted tickets for Kitchen Supervisor review.

See the connected process for the handoff and the data model for record links.