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.
- Catering Management
- Features
- Kitchen production
Kitchen production
Review the exact ticket revision before releasing work to the kitchen.
OverviewPending Production Release×
Catering Management · Kitchen production
New
Pending Production Release
Approval conditions
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| EO-64722 | Submitted | 540 | TC-336 | 06 Oct | 26 | |
| EO-38387 | Submitted | 70 | TC-572 | 04 Oct | 16 | |
| EO-26993 | Submitted | 20 | TC-557 | 10 Oct | 11 | |
| EO-84310 | Submitted | 440 | TC-581 | 13 Oct | 37 | |
| EO-27180 | Submitted | 560 | TC-911 | 13 Oct | 6 |
6 of 6 records
TC-336Production tickets · PT-52725
SubmittedParentEO-64722
Revision540
Sent at06 Oct
Guest count26
Delivery referenceDR-901
What you can do
Kitchen production in daily work
The kitchen ticket is linked to its parent event order and organization. It carries its own revision, status, table code, sent time, guest count and delivery reference. The Kitchen Lead prepares the ticket against the accepted order and gathers the supporting evidence for those details. Submission fixes the revision that the supervisor will examine; a later edit must return for review instead of inheriting an earlier decision.
How the work is organized
- Submit the current ticket. Kitchen Lead records table code, sent time, guest count and delivery reference for review.
- Decide independently. Operations Supervisor checks the submitted revision and evidence, then records a reasoned decision.
- Release the decided scope. Kitchen Lead acts on the approved revision and confirms effects before completion.
The Operations Supervisor reads both parent and ticket revision and checks table code, sent time, guest count and delivery reference against evidence. The reviewer records an independent decision and reason. Approval authorizes the guarded release for that exact scope. Rejection leaves the ticket outside completed work. The release operation records its receipt and marks the ticket Completed only after its effects persist, so a label alone never stands in for actual kitchen work.
What to agree during setup
Agree what evidence supports the ticket’s table, sent time, guest count and delivery reference. Name an Operations Supervisor who did not prepare the submitted revision. Set the rule for sending a changed ticket back through review, and decide which receipt and line records the kitchen checks before declaring the release complete.
Check the handoff on an actual case
Take a ticket for an evening service whose guest count rises after submission. The Kitchen Lead updates the ticket revision and sends it for another supervisor decision. A decision on the earlier revision cannot release the new count. Once approved, kitchen preparation records actual prepared time on each affected order line and retains the approved recipe revision. The service team still has to record delivery and served portions separately.
A ticket can be approved yet still await its actual release effect. Before marking the work complete, compare the receipt with the affected order lines and preparation time. If the release fails or the guest count changes, keep the earlier decision and receipt for the original revision; send the changed ticket through review again.
What your team sees
- Pending Production Release — Submitted tickets awaiting a decision on their current revision.
- Approved Event Menus — Recipe revisions available as the basis for released kitchen work.
Follow the work through
Follow the process and review roles and permissions before a live handoff.
What it keeps track of
Data model- Production tickets
- Kitchen tickets submitted for review and release against a meal order.
- Event orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Event order lines
- Individual menu item lines within a meal order.
- Event menus
- Versioned recipe headers for products, with yield and approval state.
- Review decisions
- Independent reviewer decisions on submitted revisions.
- Operation receipts
- Durable receipts for guarded operations and their outcomes.
Who uses it
Permissions- Kitchen Lead
- Prepares the ticket and releases approved work.
- Operations Supervisor
- Makes the independent decision on the submitted revision.
Set up Catering Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.