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 Reservation System
- Process
- Kitchen ticket review
Kitchen ticket review
Submit a kitchen ticket and record an independent decision on its revision.
Step by step
-
Draft ticket Kitchen Lead
Link the ticket to its meal order and organization. Record the revision, guest count or table code when those details guide the kitchen.
- Link a draft ticket to the current order and organization
- Updates Kitchen tickets, Meal orders
-
Submit ticket Kitchen Lead
Move the ticket from Draft to Submitted with a sent time so the supervisor has a clear queue. Submission requests a decision.
- Move Draft to Submitted and record sent time
- Updates Kitchen tickets
-
Review revision Kitchen Supervisor
The supervisor compares the submitted revision with the order and menu context, then records an Approve, Reject or Return decision with a reason and time. An approval may move the ticket to Approved; rejection keeps preparation from proceeding.
- Retain source revision, reviewer, reason and decision; update ticket state
- Updates Kitchen tickets, Review decisions
ApprovalA person approves before the work moves on. -
Release preparation Kitchen Lead
The lead works from the reviewed scope, recording preparation times and portions on meal lines. A changed revision returns for review.
- Use the approved ticket scope to record line preparation times
- Updates Kitchen tickets, Meal lines
Who does what
Roles and permissions- Kitchen Lead
- , Kitchen Supervisor, Service Manager.
Set up Restaurant Reservation System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.