System Hub
Start 14-day free trial
Tables, parties, notes

Restaurant booking diary without double-booking

A restaurant booking diary is one place for tables, parties, and notes so the host stand does not double-book. Bookings scattered across calls, emails, and spreadsheets lose special requests between shifts. Cover counts should be readable before service, not reconstructed from voicemail.

Last reviewed: . Reviewed by Nitin Patel. Drafts are prepared with AI assistance and checked by him before publication.

Start 14-day free trial Private dining bookings

What the host stand actually needs

Time, table, covers, guest name, and the note that matters (window, anniversary, allergen). Double bookings, missed notes, and unclear cover counts are the diary chaos. A live service view with confirmed, pending, and holds is the job — not another login for its own sake.

Tables, parties, and events in one diary

A 10-cover party is not a table. A 30-cover event is not a party. If those live in a spreadsheet next to the table book, Saturday service gets sold twice. Private dining and party bookings belong in the same diary with a capacity.

Print the host-stand service sheet for Friday. If a note still dies between shifts, Saturday belongs in one diary.

How System Hub Booking runs the diary

Tables, parties, and events, customer linking, notes that survive the shift change. Works in the browser. 14-day trial, no card, then £10/week per location incl VAT via Stripe. Keep your EPOS if it works. This is the diary, not the till.

Start 14-day free trial Booking product page

How does a table get booked twice?

Two books. The phone is in a paper diary, the website is in a spreadsheet, and both sell table 12 at 19:30. One diary means the second person sees the hold. Parties and private dining have to be in that same diary, or the restaurant still sells the room the function already has.

What the row needs: name, covers, time, table or “unallocated”, the note (allergy, high chair, birthday), and who took it. A note on a sticky on the till is not on the row the host is reading. If you release a no-show, write the time you released it so the 19:45 walk-in is not a mystery.

Keep ResDiary if you already live in yield, Google, and card guarantees. System Hub Booking is the book for calls, email, and the room. £10 a week per location, VAT included, after a 14-day trial with no card. It will lose a bake-off that is only about turning tables.

  • One diary for tables, parties, and the private room.
  • Holds are visible to the next person who answers the phone.
  • Allergies and access notes sit on the booking, not in someone’s head.
  • Do not migrate a working ResDiary because a new diary looks tidier.

FSA: food allergy and intolerance.

Why does a second diary sell the same table twice?

Two places that can both say yes is how table 12 is sold twice. The phone diary and the website spreadsheet are two places. One diary shows the hold to the next person who answers. Parties and the private room have to be in that diary too, or the kitchen is planned twice.

The row needs name, covers, time, table or “not yet allocated”, the note, and who took the booking. A high chair on a sticky is not on the row the host reads at 18:50. When you release a no-show, write the time, so the walk-in is not a mystery to the person who took the original booking.

Keep ResDiary if yield, Google, and card guarantees are why the room is full. System Hub Booking is for calls, email, and a room that currently lives in a notebook. £10 a week per location, VAT included, after a 14-day trial with no card. It will lose a comparison that is only about turning tables on a Saturday.

Allergies on the booking still have to reach the kitchen. The diary is not the allergen matrix. The 14 allergens are listed in the Food Information Regulations 2014.

A booking taken for “around 7” is not a time the kitchen can plate to. Ask for the time and write that time. If the guest moves from 19:00 to 20:30, the old slot is released in the same edit, or both slots stay blocked and the next caller is turned away from an empty table.

Booking row with name, covers, time, table, and the note
One row. The second person who answers the phone can see the hold.
FAQ

Questions about the booking diary

What is a restaurant booking diary?
It is the service view of tables, parties, and events with covers, times, and notes. One diary stops the host stand confirming the same 19:00 four-top twice. Special requests belong on the booking, not on a sticky note.
Do I have to replace ResDiary or OpenTable?
No. Keep them if they work. System Hub Booking is for venues whose diary still lives on paper, email, and spreadsheets — or who want tables, parties, and events in the same hub as SFBB records. We do not claim to be a marketplace with diner traffic.
How much is System Hub Booking?
14-day trial, no card. Then £10/week per location incl VAT via Stripe. Cancel anytime.