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.
- Food Franchise Management
- Process
- Kitchen ticket review
Kitchen ticket review
The supervisor checks the parent order, ticket revision, table code, sent time, guest count and delivery reference against any supporting evidence. An approval or rejection carries the reviewer and reason. The approved ticket reaches Completed only after its effects have been persisted.
Step by step
-
Prepare ticket Kitchen Lead
Kitchen Lead links a Draft ticket to the current meal order and checks table code, sent time, guest count and delivery reference where they apply.
- Keep the draft ticket tied to its parent order
- Updates Kitchen tickets, Meal orders
-
Submit ticket Kitchen Lead
Kitchen Lead submits the ticket revision for independent review. A later material edit needs a new review of the current revision.
- Move the current revision from Draft to Submitted
- Updates Kitchen tickets
-
Supervisor decision Kitchen Supervisor
Kitchen Supervisor compares the submission with its parent order and supporting attachment, then records an approval or rejection with a reason. The supervisor approves only the submitted revision.
- Record reviewer, revision, reason and Approved or Rejected outcome
- Updates Kitchen tickets, Review decisions, Record attachments
ApprovalA person approves before the work moves on. -
Release ticket Kitchen Supervisor
Kitchen Supervisor releases the approved revision. The ticket reaches Completed only after the intended effects have been persisted and checked against its operation receipt.
- Persist release effects, then move Approved to Completed
- Updates Kitchen tickets, Operation receipts
Who does what
Roles and permissions- Kitchen Lead
- Prepares and submits.
- Kitchen Supervisor
- Independently approves or rejects the current revision and confirms release.
Set up Food Franchise Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.