Baccarat
Baccarat has its own module because the game is watched differently from other table games: players follow trends, and the floor watches the tables and the trends together.
The views
| Statistics | Table performance at a glance |
| Table Status | The live surveillance board |
| Trends and Roads | Live and historical trend roads |
| Baccarat Settings | Alert thresholds and data options |
Trends are the module's reason for existing
Baccarat players track outcomes on roads — the traditional grids that record how a shoe has run. The module presents the same roads your floor uses:
| Road | Records |
|---|---|
| Bead Road | Every outcome in order |
| Big Road | Outcomes grouped into streaks |
| Big Eye Road | Whether the Big Road is behaving regularly |
Alongside them, the module tracks the outcomes that matter to the game — banker and player wins, ties, naturals, pairs — and the commissions arising.
Live and historical
The same roads serve two purposes. Live, they are what a floor watches. Historically, they are how a shoe or a session is reviewed after the fact.
The distinction matters for where you put them: the live board belongs on a screen somebody is watching, historical trends belong in an investigation.
Alert thresholds
The module can raise alerts on configured thresholds, so a table behaving unusually reaches somebody without being watched continuously. See Baccarat Settings.
What is recorded
Interacting with the table status board is audited.
Queries, exports and camera viewing are audited as elsewhere. See the Audit Catalog.
Audit record
What eConnect writes to the audit trail for the actions on this page.
BACCARAT TABLE STATUS {label}