Hall Occupancy Report: How to Read and Use It

Hall Occupancy Report: How to Read Metrics and Find Weak Slots

The Session Report in IZI answers three questions at once: how many hours did devices run, what percentage of total capacity was used, and which hours and days are consistently underloaded. Open it via Analytics → Session Report. Three tabs cover different views: Metrics (aggregate KPIs), Occupancy Heatmap (hourly and day-of-week pattern), and Zone Occupancy (breakdown by zone and device). The date range at the top applies to all three tabs simultaneously.

Metrics Tab: Key Figures

The Metrics tab shows KPIs in three groups: customers, sessions, and financials. Period-over-period comparison is available for each metric.

Average Occupancy % is the core efficiency metric:

Average Occupancy % = Hours Played ÷ (Shift Duration × Number of Devices) × 100%

This is an average across the selected period, not a live snapshot. For most clubs, 60–70% represents a healthy operating rhythm; below 40% indicates significant untapped revenue potential.

Sessions < 10 min — sessions shorter than ten minutes. A high count points to device issues, startup errors, or customers misunderstanding tariff terms. Investigate these before reading occupancy figures, since aborted sessions inflate session counts while contributing little to hours played.

Average Session Value — average ticket from gaming balance only (bonuses excluded): (deductions − refunds) ÷ number of sessions. Use this as the multiplier when estimating lost revenue from idle hours.

The financial block separates cash revenue (Paid with Gaming Balance) from loyalty spend (Paid with Bonuses). When measuring true cash performance, use the gaming-balance line. The gap between total session revenue and gaming-balance revenue reflects how heavily customers rely on bonuses — useful context when evaluating the cost of your loyalty programme.

Occupancy Heatmap Tab

The heatmap is a 7-day (Mon–Sun) × 24-hour matrix. Each cell shows the average number of occupied devices at that hour on that day of the week across the selected period. Cell values are device counts, not percentages. Deeper red means higher occupancy; light cells indicate minimal activity.

Reading patterns:

• Consistent time-of-day gap — an entire row is steadily light across all days. Morning hours 11:00–14:00 light every day of the week signal a prime candidate for a daytime tariff or off-peak promotions.
• Day-of-week gap — certain days are uniformly lighter. Monday and Tuesday consistently paler than Friday and Saturday points to an underloaded start of the week.
• Peak bottleneck — Friday and Saturday evening cells are maximally red, values close to your total device count. This signals a queue risk or an expansion opportunity.

Use the zone dropdown above the heatmap to view a specific zone in isolation — a VIP area may sit idle while the standard floor runs at capacity.

The Export button downloads the matrix as CSV.

Zone Occupancy Tab

The Zone Occupancy tab (labelled “Hall Occupancy” in the interface) shows three summary figures — Average Occupancy %, Number of Hours, and Maximum Possible Hours — plus a sortable table of each zone and device.

The table ranks zones by occupancy in descending order. Click any zone row to expand it and see individual device metrics. Only devices with at least one session in the period are shown; devices in maintenance or switched off are hidden.

Turning the Report into a Decision

1. Find weak slots — open the heatmap for the last four weeks; identify cells where average occupied devices is 1–2 while your total fleet is 20 or more.
2. Estimate lost revenue — idle hours × average session value × devices in zone. Take Average Session Value from the Metrics tab.
3. Match the pattern to a tool:
   • Weekday gap 10:00–16:00 → scheduled tariff that switches pricing automatically.
   • Specific day underloaded → weekly promotion or boosted bonus for that day.
   • VIP zone idle while standard zone is full → zone-based tariffs with an upsell script for the administrator.
   • Peak bottleneck with no room to expand → multipass with time restrictions to redistribute demand.
4. Verify — two to three weeks after the change, reopen the heatmap and compare. If the weak slot is now darker, the mechanic worked. If not, the cause is not price — look at external factors such as a nearby competitor or transport access.

---

See also: Hall Utilisation — Report Overview · Scheduled Tariffs · Peak / Off-Peak Pricing Strategy · Analytics: All Reports Overview