Updated
Separate additions from corrections
Use a sample table with two dishes and send its first KOT. Add another item as a second round. Ask the cook to identify only the additional preparation, then ask the cashier to show the full running table.
Next demonstrate a quantity change using the supported workflow. Record how the change appears on paper or screen. The kitchen needs enough context to avoid preparing the entire original order again merely because a new printout has arrived.
Make cancellations explicit
Demonstrate a cancellation on sample data and ask the kitchen to explain what should stop. The reviewed DeccanPro kitchen workflow distinguishes new, changed and cancelled orders. Optional voice announcements also identify cancellations, but the full ticket or display should be checked for complete details.
Agree a staff procedure for food already in preparation. Software can communicate the update, while a person still needs to make the operational decision about work already started. Keep that responsibility clear rather than treating a changed screen as proof the cook has seen it.
Finish with the final bill
After the test changes, have a second staff member review the table from the counter. Compare item names and quantities with the kitchen's understanding, then inspect the final bill. Record any discrepancy and repeat the relevant step after it is resolved.
If a phone disconnects or a print is uncertain during the test, ask how to inspect the existing order before repeating the action. Checking first helps prevent a duplicate request from being mistaken for a legitimate second round.
PUT IT INTO PRACTICE
Your checklist
- Extra item recognised as additional preparation
- Quantity change visible to the right team
- Cancellation clearly distinguished from new work
- Final bill matches the agreed current order