How to Track and Compare Billiard Hall Performance Across Multiple Weeks Using Revenue Reports

Most billiard hall operators have a rough sense of which nights are busy and which are slow — but "rough sense" is not a management tool. Billiard hall performance tracking with weekly revenue comparison gives you the hard numbers to answer real questions: Is Tuesday actually improving since you added happy hour pricing? Did that weekend tournament bring in more or less food and drink revenue than a normal weekend? Are you trending up month over month, or just having one good week followed by three flat ones?

This article walks through how to build a practical weekly review habit using your revenue reports — what to pull, what to compare, and what to do with what you find.

Pull the Same Report Windows Every Week Without Fail

Consistency is the foundation of useful comparison. If you pull "last week" reports on different days each week, you're comparing unequal windows — a 6-day week against a 7-day week, or one that includes a holiday and one that doesn't. Pick a fixed review day (Monday morning works well for most halls) and always pull the previous Monday-through-Sunday period.

Export each week's data to CSV immediately so you have a permanent record outside the system. Over time, you'll build a local archive of weekly snapshots that lets you look back three or six months without relying on memory. Store them in a simple folder structure: Revenue Reports / 2025 / Week 23 is enough. This archive becomes invaluable when you're trying to justify a pricing change or evaluate a new promotion.

If your software supports date-range filtering on revenue reports, use it precisely. Billiard hall revenue reports with proper date filtering eliminate the guesswork and let you isolate any seven-day window you need.

Separate Table Revenue from Product Revenue in Every Comparison

A single "total revenue" number tells you very little. A week where table time drops by 15% but food and beverage sales jump 20% is a completely different story from a week where both lines fall together. Always break your weekly comparison into at least two categories: table session revenue and product/retail revenue.

Here's why this matters in practice. Suppose you run a bring-your-own-cue crowd on weeknights — those players rack up long sessions but buy almost nothing from the counter. On weekends you get casual players who rent house cues, buy drinks, and leave after 90 minutes. Your table revenue per hour might be similar both nights, but the total revenue picture is very different. If you only look at one combined number, you'll miss the dynamic entirely.

When reviewing week-over-week, track these lines separately:

• Table time revenue (total and per table)
• Food and beverage sales
• Equipment rentals (cue, rack, bridge rentals if you charge separately)
• Merchandise or accessory sales
• Membership fee collections if applicable

A shift in any one of these lines is a signal worth investigating before you act on it.

Use Week-over-Week and Year-over-Year Comparisons for Different Purposes

These two comparison types answer different questions and you need both.

Week-over-week comparison catches short-term changes — a promotion that worked, a staff issue that cost you sales, a competitor that opened nearby. If week 22 was 18% below week 21, something specific happened and you should be able to identify it. Check your shift notes, check the weather, check whether you had a full staff complement. The closer in time, the more actionable the signal.

Year-over-year comparison strips out seasonality and gives you a true read on whether the business is growing. Billiard halls in most markets have predictable seasonal patterns — back-to-school slowdowns, holiday peaks, summer lulls in some regions and summer surges in others. Comparing week 22 of this year to week 22 of last year tells you whether you're actually ahead of where you were, independent of what time of year it happens to be.

If you're new to formal tracking, start building your archive now and commit to at least one full year before drawing year-over-year conclusions. The first year is your baseline.

Identify Your Key Performance Indicators Before You Start Comparing

Raw revenue totals are a starting point, but meaningful billiard hall performance tracking requires ratios and rates that normalize for variables outside your control — like how many hours you were open, or how many tables you have.

The most useful KPIs for weekly comparison in a billiard hall context:

• Revenue per table per hour: Total table revenue divided by total available table-hours in the week. This is your utilization efficiency metric. A hall with 10 tables open 12 hours a day has 840 available table-hours in a week. If your table revenue was ₱42,000, you earned ₱50 per available table-hour — whether that's good depends on your rates, but the metric is comparable week to week.
• Average session length: Longer sessions aren't always better — a table locked up for four hours by two players at base rate may earn less than three 90-minute groups at a premium evening rate. Track this alongside revenue per table-hour.
• Peak vs. off-peak revenue split: What percentage of your weekly revenue came from your defined peak hours? If happy hour promotions are pulling people in during off-peak slots, you should see this ratio shift over time. Understanding how happy hour pricing affects revenue distribution week over week is one of the clearest ways to evaluate whether a promotion is working.
• Attachment rate: Product orders per session started. If 60% of sessions include at least one product purchase this week versus 45% last week, something drove that — a staff upsell push, a new menu item, a busier crowd type.

Build a Simple Weekly Review Routine — Not a Dashboard Project

Operators sometimes get stuck trying to build the perfect tracking spreadsheet before they start. Don't. A two-column comparison in a basic spreadsheet — this week versus last week, this week versus same week last year — is enough to start seeing patterns. Add complexity only when a specific question demands it.

A practical 20-minute Monday morning routine:

1. Export last week's revenue report, filtered Monday–Sunday.
2. Record the five to seven numbers you track (total revenue, table revenue, product revenue, sessions started, average session length, peak revenue, off-peak revenue).
3. Calculate week-over-week change for each. Flag anything more than 10% different in either direction.
4. Write two sentences in a notes column explaining flagged items. "Week 21 table revenue down 12% — hall closed early Thursday for maintenance" is a complete note.
5. Compare to same week last year if the data exists.

That's the whole routine. The value compounds over time. After three months, you'll have enough data to spot your actual seasonal rhythm, evaluate whether a rate change stuck, and make staffing decisions with evidence behind them rather than instinct.

CuePoint's revenue reports support date-range filtering and CSV export, so pulling consistent weekly snapshots takes under a minute. If you're currently tracking revenue in a logbook or pulling numbers from memory at month-end, the difference in visibility is significant — and worth reviewing how your current setup compares before another quarter passes.

What to Do When the Numbers Show a Problem

A revenue dip two weeks in a row is worth attention. Three weeks is a trend. The weekly review habit only pays off if you're willing to act on what the numbers show.

When table revenue falls without an obvious operational explanation, check utilization by time slot before assuming you need a price change. A pricing adjustment that makes busy hours cheaper will hurt you; the problem might be that your slow hours are dead and your peak hours are actually fine. Slot-level data — even if just mentally mapped from your session logs — tells you where the gap is.

When product revenue falls, it's almost always a staff behavior issue before it's a product issue. Check whether new staff members are prompting orders at session start. Check whether your displayed menu is visible from the tables. A clear staff permissions and accountability structure helps you investigate quickly without guessing.

The goal of weekly revenue comparison isn't to generate reports — it's to shorten the time between something going wrong and you knowing about it.

Practical Takeaway

Start this Monday. Pull your last seven days of revenue data, break it into table and product lines, and write down five numbers. Do the same next Monday and compare. You don't need sophisticated software to begin — you need consistency. Once you have four weeks of data in the same format, you'll have more business intelligence about your hall than most operators accumulate in a year of vague impressions. Build from there.