How to Prevent Staff Theft in Billiard Halls

This is a sensitive topic, but it needs to be addressed directly. Billiard halls are cash-heavy businesses with multiple transaction points — table time, food, drinks, rentals. The more manual the process, the more opportunity exists for revenue to go unrecorded.

The goal isn't to create a culture of suspicion. It's to build systems that remove the opportunity for theft entirely, so you never have to question your staff and they never have to defend themselves.

Common theft vectors

Unrecorded sessions: A table runs for 2 hours. The staff member collects cash from the customer but never logs the session. The money goes in their pocket, and the system shows the table was idle. With no system-enforced tracking, there's no evidence it happened.

Underreported time: A table runs for 2 hours and 15 minutes but gets billed for 2 hours. The staff member collects the full amount but records the shorter time. The difference is small per session but adds up fast.

Pocketing product sales: A customer buys a beer. The staff member hands it over and takes the cash but never rings it up. With no system deducting inventory on sale, there's no way to trace what happened.

Buddy discounts: Friends and family get discounted rates or free sessions that the owner never authorized. No system enforcing rates means staff can charge whatever they want.

System-level prevention

The most effective prevention is automatic tracking. When every session must be started through the system, every product sale deducts from inventory, and every checkout is recorded, it becomes very difficult to operate off-book.

• Every table session is system-tracked with automatic timing — no unrecorded sessions
• Every checkout generates a receipt and a transaction record — no undocumented cash
• Product sales deduct from inventory — discrepancies between stock and sales become visible
• Revenue reports are generated by the system, not by staff — the numbers can't be edited

Role-based access

Not everyone needs the same permissions. A well-structured access model looks like:

• Cashier: Start sessions, add orders, checkout. Cannot edit rates, void transactions, or view revenue reports.
• Manager: Everything a cashier can do, plus void transactions (with a record), view reports, and manage reservations.
• Owner: Full access — rate configuration, staff management, all reports, all data.

When a cashier physically cannot change a rate, the rate is always correct. When voids require manager approval, they get scrutinized.

Daily reconciliation

Compare the system's revenue report against actual cash and payments collected. Do this daily, not weekly. The longer you wait, the harder it is to trace discrepancies.

The comparison is simple: the system says you earned X today. Count the cash and card receipts. If they match, you're clean. If they don't, investigate while the trail is still fresh.

Culture, not cameras

Systems remove opportunity. Culture removes intent. Pay your staff fairly. Acknowledge good work. Make the system the accountability layer — not surveillance, not interrogation.

When staff know that every transaction is automatically recorded and revenue is system-reported, the environment shifts from "can I get away with it?" to "the system handles it." That's where you want to be.

CuePoint's role-based access and automatic session tracking make it harder for revenue to go unrecorded — by design, not by suspicion.