A spreadsheet can run a small dining room perfectly well. It stops working when the information splits across a notebook, a phone, a few text threads and three versions of the same file. At that point nobody is sure which table is committed, who confirmed, or what changed during service.

The fix is not more columns. It is deciding which details the floor actually needs, and keeping one version current.

The fields that belong on every reservation

One row per booking. These columns cover what most restaurants need:

FieldWhat to recordWhy it matters
DateDay of the bookingSeparates services and builds the agenda
TimeAgreed arrival timeSequences groups through the evening
Guest nameWho bookedIdentifies the booking at the door
ContactPhone or email, when neededFollow up on changes or details
Party sizeNumber of guestsPrepares the room and table shapes
Table or sectionAssignment, once decidedPrevents double assignment
StatusPending, confirmed, cancelled, seated, no-showShows what actually happened
SourcePhone, website, social, walk-inShows where demand comes from
NotesRelevant guest requestsShares only what the team needs

Keep notes short and respectful. Do not collect details you never use, and restrict the file to people who work the service.

A simple example

DateTimeGuestPartyTableStatusSource
Nov 148:30 PMLucia G.2TBDConfirmedWebsite
Nov 149:00 PMMartin P.5TBDPendingPhone

Names are illustrative. Replace them with real bookings and avoid leaving the file open on shared devices.

Organizing it for service

1. Split by date and service

One tab per day, or filters by date and time. If you run lunch and dinner, keep the service visible on each row.

2. Agree on what each status means

"Pending" and "confirmed" cannot mean different things to two people. Define a short list: pending, confirmed, cancelled, seated, finished.

3. Assign one owner for updates

If one person changes a time by phone while another edits the file, the version on screen stops being true. Decide who records changes and when.

4. Review the agenda before doors open

Check total covers, clusters of arrivals at the same time, and tables that need rearranging.

5. Close the shift with real statuses

Mark who arrived, who cancelled, who never showed. Tomorrow should not start on yesterday's assumptions.

Common mistakes with Excel and Google Sheets

  • Several people keeping separate copies.
  • Deleting cancelled bookings and losing the record of the change.
  • Writing "ok", "done" and "confirmed" for the same thing.
  • No record of who edited a row.
  • Collecting data the team never reads.
  • Depending on one person who knows how the file works.
  • Taking bookings through several channels with no routine to consolidate them.

When to move to a booking system

Consider software when guests ask to book outside opening hours, when the team needs one shared agenda, or when you want visit history without copying rows between files.

If groups end up waiting at the door, a waitlist keeps the queue in one place instead of on a scrap of paper.

Check that the tool supports the hours and availability your restaurant actually runs, that staff understand it without training, and that the features you need sit in the plan you are paying for. Paying for unused capability does not improve service.

Bookity provides a public booking page and a dashboard for reservations and guest profiles. Current features and limits for each plan are listed on the pricing page.

Frequently asked questions

What is the minimum a reservation record needs?

Date, time, guest name, party size and status. Add contact details when you need to coordinate, and notes only when they help the service.

Should cancelled reservations be deleted?

No. Mark them cancelled. A cancellation and a booking that never existed are different facts, and the team needs to tell them apart.

Can Excel handle restaurant reservations?

It can while the volume is manageable, one file is authoritative and changes are recorded. Once requests get lost between channels, a shared tool saves more time than a cleaner spreadsheet.

Does a spreadsheet confirm bookings automatically?

No. It stores what the team types. Online requests and automatic guest emails require a booking tool.