Measure Your Kitchen's Speed: The KDS Performance Report 🧑🍳⏱️
During a heavy rush, a backup in the kitchen can cause a ripple effect that slows down your entire dining room and impacts the guest experience. The KDS (Kitchen Display System) Performance Report is designed to answer one crucial question: "How fast is my kitchen?"
This report measures the exact time from when a ticket first fires onto a kitchen display screen to the moment it gets bumped off by your culinary team. It provides a precise look at your actual food prep and service speeds, making it the perfect tool to run after a busy weekend to spot bottlenecks, compare line stations, or track whether kitchen efficiency is improving over time!
📊 What You'll See on the Dashboard
The report breaks your kitchen's speed data into three progressive layers, moving from high-level station overviews down to precise hour-by-hour breakdowns.
1. Station Summary 🍳🥩
(Always included in the report) This section displays one clean row per physical kitchen station (such as Grill, Fry, Salad, Bar, or Expo), showing aggregated performance metrics over your full date range. This is your go-to view for immediately identifying which stations are keeping pace and which are falling behind.
2. Performance by Business Date 📅
(Appears automatically when running multi-date ranges) This table provides a single row per day across your selected timeframe. It is designed to show you exactly how your kitchen speed is trending day-over-day throughout the week or month.
3. Station Hourly Breakdown ⏳
(Generates one dedicated table per station when hourly data is active) This layer pulls back the curtain on individual station workflows, plotting performance metrics hour-by-hour. It is your best tool for pinpointing exact rush-hour trouble spots.
📖 Column Definitions: Understanding Your Speed Metrics
To help you analyze your line speed, here is a breakdown of what the tracking columns measure:
Tickets: The total count of individual tickets successfully bumped at that specific station during the period.
Avg Dwell: The average time a ticket remained live on the screen from fire to bump. This is your primary speed benchmark.
Median: The exact middle dwell time—meaning half of your tickets were faster than this number, and half were slower. This metric is great because it won't be skewed by an occasional, unusually slow ticket.
p95 (95th Percentile): 95% of your tickets were bumped faster than this speed. Think of this as your "typical worst-case scenario." If your p95 is massively higher than your Median, it tells you that while most tickets are fast, a few select orders are taking an unacceptably long time.
On-Time %: The percentage of total tickets that were successfully bumped within your restaurant's custom target time window.
Late: The raw count of tickets that exceeded your target preparation time.
Avg Items: The average number of menu items included per ticket at this station. A high item count can easily explain slower dwell times!
🍳 Advanced Metrics: "Mark as Cooking"
If your kitchen utilizes the "Mark as Cooking" interactive feature on your KDS hardware, these two advanced columns will automatically unlock on your report:
Avg Queue: The average time a ticket sat idle on the screen before a cook interacted with it and clicked to start prep. A high queue time indicates an attention or floor staffing problem—tickets are being ignored.
Avg Cook: The active, hands-on cooking time once prep officially started. A high cook time indicates a preparation or assembly problem.
🛠️ Strategic Ways to Use This Data
Diagnose a Rough Shift: After a difficult service, pull up the Station Hourly Breakdown. Pinpoint the exact hour that dwell times spiked and cross-reference it against your schedule to see if the slowdown was caused by a staffing shortage or a sudden wave of incoming tickets.
Locate the True Bottleneck: On long-ticket nights, compare your Grill station's p95 speed directly against your Expo line. This helps you identify whether food is getting stuck on the line or if the final plate assembly and packaging is where the delay is happening. 🥩🏁
Track Staff Training Success: Monitor your On-Time % week-over-week after retraining kitchen staff or launching a new menu layout. This gives you measurable proof of whether your kitchen coaching is moving the needle.
Isolate Station Managers: Use the Station Filter to narrow the report down to a single station. This generates a clean, focused hourly table that you can hand straight to your line leads or kitchen manager for a performance review.
📈 Visual Charts Included
When you check the option to enable charts in the NX Portal, the system generates three interactive visuals to map your kitchen data:
Avg Dwell Time by Hour: A line chart illustrating when kitchen speeds slow down across the day, plotting one distinct line per station for easy comparison.
Ticket Volume by Hour: A clear bar chart mapping out your kitchen's busiest time blocks. Overlay this with your dwell chart to see if your line slowdowns happen only during volume spikes or if they occur independently due to other issues.
On-Time Rate by Business Date: A running trend line that tracks whether your kitchen's overall consistency is improving or declining over your full date range.
Need Help? 💡
Why are my station dwell times showing up as zero or incredibly low?
This usually happens if line cooks are "panic-bumping" tickets (hitting the bump button the second an order lands on the screen just to clear their display view, rather than bumping it when the food is actually cooked). If you notice an Avg Dwell of under a minute on hot-food stations, it's a good time to talk to the team about proper KDS usage! 🛑🖥️
Can I set different target on-time windows for different stations?
Absolutely! Your Salad/Appetizer station should naturally have a faster target time than your Mains/Grill station. You can customize your target time parameters by navigating to Configuration > Printing > Routing > Destinations in your NX Portal settings.