Revenue, bookings and product performance
What actually sold, by activity and by product, rather than a single revenue line.
From reporting to action
Reporting says what happened. A brief says what to do.
Most leisure venues already produce numbers. What is usually missing is the step after: a single recurring view that compares the week with the previous one and with the same period last year, separates noise from signal, and ends on a short list of actions for the days ahead.
The brief is deliberately short. It is built to be read on a Monday morning by someone who has a venue to run, not to be archived.
WEEKLY PERFORMANCEDecision brief
Revenue+12%vs previous week
Online bookings+8%week-on-week
Meta ROAS5.2×last 7 days
SEA CPA€7.80last 7 days
NEXT WEEK
Weather: rain expected Saturday — stronger indoor leisure demand likely.
Catchment: school holidays in a nearby market within the regional radius.
Action: reinforce family campaign, maintain high-performing SEA coverage and adapt promotional emphasis to weekend conditions.
What it contains
Six inputs, one weekly view.
Commercial performance and the context that explains it, in the same place. Marketing spend sits next to the revenue it is meant to produce, and external factors that move leisure demand are stated before the weekend rather than after it.
Week-on-week and year-on-year comparison
Both references in the same view, so a good week is read against the right baseline.
Google Ads / SEA and Meta campaign performance
Paid performance sits next to the revenue it is supposed to produce, not in a separate tool.
Key deviations, opportunities and recommended actions
The numbers that moved, why they matter, and what to do about them.
Weather outlook, with focus on the coming weekend
Indoor leisure demand shifts with the forecast; the brief says so before the weekend, not after.
School and public holidays in the catchment area
Holidays in neighbouring markets change who can travel to the venue that week.
How it runs
Weekly, and built around your operation.
The view is assembled from the systems already in place, which is why it starts with the configuration work rather than with a reporting tool. Consistent product structures and clean naming in the booking and POS platform are what make week-on-week comparison meaningful in the first place.
Engagements run either as defined projects or as recurring support, and the two are often combined: a project fixes the structure, the weekly brief keeps it honest.
Common questions
Performance intelligence, clearly explained.
What does a weekly management dashboard contain?
Revenue, bookings and product performance; week-on-week and year-on-year comparison; Google Ads / SEA and Meta campaign performance; key deviations, opportunities and recommended actions; the weather outlook with specific focus on the coming weekend; and school and public holidays in the venue's market and surrounding catchment area.
Is this reporting, or decision support?
Decision support. A report states what happened. The weekly brief compares the week with the previous one and with the equivalent period last year, isolates the deviations that matter and ends on concrete actions for the week ahead. If a week produces no decision, the brief has failed its purpose.
Can this run alongside a one-off project?
Yes. Engagements run either as defined projects, such as a configuration audit or a pricing restructuring, or as recurring support of which the weekly brief is part. The two are often combined: a project fixes the structure, the recurring view keeps it honest.
Start a conversation
Want a weekly view you can actually act on?
Tell Revenstone which systems you run and what you currently measure.
Discuss your reporting