In summary
What you need to know
Turn booking, seating and guest data into useful operational decisions.
- Connect metrics to decisions
- Segment operational averages
- Review weekly and monthly at different depths
- Best for
- Hospitality operators reviewing revenue management
- Reading time
- 4 min read
- Last reviewed
- 6 August 2026
Share this guide
Reservation analytics should help a manager decide what to change. A dashboard full of totals is less valuable than a small set of metrics connected to capacity, channel and guest behaviour.
01
Demand metrics
Track searches, bookings, unavailable requests, cancellations, no-shows and waitlist demand by service. Unavailable searches reveal demand the restaurant could not accept, but not all of it can be profitably served.
02
Operational metrics
Review planned and actual arrival, seating delay, duration, turn time and occupancy. Segment by party size and area to avoid averages hiding bottlenecks.
Decision dashboard
Move from demand to delivery before judging value
Each layer answers a different management question and prevents one attractive total from hiding an operating problem.
| Layer | Core measure | Decision |
|---|---|---|
| Demand | Searches and unavailable requests | Where capacity is constrained |
| Conversion | Confirmed bookings by source | Where the journey loses guests |
| Delivery | Arrivals, seating delay and duration | Whether service kept the promise |
| Value | Contribution and repeat visits | Which demand is worth growing |
03
Channel and guest metrics
Compare acquisition cost, cancellation, spend where available and repeat rate by booking source. Track first-time versus returning guests and the share of bookings linked to usable guest records.
04
Build a review rhythm
Use a short weekly operational review and a deeper monthly commercial review. Assign every metric an owner and a possible action; retire numbers that never influence a decision.
05
Procurement and operating depth
Create a metric dictionary before comparing reports. Define when a booking becomes confirmed, cancelled, a no-show or seated; which timezone controls service dates; and whether covers or reservations are the unit. Small definition differences can create large apparent performance changes.
Use a decision hierarchy. Start with demand, then conversion, operational delivery and realised value. A higher booking rate is not automatically better if it creates seating delays, overwhelms the kitchen or attracts bookings that cancel before service.
Limit access to guest-level data and use aggregated views whenever an operating decision does not require identity. Keep exports controlled and give each reporting workflow a clear operational owner.
Venue-specific application
A realistic operator example
A restaurant sees 1,240 monthly reservations in its dashboard, but the total alone does not explain what to change. The manager builds a weekly view by service and booking source: searches, unavailable requests, confirmed covers, cancellations, no-shows, seated covers and actual seating delay. Friday at 20:00 shows high rejected demand and a 17-minute seating delay, so the first action is to adjust pacing, not simply expose more tables. The following four weeks are compared with the same services and the team records whether conversion improves without increasing delay.
- Define one operating decision for every dashboard
- Use consistent booking and service-status definitions
- Segment results by service, source and party size
- Compare planned with actual arrival and seating times
- Separate reservations from seated covers
- Assign a metric owner and review cadence
What to measure
Signals that belong in this review
Next operational step
Use the relevant UpSalt workflows
- Connect metrics to decisions
- Segment operational averages
- Review weekly and monthly at different depths