When a preparation line closes during service, move each open item to a named receiving station only after checking its preparation status and the receiving line’s capacity. Untouched items may be candidates for reassignment. Partly prepared items need a physical handoff as well as a clear ticket owner. Expo should confirm the final assignment before the closing team leaves.
The buying question is whether your kitchen display workflow makes that transition visible and manageable. A screen that shows a ticket is useful, but the team also needs to know who is cooking each item, what has already happened to it, and what to do if the display cannot show the handoff.
Inventory open work before the line closes
Choose a cutoff point and have the closing cook and expo review the open queue together. Count items, not just tickets: one guest order can contain work for several stations. Record the ticket identifier, item and quantity, modifiers, preparation status, and intended receiving station.
Separate untouched items from those already started. For started items, write down the useful handoff detail: what has been prepared, where it is physically located, and what still needs to happen. Do not mark an item complete merely to clear the closing screen. Likewise, do not assume a ticket has moved just because someone verbally agreed to take it.
For the following hypothetical simulation, a cold station is closing. Four open tickets contain six item units assigned to it. The hot line can take at most three additional units in this exercise; the prep station can take at most two. One unit is already finished and waiting at expo, so it needs confirmation rather than a new cooking assignment. These limits are exercise assumptions, not claims about a display system’s capacity.
| Open work | Status and location | Decision | Expected owner |
|---|---|---|---|
| Ticket A: 2 salads | Untouched | Assign both to prep; retain modifiers | Prep: 2 units |
| Ticket B: 1 sandwich | Partly assembled at cold station | Transfer item and preparation details | Hot line: 1 unit |
| Ticket C: 2 side items | Untouched | Assign both to hot line | Hot line: 2 units |
| Ticket D: 1 salad | Finished; waiting at expo | Confirm against ticket; do not recook | Expo: 1 unit |
The worksheet accounts for all six units: two at prep, three at the hot line and one at expo. The receiving stations are exactly at their assumed limits. If another item arrives for the closing station, the team needs a separate capacity decision rather than quietly adding it to either queue.
Expected result: every unit has a status and a responsible person or station. A pass means the count and modifiers match the original tickets and expo can identify the next action for each unit. A fail includes an uncounted item, an unexplained duplicate, or a finished item sent back for preparation.
Move untouched work differently from started work
For the two untouched salads and two untouched sides, the desired outcome is straightforward: the receiving station gets the correct work with the original quantities and modifiers. Ask a vendor to demonstrate how an operator selects those items and changes their destination. If only a whole ticket can be moved, ask how the team should handle a ticket containing items that belong to different stations.
The sandwich needs more than a screen change. The closing cook should tell the receiving cook what is done and what remains, then physically hand over the partly assembled item. The receiving cook acknowledges it, and expo records or sees the agreed owner. Agree on a safe location for the item during the exchange, following your restaurant’s food-handling procedures.
In the simulation, use a labeled prop or a written preparation card instead of preparing food. The expected result is one sandwich owned by the hot line, with its stage of preparation understood. A pass requires both the physical handoff and the agreed ticket assignment. A fail is a moved ticket with no handoff, a handed-off item with no visible or recorded owner, or two cooks believing the other will finish it.
Also ask what happens if the receiving cook cannot take an item. Can the move be stopped or reversed? How does expo learn that the work still needs an owner? Do not build a closing procedure around a rerouting or recall control until the vendor demonstrates it in your intended setup.
Check the receiving line and expo agree
Run the same six-unit exercise on the intended screens and order flow. Fleksa’s kitchen display system is linked to restaurant orders; its public product information describes item names, quantities and modifiers on the display. Ask how your proposed configuration presents a station change and what expo sees after it.
The closing cook should read the final assignment aloud: two salads to prep, one partly assembled sandwich and two sides to the hot line, and one finished salad at expo. The prep cook, hot-line cook and expo should each confirm their own work. Compare those acknowledgments with the screens or written fallback record. Check item-level details, not only the number of tickets.
Pass if each participant can identify the same owner and next action for every unit, the receiving lines remain within the exercise limits, and expo can account for the finished salad without ordering it again. Fail if the old station still appears responsible without explanation, a receiving station cannot identify its new work, or expo has a different count. Stop and resolve the mismatch before treating the line as closed.
Use the same demonstration for any product on your shortlist. Square describes station routing and expeditor functions for its KDS; Toast also offers a kitchen display product. Ask each vendor to show the specific handoff, item-level behavior and expo view you need. A feature name alone does not establish how the move works in your configuration.
For the regular setup that precedes a closure, the guide to routing kitchen tickets by preparation station can help you frame questions about normal station assignments. The closure test should focus on changing ownership of work already in progress.
Set a verbal fallback and reconcile before departure
Decide in advance who leads a handoff when the display cannot represent it clearly. A practical fallback is for expo to maintain one written list of open items and their owners. The closing cook reads each item and status; the receiving cook accepts it; expo repeats the assignment and records it. Keep that list alongside the normal ticket workflow so a second, conflicting queue does not develop.
Reconcile before the closing cook leaves: compare the written list with the original open tickets, check the physical location of started and finished items, and confirm that each receiving station has capacity. Cross off work only when its actual next step is confirmed. If the counts disagree, pause the closure and find the missing or duplicated item. A verbal fallback is a controlled way to resolve an exception, not proof that the software reassigned anything.
Practice first in a vendor-supported training environment using simulated tickets and props. Set the exercise so it cannot trigger a real card payment, guest message or courier dispatch. Once staff can complete the simulation, plan a separate supervised service pilot with a manager present, real capacity limits and a clear way to pause the closure. A live pilot involves actual orders; do not treat it as a simulation or promise uninterrupted service.
Before buying, bring the worksheet to a demonstration and ask the vendor to walk through the exact steps, including a rejected handoff and a mismatch at expo. Consider how the display fits your restaurant POS system, and ask for a written quote covering the equipment, screens, setup and ongoing charges relevant to your configuration. Compare quoted totals on the same scope; ask a qualified adviser about contract or tax treatment when needed.
Compare these requirements with Fleksa and confirm current availability and the handoff workflow in a demonstration before choosing your setup.
Frequently asked questions
Should a partly prepared item be reassigned like an untouched item?
Not on its own. The receiving cook also needs the physical item and a clear account of what has been done. Expo should confirm the new owner and next action.
What if the receiving station is already full?
Do not add work beyond the limit the team has agreed for the exercise or service. Have expo identify another capable station or decide when the work can be accepted, then record the owner and timing.
How do we know the line is ready to close?
Reconcile every open item against the original tickets, receiving-station acknowledgments and physical items. Resolve missing work, duplicates and conflicting ownership before the closing cook leaves.
