Ten reservation mistakes that cost you covers

Few restaurants lose covers through one dramatic failure. They lose them through small reservation mistakes that repeat every week: a turn time that is twenty minutes too long, a table held for a regular who never comes, a note nobody read, a no-show nobody recorded. Each costs a table here and there. Added up over a year, they can cost more than a quiet month.

The good news is that these mistakes are ordinary and predictable. The same ten appear in venue after venue, and each has a simple check that catches it before it costs anything. None of the checks needs new staff or a large budget; most need ten minutes and a habit.

This guide sets out ten reservation mistakes that cost covers, what each looks like on the night, what it costs, and the check that catches it. Every figure in it is an example, not a benchmark.

A single empty table on a Saturday night is easy to shrug off. But a mistake that costs one table of two once a week costs over a hundred covers a year. Five such mistakes, each costing a table a week, cost over five hundred. At an example spend of 40 a head, that is twenty thousand of sales that walked past the door.

Mistakes also combine. A turn time that is slightly too short only causes a wait when a large party is also late and the host is also on the phone. Safety engineers call this the Swiss cheese model: each layer has holes, and things go wrong when the holes line up. Closing a few of the holes makes the bad nights far rarer.

The diary assumes each table will be free again after a set time. If that time is too long, tables sit empty between bookings while the diary says they are taken, and the booking page shows the evening as full when it is not. If it is too short, booked guests wait at the door for tables that are still eating dessert.

What it costs: on the long side, a second sitting that never gets sold; on the short side, waits, complaints and guests who do not come back.

The check: once a month, compare the turn time in your booking rules with how long tables actually stay, by party size and service. Our guide to turn times explains how to measure them from your own seating times and set the figure properly.

Many venues hold tables back from online booking: for regulars, for walk-ins, for phone bookings, for a group that might confirm. Holding tables is sensible. Forgetting to release them is not. A table held "just in case" for a regular who does not call, or for a group that never confirmed, stays empty through the evening.

What it costs: a table per held slot that nobody used, often on the busiest nights, when holds are most common.

The check: give every hold a release time, written down, such as noon on the day for walk-in tables or a date for a provisional group. Check the holds each morning and release anything past its time. A hold without a release time is an empty table waiting to happen.

A guest mentions an allergy, an anniversary or a wheelchair when booking. The note is recorded, and then it sits in the booking, unread, while the guest is seated at the wrong table, the occasion passes unmarked and the kitchen hears about the allergy only from the guest.

What it costs: less obvious than an empty table, but real. Guests whose notes are missed are far less likely to return, and far more likely to say so publicly.

The check: read every note for tonight's bookings before service, and share the important ones at the briefing. Make sure notes appear where they are needed: at the door, on the table and, for allergies, on the kitchen ticket. Our guide to booking notes the whole team will actually read covers how.

At the end of the night, the diary should reflect what actually happened: who arrived, who did not, who walked in, which bookings were cancelled at the door. In many venues, nobody closes it. No-shows are never marked, walk-ins are never recorded, and parties that changed size stay at their old numbers.

What it costs: the diary becomes unreliable, and so does everything built on it. Reservation reports show the wrong no-show rate, capacity is set from wrong numbers, and a guest who failed to turn up three times looks like a reliable regular.

The check: a five-minute close at the end of each service. Mark every no-show, record every walk-in, correct every party size, and note anything the next shift should know. Make it one person's job each night.

The venue takes bookings in more than one place that do not share availability: a booking platform and its own page, an online system and a paper book, a phone pad and a screen. Each place can sell the same table. Double bookings follow.

What it costs: two parties for one table, one of them disappointed, and a host left to apologise for a mistake made hours earlier.

The check: one diary behind every channel, with every booking, change and cancellation entered at once. Where a channel cannot share your diary, give it its own tables. Our guide to double bookings sets out the six causes and a fix for each.

Capacity limits are set when the booking system is first switched on and never touched again. Meanwhile the menu changes, the team changes, a terrace opens, and the busiest night moves from Friday to Saturday. The limits no longer fit the room.

What it costs: either too few bookings on busy nights, with tables left for walk-ins who never come, or too many at once, with a kitchen swamped at eight and slow service for every table.

The check: review booking capacity at the start of each season, and whenever the menu, the team or the room changes. Look at when the room fills and when the kitchen struggles. Our guide to booking capacity covers how to set it by service.

A party is twenty minutes late on a full night. Does the table wait, go to the waitlist, or go to a walk-in? In many venues, nobody knows, and the host decides under pressure, differently each time. Sometimes a table waits half an hour for guests who never come; sometimes a guest who called ahead to say they were running late arrives to find their table given away.

What it costs: tables held empty for no-shows, and guests who were treated unfairly.

The check: a written rule for late arrivals that the whole team knows. A grace period, such as fifteen minutes; a call to the guest at the end of it; and what happens next. Tell guests the rule in the confirmation, and ask them to call if they are running late. Our guide to a no-show policy guests read once and remember covers the wording.

Guests forget, plans change, and some guests who cannot come do not think to cancel. Without a reminder, they do not realise until it is too late; without an easy way to cancel, they do not bother. The table sits empty.

What it costs: no-shows that a single message would have turned into cancellations, which can be re-let from the waitlist or a standby list.

The check: send a reminder before every booking, with a link to change or cancel in a tap. Look at when cancellations arrive; if many come too late to re-let, send the reminder earlier. Our guide to keeping a standby list covers filling the tables that cancellations free up.

A guest calls for Saturday at eight, and the answer is "sorry, we're full." The call ends, and the guest books somewhere else. The same happens at the door and on the booking page, where a full time simply shows nothing.

What it costs: guests who would happily have come at six-thirty, on Sunday, or after a short wait, lost entirely, along with the knowledge that they wanted to come.

The check: never end at "we're full." Offer another time, the waitlist, another evening or a short-notice list. On the booking page, show the nearest available times. And count how often you turn guests away, because that refused demand tells you where to add capacity. Our guide to taking bookings by phone when the room is full covers what to say.

The booking system records everything: covers, sources, no-shows, cancellations, party sizes, lead times. Nobody reads the reports, or someone reads them and nothing changes. The same mistakes repeat, because nobody sees them in the numbers.

What it costs: every other mistake on this list, for longer than necessary.

The check: a twenty-minute review every Monday, ending in three written decisions for the week. Our guide to reservation reports worth reading on a Monday sets out which reports to read and how to turn them into decisions.

Several of the checks above fit into one short weekly routine, separate from the Monday reports:

Ten minutes a week catches most of these mistakes before they cost a full weekend of covers.

Many reservation mistakes happen because nobody owns the diary. Everyone uses it, but nobody is responsible for keeping it accurate, closing it at night, reviewing the rules or reading the reports.

Give the diary an owner, usually a manager, with a deputy for days off. The owner does the Monday review, the weekly check and the seasonal capacity review, and makes sure the nightly close happens. Owning the diary does not mean taking every booking; it means making sure the system everyone uses tells the truth.

Many of these mistakes start with a new member of staff who was never shown how bookings work in your venue: how to enter a phone booking, where notes go, what to say when the night is full, how to close the diary. They do their best, and their best is different from everyone else's.

Train everyone who might take a booking or run the door on the same few routines, write them down, and keep them at the host stand. A short practice session before a new starter's first busy night prevents mistakes that would otherwise take weeks to notice.

Despite every check, a mistake sometimes reaches a guest: a double booking, a lost note, a table given away too early. When it does, put the guest first. Apologise without excuses, fix what you can at once, and offer something that shows you mean it: a drink, a dessert, a better table next time.

Then trace the mistake back to its cause, using the ten above. A mistake that is traced and fixed costs one evening; one that is shrugged off costs the same evening again next week.

Putting a figure on each mistake makes it easier to decide which to fix first. The sum is simple: tables lost each week, multiplied by the guests at each table, multiplied by an average spend, multiplied by the weeks in a year.

An invented example: held tables that are never released cost one table of two on most Friday and Saturday nights, about 90 tables a year. At an example spend of 40 a head, that is around 7,200 of sales a year from one habit. A no-show rate a few points higher than it needs to be, on a busy room, can cost several times that. The figures are rough, and they do not need to be precise; they only need to show which mistakes are expensive and which are small.

Not every mistake needs fixing at once. Start with the ones that are cheap to fix and costly to leave:

The others, turn times, booking capacity and a single diary for every channel, need a few weeks of data or a change of system, so plan them next. Fixing the quick ones first also gives you better figures for the harder ones.

Some reservation mistakes happen before a guest reaches the venue, on the booking page itself. A page that offers only a few times, hides the nearest free time when the chosen one is full, or caps party sizes too low sends guests away or to the phone. A page with too many steps, or one that asks for more than it needs, loses guests halfway through.

Book a table on your own page every few weeks, on a phone, as a guest would, for your busiest night and for a party larger than usual. Note every moment you hesitate. Our guide to booking abandonment covers where guests give up and how to keep them.

An invented restaurant with 60 seats feels busy but sees covers flatten over a year. The new manager runs the weekly check for a month and finds four of the ten mistakes: turn times thirty minutes too long for twos, tables held for walk-ins all evening on nights when none came, no-shows never marked, and "we're full" said to callers without alternatives.

The fixes are small. Turn times for small tables are shortened, holds are released at seven, the diary is closed every night, and callers are offered another time or the waitlist. Within two months, the restaurant serves noticeably more covers on its busiest nights without adding a seat, and the reports finally show an accurate no-show rate to work on.

servearound builds several of these checks into the reservations module. Booking rules set the booking duration and the times each shift offers, the notice you need and the largest party online, and a reminder email goes out a set number of hours before each booking, with a link for the guest to change or cancel. Every source, the booking page, the widget, the phone, staff and walk-ins, goes into one diary. See the reservations module.

Staff mark no-shows and record walk-ins, so the figures stay true, and a "Missed reservation" email can go to guests who did not arrive. The waitlist catches guests when a time is full, notes and allergies show on the reserved table, and reservation analytics show covers, sources, party sizes, notice, no-shows and how late cancellations arrive. If you would like to see how it fits your room, talk to us.

Wrong turn times, held tables never released, unread notes, a diary nobody closes, more than one place to book, stale capacity limits, no late-arrival rule, no reminders, "we're full" with no alternative, and unread reports.

It varies, but small mistakes repeat. As an example, one table of two lost each week is over a hundred covers a year.

Keep one diary for every channel, enter every booking and change at once, and give channels that cannot share it their own tables.

Have a written rule: a grace period, a call to the guest, and what happens to the table after it, told to guests in the confirmation.

So that no-shows, walk-ins and changed party sizes are recorded, and the reports built on the diary are accurate.

Review it each season, and whenever the menu, the team or the room changes.

Offer another time, the waitlist, another night or a short-notice list, and count how often you turn guests away.

One manager, with a deputy, responsible for the nightly close, the weekly check, the Monday reports and the seasonal reviews.

Covers by day and service, sources, no-shows and cancellations, and refused demand, every Monday, ending in written decisions.

Usually closing the diary every night, because it costs five minutes and makes every other fix measurable. Then reminders, alternatives to "we're full" and release times for held tables.

Most lost covers come from ten ordinary reservation mistakes: turn times that do not match reality, held tables never released, notes nobody reads, a diary nobody closes, two places to book, booking capacity set once, no rule for late arrivals, no reminders, "we're full" with no alternative, and reports nobody reads.

Each has a simple check. Measure turn times, give every hold a release time, read notes before service, close the diary every night, keep one diary for every channel, review capacity each season, write down the late-arrival rule, send reminders with an easy way to cancel, always offer an alternative, and read the reservation reports every Monday. Give the diary an owner, and the checks become habits that keep tables full.