The covers report, read on a Monday morning

The covers report is a simple record of how many guests the venue served: by day, by service, and ideally by where they came from and how large their parties were. It is one of the most important numbers in a restaurant, because covers drive almost everything else: sales, staffing, purchasing and the kitchen's workload. Yet many venues look only at sales, and treat covers as a detail.

Read on a Monday morning, the covers report is the quickest way to understand the week just ended and prepare for the week ahead. It shows whether the venue was busier or quieter than usual, which services carried the week, where the guests came from, how many booked and did not arrive, and how next week is shaping up. It can be read in a few minutes, before the first coffee is finished, if it is set up to answer the right questions.

This guide sets out what belongs in the covers report, how to read covers by service, source and party size, the year on year comparison that makes the numbers meaningful, how reservation reports add the bookings view, how the report feeds the covers forecast for next week, and the three questions the report should answer every Monday.

Sales tell you how much money came in; covers tell you how many people it came from. The two can move differently. Sales can rise because each guest spent more, even while covers fall. Covers can rise because the venue filled more tables, even while spend per cover falls. Knowing which happened changes what you do next.

Covers also drive the work. The number of guests decides how many servers and cooks each service needs, how much the kitchen prepares, and how full the room feels. A venue that plans from sales alone can miss a busy night with low spend, or overstaff a quiet night with large tables.

That is why the covers report belongs alongside the daily sales figure, not beneath it.

A useful covers report shows, for the week just ended:

And for the week ahead: covers already booked by service, compared with the same point last week.

Keep it to a single page or screen. If it takes longer than a few minutes to read, it is too detailed for a Monday morning.

Covers by service show which parts of the week carried the trade. A week with strong Saturday and Friday dinners but weak weekday lunches tells a different story from one with steady trade every service. Look at each service against its own recent average, not just against other services.

Covers by service also show trends. A Tuesday lunch whose covers have fallen for four weeks in a row deserves attention, even if the week's total looks fine. A Sunday that is growing steadily may deserve more staff or a longer service.

Covers by source show where guests came from: the venue's own booking page, an embedded booking widget on the website, phone bookings, walk-ins, booking platforms and other channels. Each source has its own cost and behaviour. Guests who book directly cost nothing extra; guests from platforms may carry fees; walk-ins reflect passing trade and the waitlist.

Watch the mix over time. A rising share of direct bookings is good news for margin; a rising share of walk-ins may reflect good weather or a growing reputation; a falling share of one source may point to a problem, such as a broken booking link. Our guide to online booking on your own site covers the direct channel.

Covers by party size show how guests came: as couples, small groups or large parties. Party size affects the room, the kitchen and spend. A week with many large parties fills the room differently and puts different pressure on the kitchen from a week of couples.

It also affects no-shows. Large parties that do not arrive leave big holes; couples that do not arrive leave small ones. Looking at no-shows by party size shows where the risk is.

No-shows, guests who booked and did not arrive, and late cancellations are part of the covers report because they are covers the venue planned for and did not serve. They cost money in wasted preparation and empty tables that could have been filled.

Show them as a rate as well as a number: the share of booked covers that did not arrive. Compare with recent weeks and by service. A rising no-show rate on a particular night is worth acting on. Our guide to your no-show rate covers how to measure it fairly, and our guide to how to reduce no-shows without annoying guests covers what to do about it.

The single most useful comparison in the covers report is year on year: this week against the same week last year. It strips out the seasonal pattern, so a quiet January week is compared with last January rather than with December. It shows whether the venue is genuinely growing or shrinking.

Compare the same week of the year, adjusted for moving holidays. A week that contained a public holiday last year but not this year, or Ramadan in one year and not the other, needs care. Note the difference rather than ignoring it.

Recent weeks are a useful second comparison, showing the short-term trend. Together, year on year and recent weeks tell you whether a change is seasonal, a trend or a one-off.

A year on year comparison only works if the weeks are truly alike. Compare by weekday rather than by date: the second Saturday in March this year against the second Saturday in March last year, not 14 March against 14 March, which may have fallen on a Thursday. Mark weeks that held a public holiday, a school break, a big local event or a change in opening hours, so that a jump or a dip is not read as a trend.

Moving festivals need the most care. Ramadan, Easter and Diwali move from year to year, and a week that held one of them last year may not hold it this year. When that happens, compare the festival period with last year's festival period instead, and the ordinary weeks with ordinary weeks.

Reservation reports add the bookings view: how many covers were booked for each service, how far ahead guests booked, how many arrived, cancelled or did not show, and how many bookings came through each channel. They connect the covers that were served to the bookings that were made.

For the week ahead, reservation reports show how many covers are already booked for each service compared with the same point last week or last year. That is the starting point for next week's forecast. Our guide to a covers forecast your kitchen will believe covers how to build it.

Lead time, the gap between the moment a booking is made and the time of the table, tells you how much warning the venue gets. A venue where most guests book a week ahead can plan its rota and ordering from the book with confidence. One where most book on the day, or walk in, has to keep more in reserve and read the weather and the street as much as the diary.

Watch lead time by service and by source. If Saturday dinners are booked further ahead than they used to be, open the diary further ahead and release large tables earlier. If more guests book within two hours of arriving, the waitlist and the walk-in routine matter more.

Not all cancellations cost the same. One made three days ahead can usually be refilled from the waitlist or by new bookings. One made an hour before the table often cannot. Look at when cancellations arrive, measured against the time of the booking, as well as how many there are.

If late cancellations cluster on a particular service, or among a particular party size, a reminder sent at the right time and a clear change or cancel link usually help more than a stricter policy. A guest who can cancel in two taps the evening before is far more useful to the venue than one who simply does not arrive.

The seated rate is the share of bookings that actually sat down. It is the mirror image of no-shows and cancellations together, and it is the simplest single figure for how reliable the book is. A seated rate that slips week after week means the venue is planning for guests it will not see.

Read it by service and by source. A source with a low seated rate is not necessarily a bad source, but its bookings deserve a reminder and perhaps a confirmation step, and the kitchen should plan from what that source usually delivers rather than from the raw number booked.

Covers by day and service give the totals; sales by hour gives the shape. Together, they show not only how many guests came but when. A service with the same covers as last week but a sharper peak may have felt busier and been harder to cook for.

Our guide to sales by hour covers how to read the hourly curve.

Spend per cover, sales divided by covers, connects the covers report to the money. Show it by service. A service where covers held steady but spend per cover fell earned less than it seemed; one where covers fell but spend per cover rose may have earned more.

Watch for changes in spend per cover after menu changes, price changes or promotions. Our guide to average spend per head, split properly covers how to read it by service.

The covers report looks back; the forecast looks forward. The bridge between them is simple: covers already booked for each service next week, plus the walk-ins that service usually brings, adjusted for anything unusual, such as a holiday or an event nearby. That is a practical form of demand forecasting that a kitchen can use without a statistician.

Write the forecast as a number per service, share it with the kitchen and the floor on Monday, and check it against what happened the following Monday. After a few weeks, the gap between forecast and actual covers shrinks, and the team starts to trust the number.

The first question the covers report should answer on a Monday morning is how last week compared with the same week last year and with recent weeks. Were covers up or down, overall and by service? If they changed, was it a particular service, a particular day, or across the board?

Write the answer in a sentence: "Covers were up 6 per cent on the same week last year, mostly on Friday and Saturday dinner; weekday lunches were flat."

The second question is about source and no-shows. Where did last week's guests come from: direct bookings, the phone, walk-ins, platforms? Did the mix change? How many booked covers did not arrive, and on which services?

Write the answer in a sentence: "Direct online bookings rose to just over half of booked covers; no-shows were higher than usual on Thursday, mostly from two large parties."

The third question looks forward. How many covers are already booked for each service next week, compared with the same point last week or last year? Are any services running well ahead or behind? Are there large parties, events or holidays to plan for?

Write the answer in a sentence: "Next Saturday is already 15 per cent ahead of last Saturday at this point; Tuesday is behind; there is a party of 20 on Friday."

With those three sentences, the manager has what they need for the week's rota, purchasing and promotions.

Each answer leads to actions. A strong Saturday ahead means checking the rota and the kitchen's preparation. A weak Tuesday may call for a promotion or a lighter rota. A rise in no-shows from large parties may call for confirming large bookings a day ahead. A falling share of direct bookings may mean checking the booking page.

Write the actions down, with owners, as part of the weekly review. Our guide to a weekly review that takes thirty minutes sets out the agenda.

A covers report is only as good as the covers recorded. Bookings are usually counted automatically; walk-ins often are not. If walk-ins are not recorded, the report undercounts covers and misses an important source of trade.

Record walk-ins at the host stand, by service, even with a simple count. Record covers for tables that order without a booking. Over time, the walk-in figure becomes one of the most useful parts of the report, especially for forecasting.

In a group, produce the covers report for each venue and a short summary across the group. Comparing venues on the same measures shows which are growing, which are shrinking and which have changing patterns of source and no-shows.

Keep definitions the same across venues, such as what counts as a service and how walk-ins are recorded, so the comparison is fair.

The covers report is not only for the owner. The head chef needs next week's covers by service to plan preparation and ordering. The front of house manager needs them for the rota and the table plan. The owner or general manager needs the year on year comparison and the trends. Each reader takes something different from the same page.

Share it in the same form every week, at the same time, so people know where to find it. A short note at the top with the three sentences, last week, sources and no-shows, next week, is often all most readers need.

The report is only useful if the numbers behind it are recorded the same way every week. Agree what counts as a cover: guests seated, not bookings made. Agree how a party that grew from four to six at the door is recorded, and how staff meals and tastings are kept out. Record no-shows at the end of each service rather than days later, when memory has faded.

When a definition changes, note it in the report for a few weeks, so nobody reads a change in method as a change in trade.

Here is an illustrative Monday reading of the covers report for a venue. The figures are examples.

In servearound, reservation analytics shows covers day by day against the previous period, by meal period, by source and by party size, with covers by day and hour across the week. Each source, such as the booking widget, the embedded widget, the phone, walk-ins and staff-entered bookings, shows its bookings, covers, no-show and cancellation rates and median lead time. The same page shows how much notice guests give, how late cancellations arrive, party size against no-show rate, recent cancellations and no-shows with any reason recorded, and how bookings move from booked to confirmed, seated and completed.

Walk-ins added at the host stand are counted with the rest, and the figures can be read with or without them. Every day and hour is on the venue's local clock, and the reservations calendar has a week view, so next week's book is in front of you on Monday morning. See Analytics and the reservations module.

A record of how many guests the venue served, by day and service, ideally with source, party size and no-shows.

Because it removes the seasonal pattern and shows whether the venue is really growing or shrinking.

Yes. Without them, the report undercounts covers and misses an important source of trade.

A few minutes. It should answer three questions before the first coffee of the week is finished.

It shows covers already booked for next week, which is the starting point for the forecast, the rota and purchasing.

Spend per cover has fallen. Look at the menu mix, prices and promotions.

There is no single figure that suits every venue. Compare your rate with your own recent weeks and the same weeks last year, by service and party size, and act on changes rather than on a benchmark.

No. Keep covers to paying guests, so the report compares like with like and spend per cover is not diluted.

Last week, the last four weeks and the same week last year are usually enough for a Monday reading.

The covers report shows how many guests the venue served, by service, source and party size, with no-shows and spend per cover alongside. Read it every Monday morning with a year on year comparison and recent weeks, and connect it to sales by hour and reservation reports.

Answer three questions: how did last week compare, where did the covers come from and who did not come, and what does next week look like? Turn the answers into actions for the rota, purchasing and promotions, record walk-ins so the report is complete, and use it as the starting point for next week's covers forecast.