A drop schedule is the approved timetable and operating plan for collecting drop boxes, currency acceptor containers, or other controlled gaming-revenue containers and transferring them into the count process.
It is more than a list of times. A workable schedule coordinates authorized staff, surveillance awareness, transport equipment, replacement containers, access control, count-room capacity, gaming-floor continuity, and exception handling.
What the schedule must coordinate
A drop affects several functions at once:
- the gaming department whose positions are being serviced;
- the team responsible for collection and custody;
- surveillance coverage;
- security or escort functions where required;
- the count room or receiving function;
- accounting and reconciliation;
- facilities or technical support if equipment fails;
- management when the approved plan cannot be followed.
The schedule should not reveal sensitive routes, exact protective arrangements, or access details to people who do not need them.
Fixed time does not mean careless routine
Many properties perform drops at recurring times because staffing, count-room work, and accounting periods must align. Repetition makes planning easier, but it can also encourage complacency.
Before the drop begins, the responsible manager should confirm:
- authorized personnel are present;
- required segregation of duties is preserved;
- equipment and replacement containers are ready;
- the receiving area can accept the transfer;
- surveillance and affected departments know the process is starting;
- unusual floor conditions have been considered;
- any deviation has proper approval.
Nevada publishes current minimum internal-control standards for table games, slots, cage, and other regulated functions through the Nevada Gaming Control Board MICS library. Exact scheduling requirements vary by jurisdiction and approved internal-control system.
Drop schedule, drop window, and count schedule
These are related but different:
- Drop schedule: when and how collection is planned.
- Drop window: the authorized period in which the collection may occur.
- Count schedule: when the received contents are opened, counted, verified, and recorded.
A casino may collect containers at one time and count them later under secured custody. The schedule must account for that gap.
Operational factors that can change the plan
A schedule may need controlled adjustment because of:
- a major event or unusually high floor traffic;
- staff shortage;
- a safety incident;
- count-room delay;
- damaged transport equipment;
- surveillance or access-control issue;
- severe weather or building disruption;
- a container exception;
- a regulatory or management hold.
The correct response is not an undocumented shortcut. The deviation should be authorized, communicated to affected functions, and recorded with the reason and revised custody plan.
How to evaluate a schedule
A drop can be “on time” and still poorly controlled. A balanced review can include:
- percentage completed within the authorized window;
- missing or unexpected container rate;
- identifier or documentation mismatches;
- unplanned gaming disruption;
- receiving delays;
- custody exceptions;
- overtime created by the schedule;
- repeat deviations by location or shift;
- count-room backlog after collection;
- time to resolve high-risk exceptions.
A simple schedule-adherence measure is:
[ \text{Schedule adherence}=\frac{\text{drops completed within approved window}}{\text{drops scheduled}}\times100 ]
If 96 of 100 scheduled collections occur within the approved window, adherence is 96%. Management must still review the four exceptions. A delayed drop caused by a medical emergency is not equivalent to a delay caused by poor preparation.
Why staffing depth matters
The schedule should include relief and contingency capacity. A team assembled with no substitute for sickness, late arrival, or equipment failure creates pressure to combine duties or delay the count.
Cross-trained employees can support the plan only if they are currently qualified and authorized. Familiarity with the process does not replace the required role, license, access permission, or independent verification.
What should remain confidential
Public education can explain that casinos use scheduled, documented collection and custody controls. It should not publish:
- exact live drop times;
- routes or staging points;
- alarm and access arrangements;
- employee positions during collection;
- keys, credentials, or override procedures;
- known blind spots or contingency tactics.
Those details belong in restricted operating procedures.
Designing the schedule around workload
The schedule should reflect how much work the receiving and count functions can process, not only how quickly a collection team can move. If 300 containers arrive together but the count room can safely receive and verify only 100 per hour, the schedule has created a custody backlog.
A simple planning relationship is:
[ \text{Required processing hours}=\frac{\text{containers scheduled}}{\text{sustainable containers per hour}} ]
If 240 containers are scheduled and the verified sustainable rate is 80 per hour, the receiving and count process needs about three hours. That estimate should then be adjusted for breaks, exceptions, equipment changes, and independent checks. The highest observed speed on an unusually easy day is not a safe planning rate.
Managers should also avoid concentrating every controlled activity into the same window. A major table drop, slot collection, cage inventory, and shift change occurring together may overload surveillance, security, accounting, and management even when each process is adequately staffed in isolation.
Review changes as a control event
Every recurring deviation deserves review. A schedule that is changed daily may no longer describe the real operation. Management should compare planned and actual start times, staffing, volume, exceptions, and completion, then decide whether the official schedule needs redesign.
A useful change record states:
- who approved the change;
- why the original plan could not be followed;
- which departments were notified;
- how custody and segregation of duties were preserved;
- whether the count schedule also changed;
- what follow-up is required.
This turns a delay into usable operational evidence instead of an informal exception that disappears after the shift.
Relationship to the count
The drop schedule ends with controlled receipt, not with a final financial result. The count team must verify what arrived, inspect identity and condition, document exceptions, and count under its own controls.
For the broader flow, read What Happens During a Drop and Drop to Count Room Workflow. For container controls, see Drop Box Control.
The practical meaning
A drop schedule is a coordination control. It places the right authorized functions around a predictable transfer of gaming revenue without turning routine into complacency.
A good schedule is achievable, resourced, confidential where necessary, and flexible only through documented authority. The test is not simply whether boxes moved on time. It is whether the casino can reconstruct what was scheduled, what occurred, who held custody, what changed, and how every exception was resolved.