A time isn't showing that should be

Work down six settings in order: the shift, turn times, the gap between seatings, pacing, the booking window and cutoff, and table capacity.

A time is offered only when every one of these agrees. Work down them in order — the first four are the usual culprits, and the order is roughly how often each is to blame.

The checklist

  1. Is there a shift covering that time, on that day? SettingsHours. Guests can only book inside a service period, and shifts are per day of the week — it is easy to have Saturday dinner and no Sunday.

  2. Are your turn times too long? SettingsCapacity. If a two-top is held for three hours, an evening fits two sittings instead of four. This is the most common cause by a distance.

  3. Is the gap between seatings large? Same screen. A 45-minute reset silently removes a sitting from every table.

  4. Is a pacing cap full? Same screen. If 7:00 PM has reached your max covers, it stops being offered to a party that would exceed it — while remaining available to a smaller one. Two people checking the same night can honestly see different times.

  5. Is the date inside your booking window, and past the cutoff? Venues have a limit on how far ahead guests can book and how close to the sitting. A time forty minutes away may be past the cutoff.

  6. Does any table actually fit that party? Floor plan. Check both ends: a party of two will not be offered a table whose Min guests is 4, and a party of ten needs either a big table or a saved combination.

If it is still wrong

Open the book for that date and look at the table you expect to be free. The timeline shows what is actually holding it — a booking, a block, or nothing at all.

If the row is genuinely empty at that time and no cap applies, the remaining explanation is table capacity: the party does not fit the tables you have free, even though the room looks open.

Last checked against the product on 12 August 2026.