Dealer Casebook: Power or Network Outage at a Live Table

The roulette display goes dark.

Then the overhead lights dip.

At another table, the electronic side-bet screen freezes. A cashless or rating terminal stops responding. The shuffler shows an error. The pit phone may still work, or it may not.

Players immediately ask:

“Does the bet count?”

“Can you just keep dealing?”

“Use your phone and calculate it.”

A power, lighting, or network outage can look like one problem, but it may actually create several different ones at once: safety, visibility, game-state, device-status, transaction, communication, and evidence questions.

The dealer’s job is not to repair the infrastructure.

The professional question is: what can safely remain under control at the table, what must stop, and who is authorised to decide how the game recovers?

First decide whether the area is safe to remain in

Not every outage requires evacuation, but every outage changes the working environment.

Lighting may be reduced. Electronic equipment may power down or restart. Access routes may be less clear. Other departments may issue instructions.

If the property directs staff or guests to leave the area, follow that instruction.

If the area remains open, work only within the conditions the property has authorised.

Do not treat “the emergency lights are on” as proof that normal game conditions exist.

Safety comes before continuity.

Stop creating new action

If the table can no longer operate normally, do not keep accepting fresh bets simply because players want the game to continue.

A useful statement is:

“The game is on hold while the outage is checked. Please leave the current wagers and cards as they are.”

This is especially important when the failure affects:

• result displays;
• electronic side bets;
• cashless or player-rating functions;
• automatic shufflers;
• card readers;
• progressive or linked systems;
• communications needed for authorisation;
• lighting sufficient to verify wagers and payouts.

The goal is to prevent an infrastructure failure from creating a second layer of preventable disputes.

Preserve the real table state, not the state you wish you had

Suppose the outage happens after betting closes but before a result is settled.

Do not clear the layout because you assume the hand will be void.

Do not pay because you assume the visible result is final.

Do not gather cards into the discard rack because you want a clean restart.

Keep the state identifiable where it is safe and practical.

That may mean leaving wagers in place, keeping cards separated, noting the point in the sequence, and calling the floor.

Dealer Casebook: Shuffler or equipment fault during a live hand covers the related principle that a device problem and a game ruling are two different questions.

A failed screen is not automatically the ruling

Players often trust a display because it normally reflects the game.

During an outage, a display may freeze, blank, restart, or show incomplete information.

Do not say:

“The screen says zero, so the side bet lost.”

Or:

“It came back showing a win, so we have to pay it.”

The authorised recovery may depend on the physical game state, system records, a supervisor ruling, technical confirmation, or a combination of evidence.

The dealer should preserve observations and wait for the approved decision path.

Do not improvise a technical reset

A dealer who knows how to unplug, reboot, bypass, or reset something can be tempted to “help.”

Do not improvise.

Do not:

• disconnect equipment unless the procedure specifically instructs you to do so;
• cycle power because a player suggests it;
• enter service menus outside your authority;
• borrow another table’s device to create an unofficial workaround;
• reconnect network cables or access panels to diagnose the fault;
• try repeated resets that could overwrite useful state.

The outage may need IT, slots/electronic-table support, engineering, the vendor, or another authorised function.

Your table control should not become technical experimentation.

Do not use personal devices as substitute casino systems

A player may say:

“Just use your phone calculator.”

Another employee may offer a personal hotspot.

That can create privacy, recordkeeping, accuracy, and control problems.

Do not move casino data, player information, transaction details, or internal system access onto a personal device unless the property explicitly provides an authorised method.

A calculator may be harmless in some contexts, but it cannot recreate a missing approval, system record, progressive state, or controlled transaction.

The correct question is not “Can I make this work somehow?”

It is “What recovery method is authorised for this specific function?”

Keep chip and cash custody visible

An outage attracts attention.

Players stand up. Supervisors move between tables. Staff may carry flashlights or radios. Normal sightlines change.

That makes basic custody discipline more important, not less.

Where conditions are safe:

• keep the rack under normal control;
• avoid unnecessary chip movement;
• do not start ad-hoc colour-ups;
• do not combine disputed stacks;
• keep pending cash/chip transactions identifiable;
• ask for relief or supervisor support if you cannot safely watch both the table and the surrounding disruption.

Do not create a private “temporary” storage method that nobody else understands.

Network failure can create invisible transaction uncertainty

The lights may be on while the network is down.

That can be more deceptive because the table looks normal.

A transaction might appear submitted but not confirmed. A player rating may not update. An electronic wager may be pending. A cashless balance may not display correctly.

Do not tell the player:

“It definitely went through.”

unless you have the authorised confirmation used by your property.

Likewise, do not repeat a transaction simply because the first attempt is not visible if doing so could create a duplicate.

Escalate the uncertain state.

Separate floor observation from system evidence

The dealer can report what happened at the table:

“The player placed the wager before betting closed. The display froze after the cards were dealt. I did not settle the wager.”

That is useful.

What the dealer should not do is claim knowledge of system logs, server state, Surveillance recording, network failover, or data recovery.

Those may be reviewed by other authorised functions.

Do not promise what will be found.

Do not discuss system architecture, backup coverage, camera operation, or recovery vulnerabilities with players.

Communication failures need a clear authority path

Sometimes the normal phone, terminal, or messaging method is part of the outage.

Use the alternative communication channel the property has designated.

That may be a radio, runner, supervisor route, or emergency communication plan.

Do not invent a chain of command because the usual device is unavailable.

If you cannot obtain an authorised ruling, keep the game on hold rather than deciding that silence gives the dealer permission to improvise.

When service returns, do not restart automatically

A screen lighting up is not the same as operational recovery.

Before reopening, the property may need to confirm:

• safe lighting and environment;
• equipment status;
• network connectivity;
• pending transactions;
• game-state recovery;
• rack or inventory status;
• system timestamps;
• progressive or side-bet status;
• which supervisor owns unresolved disputes.

Wait for the authorised release.

A rushed restart can overwrite evidence or create a second version of the same transaction.

Resolve the interrupted hand through the approved process

Players will want a fast answer.

The dealer should not create a universal rule such as:

“Every hand during a power cut is void.”

or:

“If the cards were out, the result always stands.”

Games, systems, jurisdictions, and house procedures differ.

The clean statement is:

“The hand was interrupted at this point. The floor is applying the property’s recovery procedure.”

That protects the player and the operation from an invented rule.

Relief during an outage must inherit the uncertainty

If a relief dealer arrives while systems are still down, do not perform a normal handover that pretends the table is clean.

State the unresolved points clearly:

• whether betting is closed;
• whether a hand is live;
• what wagers remain unsettled;
• whether a cash/chip transaction is pending;
• which device or function failed;
• who has been called;
• whether reopening has been authorised.

Managing shift handover explains why open issues need explicit ownership rather than a vague “the system is down” comment.

The post-outage report should be factual and non-technical

If documentation is required, record what you observed and what you did.

For example:

“At approximately 02:07 the table display and rating terminal lost service during an active hand. I stopped further betting, left the existing wagers in place, and called the floor. I did not reset the equipment. Play resumed only after the supervisor authorised recovery.”

Avoid unsupported statements such as:

“The server crashed because the backup network failed.”

unless that information comes from the authorised technical finding and belongs in your report.

The dealer’s strongest evidence is usually sequence, not diagnosis.

Outage mistakes that create false certainty

Do not:

• keep dealing when visibility or required systems are inadequate;
• invent a universal void/stand rule for interrupted games;
• use a frozen or restarted display as automatic proof of a result;
• improvise resets, repairs, service-menu access, or cabling changes;
• bypass required approvals because the normal system is unavailable;
• put casino or player data onto a personal phone or hotspot without an authorised method;
• duplicate a transaction merely because confirmation is missing;
• promise what Surveillance, server logs, or backup systems recorded;
• restart the table merely because power or connectivity appears to have returned.

Hold the game until the next step is trustworthy

Outages create pressure because everyone wants normality back immediately.

A strong dealer resists that pressure.

The disciplined response is to stop fresh ambiguity, protect the table where safe, describe exactly what was observable, keep technical recovery with the authorised function, and reopen only when the property has restored the conditions needed for a controlled game.

Continuity is not the same as speed.

Sometimes the best continuity decision is to hold the game exactly where it is until the operation can trust the next step.