Table booking for a US restaurant: floor-plan seating and no-show control
A booking is more than a line in a notebook. It is a specific table, chosen on the floor plan and held for a specific party at a specific time. This guide shows how to seat bookings well and how to limit no-shows, with steps you can use on your next Friday service.
How it works (short answer)
- Enter the booking with its date, time and party size.
- On the floor plan, you see which tables are free and which are reserved at that time.
- Choose a table of the right size for the party.
- Confirm the booking by phone or in person, and note any special request on the record.
- Write the outcome in your own notes after the service, so the next booking decision uses real history.
What helps handle no-shows
- Ask for a name and a phone number at booking, so the host can call if the table is at risk.
- Tell the guest how to cancel in good time, so they free the table instead of simply not arriving.
- A clear cancellation policy for large parties and busy nights, if you have one.
- A cancellation policy written plainly and shown before the booking is confirmed.
- Confirm the evening's bookings by phone on the day.
- A stricter policy for guests who repeatedly fail to show, which you decide on.
Table: reservation channels
Where bookings come from and what to track on each channel
| Channel | What works well | The main risk |
|---|---|---|
| Phone | Special requests and large parties | Lost if the host does not enter it straight away |
| Website form | Bookings that come straight from guests | Overbooking, if nobody checks the floor plan |
| Social media and messaging | A younger crowd and last-minute bookings | Unfinished conversations with no phone number attached |
| Third-party platforms | Visibility with new guests | Commission, and guest data that does not stay with you |
| Walk-in | Fills the gaps left by cancellations | Blocks reserved tables if the list is out of date |
A practical example, with your own figures
Hypothetical example: on a Friday night, a 60-seat restaurant has two seatings and 25 bookings, and some guests do not show up. Every empty table is seats you cannot sell again that evening.
Work it out with your own figures: the number of empty tables per night, multiplied by your average check, then by the nights in a month. The result shows what one cause costs you.
Confirming bookings on time, a clear cancellation policy, and noting empty tables after each service are things you can track yourself, month by month. Compare the figures from one month to the next.
What US rules mean for bookings
- Guest names, phone numbers and email addresses are personal data. Keep them only as long as you need them for bookings and guest history. State privacy laws can add duties, so check with counsel.
- A reminder about an existing booking is service information. Promotional text messages generally need prior consent under the Telephone Consumer Protection Act, so check before you send any.
- Post the cancellation policy where guests can see it before they book. If you take deposits or hold cards, state disclosure and consent rules apply, so check with counsel.
- Your booking records are business records. Keep them consistent with how you report sales and tax, and confirm the approach with your accountant.
Common mistakes
- Confirming a booking by seat count instead of by table, then finding no free table for six.
- Taking a booking and never following up, so a guest who forgot hears nothing from you.
- Not writing down the guests who did not show up, so you repeat the same mistake next time.
- Not stating the cancellation policy before you confirm. That is both a legal risk and a lost booking.
- Missing the tables freed by cancellations in time, so a table sits empty until 9 p.m.
How 4restaurants.net helps
- The floor plan shows which table is free and which is booked at a given time.
- Each booking sits on a specific table, by room and by time, so the host sees a clash before the guest arrives.
- Bookings, the floor plan and table orders sit in one application, so the host and the servers work from the same list.
- The day's list and the floor plan sit side by side, so you can plan the service in one view.