At the end of a café observation, the easiest visits to average are the ones that have already finished. The party still enjoying its drinks disappears from that calculation unless someone records it. So can the party whose departure nobody saw. A tidy average can therefore describe only part of the group you meant to observe.
This guide records elapsed time for parties seated during one defined window. It keeps completed visits, parties confirmed still seated at the cutoff and unknown outcomes separate. The example is original fiction. It sets no ideal visit length and does not measure seat utilisation, table turns, guest satisfaction or revenue.
Define the visit and the observation window
Choose one outlet, service format and observed seating area. Write the date, window start, cutoff and timezone before collecting observations. In this guide a visit starts when the party is seated and finishes when its last guest leaves the seating area. Record arrivals and waiting separately: arrival at the door is a different starting point.
Include every eligible party seated from the window start up to, but not including, the cutoff. Keep anonymous visit IDs and party size. Parties already seated before the window started are outside this new-arrivals group; record their presence and the exclusion reason in the context log. Do not quietly add a pre-existing party with an invented seating time.
State how late arrivals joining a party, split parties, seat changes and departures followed by returns are handled. Keep the same rule throughout the observation. Table references can help locate a record, but a party remains one visit even if it uses several seats. Its elapsed minutes are counted once.
Use observed events rather than convenient timestamps
Record the seating event and its evidence as it happens. Record departure independently. Opening a bill, taking an order, receiving payment and clearing a table are different events; do not substitute one of them for a missing seating or departure time without changing and clearly naming the measure.
Use full dates and times on one fixed UTC-offset basis. The worksheet accepts whole-minute timestamps, so record the source precision and use one agreed method consistently. A same-minute completed visit has zero recorded minutes at that precision; that does not mean no visit occurred. Convert times across a clock change to one fixed offset before entry.
Keep only the information needed for the observation. Anonymous IDs, party sizes, role labels and protected evidence references are sufficient here. This is an operating record, not a reason to gather names, contact details or recordings of guests.
Give every included visit an outcome at cutoff
Use Departed only when the departure was observed by the cutoff and its timestamp is supported. Completed minutes are departure minus seating. Use Still seated only when a cutoff check confirms that the party remains seated; elapsed minutes to cutoff are a lower bound on its eventual completed visit, not its final duration.
Use Outcome unknown when the departure was not observed and continued presence at cutoff cannot be established. Keep the seating time and a missing-evidence reference, but leave completed and ongoing minutes blank. An unknown outcome is neither a zero-minute visit nor a party assumed to remain seated.
Reconcile the included visit IDs against the complete observation register before confirming the group. A record of five convenient visits from a busier service is not the full group merely because all five rows are filled in. If observation ends early, keep the original scope and identify missing outcomes, or create an explicitly revised observation record.
Worked example: five parties, three completed visits
In this fictional observation, the window runs from 12:00 to 14:00 IST on 8 November 2026. Five eligible parties were seated before the cutoff. The team has evidence for the first three departures, confirms V04 still seated at 14:00 and cannot establish V05's outcome.
| Visit | Seated (IST) | Outcome at 14:00 | Supported duration |
|---|---|---|---|
| V01 | 12:00 | Departed 12:35 | 35 completed minutes |
| V02 | 12:10 | Departed 13:00 | 50 completed minutes |
| V03 | 12:40 | Departed 13:20 | 40 completed minutes |
| V04 | 13:00 | Still seated; confirmed at cutoff | At least 60 minutes; not completed |
| V05 | 13:20 | Outcome unknown | No completed or ongoing duration established |
Read the completed-only average with its missing outcomes
The three completed visits total 125 minutes. Their mean is 125 divided by 3, or 41.67 minutes. Report it beside the counts: five included visits, three departed, one still seated and one outcome unknown. The average for all five completed visits is not available.
Do not insert V04's 60 minutes into the completed average or turn V05 into zero. Nor should the completed-only average become the expected length of a new visit. A short observation can favour visits that finish quickly, while longer visits remain ongoing. The conditions and the unfinished records belong beside any comparison.
This is a party-level elapsed-time measure. Two parties can be seated at the same time, so their minutes are not a partition of the service window. Do not divide summed party minutes by the window and call it table utilisation. Seating capacity, shared tables, clearing, resetting and the next assignment require their own records.
Keep later evidence and follow-up separate
If a departure after 14:00 is observed later, keep it as linked follow-up. It must not replace the original fact that V04 was still seated at the 14:00 cutoff. The worksheet summary stays tied to its original window. A longer follow-up register needs its own endpoint and preserves the original selected group; do not extend the seating window to admit later arrivals or drop unresolved visits.
If later evidence establishes a departure that actually occurred before the original cutoff, preserve the first entry and record the correction, evidence, reviewer and date. Distinguish that correction from extending the observation. Keep each version so the basis of a changed summary is visible.
Review comparable services with their menu, party mix, staffing and unusual events recorded. Use the findings to investigate guest experience and service delays with the team. A duration record by itself does not justify rushing guests, changing staffing or promising that a different table layout will increase sales.
Keep expectations separate from measured visits
Cornell's publication abstract for How Long Should Dinner Take? describes research into customers' expected dining duration in a particular casual-restaurant setting. Expectations are a different question from the observed seating-to-departure times recorded here. This guide applies none of that study's numerical findings, preferred durations or revenue implications. Its observation procedure, example and worksheet are original.
Put it into practice
Your action checklist
Your progress saves in this browser. No sign-up needed.
0 of 8 complete
From reading to doing
Visit Duration
Open Visit Duration for one outlet, seating area, service format and observation window. Record full dates and whole-minute times on a fixed UTC-offset basis. Enter up to 12 included visits with anonymous IDs, party size, seating time, outcome, supported departure time when relevant and evidence references. Valid departed rows show completed minutes; confirmed still-seated rows show elapsed minutes to cutoff as a lower bound. Unknown outcomes show neither. After scope and group completeness are confirmed, the sheet shows counts and the completed-only mean with its denominator. The full-group mean is withheld unless every included visit departed with evidence. Manual sections retain inclusion rules, excluded pre-existing parties, observation conditions, corrections and later follow-up. Use a fuller register for more than 12 visits rather than omitting parties.
Open the Visit Duration 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
- How Long Should Dinner Take? Measuring Expected Meal Duration for Restaurant Revenue Management — publication abstract (Cornell eCommons) ↗
Kimes, Wirtz and Noone, 2002; publication abstract retrieved 8 November 2026. Used only to distinguish research on dining-time expectations from this original observed-duration record. No numerical findings, time targets, nationality comparisons or revenue effects are applied. The example and worksheet are original fiction.
Published by Keystonne Grow. Product links connect to the Keystonne ecosystem; check the linked product or service for its current scope.
