A kitchen ticket report can show an average that looks settled while orders from the same period are still on the line. If those tickets drop out of view, the average describes only the completed group and can hide long-running orders.
This guide measures elapsed time from ticket acceptance to ready at the pass for one fixed cohort. It keeps open, cancelled and incomplete tickets visible beside the result. It does not diagnose bottlenecks, measure collection or set a speed target. KT-029 is an original fictional example.
Fix the cohort before reading any times
Name the outlet, the channel and the acceptance window, then set an observation cutoff. In KT-029 the cohort is every counter ticket accepted at one outlet from 12:00 inclusive to 12:30 exclusive IST on 8 November 2026, reviewed at 13:00. A ticket belongs to the cohort because of when it was accepted, not because it finished. A ticket accepted at 12:29 is in; one accepted at 12:30 belongs to the next window.
The unit is one whole ticket. Give each ticket a stable ID from the source record so it is counted once and can be traced back to its evidence. Record every timestamp on the same clock. Times copied from two devices that disagree cannot be safely subtracted from each other.
Define the two timestamps
Accepted means the original acceptance of the ticket. Ready means every item on the current accepted revision of the ticket is ready at the pass under the outlet’s existing controls. Write both definitions down before anyone records a time, and do not loosen food safety or quality checks to produce an earlier ready time.
Ready is not handover to the guest, meeting a promised time or the amount of active work. Collection and promised times belong to a separate record. Do not reset the start when a ticket is amended or held; the elapsed time always runs from the original acceptance.
Worked example: KT-029 at the 13:00 cutoff
Six tickets were accepted in the window. Each row keeps its state, notes and evidence reference in the source record.
| Ticket | Accepted (IST) | Ready or state at 13:00 | Elapsed or age | Treatment |
|---|---|---|---|---|
| T1 | 12:00 | Ready 12:08 | 8 min | In ready mean |
| T2 | 12:04 | Ready 12:16 | 12 min | In ready mean |
| T3 | 12:10 | Ready 12:30 | 20 min, including a 5 min internal hold | In ready mean |
| T4 | 12:20 | Open | 40 min age at cutoff | Shown as open, outside mean |
| T5 | 12:25 | Cancelled 12:28 | Not applicable | Shown with cancellation evidence, outside mean |
| T6 | 12:28 | Marked ready, time missing | Unknown | Review, outside mean |
Read the mean beside the other counts
Three tickets have valid ready times: 8, 12 and 20 minutes, a sum of 40. Their mean is 40 ÷ 3 = 13.333 minutes, shown as 13.3. Report it together with the rest of the cohort: six tickets, three ready with valid times, one open, one cancelled and one needing review.
The 13.3 minutes describes those three tickets only. It is not the typical guest’s wait, not the time for the whole cohort and not evidence that the period went well. T4 had already been open for 40 minutes at the cutoff, longer than any completed ticket. Leaving it out of the mean must not remove it from the report.
Held tickets stay in, cancelled tickets stay visible
T3 was held internally for 5 minutes before work continued. That hold is part of its 20 minutes. Do not subtract it, and do not drop the ticket because it was held: a held ticket that becomes ready remains in the mean. Note the hold and its reason so a reader can see why the time is longer.
A cancelled ticket is different. T5 never became ready, so it has no ready time. Keep its cancellation evidence and show it in the count rather than deleting the row.
Missing data is a review item, not zero
T6 was marked ready but its ready time was not recorded. Its elapsed time is unknown, not zero and not an estimate. Leave it outside the mean, list it for review and correct it only from evidence. Treat a duplicate ID, a ready time earlier than acceptance or an otherwise inconsistent entry the same way. A ticket accepted outside the window is retained with a separate classification rather than being mixed into this cohort.
If tickets repeatedly need review, fix the recording before comparing one cohort with another. Questions about which station slowed a ticket belong to a separate workflow review.
Keep the original cutoff snapshot when later evidence arrives. A ticket becoming ready after 13:00 changes a later review; it must not be backfilled as ready in the 13:00 record. Full dates and times are needed for service that crosses midnight.
What a reporting tool’s average covers
Square’s support article on restaurant performance reports describes a kitchen performance report that shows a completed ticket count and an average completed ticket time. It notes that the report tracks only tickets sent to kitchen displays, not those sent to printers. That supports reading any average as a statement about the tickets it includes. Square’s report design and terms are not adopted here, and no Keystonne feature is implied.
Put it into practice
Your action checklist
Your progress saves in this browser. No sign-up needed.
0 of 9 complete
From reading to doing
Kitchen Ticket Times
Open Kitchen Ticket Times and enter the cohort start, end and cutoff as dates and times, then record up to 20 tickets. Each ticket has a stable unique ID, accepted and ready date-times, a state of Ready, Open or Cancelled, a hold, cancellation or context note, and an evidence reference. Formulas classify each ticket's eligibility, calculate ready elapsed minutes and open age at the cutoff, and summarise the counts and the mean of eligible ready tickets, with the review and outside-cohort counts kept visible. Invalid or duplicate IDs and missing or inconsistent dates are marked Review. Blank rows stay blank. Tickets outside the cohort are retained separately. There are 6 manual follow-up rows. The sheet has no system connection. It does not track collection, diagnose bottlenecks or approve readiness. To go beyond 20 tickets, copy the formulas and expand every summary and duplicate-check range, or start a separate copy for another cohort.
Open the Kitchen Ticket Times tab in the launch workbook. Keep a copy for your own business.
Download the free workbook See what’s inside the toolkit →Sources & further reading
- Run restaurant performance reports (Square Support Center) ↗
Retrieved 8 November 2026. Used only for the point that a kitchen performance report states a completed ticket count and average completed ticket time and covers only tickets sent to kitchen displays, not printers. Its subscription requirements, report navigation and any figures are not adopted, and no Keystonne capability is implied. KT-029, its times and its treatment rules are original fiction.
Published by Keystonne Grow. Product links connect to the Keystonne ecosystem; check the linked product or service for its current scope.