A table-game drop is not complete when a locked box leaves the table. It is complete when the contents have been counted, recorded by source, reconciled to the supporting documents, and accepted into the next department’s accountability.
That distinction explains the whole workflow. The casino is moving custody, not merely moving cash.
The control chain at a glance
| Stage | Control objective | Evidence created or checked |
|---|---|---|
| Preparation | Only authorized boxes, carts, keys, and staff enter the process | Drop schedule, key access, team assignment |
| Removal | The correct locked box leaves the correct table | Table identity, box identity, observation |
| Transport | Custody remains continuous and restricted | Team presence, secure cart or container, route completion |
| Count-room intake | Every received box is accounted for before opening | Intake log, sequence or source check, exception record |
| Count | Contents remain attributable to one source until recorded | Table-by-table count entry, documents from the box |
| Reconciliation | Physical contents agree with game and cage records | Master games summary, fills, credits, markers, inventory forms |
| Transfer | Cage or vault formally accepts the proceeds | Signed or system-recorded accountability transfer |
The exact team size, key arrangement, route, timing, and surveillance plan belong to the property’s approved internal controls. Publishing those operational details would not improve public understanding. The useful principle is that no gap should exist between one accountable stage and the next.
Before the first box moves
Preparation begins away from the gaming table. Management determines which tables are scheduled for drop, who is assigned, whether required independent roles are present, and whether empty replacement boxes and transport equipment are controlled.
A strong process prevents three basic errors before they happen:
- removing a box from the wrong table;
- leaving a table without the correct replacement box when one is required;
- allowing one person to gain unobserved control of the box or the relevant keys.
The drop team should not need to invent a solution on the floor. Exceptions such as a closed table, damaged lock, missing label, active dispute, or inaccessible area need a defined escalation path.
Removal is a handoff, not a collection chore
At the table, the locked drop box is identified and removed under the prescribed observation. A replacement box may be installed as part of the same continuous process. The table number and box identity must remain clear because the count later depends on source attribution.
This is why a drop box cannot be treated like an anonymous cash container. The amount inside will be used with the table’s opening and closing inventory, fills, credits, markers, and other documents. Lose the table identity and the cash may still exist, but the accounting evidence has been damaged.
Players may see a brief pause, staff around the base of the table, and a cart moving through the pit. The visible action is short. The responsibility attached to it continues into the count room.
Secure transport preserves continuous custody
The transport stage is deliberately uneventful. Boxes remain locked and controlled while they move directly to the count room or another approved secure area. If several trips are required, previously collected boxes must remain secured rather than waiting in an uncontrolled intermediate location.
Separation of duties matters here. The pit employees whose shift is being dropped should not have sole control over removal, transport, counting, and reconciliation. Independence does not imply distrust of a particular person. It reduces the opportunity for one error or deliberate act to pass through every stage without challenge.
Surveillance can document the movement, but a camera does not replace physical custody. A perfect recording of an uncontrolled handoff is still evidence of a weak handoff.
Intake should identify exceptions before counting begins
When the boxes reach the count room, the team confirms that the expected sources have arrived and that nothing obvious is missing, duplicated, damaged, or out of sequence. An unexplained box should not silently enter the normal count stream.
Common intake exceptions include:
- a box identity that does not match the schedule;
- an expected table with no box;
- an unexpected box from a closed table;
- visible damage or a control irregularity;
- a late box arriving after the count sequence has started;
- incomplete documentation for a transfer or unusual event.
The response is to stop, preserve the condition, and document the exception under the approved procedure. “Fixing” the record so that the list looks complete destroys the very evidence the control is meant to protect.
Count each source before commingling
In the count room, a box is opened and its contents are counted in a manner that keeps them attributable to that source until the result has been recorded. Currency, chips, wagering instruments, receipts, coupons, and transaction documents can require different handling.
The count is not only a currency total. Documents removed from the box connect physical value to transactions recorded elsewhere. Fill and credit slips, marker records, opening and closing inventory forms, and other approved items are traced or reconciled according to the system in use.
The current Nevada table-games minimum internal control standards provide a formal example: locked boxes are removed with independent participation, transported directly and secured, counted individually before commingling, and reconciled with supporting table-game records. The standards also define the count as continuing until cage or vault personnel sign the master summary and assume accountability.
The final signature changes ownership of the total
A count total is not finished merely because the currency counter stops. The proceeds and supporting summary must be reviewed and formally accepted by the cage, vault, or other designated accountability area.
That acceptance creates a clean boundary:
- the count team attests to what it counted;
- the receiving department accepts the proceeds;
- accounting retains the ability to trace the total back to each table and supporting transaction;
- unresolved variances remain visible rather than disappearing into the transfer.
Digital systems may replace parts of the paper trail, but they do not remove the need for role separation, locked records, auditability, and controlled correction.
A worked reconciliation example
Suppose the count team records the following for Table 12:
- currency and approved instruments from the drop box: $18,400;
- opening table inventory: $30,000;
- closing table inventory: $36,500;
- fills delivered to the table: $5,000;
- credits removed from the table: $1,000.
A simplified table-win calculation is:
Table win = closing inventory + drop + credits − opening inventory − fills
Table win = $36,500 + $18,400 + $1,000 − $30,000 − $5,000 = $20,900
Every variable has a separate source. “Drop” comes from the box count. Opening and closing inventory come from the table records. Fills and credits must agree with cage and table documentation. The formula does not prove each source is correct; it shows why all of them must survive the workflow.
The result is a gross table-game figure, not net casino profit. It does not include payroll, promotions, uncollectible credit, taxes, or other operating expenses.
Measuring the process without rewarding bad speed
Cycle time can help management identify staffing or equipment problems, but speed should never become the only target. Useful control measures include:
Exception rate = documented drop exceptions ÷ drop events
If a property records 9 exceptions across 1,500 table-drop events, the rate is:
9 ÷ 1,500 = 0.006 = 0.6%
The number needs context. A rising rate may point to labels, scheduling, training, hardware, or staffing. A sudden rate of zero may represent excellent performance—or under-reporting. The purpose of the measure is to find process weakness, not to punish employees for documenting it.
Where the workflow can fail
The most dangerous failures are often ordinary:
- a team assumes a familiar box does not need to be checked;
- a custody change occurs during a distraction but is not recorded;
- contents from two boxes are mixed before the first total is saved;
- a count correction overwrites the original entry without an audit trail;
- a missing document is replaced from memory;
- staff hurry to meet a time target and postpone an exception report;
- surveillance is expected to reconstruct controls that were never performed.
A good drop is intentionally boring. Each handoff is visible, each source remains identifiable, and each discrepancy has somewhere to go. For the floor-removal view, continue with what happens during a drop. For the restricted counting environment, use what happens in the count room. Cash variance and over/short reports explains what happens when the records do not agree.