Help centre › Analytics

Reading the reports

The analytics dashboard surfaces numbers; this article is about turning those numbers into operating decisions. It runs through each chart on the page, what is worth paying attention to, and what the common patterns usually mean. For a tour of the layout itself, start with Your analytics dashboard.

Past data, forecasts, and how to tell them apart

Two charts on the Restaurant tab — Bookings & covers and Occupancy — show past and future on the same line. Today is marked with a red vertical rule. Everything to the left of it is what actually happened; everything to the right is a forecast based on your recent pattern.

A few practical implications:

  • Trust the past more than the future. The forecast is best read as "what to expect if nothing changes" — not as a guarantee.
  • Watch the slope of the forecast, not the absolute number. A forecast that is gently rising or falling tells you more than the exact predicted figure on any one day.
  • Compare last week to this week. If you ran an offer or had a one-off event, switch the date range to that week and the week after to see what carried over.

Reading the summary cards

Total covers vs total bookings

Bookings is the number of parties; covers is the number of guests. The ratio tells you the average party size for the range. If it falls noticeably below your usual, your bookings are skewing towards couples and pairs — useful to know before planning a tasting menu that needs a group of four to make sense.

Total covers stops at yesterday on purpose — so the figure stays a record of what has actually happened. Total bookings includes today and any confirmed bookings in the future, since those are bookings on the books rather than predictions.

Estimated revenue

Revenue is your average price per head, multiplied by total covers up to yesterday. There is no calculation involving real payments — it is a rough sizing of how busy the kitchen has been, in pounds, so it can sit next to your covers and bookings numbers.

To make it meaningful, set your average price per head under Business details → Basic. Until you do, the dashboard uses a placeholder so the card has something to show — but the figure will be off until your real average is in.

No-shows

The no-show card is a prediction based on past behaviour, not a count of bookings you have actually marked as no-shows. Use it to plan headcount and prep rather than to follow up with specific guests.

For the day-by-day reality, mark no-shows in the Calendar after service and the predictions will improve over time.

Reading the occupancy chart

Occupancy is plotted as two lines — covers and tables:

  • Covers occupancy is the share of seats taken. The headline measure of how full you are.
  • Tables occupancy is the share of tables seated, regardless of party size.

When the two lines move together you are well-matched — your table layout fits the party sizes you actually take. When tables occupancy is meaningfully higher than covers occupancy, you are seating small parties on large tables and leaving covers on the table. Reach for the floor plan editor if that pattern is consistent.

Reading the AI-generated insights

The insights panel summarises the days ahead, with a per-date card listing the predicted bookings and a short note about the underlying pattern. It is built from the same forecast that drives the Bookings & covers chart, plus the seasonality the model has learned from your past data.

A few rules of thumb:

  • Use it as a heads-up, not a brief. It points you at the days worth paying attention to; the decision about what to do is yours.
  • It improves as your data grows. A restaurant with three months of bookings will get more useful summaries than one with three weeks.
  • Cross-check against the past. If the model predicts a slow Tuesday, scroll back through past Tuesdays in the same range to see if that is normal or a one-off.

Reading the Web tab

Visitors and conversion rate

The conversion rate is bookings divided by visitors. There is no universal benchmark — your figure depends on whether visitors came looking to book or were browsing for the menu. Some rough patterns to watch for:

  • Visitors up, conversions flat. Something is stopping people on the booking flow — too few times available, a busy weekend with no slots, or copy that does not explain the rules clearly. Review your availability and the widget's wording.
  • Visitors flat, conversions down. Often seasonal — a quieter month for the cuisine or area. Compare against the same window last year before changing anything.
  • Both up. Something you did is working. Switch the interval to weekly and look at the slope so you can tell whether it is a one-off spike or a trend.

Visitors by referrer

The pie chart tells you where your traffic is coming from. A few common shapes:

  • Mostly direct. Loyal guests typing your URL or coming via a bookmark. Good sign — but limits your growth until search and social start contributing.
  • Mostly search. Strong organic presence. Worth looking at which pages on your own site you are sending visitors to; the widget on your homepage is usually the lowest-friction path from a search result to a booking.
  • Mostly social. Campaign-driven traffic. Watch conversion rate carefully — social visitors often browse rather than book.
  • Mostly Make a Rezzy referrals. Diners discovering you through the Explore directory. Polishing your listing — photos, description, menu — is the direct way to lift this slice.

Putting it together

A monthly habit that catches most things:

  1. Set the date range to the last month and the interval to daily.
  2. On the Restaurant tab, check covers occupancy. Are there whole days or services consistently below 60–70%? That is where pacing changes, an offer, or an event would make the biggest difference.
  3. Switch to the Web tab. If conversion rate is meaningfully below the previous month, walk through your widget yourself — see the booking flow as a guest does.
  4. Look at the referrer pie. The biggest slice tells you which channel to invest in next; the smallest, what to fix.
  5. Switch the interval to weekly and pull the date range back to the last quarter. The longer view picks up trends that day-to-day noise hides.

Where to go next