These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Restaurant + POS + Inventory + Delivery
- Features
- Kitchen handoff
Kitchen handoff
Coordinate meal-line preparation with reviewed kitchen ticket revisions.
OverviewPending Kitchen Release×
Restaurant + POS + Inventory + Delivery · Kitchen handoff
New
Pending Kitchen Release
Approval conditions
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| MO-76978 | Submitted | 780 | TC-103 | 14 Oct | 35 | |
| MO-67791 | Submitted | 90 | TC-463 | 04 Oct | 14 | |
| MO-85715 | Submitted | 280 | TC-676 | 04 Oct | 23 | |
| MO-57867 | Submitted | 100 | TC-394 | 13 Oct | 29 | |
| MO-69948 | Submitted | 80 | TC-852 | 08 Oct | 19 |
6 of 6 records
TC-103Kitchen tickets · KT-92952
SubmittedParentMO-76978
Revision780
Sent at14 Oct
Guest count35
Delivery referenceDR-575
What you can do
Make the release decision visible
A kitchen ticket belongs to a meal order and operating organization. It holds the service details the kitchen needs, including table code, sent time, guest count and delivery reference where relevant. Its revision and status tell a supervisor which submitted version is being considered. A ticket marked Completed should represent a release whose effects have actually been persisted, rather than a request that someone still needs to execute.
Meal lines carry preparation time and served portions. Kitchen Operator can record when a dish was prepared without implying it was served or delivered. That distinction helps the Service and Delivery Lead answer a basic question: is the guest still waiting, is the kitchen still working, or has this portion already left the handoff?
How the work is organized
- Prepare against the order. The meal line remains attached to its parent order, so kitchen progress has the same customer and service context.
- Review a fixed revision. A submitted ticket goes to Kitchen Supervisor with its revision and supporting details.
- Separate preparation from service. A preparation time and a served portion answer different questions and should be checked separately.
What to agree during setup
Define what a table code means for each service location and when a delivery reference is required. Decide which evidence must be attached before the supervisor approves a release. Set the expected order of ticket submission, independent review and completion. A reviewer should be a different person from the preparer and editor for the revision under review.
Agree how a rejected ticket returns to the kitchen and how the next revision is identified. A change to guest count or destination can alter the kitchen’s work; staff should see that change before they prepare the meal. For portions that were already prepared, decide how the team records remaining scope and waste rather than erasing earlier work.
Check the handoff on an actual case
Use an accepted order for a table with three guests. Kitchen Operator creates the ticket, records the table and sent time, then submits it. Kitchen Supervisor checks the order, ticket revision and attached evidence before deciding. If the guest count on the ticket differs from the order context, the supervisor rejects or returns the work for correction. The next review should concern the corrected revision, while the original decision remains available.
Once approved, inspect the linked meal lines. A dish may be prepared while another remains in progress. Record preparation time for the line that was worked on; its served count changes only when service occurs. When the ticket reaches Completed, staff should be able to trace the review decision and the operation receipt for its release. An unresolved receipt belongs in the exception queue for investigation.
What your team sees
- Pending Kitchen Release — Submitted ticket revisions awaiting supervisor review.
- Kitchen Ticket Board — Ticket status across draft, submitted, approved and rejected work.
Follow the work through
What it keeps track of
Data model- Kitchen tickets
- Kitchen tickets submitted for review and release against a meal order.
- Meal orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Meal lines
- Individual menu item lines within a meal order.
- Review decisions
- Independent reviewer decisions on submitted revisions.
- Operation receipts
- Durable receipts for guarded operations and their outcomes.
- Record attachments
- Files and evidence attached to operational records.
Who uses it
Permissions- Kitchen Operator
- Prepares lines and submits tickets.
- Kitchen Supervisor
- Makes the independent review decision.
- Order Manager
- Checks the guest promise, and Service and Delivery Lead records what was served.
Set up Restaurant + POS + Inventory + Delivery your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.