Dispute Documentation

Casino dispute documentation is the record that lets another qualified person reconstruct what was claimed, what evidence existed, what was reviewed, who had authority, and why the final decision was made. It can concern a table-game ruling, machine event, ticket, jackpot, cage transaction, marker, comp, exclusion, promotion, or service decision.

The purpose is not to create a long report for every disagreement. The purpose is to prevent a contested event from turning into a contest of memories after the table has reopened, the shift has changed, or the player has escalated the complaint.

Start by defining the disputed question

A weak record begins with a conclusion: “Player wrong; payout correct.” A useful record begins with the issue that needed to be decided.

Examples:

• “Player states the dealer failed to pay a winning side bet on hand 184.”
• “Guest states TITO ticket 74291 showed $380 but kiosk redeemed $80.”
• “Player disputes the amount deducted from promotional free play.”
• “Guest states a roulette wager was placed before the dealer called no more bets.”
• “Marker customer disputes the balance shown by the cage.”

The claim should be written neutrally. Recording the player’s version does not mean accepting it. It tells the reviewer what question the evidence has to answer.

Build a timeline before building an argument

Casino evidence is highly time-dependent. Surveillance, table records, transaction logs, machine events, player tracking, cage records, access-control logs, and staff memory are much easier to align when the time is precise.

Capture the best available timestamp immediately. If the exact second is not known, document the range and explain how it was derived.

A simple chronology might look like this:

The value of this table is not the format. It is the discipline of tying each statement to a time and a source.

Separate evidence from interpretation

A dispute file is stronger when it distinguishes three layers:

1. Observed or system-recorded facts — what a camera, meter, transaction log, ticket, or signed record shows.
2. Statements — what the player, dealer, cashier, security officer, or witness says happened.
3. Interpretation and decision — what the authorized reviewer concludes after applying the relevant rule or procedure.

These layers can disagree. A dealer can sincerely remember a chip in one position while video shows another. A machine screen can display a message that the transaction log later explains differently. Surveillance can be unable to see the exact denomination even though the camera shows the placement area.

Do not convert uncertainty into certainty just to make the report look decisive.

Evidence should be identified precisely

“Surveillance checked” is not enough. The useful question is what was reviewed and what did it establish?

Depending on the dispute, supporting material can include:

• surveillance camera numbers or review reference;
• table number, game, shoe, hand number, spin, or round identifier;
• dealer and supervisor names or employee IDs;
• player rating or account record;
• machine asset number and game/version information;
• event, meter, jackpot, or voucher logs;
• ticket or TITO number;
• cage transaction number;
• marker or credit documentation;
• promotional terms in force at the time;
• point-of-sale checks, comp authorization, or room folio;
• incident, security, or exclusion records;
• screenshots supplied by the customer;
• emails or recorded service contacts when those are part of the approved record system.

A good record does not dump every available document into a file. It identifies the evidence relevant to the disputed question and preserves what may be needed later.

Surveillance is evidence with limits

Surveillance can be powerful because it captures sequence and behavior independently of later memory. It is not omniscient.

A report should state what the footage actually supports. “Video confirms the player placed a red chip on the line between 17 and 20” is specific. “Surveillance confirms casino procedure” may be too broad if the camera cannot see the chip value, the verbal exchange, or a system transaction.

Useful wording includes:

• “Camera 214 shows placement before the dealer’s hand signal.”
• “Chip denomination cannot be confirmed from available angle.”
• “Audio is not available.”
• “The relevant screen is obstructed for approximately six seconds.”
• “No footage exists because retention period had expired before the complaint was received.”

An inconclusive review is still a result. Pretending that missing evidence proves the casino’s position creates a weaker file.

For the review process itself, see Surveillance Incident Review.

System records need context, not blind trust

Casinos generate large amounts of machine and transaction data, but a number on a report is only useful if the reviewer knows what it represents.

A slot dispute may require distinguishing credit meter, cashable credits, promotional credits, jackpot events, ticket issuance, ticket redemption, cancelled credits, and wallet transfers. A table dispute may involve ratings or electronic game history that record some parts of the event but not every physical action.

Before relying on a log, document:

• system name;
• record or transaction identifier;
• timestamp and time zone if relevant;
• field being relied on;
• who obtained or interpreted the record;
• known limitations;
• whether the record was exported, printed, or preserved.

The objective is reproducibility. Another reviewer should be able to find the same source and understand the same field.

Record the rule that was applied

Disputes are decided by facts and rules. The file should identify the controlling rule or procedure when one exists.

That might be:

• the posted table rule;
• approved game rules;
• house procedure;
• promotion terms;
• ticket or voucher rules;
• credit agreement;
• internal control requirement;
• regulator instruction;
• customer-account terms.

Do not invent a rule after the event to justify the desired outcome. If staff discover that the procedure was ambiguous, document the ambiguity and escalate it. A dispute can reveal a training or policy problem even when the immediate customer decision is correct.

Authority matters as much as the conclusion

The person writing the first note may not have authority to make the final ruling.

A clean record shows the escalation path:

Initial handler → supervisor → department manager → surveillance/compliance review → senior authority or regulator path

Not every dispute requires every level. The important point is that the value, subject, or regulatory significance of the dispute determines who can close it.

For example, a small obvious table correction may be resolved by floor supervision. A disputed jackpot, large marker balance, allegation of cheating, or issue involving self-exclusion can require completely different authority and documentation.

Read Complaint Handling and Escalation for the broader escalation structure.

The decision record should answer seven questions

A manager reviewing the case later should be able to answer:

1. What exactly did the customer dispute?
2. When and where did it happen?
3. Who was involved?
4. What evidence was reviewed?
5. What did that evidence prove, fail to prove, or contradict?
6. Which rule or authority controlled the decision?
7. What was communicated and what follow-up remains?

If any of those questions is missing, the file may be operationally incomplete even if the decision itself was correct.

Example: disputed TITO redemption

A player presents a kiosk receipt and says a $380 ticket paid only $80.

A poor note says: “Checked system. Ticket was $80. Customer informed.”

A stronger record identifies the ticket number, issue time, machine asset, original ticket amount, kiosk transaction, redemption time, and whether any other ticket was printed around the same period. It records the customer’s claimed $380 amount, checks relevant surveillance if necessary, and identifies the supervisor who approved the final response.

The investigation may find that the customer confused two tickets. It may find a printer or scanner issue. It may find a system discrepancy requiring technical escalation. Documentation should make each possibility testable rather than choosing one because it sounds likely.

Example: disputed roulette placement

A player says a $100 chip was on a winning split. The dealer says the chip was on a straight-up number.

The record should preserve the spin time, table, winning number, dealer, floor supervisor, disputed amount, and exact claimed chip position. Surveillance may resolve the geometry even if chip denomination is unclear. Table inventory or buy-in history may help identify whether a $100 chip was in play, but that is supporting context rather than proof of exact placement.

If the video is inconclusive, the report should say so. The final decision may still be made under house procedure and authorized discretion, but the evidence and the decision should remain distinct.

Documentation protects staff as well as customers

Neutral records are not anti-player or anti-employee. They protect both.

If the casino made an error, the file supports correction, refund, training, or control improvement. If staff followed procedure, the evidence protects them from an unsupported allegation. If a recurring dispute appears across shifts, management can identify whether the real problem is a confusing sign, ambiguous rule, equipment issue, or inconsistent training.

This is why dispute data should be reviewed in aggregate rather than filed and forgotten.

Useful operational measures include:

Documentation Completion Rate = Fully Documented Disputes / Total Disputes

Repeat-Issue Rate = Disputes Sharing the Same Root Issue / Total Disputes

Median Resolution Time = Median time from recorded complaint to final response

Evidence-Supported Decision Rate = Decisions with identified supporting records / Total decisions

These measures should improve control, not create incentives to reject complaints quickly just to make a dashboard look better.

Common ways a dispute file becomes unreliable

Writing the conclusion first. Staff then unconsciously select facts that support it.

Using emotional labels. “Aggressive,” “dishonest,” or “confused” should not replace observable behavior and evidence.

Failing to record the customer’s claim. A later reviewer cannot tell whether the casino actually answered the complaint.

Vague surveillance references. “Camera reviewed” does not show what was visible.

Mixing service recovery with the ruling. A goodwill meal can be appropriate even when the casino’s technical decision stands. Record the two decisions separately.

Editing the history without preserving the audit trail. Corrections should be attributable, especially in regulated or security-sensitive systems.

Keeping the real explanation in private messages. Material evidence and approvals belong in the authorized record system.

A regulator example of why records matter

The UK Gambling Commission’s guidance on complaints and disputes records illustrates the principle that licensed operators may have specific recordkeeping obligations around complaints. Its current complaint framework also distinguishes an operator’s internal process from later independent dispute resolution.

A player in Great Britain who remains dissatisfied after the operator process may, in qualifying circumstances, proceed to an approved alternative dispute resolution provider. Other jurisdictions use different procedures, deadlines, regulators, and appeal routes.

The operational lesson is broader than any single jurisdiction: a dispute that may leave the property needs a record strong enough to survive independent review.

Questions managers should ask before closing the file

Did we document the player’s version fairly?

The record should describe the claim in terms the customer would recognize, even when the casino rejects it.

Did we preserve evidence before it could disappear?

Video retention, temporary logs, tickets, and staff availability can all be time-sensitive.

Did the evidence actually support the wording in the decision?

Do not say “confirmed” when the evidence only “did not contradict.” Precision matters.

Was the decision made at the correct authority level?

A technically sound decision can still be a control failure if an employee exceeded approval authority.

Does this dispute reveal a larger problem?

Repeated complaints about the same rule, machine message, promotion term, or procedure should trigger root-cause review.

A dispute is finished when the record can survive tomorrow

The operational test is not whether the customer walked away or whether the table resumed play. The test is whether tomorrow’s manager, compliance officer, regulator, or auditor can understand the dispute without relying on the memory of the person who handled it.

Good dispute documentation is factual, proportionate, time-anchored, evidence-based, and explicit about uncertainty. It records both the customer’s allegation and the casino’s reasoning. That is what turns a tense moment into a reviewable business record.

Continue with Incident Reporting, What Casinos Must Document, and Dispute Resolution at the Table for the connected procedures.