TableIQ — a module of PlayerIQ

Table games operations, built for how a card room actually runs.

Fills, credits, NOEs, drops, ratings and progressives — with a native Windows client in the pit, slips that print themselves to the right printer, and supervisor corrections that don’t need a support ticket.

Request a demo See TableIQ – Pit
18table games features
11WAC-compliant slip types
Livein multiple WA card rooms
SOC 2Type 1 certified
New — TableIQ – Pit

A real Windows application, not a browser tab.

Pit supervisors spend a whole shift in this. So we stopped making them work through a browser and built a native client that opens full-screen on the pit PC and stays there.

Built for a touch screen and a busy pit
  • Pit-wide rating grid. Every active rating across every table in the pit, on one screen, with a persistent side panel instead of a modal for the common path.
  • Dealer’s-eye seat view. One card per seat, laid out to mirror the physical table, with cash-in and cash-out totals in the header. Toggle between grid and table.
  • Full rating lifecycle. Open, edit, pause, resume, move, and close with cash-out capture and win/loss.
  • Driver’s license scan. Scan the barcode on the back of a license and the patron record is filled in for the operator to confirm.
  • On-screen keyboard. Large touch targets, and it never gets in the way of a physical keyboard.
  • Kiosk mode. Full screen, hard to exit by accident, and it re-authenticates without losing the station’s context.
Boring where it should be boring
  • One installer, no runtime. Self-contained single-file build — nothing to install on the PC first. Windows 10 or 11, 64-bit.
  • Signed. Authenticode-signed installer, so it doesn’t argue with your endpoint protection.
  • Zero business logic on the client. It calls the same PlayerIQ API the web app does. Permissions, multi-tenancy, auditing and the self-exclusion and barred-patron gates are all enforced server-side — the desktop app cannot route around them.
  • Every action attributed. It signs in as a real user, so who did what is recorded on the server, not assumed from the workstation.
  • Shows people only their job. The launcher is driven by permissions — a cashier sees fills and credits, a pit supervisor sees the rating screens.
  • Light and dark. Follows the operating system, or set it per station.
One deliberate limitation, stated plainly. TableIQ – Pit is online-only. If the network to the property drops, ratings are unavailable — exactly as they are in the browser today. We would rather say that than imply a resilience the product doesn’t have.
New — server-based printing

Slips print themselves, to the right printer, every time.

Printing used to happen in the browser: a slip was a web page, and someone had to be standing at the right screen for paper to come out. That model had four failure modes, and every card room knows all of them.

Nobody at the screen, nothing prints

An automatic comp only issued if that machine happened to be on, logged in, and sitting on the right page.

Every workstation configured separately

A new PC, a driver update, or somebody changing the default printer, and slips went to the wrong place — or nowhere.

No record of whether it printed

Jammed, out of paper, switched off — the slip was simply lost. Nothing recorded it and nobody was told.

Reprints looked like originals

A second copy was indistinguishable from the first. For a WAC-required document, that is a real problem.

How it works now

1

Something happens

A table closes, a fill is approved, a comp is issued.

2

The server builds the slip

PlayerIQ renders it server-side and puts it in a queue — no browser involved.

3

The Print Agent collects it

A small program on one PC at the property checks the queue every few seconds and sends the slip to the correct printer. Outbound HTTPS only — no inbound ports to open.

4

The result is written back

Printed, or failed and why. Visible in a Print Jobs screen your team and ours can both see.

What changes on the floor

  • Staff don’t choose the printer, and can’t choose wrongly. Routing is configured once in PlayerIQ — by table, by pit, by location, or a property default.
  • Nothing is silently lost. An offline printer holds the slip in the queue instead of it vanishing.
  • Reprints are stamped as reprints. Every formatter prints a reprint marker, so a second copy is never mistaken for the original.
  • No per-workstation setup. No driver installs on every PC in the building.
  • The forms match the paper you already use — including three-part white/yellow/pink routing where the rule calls for it.
  • One system, not two. The separate comp auto-print tool is retired and folded in.
Why this had to come first

A desktop application has no browser and no print dialog. Under the old model, a pit app simply could not print at all. Moving printing to the server isn’t a separate improvement that happened to land at the same time — it is the thing that made a modern pit client possible. Keeping printing in the browser would have meant keeping the browser.

Safe by design. Printing is enabled per property, off by default, so sites migrate one at a time. A printing problem can never roll back the fill, comp or drop that triggered it — and if routing isn’t configured or the agent is down, it falls back to the browser. No configuration mistake leaves an operator without paper.

Epson TM-T88V / TM-T88VI or compatible ESC/POS, 80mm, network or USB. Eleven slip types: fill request and supplied, credit request and supplied, cage receipt, player rating, reward receipt, drop, table inventory, NOE and soft count — each with a reprint variant.

Supervisor corrections

Fix a mistyped fill without calling your vendor.

Reversing a fill deleted by mistake, correcting a denomination on a mistyped credit, fixing an NOE — these are routine card room corrections. They should be handled by a shift manager or an accounting supervisor, not by a software vendor on a support ticket while the daily record sits wrong.

TableIQ never edits a record in place. A correction voids the original, preserves it, and creates a linked replacement — with a mandatory reason and supervisor authorisation. That is the same model the paper rule describes, which is exactly why it holds up under inspection.

What a supervisor can do

  • Void and reissue a fill or credit
  • Restore a record voided by accident
  • Amend details with a recorded reason
  • Review every correction on one page for accounting
The person authorising a correction must be a different user from the one who made it. Separation of duties is enforced by the software, not by policy.
Washington — WAC 230

Every feature cites the rule it satisfies.

TableIQ is deployed in Washington card rooms and built directly against WAC 230-15. Each screen names the regulation behind it, so your staff don’t have to memorise the rule book — the software carries it.

Table configuration

Game types, limits, positions, multi-site

230-15-345
Table open & close (NOEs)

Tray balance with sequential NOE numbers

230-15-495/535
Fill requests

Three step: request, cage process, pit confirm

230-15-515
Credit requests

The same three-step workflow as fills

230-15-520
Void & reissue corrections

Never edit in place. Full audit trail, reason required.

230-15-530(13)
Records in permanent form

Reason required on every correction

230-15-190
Separation of duties

Authoriser must differ from creator

230-15-435
Drop box management

Per table, per gaming day, by denomination

230-15-090
Progressive jackpots

Types, table assignment, balances, soft count

230-15-640/650
Business hours

Per site, with the 2am–6am restriction enforced

230-15-025
Player ratings

Buy-in, average bet, time, theo, win/loss per session

230-15
Self-exclusion

Full lifecycle, enforced server-side at every seat

230-23-030
Slip content & copy routing

Original, duplicate, triplicate; void rendering

230-15-520/535
Temp win reports

Hourly win/loss across 24 configurable slots

Gaming day rollover

Automatic nightly background job

Shift manager dashboard

Report sheet, hourly, comments, call-ins

WSGC product determination — July 2026

The Washington State Gambling Commission has determined that PlayerIQ does not meet the definition of gambling equipment, renewing the determination first issued in 2020. In practice that removes the regulatory approval barrier to deploying the software — a card room does not need equipment approval to run its floor on PlayerIQ.

WSGC PRODUCT DETERMINATION · JULY 2026 DEPLOYED IN WASHINGTON BUILT TO WAC 230-15 SOC 2 TYPE 1 MICROSOFT AZURE

The July 2026 determination concerns the regulatory classification of the software — that it is not gambling equipment. It is not an endorsement of the product, and it is not an approval of any particular operational workflow. Regulatory references above describe the requirements TableIQ is built to satisfy; they are not legal advice. Confirm your own obligations with the Commission and your counsel.

See TableIQ run a gaming day.

Thirty minutes, your table layout, your slips. We’ll show you a fill from request to printed cage copy, a correction with its audit trail, and the pit client on a touch screen.

Request a demo andrew@strategy9.com