# Restaurant Table Reservations and Peak Hours
*A day book of four fields, where the guest fifteen minutes late is the only decision on screen*

> **In short:** How restaurant table reservations are run: four fields are enough, handling late arrivals, turning a booking into an open order, and measuring occupancy.

- **URL:** https://www.snad.io/en/blog/hajz-tawilat-almataam-idarat-althurwa
- **Arabic original:** https://www.snad.io/blog/hajz-tawilat-almataam-idarat-althurwa
- **Category:** Industry — Restaurants & Cafés
- **Tags:** Restaurants, Cafes, Bookings, point of sale
- **Published:** 2026-09-06
- **Updated:** 2026-09-06
- **Publisher:** Snad (snad.io)

What wastes the most seats across a full evening is not weak demand. It is **a table held for someone who never came**.

It stays reserved, the host walks past it repeatedly, a group is turned away at the door because it is held — and at ten it turns out nobody ever arrived.

A paper reservation book does not prevent that, because it lists bookings ordered by time rather than ordered by **what needs a decision now**. This article is about the difference between the two.

## Reservations are an occupancy problem, not a calendar one

The first mistake with reservations is running them as appointments. An appointment means a slot in a calendar. A restaurant booking means **a seat taken out of service** until its owner arrives or forfeits it.

| | Run as appointments | Run as occupancy |
|---|---|---|
| The question | Who is coming at eight? | How many seats are out of service now? |
| The ordering | By time | By what needs a decision |
| Late arrivals | A line in a list | An alert at the top |
| The measure | Number of bookings | Attendance rate and occupancy |

**The practical difference shows at half past eight.** Run as appointments, the booking nobody honoured is still a quiet line among lines. Run as occupancy, it is the first thing on screen — because it is the only decision actually pending.

The rest of the bookings need nothing from you right now: their owners have either sat down or are not due yet.

## Four fields are enough

The reservation book that actually gets used is the light one. Every field you add is a field the host hesitates over with a phone against their ear.

**The four you cannot drop:**

1. **The name** — to call at the door.
2. **The mobile** — to ring when they run late, and the only field that turns a lost booking into a freed table.
3. **Party size** — to know which table suits.
4. **The time** — to order the day.

**What not to add at the start:** seating preferences, the occasion, allergy notes, and a specific table chosen in advance. Some of those serve a fine dining room with a dedicated host. In a busy restaurant all of them are fields left blank, and blank fields cost you trust in the whole book.

**Assigning a specific table at booking time looks like organisation and is usually a constraint.** Better to book a **party size** than a **table**: the room changes between booking and arrival, and fixing the table in advance stops you seating the group on whatever is genuinely free.

## The guest fifteen minutes late is the decision

Of everything on a reservations screen, one thing needs action: **whoever is late**.

So it is flagged in a different frame past a limit you set — and fifteen minutes is a common and reasonable one in most restaurants.

**Why flag rather than simply order by time:** a late booking buried in a time-ordered list stays invisible. The host is busy at the door and only opens the book when asked. The result is a held table sitting idle all evening because nobody noticed its time had passed.

**Three reasonable responses to the flag:**

1. **Call.** Most late guests are on their way, and one call keeps the booking and gives you a realistic time.
2. **Free the table for now.** Seat a group you know will leave quickly.
3. **Cancel.** After a known grace period and after an attempt to call.

**A written policy beats each host's judgement.** Set the grace period, set who owns the cancellation decision, and write both down. Individual judgement here means the same table is freed after ten minutes under one host and after an hour under another.

## From booking to open order

The moment guests arrive is where data is most often thrown away: the booking is crossed out of the book, a fresh order is opened from nothing, and the thread between what was booked and what happened is cut.

**The booking itself should become the open order on the table.** One press carries the name and party size across, opens the bill, and starts the seating timer.

**Three things are gained from that link:**

1. **Party size arrives correctly** on the order with no second entry, and it is the number average spend per guest rests on.
2. **Which bookings were honoured** is known without a manual log, because arrival became an event in the software rather than a crossing-out in a book.
3. **The timer starts at seating** rather than at a moment somebody recalls later.

From there everything continues on the usual path: rounds are added, kitchen tickets print, and payment closes the bill and frees the table.

## Measuring what reservations do to occupancy

The number of bookings on its own says nothing. Two numbers do say something:

**Attendance rate.** How many bookings out of a hundred showed up. It measures the quality of your book rather than the quality of your guests: a low rate usually means no confirmation before the slot, or bookings taken without a mobile number to call.

**Seats out of service.** How many seats stayed held for people who never came, and for how long. That is the number that turns reservations into money.

| Indicator | What it measures | What fixes it |
|---|---|---|
| Attendance rate | Book and confirmation quality | Pre-slot confirmation, a mobile field |
| Seats out of service | The cost of a lost booking | A clearer grace period, a late flag |
| Average sitting time | Table turnover | A limit per room |

**All three are read together, never alone.** A restaurant with a high attendance rate and long sittings may occupy worse than one with a lower attendance rate and faster turnover. The decision differs completely: the first treats sitting time, the second treats confirmation.

Seating timers and turnover are covered in detail in the table management guide on this site.

## Frequently asked questions

### What details do I need to book a table?

Four fields are enough: name, mobile, party size and time. The mobile matters most, because it is what turns a late booking into a freed table with one call.

### How long should I hold a reserved table?

Fifteen minutes is a common and reasonable limit. What matters is that the grace period is written down and known to every host, rather than judgement that differs by employee.

### Should I book a specific table or a party size?

Book a party size. The room changes between booking and arrival, and fixing a specific table in advance stops you seating people on whatever is genuinely free.

### How do I know what reservations do to my occupancy?

By measuring attendance rate and seats out of service together, not the number of bookings. The first measures your book, the second turns a lost booking into a cost.

---
## About the publisher
**Snad (سند)** — a private Saudi software company
based in Riyadh, founded 2025. Legal form: Sole proprietorship.
Commercial registration: 7038154642
VAT number: 310959226500003
Only official domain: snad.io
> Snad is a private commercial business-management platform. It is not a
> government body, not a bank, and not a government services portal, and it
> is not affiliated with any government entity. Any site or app with a
> similar name is unrelated to Snad.