Booking form fields: which ones to delete

A restaurant's booking form tends to grow. A field is added for birthdays because someone wanted to send cards. Another for postcode, because the owner wondered where guests came from. Another for how the guest heard about the venue, for a marketing report nobody reads. Each field seemed harmless when it was added. Together, they turn a booking that should take a minute on a phone into a chore, and some guests give up before they finish.

Every booking form field has a cost: a little more typing, a little more time, a little more chance that a guest on a bus decides to do it later and never does. Some fields are worth that cost, because the venue genuinely needs the information to hold the table and serve the guest well. Many are not.

This guide goes through booking form fields one by one: the four worth keeping, the two that are better asked after the booking is confirmed, and the rest, which most venues should delete. It also covers how to ask for special requests without slowing the form, and what the law says about collecting guest data. Every figure in it is an example.

On a phone, each field means a tap, a keyboard appearing, typing with a thumb and checking for mistakes. Most guests booking a restaurant are on a phone, and many are doing something else at the same time. A form with four fields can be finished in under a minute; one with eleven can take several, and each extra step is a point where some guests stop.

There is no fixed figure for how many bookings each field loses, and any published number describes someone else's form. The principle is simpler: fewer fields, fewer abandoned bookings. Our guide to booking abandonment shows where in the flow guests most often give up, and the details form is one of the main places.

You need a name to greet the guest, find the booking when they arrive and match them to their history. One name field is usually enough. Separate first-name and surname fields add a step for little gain; if you need both, keep them on one line.

Email is how the guest receives their confirmation, their reminder and their link to change or cancel. Without it, the guest has no record of the booking and no easy way to cancel, which is a quiet cause of no-shows. Make it required, and use a field that opens the email keyboard on a phone.

A phone number lets the venue contact the guest on the day: a table running late, a question about a large group, a guest who has not arrived. Many venues make it required for that reason. Use a field that opens the number pad and accepts the formats people actually type.

An optional notes field lets guests tell you what matters: allergies, dietary needs, accessibility requirements, a high chair, an occasion. It costs nothing for guests who have nothing to say, and it is invaluable for those who do. Make sure what guests write reaches the floor and the kitchen.

Some information is useful but not needed to hold the table. Asking for it after the booking is confirmed, in the confirmation email or on the confirmation screen, gets you much of the same information without costing bookings.

Knowing that a booking is for a birthday or an anniversary lets the team make something of it. But it is not needed to book, and many guests skip it anyway. Ask in the confirmation or the reminder: "Celebrating something? Let us know." Guests who are celebrating will tell you; the rest are not slowed down.

This is the field most often added for a report and least often answered honestly. If you want to know, ask after the booking, with a single optional question, or ask at the table. Better still, measure where bookings come from by tagging the links you share, which is more reliable than guests' memories.

Most other fields on a typical booking form can go.

Some venues need one of these for a genuine reason, and that is fine. The test for every field is simple: do we need this to hold the table and serve this guest well, now? If not, ask later or not at all.

It is tempting to replace the notes field with a list of tick boxes: high chair, wheelchair access, window seat, quiet table, birthday. Checklists look tidy, but they add length to the form, they suggest promises the venue may not be able to keep, and they never cover every case.

A single notes field with a short prompt usually works better: "Allergies, access needs, a celebration? Let us know." Then make sure every note is read before service and reaches the people who need it. Be careful with requests you cannot guarantee, such as a particular table. Acknowledge them as requests, not promises.

Allergy information is the most important thing a guest can write in the notes field, and it needs handling with care. A note about a severe allergy must reach the kitchen and the server, and the guest should still be asked about allergies when they order, because a note made days earlier is not a substitute for a conversation at the table.

Some venues add a separate allergy prompt for this reason. If you do, keep it optional and short, and make sure it travels with the booking to the table and the kitchen ticket. A field that guests fill in and nobody reads is worse than none, because the guest believes the venue knows.

Many venues want to invite guests back by email, and the booking form is a natural place to ask. Ask clearly and fairly: an optional, unticked box, with a short explanation of what guests will receive. Pre-ticked boxes or consent buried in the terms do not give you valid consent in many places.

Asking for consent does not need to slow the form much: it is one tap for guests who want it and none for those who do not. Our guide to marketing consent collected so it holds up covers what makes consent valid and how to record it.

Data protection law in many places expects businesses to collect only the personal data they need for the purpose. In the UK, the Information Commissioner's Office describes this as the principle of data minimisation. A booking form that asks only for what is needed to hold and manage the booking is easier to justify, easier to protect and kinder to guests.

That principle and good booking conversion point the same way. Every field you delete is data you no longer have to store, protect and explain. Our guide to guest data: what to collect and what to leave covers the wider picture.

Some booking systems ask guests to confirm their email address with a short code before the booking is made. It is an extra step, and on a phone every step costs a little. It also solves real problems: a mistyped address means the guest never receives the confirmation or the reminder, and a fake booking made with an invented address takes a table someone else could have had.

Whether the trade is worth it depends on the venue. A busy venue with frequent fake or duplicate bookings gains more from verification than a quiet one. If your system verifies email, make the step as quick as possible: the code should arrive within seconds, the field should accept a pasted code, and the screen should say clearly why it is asked for. Then watch it in your tests like any other screen.

For each field you keep, decide whether it is required. Required fields stop the booking until they are filled in; optional ones do not. Keep the required list as short as possible: usually name, email and phone. Make the notes field optional.

Mark required and optional fields clearly, so guests do not spend time on optional fields they could skip, or fail to submit because a required field was not obvious.

Small details make the fields you keep quicker to fill in.

Each saves a few seconds; together they make the form feel effortless.

Large groups and private events need more information than a table for two: the occasion, a set menu choice, dietary needs for everyone, a budget, sometimes an invoice address. Adding all of that to the public form makes every ordinary booking longer for the sake of a few large ones.

Keep the public form short, and handle groups separately. Above your online party size limit, direct guests to a separate enquiry by email or phone, where the extra questions can be asked in conversation. Our guide to private dining that pays for the room it uses covers what to ask when a group gets in touch.

Every field you keep should lead somewhere. A phone number is only useful if someone calls when a table is running late. A marketing opt-in is only useful if you send emails people want to read. A notes field, where your system has one, is only useful if the notes are read before service.

For each field, write down who uses it and when. A field with no answer to that question is a field to delete. A field whose answer is "nobody, but we might one day" is a field that costs bookings today for a benefit that may never come.

Some fields earn their place for a season and then stop. A field asking whether guests want the terrace makes sense in summer and not in winter. A field for a special event makes sense until the event is over. Fields added for a campaign are often left behind long after the campaign has ended.

Give temporary fields an end date when you add them, and remove them when it comes. A form reviewed every season stays as short as the current trade needs.

The same discipline applies when a booking is taken by phone. A host who asks a long list of questions on the phone takes longer to answer each call, keeps other callers waiting and annoys the guest who just wanted a table. Give the team the same short list the online form uses: name, phone, email for the confirmation, and a question about allergies or anything else the venue should know.

The phone does have one advantage over the form: a conversation. A host can hear that a booking is for a celebration, or that a guest sounds unsure about the menu, and respond in a way no field can. Use that, rather than reading out a script.

Fill in your own booking form on a phone, one-handed, and time it. Then watch someone who has never seen it do the same. Note every hesitation: a field they did not understand, a keyboard that did not match, an error message that confused them.

Review the form every few months. Fields tend to creep back, added one at a time for good reasons. A regular review keeps the form as short as it needs to be.

An invented brasserie's booking form has eleven fields: title, first name, surname, email, confirm email, phone, postcode, date of birth, how did you hear about us, occasion and notes. On a phone, it takes most guests well over a minute, and the manager notices many visits to the booking page that end without a booking.

The brasserie cuts the form to name, email, phone and notes, with an optional marketing box. It moves the occasion question into the confirmation email and drops the rest. Over the next month, by its own count, more booking page visits end in a booking, and the occasion question in the confirmation email gets answered by many of the guests who are celebrating, which is all it needed.

servearound's booking page asks for first and last name, phone and email, and confirms the email with a six-digit code before the booking is made. Guests can tick an optional box to receive the venue's emails, and confirm it from their inbox. Confirmation and reminder emails carry a link to change or cancel. There is no notes field for guests on the booking page today, so allergies, access needs and occasions are taken by your team, by phone, in the reminder conversation or at the table, and recorded on the booking or the guest's profile, where they show on the reserved table and the kitchen ticket. See the reservations module.

Every booking adds to the guest's profile in guest profiles, with their visits and the notes and allergies your team records, so information collected once is there next time without asking again.

Name, email and phone, with an optional notes field. Those hold the table, confirm and remind the guest, and tell you about allergies, access needs and occasions.

Each field adds time and effort, especially on a phone, and some guests give up. The exact cost depends on your form and guests, but fewer fields mean fewer abandoned bookings.

Not on the booking form. Ask later, optionally, if you want to celebrate birthdays, and only with a clear reason.

After the booking, optionally, or at the table. Tagged booking links are a more reliable way to see where bookings come from.

Usually a single optional notes field works better: shorter, more flexible and less likely to imply promises you cannot keep.

Yes, as an optional, unticked box with a clear explanation. Pre-ticked boxes or consent hidden in the terms are not valid consent in many places.

In many places, yes. Principles such as data minimisation mean collecting only what you need for the purpose.

No. Accounts and passwords add steps and lose bookings.

Many systems ask for both, so the venue can find the booking and greet the guest properly. If yours does, keep both fields on one line and make each obvious. What matters more is not adding anything else that is not needed.

They miss the confirmation and the reminder, and may not turn up. Showing the email back on the confirmation screen, or verifying it with a short code, catches most mistakes.

Only if it changes what you prepare, such as high chairs or a children's menu. A question in the confirmation, or a quick call for larger family bookings, covers most cases without adding a field that every other guest has to skip.

Every few months, and whenever someone proposes adding a field. Ask whether each field is needed to hold the table and serve the guest now.

Every booking form field costs some bookings, so keep only what you need now: name, email, phone and an optional notes field for allergies, access needs and occasions. Ask for the occasion and how guests heard about you after the booking is confirmed, and delete titles, addresses, birthdays, confirm-email fields and mandatory accounts.

Use a single notes field rather than a checklist, make sure allergy notes reach the kitchen, ask for marketing consent with an unticked box, and collect only the guest data you need. Use the right keyboards and autofill, mark required fields clearly, and review the form every few months so it stays short. A shorter form is better for booking conversion, for guests and for data protection alike.