Hourly heatmaps for restaurant operations: a primer that works
If you've never plotted your busiest hour against your quietest day, you are very likely leaving money on the table. A step-by-step guide to reading hourly heatmaps, with real operator examples.
The monthly revenue report tells you what happened. An hourly heatmap tells you when — and operational decisions almost always come out of the second one.
How to read a heatmap
Days of the week run down the vertical axis, hours across the horizontal, and your metric determines the cell colour. The critical point: pick revenue as the metric and you see one picture; pick transaction count and you see a very different one. Don't decide before plotting both.
- Revenue heatmap: for pricing and menu decisions.
- Transaction-count heatmap: for staff planning.
- Basket-average heatmap: for spotting upsell opportunities.
- Void/refund heatmap: for catching operational problems — the most commonly ignored one.
Three patterns operators see most
- 1Twin peaks: lunch and dinner form two separate spikes with a dead band between. Calls for a split shift.
- 2Sliding weekend: Saturday's peak starts 90 minutes later than Friday's. Applying the same shift times to both days is a mistake here.
- 3Silent erosion: transaction count in a time band holds steady while basket average declines for weeks. Usually caused by an item going out of stock.
What to do in your first week
Open the transaction-count heatmap for the last 8 weeks and mark your three busiest and three quietest cells. Then look at your staffing at those hours. In most businesses the two tables disagree substantially, and fixing that is free.
