Dealer Casebook: End-Shift Document Custody Gap

The table or shift is closing. Paperwork has been collected: fills, credits, transaction slips, exception notes, voids, count-related records, or another controlled packet. Staff are changing. Someone places the documents on a podium, hands them toward another employee, or says, “They know where these go.”

A few minutes later nobody can say with confidence who actually received the packet.

That is more than an organisational inconvenience. If the documents support value movements or unresolved discrepancies, unclear custody can break the ability to reconstruct what happened.

At shift end, document custody should become explicit. Know what is being transferred, who receives it, what remains unresolved, and do not certify closure while the controlled packet is effectively ownerless.

Separate document custody from transaction completion

A packet can be physically handed over even though a transaction inside it is still open.

Likewise, a transaction may be complete while the packet has not yet reached its authorised receiving role.

Treat those as separate states. Do not assume that because the table is closed, every document is reconciled. Do not assume that because the papers left your hands, the underlying open item disappeared.

Identify what belongs in the handoff

Before transfer, know what the packet contains at the level your role is authorised to check.

That may include completed records, voided or spoiled forms, pending items, exception notes, duplicate copies, unresolved slips, or documents awaiting another authorised step.

You do not need to invent a master checklist if the property does not use one. But you should understand whether you are handing over a closed packet or a packet with open items.

Do not leave controlled documents unattended

A busy pit can make temporary surfaces feel safe: a podium, closed table, drawer top, chip-tray cover, office counter, or cage window.

But if no receiving person has accepted custody, placing the packet nearby is not the same as handing it over.

Keep the documents within the authorised control process until the next holder is clear.

A casual verbal handoff may be too vague

“Those are for nights” or “give these to the cage later” may not establish who currently owns the packet.

The exact custody method varies by property. The principle is that the transfer should be clear enough that staff can identify the last confirmed holder and the intended next holder.

If nobody can answer that question, custody is ambiguous.

Do not mix unresolved records into a closed packet silently

If a fill is missing a witness, a slip number is unaccounted for, two timestamps conflict, or another transaction remains under review, do not bury it among ordinary completed paperwork.

Make the open state explicit through the property’s authorised handover or exception process.

The related case Close Begins With an Unresolved Transaction explains why closure should not be forced by hiding an unresolved value or record state.

Confirm the receiving role, not just the destination

“The packet goes to the office” may describe a location without identifying custody.

Who accepts it there? A floor? Inspector? Pit? Cage/control employee? Shift manager? Another authorised function?

Do not invent the role from another casino’s practice. Use the process that applies at the property. The important point is that a real authorised receiver accepts the transfer.

If documents are passed through an intermediary

Sometimes one employee carries a packet to another department or control point.

If that is authorised, the intermediate custody should still be clear. Do not assume the final department received the documents merely because a runner, supervisor, or coworker walked away with them.

Your own statement should stop at the last transfer you actually observed.

If you find a packet after the shift has changed

Do not browse through controlled documents beyond what your role requires, and do not assume the packet belongs to your shift.

Preserve where it was found, limit handling, notify the authorised role, and establish whether anyone can confirm the last custody transfer.

Avoid reorganising the papers before the receiving role sees their original state.

Keep player information and sensitive records protected

Some controlled documents may contain player identifiers, marker/credit information, amounts, signatures, or operational details.

Do not photograph them on a personal phone, send them through personal messaging, or carry them home to “keep them safe.”

Use the property’s authorised custody and privacy controls. The earlier case Sensitive Marker or Credit Document Left Near the Table reinforces the same boundary.

If the outgoing dealer says “the floor has it”

Ask only enough to establish the confirmed state.

Did the dealer physically hand the packet to a named authorised role, or did they leave it near that person? Was the open discrepancy explained? Did the receiver accept it?

Do not turn a vague memory into a documented handoff that nobody actually observed.

If the receiver refuses or is unavailable

Do not leave the packet at the destination and assume refusal transfers responsibility.

Escalate through the authorised chain and keep custody with the recognised holder until another authorised receiver accepts it or instructs a controlled alternative.

The dealer should not invent a storage location, hide the packet, or pass it to an unrelated employee simply to finish the shift.

Reconcile open items before calling the packet closed

A packet may contain an unresolved timestamp conflict, missing form, duplicate-active document, or incomplete witness field.

Those do not always prevent the table itself from closing, but they should remain visible as open items until the authorised process resolves them.

Do not mark the documentation “complete” simply because it has been bundled.

If a packet changes hands more than once

A packet may pass from dealer to floor, then to pit, then to another authorised receiving function. Do not compress that chain into “it was handed in” if you only observed the first transfer.

Record or communicate the custody step you actually know. Later roles can confirm their own receipt. This keeps each person responsible for the part of the chain they genuinely observed instead of creating one unsupported end-to-end statement.

Avoid accusation when custody is unclear

If a packet cannot immediately be located, say what is known: who last held it, where it was last seen, when the attempted transfer occurred, and whether receipt was confirmed.

Do not accuse the receiving department, outgoing shift, or individual employee of losing it unless evidence supports that conclusion.

Custody ambiguity is a fact; blame is a separate determination.

Handover the custody problem itself

If your shift ends while custody is still unresolved, the custody problem becomes an explicit open item.

State what documents are involved, their last confirmed location, the last confirmed holder, the intended destination, any unresolved transaction inside the packet, and who is now responsible for follow-up.

Do not let “we could not find who had it” become the next shift’s surprise.

If you need to document the custody handoff

A useful account might say:

“At approximately 02:05, after Table 5 closed, I assembled the table’s transaction packet and retained it at the pit podium while waiting for the authorised receiver. At 02:12 I handed the packet directly to the night floor and advised that one credit slip remained under reconciliation. I did not leave the packet unattended before that handoff.”

If custody was not confirmed, say so just as plainly.

Custody must end with a named receiver

A clean shift change requires more than moving papers from one surface to another.

At end of shift, controlled documents should have an identifiable custody path. Separate completed records from open discrepancies, keep sensitive papers within authorised control, confirm the receiving role, and hand over any unresolved custody or transaction state explicitly. Do not certify closure while nobody can say who owns the packet.