For two genuinely equivalent kitchen lines, assign the next ticket to the line with the lighter workable queue. If ticket sizes vary, count the remaining preparation work, not just the tickets on each screen. Give one person authority to move unstarted tickets when the queues get uneven, and require both lines to acknowledge the change before cooking begins.
That approach depends on the display and the crew. Some kitchens may prefer alternating tickets or assigning them by hand. The right choice is the one staff can see, explain, and correct during a rush without preparing the same order twice.
First, decide whether the lines are truly equivalent
Two screens showing the same menu do not automatically make two lines interchangeable. Each line needs the equipment, ingredients, space, and trained staff to prepare the tickets it might receive. A line with an empty grill position or one cook covering two stations has less practical capacity than its neighbor, even if both have identical equipment.
Walk through the actual menu with the people who work each line. Can both handle the same cooking methods and modifiers? Are the same ingredients within reach? Can either line complete a large ticket without borrowing a cook or crossing into the other line's workspace? If an item requires a specialist station, route it according to that need rather than treating it as ordinary interchangeable work.
Capacity also changes during service. One cook may step away, a fryer may need attention, or a line may be finishing a large table's order. Decide who can mark a line temporarily unavailable and how the other line learns that its capacity has changed. If the system cannot reflect that status clearly, agree on a visible manual signal and a person responsible for changing it.
Assignment between equivalent lines is different from routing food to different preparation stations. A burger and a salad may need different stations; two equally equipped burger lines present a choice of where the same work should go. For the first problem, see the guide to routing tickets by preparation station.
Choose how the next ticket gets assigned
Three approaches are worth comparing. None fixes a capacity problem by itself. Before selecting one, ask the vendor to demonstrate how tickets reach a line, what staff can change, and what each screen shows after a change.
Round-robin: alternate between lines
Send one ticket to Line A, the next to Line B, and continue alternating. This is easy to understand when both lines are staffed equally and tickets take roughly similar effort. It can become uneven quickly when one ticket contains several complex items and the next contains a single simple item.
Ask what happens if a line is unavailable. Does someone pause assignments to it, and who restarts the rotation? A simple alternating rule needs a practical override for breaks, equipment problems, and unusually large orders.
Shortest queue: send work to the lighter line
Choose the line with less work waiting. Ticket count is a useful quick signal, but it is not a reliable measure on its own. One ticket with six cooked-to-order entrées may represent more work than three tickets for simple items. If staff can see item quantities and modifiers before accepting work, they can make a better judgment.
Agree on what counts as queued work. For example, count tickets not yet started separately from those already being prepared. The next assignment should consider both, because a line that has begun a large order may not be ready for another one. Ask whether the display can show the information needed for that judgment and whether assignment is automatic, manual, or a combination.
Manual assignment: let an expediter decide
An expediter or shift lead can look at ticket complexity, staffing, and imminent pickup times, then choose a line. This allows judgment when the kitchen is changing quickly. It also creates a bottleneck if that person is busy packing orders or leaves the station.
Make the backup explicit: who assigns tickets when the lead is occupied, and what happens while nobody is available? Manual assignment works best when the decision is recorded where both lines can see it, rather than shouted across the kitchen.
Use a two-line queue worksheet
The following is a hypothetical comparison, not a claim about any product. Both lines can make every item, and each has one available cook. At the decision point, A has one unstarted ticket estimated at eight minutes of work; B has two unstarted tickets estimated at two minutes each. Neither line has other work in progress. A new ticket is estimated at three minutes. These are workload estimates, not guaranteed cook times.
The table shows what each rule would do and the estimated work left on each line immediately after assignment. It assumes the new ticket joins the end of its assigned queue and no cooking finishes during the decision.
| Method | Next assignment | Estimated work after assignment | What to watch |
|---|---|---|---|
| Round-robin | A, because B received the previous ticket | A: 11 minutes; B: 4 minutes | Equal ticket turns do not mean equal work. |
| Shortest queue | B, because four minutes is less than eight | A: 8 minutes; B: 7 minutes | Estimates must reflect ticket size and current capacity. |
| Manual | B, based on the lead's assessment | A: 8 minutes; B: 7 minutes | The lead needs a clear view and a backup. |
Under these assumptions, shortest estimated workload is the sensible default: it leaves the lines one minute apart. It does not mean the new guest waits only three minutes. With the new ticket behind B's existing four minutes of work, its estimated wait before preparation starts is four minutes, and its estimated completion is seven minutes from assignment. Actual service can differ as tickets change and cooks work at different speeds.
If the team can only count tickets, a shortest-queue rule would pick A in this example because A has one ticket and B has two. That produces the same 11-versus-4 split shown for round-robin. Ask whether staff can see enough detail to distinguish a short queue from a light workload; do not assume the words "shortest queue" mean the software estimates preparation effort.
Rebalance without creating duplicate work
Rebalancing means changing ownership of work that has already been assigned. It is a separate decision from choosing where the next ticket goes. It also differs from deliberately showing information in more than one place: a visible copy is not permission for both lines to prepare it.
Set a trigger that staff can apply without a calculation every time. For example, the lead might check the queues when one line has clearly more unstarted work, when a line loses a cook, or when a ticket has waited longer than the kitchen's chosen threshold. A trigger prompts a decision; it does not require a move if the other line is about to become busy or cannot make the item.
Move unstarted work first. Before moving anything, the lead checks the destination line's capacity, the ticket's items and modifiers, and any timing instructions. Avoid moving work already being prepared unless the kitchen has a specific handoff procedure. Half-made food, partly completed modifiers, and items already on the pass make ownership harder to establish.
- Identify the ticket. The lead selects a specific unstarted ticket and confirms that the receiving line can prepare it.
- Stop the original start. The original line acknowledges that it has not begun the ticket and will not start it during the move.
- Record the new owner. Use the system's demonstrated reassignment process, or an agreed manual record if the system does not support the needed change. Do not assume a ticket has moved because someone tapped a screen or gave a verbal instruction.
- Confirm on both sides. The receiving line acknowledges the ticket, including its quantities and modifiers. The lead checks that the original line can distinguish it from work it still owns.
If the move cannot be confirmed, pause the handoff and have the lead establish one owner before preparation begins. Ask the vendor to show exactly what both lines see after a reassignment and how a mistaken move is corrected. Also ask how changes or cancellations are communicated to the current owner; do not build a procedure around a recall or rerouting function until you have seen it work in the intended setup.
Test the workflow before buying or expanding
Run the same scenarios with each vendor in a supported training environment. A simulation must not take a real card payment, send a guest message, or dispatch a courier. Use fictional orders and have the vendor confirm that the training setup isolates those actions. This is a practice check, not a live service pilot.
Give each line a person playing the cook and name a lead. Start with a balanced queue, add a large ticket, then make one line temporarily unavailable. Have the lead assign a new ticket and move one eligible unstarted ticket. Include a changed modifier and a cancellation in separate scenarios so the team can see how the current owner receives that information.
Record three things: the time a new ticket waits before a line accepts it, the time and steps needed to confirm a reassignment, and the staff effort required to keep ownership clear. Count interruptions or extra verbal checks as well as screen taps. Use the same fictional tickets and staffing assumptions for each demonstration; otherwise, the results are hard to compare.
Set a pass/fail test before the demonstration. For the move, pass only if the original line confirms it has not started, the receiving line accepts the complete ticket, and both lines can identify one owner within the kitchen's chosen time limit. Fail if ownership is ambiguous, a modifier is missing from the receiving line's view, or either line must guess whether to start. Also fail the workflow if it cannot meet your chosen wait-time limit under the stated staffing and queue conditions. Pick those limits with your team rather than borrowing a number from another restaurant.
After a satisfactory simulation, plan a separate supervised live-service pilot with the vendor and your team. Define who monitors assignments, when to stop the pilot, and how to return to the existing process. Live service involves real orders and normal operating actions; it should not be confused with the isolated practice scenarios.
Compare the full written quote for the intended setup, including screens, setup, recurring charges, and any charges for changes or support. Ask which costs are fixed, which vary with usage, and what happens when you add a line. Check how the proposed workflow connects with your restaurant POS system and broader restaurant management software. Request contract advice from a qualified adviser where needed.
Bring your queue worksheet and pass/fail criteria to a demonstration of the Fleksa kitchen display system. Compare your requirements with Fleksa and confirm current availability and setup-specific behavior before choosing a workflow.
Frequently asked questions
Should two kitchen lines receive an equal number of tickets?
Not necessarily. Equal ticket counts can hide very different amounts of work. Consider item quantities, complexity, work already started, and available staff before assigning the next ticket.
When should a ticket move to the other line?
Consider moving an unstarted ticket when its assigned line has substantially more work or loses capacity and the other line can prepare it. Confirm that the original line has not started and that the receiving line accepts ownership.
Can a kitchen display automatically balance two lines?
Ask each vendor to demonstrate its assignment and reassignment options in your intended setup. If the required behavior is unavailable, decide whether a clear manual process meets your service and staffing needs.
