Reservation reports worth reading on a Monday

Most booking systems produce more reservation reports than anyone has time to read. Covers by day, bookings by source, no-shows by month, lead times, cancellations, party sizes: the numbers pile up, and on a busy Monday it is tempting to glance at the total for last week, feel pleased or worried, and close the screen. Nothing changes, and the same problems come round again the following weekend.

The reports worth reading are the ones that lead to a decision about next week: how many staff to roster on Friday, whether to open more times on Saturday, which guests to remind, which channel deserves more attention. Read that way, four reports cover almost everything a venue needs: covers, sources, no-shows and refused demand.

This guide sets out those four reservation reports, what to look for in each, the decision each one should lead to, and a twenty-minute Monday routine for reading them. It also covers the supporting reports worth a glance and the numbers that look important but rarely change anything. Every figure in it is an example.

A report that describes tells you what happened: 412 covers last week, up from 388. A report that decides tells you what to do: Friday's covers were up a quarter on the previous Friday, almost all between seven and eight, so next Friday needs another server at seven and fewer bookings offered at half past seven.

The numbers can be the same; the difference is the question you bring to them. Before opening any report on a Monday, ask what you could change this week if the answer were different. If nothing would change, the report can wait for the monthly review.

Twenty minutes, at the same time every Monday, is enough. A routine that works for many venues:

The last step is the one that matters. A Monday routine that ends without a written decision is just reading. Our guide to reading the covers report on a Monday morning goes deeper on the first report.

Covers are the simplest and most useful number in any set of reservation reports. Look at covers for each day of last week against the same day the week before, and split them by service, lunch and dinner, and by booked guests and walk-ins.

Look for three things. Days that moved sharply up or down, and why: a local event, the weather, a review. Services that are consistently full, where you may be turning guests away. And services that are consistently quiet, where an offer, a different menu or fewer staff might make sense.

The decision this report leads to is usually about staffing and capacity: more people on the busy services, fewer on the quiet ones, and more or fewer bookable times where demand has shifted.

A covers forecast is your best estimate of how many guests will come next week, service by service. It does not need to be sophisticated to be useful. A simple version, for each service next week:

Write the forecast down, and next Monday compare it with what actually happened. Within a few weeks, the forecast becomes reliable enough to roster staff and order stock from. The general principles of demand forecasting apply: use recent history, adjust for known events, and check your forecasts against reality.

The second report shows where bookings come from: your own booking page, a widget on your website, the phone, bookings entered by staff, and walk-ins. Look at each source's share of bookings and covers, and how it is changing.

A rising share of phone bookings may mean guests cannot find or use your booking page. A falling share of walk-ins on a service may mean the room is fully booked in advance and walk-ins are being turned away. A source that brings many bookings but a high no-show rate deserves a closer look.

Look at notice, too: how far ahead each source books. Guests who book weeks ahead behave differently from guests who book on the day, and reminders and policies may need to differ. The decision this report leads to is usually about where to put effort: making the booking page easier to find, answering the phone at busy times, or keeping more tables for walk-ins.

The third report covers the bookings that did not happen. Look at no-shows and cancellations for last week, and the trend over the last month.

The no show rate is the share of bookings where the guest did not arrive and did not cancel. Look at it by source, by party size and by service. A rate that is much higher for one source, one party size or one service points to where reminders, confirmation calls or a firmer policy would help most. Our guide to measuring your no show rate covers how to calculate it consistently.

Cancellations are better than no-shows, but late ones are nearly as costly. Look at how much notice cancellations give: a week, a day, an hour. If many arrive on the day, a morning reminder with an easy cancellation link brings them forward to when the table can be re-let. Our guide to a no-show policy guests read once and remember covers what that reminder should say.

Read the reasons, too, where guests or staff have recorded them. A run of cancellations for the same reason, such as parking, a road closure or confusion over the time, is often easy to fix.

The fourth report is the one most venues do not have, and it is often the most valuable: the guests you turned away. Every guest who wanted a table and did not get one is demand you could have served, at a different time, on a different night, or with a different table mix.

Refused demand shows up in several places: guests added to the waitlist who were never seated, phone callers told the night was full, walk-ins turned away at the door, and times shown as full on the booking page. Each tells you something different. A waitlist that is long on Friday at eight and empty at six suggests guests would come earlier if offered. Walk-ins turned away at lunch suggest holding more tables for them.

The decision this report leads to is about capacity: opening more times, spreading bookings, adjusting the table mix, or adding a second sitting. Our guide to booking capacity covers how.

Many booking systems record who joined the waitlist but do not report on it. If yours does not, a simple tally kept by the host is enough to start: for each service, how many parties asked for a table and could not have one, how many joined the waitlist, how many were eventually seated, and roughly when they wanted to come.

Waitlist data like this, kept for a few weeks, shows which services turn away the most guests and at what times. It is the clearest evidence there is for opening more times or changing how the room is used. Our guide to waitlist management on a night with no tables covers running the waitlist itself.

Booking conversion is the share of guests who start a booking and finish it. A guest who opens the booking page, chooses a time and then gives up is a booking lost, and most venues never see it. If your booking page or website analytics can show how many people start and how many finish, it is worth checking monthly.

If you cannot measure it directly, look for signs: guests calling to book after trying online, comments that the booking page was confusing, a high share of phone bookings from guests who mention the website. Our guide to booking abandonment covers where guests give up and how to keep them.

Beyond the four main reports, a few others are worth a minute on a Monday, because they explain the main ones.

The spread of lead times shows how far ahead guests book. If most book within a day, last-minute availability matters most, and reminders can be short. If many book weeks ahead, the diary for next week is mostly set already, and the forecast is easier.

Bookings and covers by party size show who is booking. A rise in large parties may call for more joined tables and longer turn times; a rise in twos may mean the table mix needs more small tables.

A heatmap of covers by day and hour shows when the room fills. It is the clearest picture of where pacing is needed, and where quiet hours could be filled. Our guide to turn times covers how arrival times and table times interact.

A simple funnel, booked, confirmed, seated and completed, shows where bookings are lost. A large drop between booked and confirmed may point to bookings waiting too long for approval; a drop between confirmed and seated is your no-shows and late cancellations.

The reports are most useful read together. Covers rose on Saturday, but the waitlist was long at eight and the no show rate for large parties doubled. Phone bookings rose, but so did complaints about the booking page. Each report on its own describes; together, they explain.

A good habit is to look for the one sentence that connects them: "Saturday is full at eight, empty at six, and large parties are not turning up." That sentence suggests the decisions: offer six o'clock more actively, confirm large bookings by phone, and spread arrivals.

Each Monday, write down three decisions for the week. Some examples of the kind of decisions the reports lead to:

Next Monday, check whether the decisions worked. That loop, decide, act and check, is what turns reservation reports from a record into a tool.

Some numbers look important but rarely lead to a decision in a single week: the all-time total of bookings, the average spend across a whole month, a single day's no-shows taken out of context. Daily swings are often noise; a single quiet Tuesday is not a trend.

Save the long-term numbers for a monthly or quarterly review, when there is time to look at trends properly and make bigger decisions, such as changing opening hours, the menu or the room.

The Monday numbers are more useful when the people running the door and the floor see them. Share a short summary at the first briefing of the week: last week's covers, the busiest service, the no-shows, and the three decisions for this week.

Hosts who know that Saturday's eight o'clock is overbooked and six o'clock is empty will offer six o'clock to callers. Servers who know large parties are not turning up will understand why the host calls them the day before. Our guide to what a no-show costs you on a Saturday night is a useful one to share with the team.

Groups of venues can read the same reports across every site. Comparing venues side by side shows which ones have high no-show rates, which turn away the most guests, and which get the most bookings from their own booking page. A practice that works in one venue, such as a morning reminder or held walk-in tables, can be tried in another.

Keep the comparison fair: venues in different places, with different menus and guests, will have different numbers for good reasons. Look for differences that are large and persistent, and ask what the better venue is doing differently.

The Monday routine works best when it ends on a single page that anyone can read in a minute. A good sheet has six lines: covers last week by service against the week before, the covers forecast for the week ahead, the biggest change in where bookings came from, the no-show rate and the service where it was highest, the number of guests turned away and when, and the three decisions for the week.

Keep the sheets. After a couple of months, they show which decisions worked, how accurate the forecasts have been, and which problems keep coming back. A pile of Monday sheets is often more useful than any report the system produces.

Reports are only as good as the diary behind them. If no-shows are never marked, the no-show rate looks lower than it is. If walk-ins are never recorded, covers look lower and booked guests look like a larger share. If a large party that shrank from ten to six was never corrected, covers look higher.

When a number looks wrong, check the diary before acting on it. A five-minute close at the end of every service, marking no-shows, recording walk-ins and correcting party sizes, keeps the reports honest. Our guide to ten reservation mistakes that cost you covers covers the diary nobody closes.

An invented brasserie reads its reservation reports on Monday mornings but rarely acts on them. The manager adopts the twenty-minute routine and the rule of three decisions.

In the first week, the reports show Saturday full from seven-thirty to nine, a waitlist of ten parties at eight, and a no-show rate for tables of six or more far above the rest. The three decisions: offer six and six-thirty first to Saturday callers, call every large Saturday booking on the Friday, and add a second host from seven to nine. A month later, Saturday covers are up, large-party no-shows are down, and the waitlist at eight is shorter because more guests now book earlier.

servearound's reservation analytics put the Monday reports in one place, on your venue's own clock: covers, bookings, the no-show rate, the cancellation rate, the median lead time and the seated rate, with covers day by day against the previous period. You can filter by shift, by source and by party size, with or without walk-ins. See Analytics.

The reports break bookings down by shift, by source and by party size, show covers by day and hour, how much notice guests give, how late cancellations arrive, and how bookings move from booked to confirmed to seated, with recent cancellations and no-shows listed with their reasons. servearound does not forecast covers, report on the waitlist or measure booking-page conversion today, so keep those on your own sheet. For groups, a network dashboard shows every venue together. See the reservations module.

Covers by day and service, where bookings come from, no-shows and cancellations, and refused demand: the guests you turned away.

About twenty minutes, at the same time each week, ending with three written decisions for the week ahead.

Start with bookings in the diary, add the walk-ins each service usually brings, adjust for known events, and take off your usual no-shows. Check it against reality the following week.

There is no single benchmark. Track your own rate by source, party size and service, and work on the parts that are highest.

Guests who wanted a table and did not get one: waitlist guests never seated, callers told you were full, walk-ins turned away and times shown as full online.

Keep a simple tally at the host stand for each service: how many asked, how many waited, how many were seated, and when they wanted to come.

The share of guests who start a booking online and finish it. If you cannot measure it, look for signs such as guests calling after trying to book online.

Yes. A short summary at the first briefing of the week helps hosts and servers act on what the reports show.

Monthly or quarterly, when there is time for bigger decisions about hours, menus and the room.

The reservation reports worth reading on a Monday are the ones that change next week: covers by day and service, where bookings come from, no-shows and late cancellations, and refused demand. Read them in a twenty-minute routine, compare each with the week before, and end with three written decisions.

Build a simple covers forecast from the diary, usual walk-ins, known events and usual no-shows. Split the no show rate by source, party size and service, keep your own waitlist data if your system does not report it, and watch for signs of guests giving up online. Share the numbers with the team, check next Monday whether the decisions worked, and save the long-term trends for the monthly review.