Dealer Casebook: Post-Relief Discrepancy

You have already been relieved from the table, or you are the outgoing dealer finishing your shift, when the floor calls you back.

A rack shortage, fill/credit mismatch, cash problem, rating issue, marker/transaction discrepancy, or other control problem has been discovered. The current record points toward a transaction that happened before you left.

The first question may sound like an accusation:

“What did you do with this transaction?”

The professional challenge is to reconstruct the event without turning uncertainty into blame or memory into evidence that is stronger than it really is.

Do not treat being called back as proof of fault

A discrepancy appearing after your relief does not automatically mean you caused it.

Likewise, the fact that you handled an earlier transaction does not mean that transaction is irrelevant.

Hold both ideas at once: your earlier action may need review, but responsibility has not been established merely because the timeline points backward.

Start with the current known facts

Ask what discrepancy has actually been found.

Is the rack short? Is a fill slip missing? Does a credit amount disagree with the rack? Is there an unexplained cash movement? Is a player transaction recorded differently from what the table state suggests?

Do not begin by defending yourself against a vague statement such as “your table is wrong.”

A precise problem is easier to reconstruct.

Separate the present state from the earlier transaction

There are at least two time points:

1. the state when you completed or handed over the earlier transaction;
2. the state when the discrepancy was later discovered.

Value or records may have moved between those points.

A good review asks what changed at each stage rather than assuming the earlier transaction must explain the final difference.

Give memory the correct weight

If you clearly remember the event, describe it.

If you partly remember it, say which part is clear and which is uncertain.

If you do not remember it, say so.

Do not create a confident story because you feel pressure to provide an answer.

For example:

“I remember receiving the fill and counting the chips with the floor. I do not remember the exact denomination breakdown without seeing the record.”

That is useful and honest.

Use records to test memory, not replace it

A slip, table inventory record, handover note, rating record, or other controlled document may refresh the sequence.

But do not alter your statement simply to match the paperwork if you remember something different.

Say:

“The slip shows 20,000. My memory is that the transaction was 15,000, but I am not certain. I would like the sequence reviewed.”

A discrepancy between memory and record is itself a fact to preserve.

Do not accuse the incoming dealer

The outgoing dealer may think:

“The rack was fine when I left, so the relief dealer caused it.”

That conclusion may be wrong.

The incoming dealer may have inherited an already-incorrect state, a delayed record, an unclosed transaction, or another issue not visible at relief.

Focus on what was counted, stated, signed, or handed over.

Do not accept blame simply to end the discussion

Fatigue, hierarchy, and end-of-shift pressure can make someone say:

“Fine, it must have been me.”

Do not make a false admission because you want to leave.

State the facts you know. If you made an error and recognise it, say so accurately. If you do not know, say that the cause is not yet established.

Reconstruct the earlier transaction step by step

For a fill, credit, buy-in, colour-up, cash exchange, marker, or similar event, useful questions include:

• what was requested;
• what amount was announced;
• what was counted;
• what physically moved;
• who witnessed or approved the movement;
• what document was used;
• whether you signed or initialled anything;
• whether the transaction was complete before relief;
• what you told the incoming dealer.

The goal is not to produce the “right” story. It is to make the sequence reviewable.

Review the relief handover itself

Did you and the incoming dealer count or verify the rack according to the property’s procedure? Was a transaction still open? Did you mention a pending fill, credit, marker, payout correction, or cash issue?

A weak handover can allow an earlier uncertainty to travel into the next shift.

Giving and Receiving Relief at the Table explains why unresolved items need explicit transfer, not assumptions.

Do not silently change earlier records

If the review reveals that a previous entry is wrong, do not backdate, erase, rewrite, or replace it privately.

Use the authorised correction process so the original and the later correction remain understandable.

This connects directly with Asked to Backdate a Table Record.

Keep the current table state protected during review

Even though the suspected cause may be historical, the current table is live.

Do not let the investigation trigger uncontrolled chip/cash movements designed to “test” a theory. Do not change the rack to see if the numbers then balance. Do not recreate a transaction using current value unless explicitly authorised and documented.

Preserve the present state while reconstructing the past.

If Surveillance is involved, do not speculate about what it can prove

You may be told that Surveillance is reviewing the incident.

Do not say:

“The cameras will show everything.”

or:

“That area is not covered.”

Those statements may be wrong and can disclose or invent sensitive operational assumptions.

Provide your facts and let Surveillance communicate through its authorised channels.

If another employee remembers the event differently

Do not turn the reconstruction into a debate at the table.

Two people can honestly remember a busy transaction differently.

Each person should state what they personally observed. The authorised reviewer can compare statements, records, counts, and other evidence.

Distinguish error from intent

Even if the review confirms that the earlier transaction was wrong, that does not automatically establish deliberate misconduct.

A miscount, wrong denomination, incomplete record, communication failure, rushed handover, or procedural error can all create discrepancies.

Do not jump from “the transaction was wrong” to “someone stole” or “someone cheated” without evidence.

Document the timeline

A useful statement might say:

“At approximately 22:20 I completed a credit at Table 4. I recall the chips being counted with the floor and removed from the rack. I was relieved at approximately 22:45. At 23:30 I was asked about a rack discrepancy. I did not make any further transaction after relief. I reviewed the credit slip with the floor and provided the details I remembered.”

That gives investigators a sequence without pretending to know the cause.

If you discover your own mistake

Own the specific fact.

For example:

“I now see that I entered the wrong denomination breakdown on the slip. The total chips removed were correct, but the record was wrong.”

or:

“I remember returning one stack to the rack after the count, and I did not mention that during handover.”

Accuracy matters more than defensiveness.

Then use the authorised correction/reporting process rather than trying to repair the history privately.

Relief does not end the reconstruction

A post-relief discrepancy is a reconstruction problem before it is a blame problem.

Protect the current state, separate records from memory, describe your earlier transaction precisely, avoid accusing the incoming dealer, and let the authorised process connect the timeline.

A discrepancy discovered after relief does not prove who caused it. Preserve the present state, reconstruct the earlier transaction factually, and use the authorised review process rather than blame or private correction.