Manual time tracking fails in predictable ways: late start entries, rounded-down endings, “they’re regulars,” and arguments at the counter. Automatic session billing is not about distrusting staff. It is about removing the argument.
Table time is your primary inventory. When the clock lives in a notebook, every busy night becomes a negotiation. A snooker POS system that starts sessions on the table turns closing into confirmation instead of reconstruction.
Owners often underestimate the leak because each incident looks small. Five minutes here, a friendly round-down there, a forgotten restart after a table move — none of them feel like a crisis. Together they explain why a packed room can still produce thin table revenue. Session billing makes the clock boring again, which is exactly what you want.
Where the minutes go
- Start time written 8–12 minutes after the first frame.
- End time rounded to the nearest 15 minutes in the guest’s favor — every time.
- Table switches that never update the ticket.
- Paused games that stay paused on paper but not on the floor.
- “We’ll settle later” sessions that close after the group has already left.
None of these need bad intent. They need a rush, a full room, and a system that depends on memory. The leak shows up as a busy club with thin table revenue.
A walk-through of a typical leaky night
Table 3 starts while the cashier is taking a food order. Someone says “start them,” but the notebook gets the time ten minutes later. At 9:40 the group moves to Table 7 because a light flickers; the notebook still says Table 3. Closing becomes a reconstruction: “How long were you on the first table?” Guests give a low number. Staff, tired of arguing, accept it. The club donated time twice — at the start and at the move — without anyone deciding to be generous.
What good session billing looks like
Tap to start, visible elapsed time, rate that matches peak or off-peak, and a bill that can take food without resetting the clock. Guests should be able to see they are not being guessed at.
- Session starts when play starts — not when someone finds a pen.
- Elapsed time is visible to staff (and ideally explainable to guests).
- Rate cards live in software, including peak windows.
- Table moves keep the same open session history.
- Checkout merges time and F&B on one ticket.
Ten unbilled minutes on eight tables, four nights a week, is a staff salary you are lighting on fire.
Visibility matters as much as automation. When staff can glance at elapsed time, they stop guessing. When guests can understand the charge on a receipt, disputes shrink. Opaque totals invite negotiation; clear time lines invite payment.
Peak rates without staff improvisation
If peak pricing lives only on a wall chart, it will be “forgotten” when the room is loud. Session billing should apply the correct rate as the clock runs. That protects yield and keeps the conversation about the rate card, not about who the guest knows.
Connect this to your pricing strategy. Software enforces the card; the card should already make sense for idle hours and Friday nights.
Rate changes mid-session
Ask how the product handles a session that starts in off-peak and crosses into peak. Some clubs want a clean switch at the boundary; others prefer the start-rate for the whole visit. Either policy can work — inconsistency cannot. Put the rule in software so cashiers are not inventing fairness in real time.
- Define peak windows once, not as nightly verbal reminders.
- Decide mid-session boundary behavior before go-live.
- Limit who can override rates, and log every override.
- Print or show the applied rate so guests are not surprised at close.
Food tickets and the open clock
A common failure mode is two systems: a timer and a cafe till. Staff stop one, start the other, and lose either minutes or a drink line. Combined billing is why club POS matters. See POS for pool halls for the checkout side of the same problem.
The open clock should be boring while the kitchen is busy. Adding a round of drinks must not pause play, reset elapsed time, or force a new ticket. If it does, staff will batch orders poorly or skip entering items until the end — which recreates forgotten lines.
Attach rate is a useful health check after you switch. If table hours rise but F&B stays flat, staff may be closing time cleanly while still missing kitchen items. If both rise, the single-ticket workflow is doing its job.
Pauses, moves, and other edge cases
Real floors are messy. A player steps out for a call. A cloth needs a quick brush. Two friends consolidate onto one table. Session billing has to support those moments without turning into a loophole factory.
- Pauses: who can pause, for how long, and is it logged?
- Moves: elapsed time follows the group, not the furniture.
- Merges: two open sessions combining should not double-count or wipe history.
- Grace minutes: if you offer a short courtesy window, encode it — do not leave it to mood.
Encode policy once. Mood-based courtesy feels kind in the moment and unfair by the end of the month. Regulars notice who gets “a free ten minutes” and who does not.
Staff roles and disputed bills
When a guest disputes time, you need a log — not a debate. Who started the session, whether a rate was overridden, and whether a void happened should be reviewable. Pair billing with clear staff permissions so cashiers cannot silently rewrite history.
Train a dispute script. “The session started at 7:12 when you sat; here’s the elapsed time; food is listed separately.” Most disputes end when the timeline is visible. The ones that do not end that way need a manager with authority to adjust — and a reason code so Monday’s review can teach something.
Buyer criteria for session billing
Do not buy a stopwatch app and a separate till and hope staff will reconcile them forever. Buy a billing path that starts on the table and ends on one ticket. That is the same principle behind broader club management software: one operating picture beats five clever tools.
- Can staff start a session in under three taps from the floor view?
- Does a table move preserve elapsed time without a void?
- Are peak rates applied without asking a senior staff member?
- Can food attach to the open session without stopping the clock?
- Is every adjustment attributable to a user?
If any answer depends on “we train people carefully,” assume training will fail on the third busy Saturday. Design beats reminders.
How to switch without chaos
Train the floor lead on a quiet afternoon. Practice start, table move, add food, split, and close. Run one supervised peak night, then retire the notebook. Tell regulars the bill will now match the clock — most prefer clarity to informal discounts that feel uneven.
- Map every rate and pack you actually use — including verbal habits.
- Decide pause and mid-peak rules before the first live session.
- Train two people to close disputed bills using the log, not memory.
- Keep the notebook as backup for one quiet night only.
- After a supervised peak night, remove the notebook from the counter.
After two weeks, compare table revenue and void patterns to the prior month. You are looking for fewer arguments and fewer “forgotten” minutes, not a miracle overnight spike. If voids spike, you may have set permissions too tight or rates too confusing — fix the policy, do not sneak back to paper.
Session billing succeeds when the clock becomes unremarkable. Guests stop negotiating time. Staff stop reconstructing nights. Owners stop wondering why a full house felt unprofitable. That quiet is the product working.