Use recognisable references
Agree clear table, guest or takeaway references that counter and kitchen staff understand. Avoid abbreviations known to only one person. Confirm the same context is visible in preparation and service records.
Keep instructions with the dish
Enter supported preparation notes with the order or line rather than in a separate chat. Dietary wording does not establish allergen safety. Your restaurant still needs ingredient verification, staff confirmation and a reliable kitchen process.
Check station routing
Test an order containing work for multiple stations. Confirm the right staff see the right tasks while retaining the original context. Review routing when the menu or staff responsibilities change.
Define each status
Queued, preparing and ready should describe agreed milestones. Ready means food is ready for handover, not already received by the guest. Decide who updates each state and how staff confirm their view is current.
Treat printing as a process
A job record or browser dialog does not prove paper emerged. Check the actual ticket and agree when reprinting is appropriate. Repeated clicks are not a substitute for checking the previous attempt.
Review one concrete delay
After service, inspect one confusing order and its history. Identify the missing information or ownership step, then test a small operating change. Software can support a handover without owning every physical action.