A casino does not control table cash by trusting the person nearest to it. It controls the cash by building a chain in which the box, the people, the time, the route, the count, and the final handoff can all be matched.
That chain is drop box control.
A table-game drop box normally receives currency and approved documents connected with live play. The box is only one component. The real control is the sequence around it:
Identified table → secured box → authorized removal → controlled transport
→ separate count → recorded total → independent verification → accounting review
If one link cannot be explained, the casino may still have the money, but it has weaker evidence about where the money came from and whether the reported result is correct.
The box has an identity before it has money
A controlled box should correspond to a permanent table identity and, where applicable, a game and shift or accounting period. The point is not cosmetic labeling. It is to stop money from becoming detached from its revenue source.
Current federal tribal-gaming minimum standards require card-game drop boxes to correspond to permanent table numbers and be marked by game, table number, and shift where applicable. They also require documentation for tables that were not open during the shift. See 25 CFR § 543.17.
That creates two useful controls:
- every box in the drop should have a legitimate table-period assignment;
- every table-period should be accounted for as either open and dropped or closed and documented.
A box with no table identity is a cash container. A box with a controlled identity is audit evidence.
Eight control questions follow every box
| Control question | Evidence that should exist | What failure can create |
|---|---|---|
| Which table produced it? | Permanent table and game identification | Misposted revenue |
| Which period does it cover? | Shift, gaming day, or approved drop period | Duplicate or missing drop |
| Was the box secured? | Locked condition and restricted access | Unexplained access risk |
| Who removed it? | Authorized team and role separation | Weak custody trail |
| When was it removed? | Scheduled or approved emergency-drop record | Unreviewable timing |
| Where did it go? | Direct controlled transport or secure holding | Route uncertainty |
| How was it counted? | Individual box count and permanent record | Commingled funds |
| Who accepted the proceeds? | Independent final verification and signed transfer | Unclear final accountability |
The answers should come from records and observable controls, not from memory after a variance appears.
Removal is a custody event, not a housekeeping task
The drop usually occurs at a designated time or under an approved emergency process. The operation should know in advance which tables are included, which team is assigned, which equipment is used, and which department is observing or independently participating.
High-level control principles include:
- surveillance notification before the activity begins;
- more than one authorized person involved;
- participation by someone independent of the department being dropped;
- continuity once the drop starts;
- direct transport to the count room or an equivalently secure area;
- restricted access while full boxes await count;
- documented authorization for any unscheduled access.
Public guidance should explain these principles without publishing property-specific routes, key assignments, alarm arrangements, blind spots, or emergency override details.
Count one source before mixing it with another
A strong count process preserves source identity until each box total has been recorded. Currency from Table 14 should not lose its identity in a common pile before Table 14 has a recorded amount.
The sequence is conceptually simple:
- confirm the box identity;
- empty the box under count-room controls;
- count currency and approved contents;
- record the result permanently;
- address rejected notes, coupons, chips, or unusual documents;
- show the empty box as required by policy;
- move to the next box only after the current source is recorded;
- reconcile the count-room total before transfer.
Corrections should remain identifiable. An erased number gives no reviewer a way to distinguish a harmless transcription error from an unexplained alteration. A proper correction preserves the original entry, the corrected entry, and the required verification.
A worked drop-to-table example
Assume a blackjack table reports:
| Item | Amount |
|---|---|
| Opening chip inventory | $40,000 |
| Closing chip inventory | $46,500 |
| Fills received | $12,000 |
| Credits returned | $3,000 |
| Counted drop | $28,500 |
A common table-win relationship is:
Table Win = Closing Inventory + Credits + Drop
- Opening Inventory - Fills
So:
Table Win = $46,500 + $3,000 + $28,500
- $40,000 - $12,000
= $26,000
The drop is $28,500. The table win is $26,000. They are related, but they are not the same number.
Now suppose the drop box was counted as $28,500, but the count sheet was posted to Table 41 instead of Table 14. The property has not necessarily lost cash. It has created a source-allocation error that can distort both tables, their hold percentages, player review, management reporting, and audit work.
That is why identification is as important as the physical count.
Exception handling should begin with classification
Not every drop exception is theft, and not every small variance is harmless. Classify the problem before deciding the response.
| Exception type | First question | Typical evidence to review |
|---|---|---|
| Missing box | Was the table open and included in the assigned drop? | Open-table list, cart record, surveillance timeline |
| Wrong label | Is the physical box identity inconsistent with its location or paperwork? | Table assignment, box number, count record |
| Damaged or unsecured condition | When was the condition first observed? | Custody signatures, surveillance, exception log |
| Count variance | Is the difference in the count, transfer, posting, or table records? | Counter report, rejected notes, count sheet, cage receipt |
| Unscheduled access | Who authorized it and why? | Access log, management approval, surveillance notification |
| Late or interrupted drop | What prevented continuity? | Incident record, staffing log, equipment issue |
A useful exception record states the known facts, unresolved questions, temporary controls, owner, deadline, and final disposition. “Checked—okay” is not a defensible investigation note.
Three measures that reveal control quality
Box-accountability rate
Box Accountability Rate
= Properly accounted-for boxes / Expected boxes × 100
If 84 table-period boxes were expected and 83 were correctly accounted for at the first control point:
83 / 84 × 100 = 98.81%
The missing item still requires resolution even though the percentage looks high.
First-pass reconciliation rate
First-Pass Reconciliation Rate
= Boxes reconciled without correction / Boxes counted × 100
This measures process quality, not just whether differences were eventually forced to zero.
Exception closure time
Exception Closure Time = Final documented resolution time - Detection time
Aging matters. An unresolved identification issue becomes harder to reconstruct as shifts change and memories fade.
Separation of duties has a practical purpose
Drop, count, cage acceptance, accounting, surveillance, and table operations should not collapse into one person or one unchecked team. Separation creates independent observations at the moments where accountability changes.
The table department knows what happened during play. The drop team controls removal. The count team establishes the contents. The receiving cage or vault assumes accountability for the proceeds. Accounting reviews the records. Surveillance provides independent visual evidence where required.
No single department replaces the others.
What management should be able to prove
At the end of the process, management should be able to answer:
- Which tables were open?
- Which boxes were expected?
- Which boxes were collected?
- Who controlled each custody change?
- Were full boxes protected before count?
- Was each box counted separately before commingling?
- Were corrections and rejected currency documented?
- Did the counted total equal the independently received total?
- Were unresolved variances investigated and retained with the record?
- Did accounting receive the complete documentation independently of the cash?
A drop process is not strong because nothing went wrong today. It is strong because the records can still explain what happened when something does go wrong.
The operational truth
The drop box is not the revenue. It is not the table win, and it is not the profit. It is a controlled container that carries evidence from the gaming floor into the accounting system.
Its value lies in preserving the story of the money.
Continue with What Happens During a Drop, Drop to Count Room Workflow, What Happens in the Count Room, and Table Win, Drop, and Hold Explained. For the core terminology, see Drop, Fill, and Cage.