How to Keep a Restaurant Guest List Without a Spreadsheet

None of this is anyone being careless. It is what happens when one guest is spread across a booking diary, a website enquiry form, a mailing list, a notebook and a spreadsheet that has to be updated by hand. Each copy drifts from the others on its own. Entries get typed twice with different spellings, regulars go missing because their bookings never reached the sheet, notes stay in one person's memory, and copies of names, phone numbers and email addresses end up on personal laptops and phones. The list the restaurant thinks it has and the list it really holds stop being the same thing, and nobody can tell which version is right.

The first cost is service. A guest list exists so the team can recognise people, remember what matters to them and serve them better on their next visit. A list that sits three months behind does none of that. Regulars are the guests most worth recognising, and a hand-kept sheet loses them first, because their fifth and sixth bookings feel too routine to write down.

The second cost is time. Someone has to copy bookings across, merge duplicate rows, chase the enquiry emails that never made it in, and work out which of three phone numbers is current. That work happens late at night or not at all, and each skipped session leaves the sheet further behind.

There is a quieter cost as well. A restaurant that cannot see its own regulars cannot thank them, cannot invite them first when a new menu launches, and cannot tell whether this month's bookings are new faces or the same loyal few. The information was given freely, one booking at a time, and a list that loses it has thrown away one of the most useful records a small restaurant keeps.

The third cost is exposure, and here the rules are plain. A restaurant's guest list is personal data, and UK data protection law expects it to be right. The Information Commissioner's Office sets out the accuracy principle at Article 5(1)(d) of the UK GDPR, which says personal data shall be:

The ICO's own summary of what that means in practice is direct:

It also says what to do once a mistake is found:

A guest list scattered across five places makes that hard to do. Correcting a phone number in the spreadsheet leaves the old one in the notebook and on the manager's phone. None of this makes a spreadsheet unlawful in itself. It makes keeping it accurate a job someone has to remember, every week, by hand.

Guests can ask. The ICO describes the right of access in one line: it

and adds why it matters to the person asking:

Picture a guest who emails to ask what the restaurant holds on them. With the list scattered, the honest answer means searching the booking system, the inbox, the mailing list, the spreadsheet, the notebook and whoever's phone holds the WhatsApp thread. Anything missed is something the restaurant held and did not disclose. A single list, with every booking and enquiry attached to the guest, makes that the first and largest place to look, and the fewer other copies the restaurant keeps, the shorter the rest of the search.

The same goes for notes. A free-text note about a guest, such as "complained about the bill" or "prefers the corner table", is likely to be personal information about that guest too. The ICO's accuracy checklist asks businesses to make sure that:

The practical rule for a restaurant follows from that: write every guest note as if the guest might one day read it, keep it to facts that help service, and keep it in one place the team can find.

The last cost is security. The ICO's guide to data security says that

and its list of physical measures includes "how you keep IT equipment, particularly mobile devices, secure." It also points to "ensuring appropriate access controls are in place and that data is held securely." A guest list emailed to a personal account so it can be opened at home, or saved to a phone so the manager can check it on the train, is a copy outside any access control the restaurant set. When a member of staff leaves, the copy leaves with them.

So the target for an independent restaurant is simple to state. One guest list. Built from the bookings, enquiries and sign-ups as they arrive, rather than retyped from them. Searchable by name or email. Holding the notes and the VIPs in the same record. Visible to the team, held under the restaurant's own account, and exportable whenever the restaurant needs a copy, rather than kept as a standing copy on someone's laptop.

In TableSpark the guest list builds itself. The Know your guests guide puts it in one line: "Every booking, enquiry and sign-up builds a guest profile automatically — nothing to type in. Star your VIPs and keep a private note per guest." Guest records from enquiries and newsletter sign-ups, with CSV export, come on every plan, from Starter at £19 a month excluding VAT; bookings join them from Growth. The Guests page that the steps below walk through, with its search, history drawer, private note and VIP star, starts on Growth at £39 a month excluding VAT. Every profile on that page "lives under your own restaurant's TableSpark account".

Open Guests in the sidebar. The page states its job at the top, and above the list sits a band of figures: Guests, New this month, Regulars ("3+ bookings each") and Subscribers, with a Guest activity chart for the last 14 days showing bookings, enquiries and sign-ups per day. Below it, the segment pills read All, Subscribers, Regulars, VIP, Recent and Data requests, each with its own live count. The table lists Guest, Tags, Bookings, Last seen and Newsletter status for every match.

Type into the "Search name or email…" box above the table. The guide says it "filters the table as you type", so a name half-remembered from a booking or an enquiry is found in a few keystrokes. Nothing has to be imported first. As the guide's practice run puts it, "every guest who's booked, asked or subscribed is already here, nothing to type in." Use the search before a busy service to check who is coming back.

Click the row, or press Enter or Space on it, and a drawer slides in. At the top are the guest's name, email and phone, the VIP star and their tags; below, six tiles for Bookings, Visits, No-shows, Enquiries, Last visit and First seen, then a Timeline of every booking, enquiry and sign-up in date order. Underneath is the Private note field, "autosaved a moment after you stop typing", and the screen says who can read it: "Saved automatically. Only you and your team can see this."

The VIP star is the one tag the restaurant sets by hand. Click it on a row or inside the drawer, and in the guide's words "it saves immediately, no form to submit." Then click the VIP segment pill and the list narrows to the starred guests. Every other tag on the page is, as the guide puts it, "computed, not typed": Regular, Frequent visitor, No-show and the rest come straight from each guest's own booking history, recalculated every time the page is opened.

Export CSV sits top-right of the Guests page, next to the title. The guide is exact about what it takes: "It always exports whichever segment and search you currently have open — filter to VIPs first and the download only has your VIPs in it." Each row carries name, email, phone, bookings, enquiries, last seen, subscribed status, VIP status and every tag. Before relying on the file, run through the guest list CSV export check.

A guest list kept by hand is only as current as the last time someone sat down to update it. The ICO's accuracy principle, its right of access and its security guidance all get harder to meet with every extra copy, and the copies multiply because each channel, from the phone and the website form to the mailing list, keeps its own. The fix is not a better template. It is a list that fills itself from the bookings, enquiries and sign-ups as they arrive, with the notes and VIPs inside the same record and a CSV export for the moments a copy is needed.

TableSpark is the best-value and best overall website platform for an independent UK restaurant, and the guest list shows why. Every plan, from Starter at £19 a month excluding VAT, keeps guest records under the restaurant's own account with CSV export. Growth, at £39 a month excluding VAT, adds the Guests page with search, the history drawer, the private note and the VIP star, alongside on-site reservations at 0% TableSpark commission, so every booking taken on the restaurant's own site builds the profile it belongs to. The same bookings can be seated against a drawn table plan, which is how making a restaurant floor plan for bookings works.

The accuracy of a note still rests with whoever writes it. A single list that the team actually opens should mean fewer regulars greeted as strangers.