1The booking follows the guest
- Arrival sets the start, departure sets the end.
- Staff don't do anything new: it runs off the status buttons they already use.
- Times are exact to the minute, never rounded.
Confirming your Client Reservation administrator account…
Staff reference
With dynamic timing switched on, a restaurant booking's times follow what really happens. Tapping At Restaurant moves the start to the minute the guest sat down; tapping Departed moves the end to the minute they left. The table then shows when it was actually in use, and any time a party gives back goes straight back on sale.
Six points, in this order. Then open "Try it" below and show it live.
Press play and watch three bookings share one table through an evening. Pause at any moment to explain what just happened. A good way to open a demo.
Same three guests, same arrivals and departures. Switch between the two to see what Table 5 looks like in each.
Every example is on one table (Table 5), today. Names are examples; messages in quotes are the exact wording staff see.
The same four buttons as always. The times simply follow along.
Resets the booking to what was booked, on the table it was booked on. This is the undo button.
Start becomes the minute they sat down. The end stays as booked, except in the cases below.
From the restaurant: the table closes, just like a departure. The guest still shows as on site.
End becomes the minute they left. Leaving early frees the table; staying late pushes the next booking.
Rossi has booked 19:00–21:00. What happens depends on when staff tap At Restaurant.
Drag Rossi's arrival across the evening. The coloured bands are the four arrival rules; the recorded booking changes shape as you cross each line. Each case is then shown on its own below.
The start moves to 19:12. The end stays at 21:00: they booked until then, and the next party is expecting the table then. The late minutes are simply lost.
No message. The booking just updates.
Arriving at 18:40 moves the start back to 18:40, and they keep the end they booked. Someone a few minutes early is still arriving for their booking.
No message, as long as the table is free from 18:40.
Arriving at 18:20 becomes a sitting of the same length they booked: 18:20–20:20. Otherwise a guest hours early would hold the table from arrival right through to their booked end.
No message, as long as the table is free.
Tapping arrived at 21:30 on a booking that ended at 21:00 moves the whole booking to now, keeping its length. If another booking needs the table sooner, staff are asked first.
Seated at 21:30 until 23:30.
Moving a start earlier, or a sitting later, can bump into another booking. The system reads the latest bookings every time (not whatever is on screen) and never quietly double-books.
Rossi turns up at 16:00, three hours early, so their sitting would be 16:00–18:00. But Andersson has this table from 17:00. A sitting can never run into the next booking, so it is capped at 17:00. That is shorter than they booked, so staff are asked before anything is saved. The same happens to a very late arrival whose sitting would run into the next booking.
Table needed at 17:00. They are here early and the table is booked again at 17:00, so they would be seated now until then - 1 hr rather than a full sitting.
Buttons: Seat until 17:00 · Change table · Cancel. If the full sitting fits, they are simply seated. If less than 15 minutes would be left, only Change table or Cancel is offered.
Rossi arrives at 18:40, but Andersson (17:00–19:00) is still marked At Restaurant. Choosing They have left ends Andersson's booking at exactly 18:40 and seats Rossi from 18:40. No gap, no overlap.
Table still occupied. Table 5 is occupied by Andersson until 19:00.
The popup only appears when something holds the table at the minute the guest arrives. If several things do, the most serious is asked about first, then the next. Rossi (booked 19:00–21:00) arrives at 18:40: pick what is holding Table 5, then press any button in the popup to see what it does.
Table 5 is occupied by Andersson until 19:00.
"They have left" marks Andersson departed at 18:40. If Andersson is already past their end, it says they "were due to leave at 19:00 and are still seated".
Table 5 is booked to Andersson, 17:00–19:00, who has not arrived yet. Marking them a no-show frees Table 5 - you can undo this.
Andersson stays "not arrived", is flagged as a no-show and loses the table. Nobody is recorded as having eaten.
Table 5 is booked to Andersson, who is at the beach and hasn't been seated yet. Releasing Table 5 seats this guest now. Andersson's booking stays, without a table, for when they come up.
Only the table is released. Their booking, times and beach status are untouched.
Table 5 is being booked by a customer right now, for 18:00–20:00. It frees up at …
Never offers to take the table: the customer may be paying at that moment.
Table 5 is blocked for 17:00–19:00. Unblock it from the table itself if that is no longer needed.
Unblocking is left to the table itself, where the permission check lives.
Rossi was seated 19:12–21:00. Brookes has Table 5 next, 21:00–23:00.
The end becomes 20:30. The half hour they didn't use goes straight back on the table for walk-ins, new bookings and online availability.
No message.
The real departure is recorded, and the next booking's start moves to 21:20 so the two never overlap. Only the start moves, never the end, so it can't knock into a later booking. It happens automatically, with a message rather than a question.
The next booking on this table now starts at 21:20.
If a departure runs past the whole of the next booking, that booking is left alone: The next booking on this table ends before 23:10 and has been left unchanged - please check it.
Until someone taps Departed, nobody knows when they'll leave, so a party still marked At Restaurant after their end keeps holding the table up to the current minute. It isn't offered to walk-ins or new bookings meanwhile. Today only.
Over 12 min(or
Due to leave nowin their last minute).
Table occupied, with a button to open the booking that's overrunning.
Going from the restaurant to the beach ends the table exactly like a departure. The guest still shows as on site; only their restaurant time closes.
Every tap can be taken back.
Puts the booked times back, and the booked table if a table change moved them. It then re-checks the table: if something now occupies it until later, the start goes back to when the table is free rather than re-creating a clash.
Put back to 19:20 - the table is occupied until then.
Tap At Restaurant again. The booking reopens: the real arrival time is kept and the end goes back to what was booked.
Table 5 as it appears on the floor plan. Set the clock, then tap a status just as staff would, and watch the times, the table and the message change. Rossi is booked 19:00–21:00; Brookes has the table next from 21:30.
Same rules as the booking system. Set who else is on the table on the left and the clock on the right; the quick buttons jump to the common cases. Rossi is booked 19:00–21:00 on Table 5, Andersson before (17:00–19:00), and optionally Brookes after (21:30–23:30).
The rules behind the edge cases.
| Situation | What happens |
|---|---|
| Exact minutes | Times are recorded to the minute: 19:07, never rounded to 19:00 or 19:15. |
| Very short visits | A party that leaves after ten minutes is recorded as ten minutes. The only floor is one minute, so a double tap can't make a booking vanish: End set to 19:13 - a booking needs at least a minute on the table. |
| Seating a late or early guest | Needs at least 15 minutes before the table's next booking, or staff are sent to Change table. |
| After midnight | A booking can't run past midnight, so a departure at 00:15 is recorded as 23:59: End set to 23:59 - a booking cannot be recorded past midnight. |
| Departed but never sat down | Only the status changes. Times move only for guests who were actually At Restaurant. |
| Beach first, then lunch | A beach guest coming up to eat for the first time is an ordinary arrival; the start is set then. |
| Beach bookings | Beach bookings have no times, so they never move. Only the restaurant booking does. |
| No table assigned yet | The times still move, with nothing to clash with. After arrival the table picker opens so staff can seat them. |
| A booking on a past date | The status changes; the times are left alone: Status updated for … – times not changed. |
| A booking on a future date | Nothing changes. Staff are offered to move the booking to today first: This booking is for … |
| Connection trouble | If online holds can't be checked, nothing is saved and staff are asked to try again. |
| Switching it off | Settings → Arrival and Departure Times. Off: status buttons change the status only. Recorded bookings keep their times, so reports over that period mix booked and actual times. |
Short answers to give.
Staff marked the guest arrived at 19:12. The booked 19:00 is still stored and comes back if the arrival is undone.
The party before was still at the table until 21:20. Only the start moved, so the two bookings don't overlap on the record. Its end is unchanged.
Look for the red clock. The party there is past their end but still marked At Restaurant, so the table is held until they're marked departed.
Another booking starts on that table at 17:00. Staff were asked before seating them and could have picked a different table.
Six quick questions for new staff. Pick an answer to see Table 5 and the reason.