Visual summary
Dealer Casebook: Unlisted Attachment After Review: three operating principles
Use this map as a quick orientation. The article explains the evidence, limits, and exceptions behind each point.
-
An authorised review does not make every unexplained addition automatically authorised.
-
Preserve the returned packet as received before removing, rearranging or writing on anything.
-
Distinguish the original controlled record from material added during or after review.
A controlled record leaves for authorised review and comes back with something that was not listed when it departed: an extra note, attachment, label, staple, printout, or other material. The addition may be completely legitimate, but its provenance is now part of the record story.
The mistake would be to file the packet as normal before determining whether the added material belongs there and who introduced it. The returned condition is evidence in its own right.
Hold the packet exactly as returned, identify the unexpected attachment, and verify when and under whose authority it became part of the record before normal processing resumes.
Preserve the returned packet before separating anything
When the returned packet contains an attachment, handwritten note, staple, label, or other addition that was not listed when it left, the first useful step is not to tidy the paperwork. Keep a controlled record returning from an authorised review function in the condition in which the discrepancy was discovered. Note who noticed it, where it was, and what was physically present. This protects the difference between the transaction state and the later discovery state, which can matter when the responsible role reconstructs the sequence.
Identify the unexpected attachment precisely
The open question is who added the material, when it was added, why it belongs with the record, and whether it is part of the authorised review trail. Say that precisely. Broad labels such as “paperwork problem” or “bad handover” hide the decision that actually needs to be made. A dealer should separate what is visible from what is inferred and avoid turning a missing explanation into a claim about who caused the problem.
Do not normalise the packet before provenance is known
The temptation is removing the addition as clutter or accepting it silently as though it had always been part of the packet. That may make the desk look cleaner while making the evidence worse. Do not add, remove, swap, rewrite, staple, un-staple, or refile controlled material simply to make the paperwork appear normal. A cosmetically complete packet can be less trustworthy than an openly incomplete one.
Keep the attachment linked to the record it arrived with
Keep the identifying features of a controlled record returning from an authorised review function visible: form or sequence number, table, shift, transaction reference, amount, role fields, and any marks that distinguish one version from another. If something is unclear, describe it as unclear. Do not invent a missing identifier from memory or from what “must have” happened.
Check whether the addition changes the transaction story
The added material may change nothing about the underlying transaction, or it may contain information that affects the review. Establish that separately. First confirm what the attachment is and why it is present; then determine whether it changes any value, approval, exception or filing decision. A packet-content change is not automatically a transaction error.
Ask reviewers only about material they handled
Ask the person who released the packet what was listed at departure, and ask the reviewer or receiving department what they added or returned. A later handler should not certify what happened inside a review they did not witness. The aim is to identify the attachment’s entry point, not to collect broad statements that everyone “saw the same packet.”
Route provenance questions back through the review path
An unlisted attachment should be reconciled through the department or role that controlled the review. The table team should not decide on appearance alone that the note is official, irrelevant or improper. Return the provenance question to the authorised review path while preserving the packet exactly as received.
Compare the outgoing inventory with the returned contents
Compare a controlled record returning from an authorised review function with independent records that legitimately exist: transaction logs, issue records, packet inventories, table identifiers, shift records, or system references. Use them to test the reconstruction. Do not alter the questioned document first and then use the altered version as evidence that everything agrees. Compare this with the Casebook on an unexplained handwritten amendment after handover when the added material changes an existing record rather than simply expanding the packet.
Do not add a retroactive approval mark
If the attachment lacks an expected approval or identification, do not ask somebody to sign it now as though the approval existed when it was inserted. Any current clarification should be dated and described as a current action, preserving the distinction between original review material and later explanation.
Protect any new sensitive information in the attachment
An unexpected attachment can introduce new player, employee, account or investigative information that was not part of the original packet. Treat the added material at least as carefully as the controlled record itself and avoid informal copying while its status is being established.
Record how the packet changed during review
Record the outgoing packet inventory if known, the material found on return, where it was attached or placed, who received the returned packet, which review role was contacted, and whether the attachment was accepted, removed, reclassified or separately controlled under procedure. The change in packet contents should remain reconstructable.
Hand over the packet as returned-with-unlisted-material
If the issue remains open at relief or close, carry it forward explicitly. The handover should identify a controlled record returning from an authorised review function, the unresolved question, current custody, and any action already taken. “Supervisor aware” is not enough if the next shift cannot tell what is missing, conflicting, extra, or still under review. The same handover discipline appears in this related custody case, where the next team needs the unresolved state, not a cleaned-up summary.
Do not remove the attachment merely to restore the old count
Do not simply remove the extra material and restore the old packet count. If the attachment is not supposed to remain, its removal should still be authorised and traceable. Otherwise the record may later show that something appeared and disappeared with no explanation.
Explain the delay as a provenance check
Explain that the transaction record has returned from review with material that is being verified before processing continues. Do not disclose the attachment’s contents unless the role and procedure allow it. The service response is to escalate the verification, not to display internal review material.
Reconcile outgoing contents against returned contents
Secure the returned packet, compare it with the outgoing inventory or custody note, describe the added material, identify the review path it travelled through, ask the authorised reviewer about provenance, determine whether the addition affects the underlying transaction, and document the final filing decision. This keeps the attachment from becoming an invisible change to the record.
Resolution identifies whether the addition is authorised record material
The packet can return to normal custody when staff can explain what the attachment is, who added or authorised it, whether it belongs with the controlled record, and whether it changes any decision or value. If provenance cannot be established, the unresolved status should remain explicit rather than being filed away.
Do not call the attachment improper before provenance is checked
Do not claim that who added the material, when it was added, why it belongs with the record, and whether it is part of the authorised review trail has been proved unless the authorised review actually establishes it. Do not label the event theft, tampering, falsification, negligence, or misconduct from the paperwork alone. Record integrity improves when observation, inference, decision, and allegation remain separate.
Verify the addition before the packet re-enters normal filing
In this case, the safest operational judgement is to preserve the returned packet exactly as received, identify the unexpected addition, and verify its provenance before refiling or processing. That approach protects both the employee and the casino because it preserves evidence, keeps authority visible, and allows the responsible role to resolve the actual uncertainty rather than a version that has already been cleaned up.
Evidence record
Sources and verification
Each citation identifies the publisher, source date when stated, our access date, and the point the source was used to verify.
-
Gambling Dealers (opens the publisher’s website in a new tab)
Evidence used: Used for the dealer work context of exchanging chips or money, recording activity accurately, communicating with supervisors, and following established rules and procedures.
-
First-Line Supervisors of Gambling Services Workers (opens the publisher’s website in a new tab)
Evidence used: Used for the broad supervisory context of monitoring gaming operations, coordinating staff, resolving operational problems, and enforcing procedures. It does not define one property's exact authority chain.
-
Minimum Internal Control Standards (opens the publisher’s website in a new tab)
Evidence used: Used only as a jurisdiction-specific example that table-game value movements and related documentation may be subject to formal controls, records and custody. Nevada requirements are not presented as universal casino procedure.