Dealer Casebook: Received Mark, Custody Unconfirmed

A “received” mark appears to close a custody step, but the person or department that seems to be the recipient cannot confirm taking the record. The mark is evidence of something written or stamped on the document; it is not, by itself, proof of who physically accepted custody.

That distinction matters because staff can easily turn a mark into a story: “Cage received it,” “the floor signed for it,” or “Accounting must have had it.” None of those statements is safe unless the custody can actually be reconstructed.

Preserve the mark exactly as found, identify the last confirmed physical handoff, and treat the recipient as unconfirmed until the custody trail establishes otherwise.

Preserve the received mark before investigating it

When the role that appears to have received the record cannot confirm that it actually took custody, the first useful step is not to tidy the paperwork. Keep a controlled record bearing a received stamp, initials, tick, or similar mark 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.

Separate the mark from the claimed recipient

The open question is who made the mark, what the mark meant, and where the controlled record moved after that point. 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 let the stamp close an unproven handoff

The temptation is treating the presence of a mark as proof of physical custody that nobody can confirm. 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 document identity tied to the questioned mark

Keep the identifying features of a controlled record bearing a received stamp, initials, tick, or similar mark 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.

Reconcile custody separately from transaction value

An unconfirmed receipt affects custody integrity even when the underlying transaction balances. Conversely, a custody gap does not prove the value movement was wrong. Verify the transaction and reconstruct the document path as separate workstreams so a balanced amount does not prematurely close the handoff question.

Ask each person what they physically received

Ask the apparent sender what was handed over, and ask the apparent recipient what was actually received. If a third person applied the mark or moved the packet, record that separately. Do not ask one employee to confirm another person’s receipt simply because the mark sits beside that role field.

Escalate the custody gap without assigning a recipient

The custody question should go to the role that controls the relevant transfer path. A supervisor may know the normal routing, but normal routing is not proof that this document followed it. Escalate the specific gap—mark present, recipient unconfirmed—so the record owner can trace the handoff rather than ratify an assumption.

Compare logs, trays, packets and transfer records

Compare a controlled record bearing a received stamp, initials, tick, or similar mark 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 the reconstruction with a related custody-path case when the record may have travelled outside the expected handoff route.

Do not create a retroactive receipt

Do not ask the apparent recipient to sign now in the original receipt field. If that person can confirm current possession or participate in a current review, record that with the current time and purpose. A new signature cannot establish an earlier custody event that the person does not remember.

Keep recipient and player data inside authorised channels

A custody investigation can tempt staff to circulate the document widely looking for recognition. Keep player, marker, credit and staff information inside the authorised review path. Ask about custody using identifiers sufficient for the search, not unnecessary screenshots or copies.

Document the last confirmed custody point

Record the mark that was present, the role or name it appeared to indicate, the last custody point that can actually be confirmed, the people asked, and the outcome of those checks. If custody remains unresolved, say so plainly rather than converting “no confirmation” into “probably received.”

Hand over the record as custody-unconfirmed

If the issue remains open at relief or close, carry it forward explicitly. The handover should identify a controlled record bearing a received stamp, initials, tick, or similar mark, 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 turn a current acknowledgment into an earlier receipt

Do not move the record into the apparent recipient’s packet merely because the mark suggests it belongs there. Preserve current custody until the authorised role decides the next movement. Otherwise staff may create a fresh handoff that looks like evidence of the earlier one.

Explain the review without naming an unconfirmed custodian

The dealer can say that an internal record handoff is being verified and that the responsible supervisor is handling it. There is no operational need to identify an employee as the recipient before that has been established. Protect both confidentiality and fairness while the custody path is reconstructed.

Trace the document forward from the last proven handoff

Secure the document, preserve the questioned mark only through authorised means, identify the last confirmed holder, ask the apparent sender and recipient about their own actions, check transfer logs or packet records, and escalate any remaining gap. Document the result as confirmed custody, disproved custody, or unresolved custody—not as a guess.

Resolution requires a proven or formally unresolved custody path

A proper resolution establishes who actually took custody and when, or clearly records that the handoff cannot be proven. It also explains what the existing mark represents if that can be established. The important outcome is a truthful custody trail, not forcing the mark to mean more than the evidence supports.

Do not claim who made or accepted the mark without evidence

Do not claim that who made the mark, what the mark meant, and where the controlled record moved after that point 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.

Treat a received mark as a clue, not a completed custody chain

In this case, the safest operational judgement is to preserve the mark, record the custody gap neutrally, and trace the last confirmed handoff without inventing a recipient. 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.