KDS legs are the individual vertical lanes within a kitchen display system that organize orders by station or role. They act as a visual workflow engine, moving tickets through defined stages so cooks focus on the right items at the right time. For restaurants, managing KDS legs effectively reduces ticket times, limits misfires, and improves handoffs between stations. This explainer covers how legs appear on screen, how they map to your kitchen, and how to tune them for more reliable, efficient service.
How KDS legs fit into digital workflow
A KDS leg represents a logical queue for a specific station or function. When an order is entered, the KDS assigns items to legs based on menu configuration and routing rules. Items may sit in a hold queue until a cook is ready, then advance through legs as production steps complete. By aligning screen layouts with station responsibilities, legs turn a chaotic stream of orders into discrete, trackable units. Clear leg definitions also make it easier to measure station times, spot chokepoints, and coach staff.
Visual layout and information density
Each leg typically shows the order ticket, item details, and counts, along with status icons (waiting, cooking, complete). Designers balance clarity and information density by grouping related tickets and using color or icon cues rather than extra text. Too many items per leg can overwhelm cooks; too few legs can fragment responsibility and increase walking. Well-structured legs reduce mental load by making priorities instantly visible.
How restaurants define their legs
There is no single standard for naming or assigning KDS legs. Some kitchens use one leg per station, such as grill, fry, pastry, or expo. Others split complex stations into sub legs, like appetizers, mains, and desserts, or by cook assignment for high-volume services. Menu complexity, service style, and the number of screens influence how you set up legs. The goal is to create a layout that matches how your team actually moves food, not an abstract ideal.
Mapping legs to physical stations
- Small cafes may use a single leg for all items, while fine dining can have multiple dedicated legs per station.
- Fast-casual concepts often align one leg with the assembly station to simplify verification before pickup.
- High-volume dinner services might separate cold and hot legs to balance workload across cooks.
Ticket routing and hold logic
Routing rules decide when an item moves from one leg to another. For example, a ticket may start in a prep leg and advance to a cook leg once temperatures are confirmed. Hold queues prevent tickets from overwhelming a station by showing only a set number at a time. These controls reduce waste, prevent overproduction, and maintain a steady rhythm during rushes. Clear routing also makes cross-training easier when staff cover multiple stations.
Performance indicators tied to legs
Leg-level metrics reveal how each station contributes to overall service health. Typical indicators include tickets per hour, average wait time per leg, and time from assigned to complete. Comparing stations with similar menus highlights where delays occur. Teams that review leg metrics regularly can adjust staffing, retrain cooks, or reconfigure screens to keep flow smooth.
Quick compare: leg setup styles
| Leg Setup Style | Typical Use Case | Operational Benefit |
|---|---|---|
| One leg per main station | Full-service dinner with distinct grill, fry, and pastry stations | Clear ownership and reduces screen clutter |
| Split by menu category | Casual dining with broad menus | Balances workload within broader roles |
| Single holding leg | Fast-cafes with limited stations | Simple to manage with minimal training |
Common configuration mistakes
Overly granular legs can create too many small queues, making it hard to see the full picture. Conversely, too few legs may pack too much onto a single screen and slow decisions. Misaligned routing rules send items to the wrong station or delay handoffs. Test configuration changes during slow periods and refine based on actual ticket times rather than theoretical layouts.
Optimizing legs for service type
Breakfast services benefit from streamlined legs that focus on high-speed items, while dinner legs can support more complex staging and expo checks. Counter service may prioritize speed with fewer holds, whereas table service might emphasize expo legs for plating coordination. Tailoring legs to your service tempo and guest expectations makes daily execution more predictable.
Maintenance and iteration
From time to time, menu changes, new equipment, or staff turnover reveal mismatches between your current legs and real-world needs. Treat leg design as an ongoing experiment: adjust names, merge or split queues, and measure the impact on ticket times. Small, frequent tweaks often outperform rare, large reorganizations.
Action checklist for better leg design
- Review ticket times by leg each week during slow periods.
- Align leg labels with the names your team uses on the floor.
- Set hold counts based on actual cook capacity, not guesswork.
- Document routing rules so temporary staff can adapt quickly.
Summary takeaway
KDS legs are the segments of your digital ticket flow that mirror physical stations and responsibilities. Thoughtful leg setup, routing, and monitoring reduce errors, speed service, and give leaders clear insight into station performance. By revisiting leg design regularly and tying changes to measurable outcomes, restaurants create a kitchen display system that supports consistency at every service level.