Loading...
compliance

Chip Tray Verification and Inventory Log

Chip Tray Verification and Inventory Log is a table-side checklist for counting chip tray denominations at open, close, fills, and credits. It helps dealers and supervisors document float accuracy, catch discrepancies early, and keep sign-off clear.

Trusted by frontline teams 15 years of frontline software

Built for: Casino Gaming · Hospitality And Gaming Operations · Table Games Compliance

Overview

Chip Tray Verification and Inventory Log is a task template for counting and documenting chip tray contents by denomination at the points where inventory changes: table open, table close, fills, and credits. It is built for table games operations that need a repeatable record of what was in the tray, what changed, who verified it, and when the change was approved.

Use this template when you need more than a casual count. It works well for regulated gaming floors, high-volume tables, and any operation where chip movement must be traceable across a shift. The checklist format helps keep the count atomic: each denomination can be verified independently, discrepancies can be flagged immediately, and supervisor review can happen before the next game action continues.

Do not use it as a substitute for broader cage controls, surveillance procedures, or cash handling policies. It is also not the right fit for one-off informal counts where no sign-off is required. If your process does not involve fills, credits, or documented inventory events, a simpler table opening or closing checklist may be enough. The value of this template is in making each inventory event visible, verifiable, and easy to reconcile later.

Standards & compliance context

  • This template supports internal control documentation by creating a clear record of inventory verification and supervisor sign-off.
  • If your jurisdiction or house rules require dual control, use separate fields for the counter and verifier so the approval trail is explicit.
  • Keep the log consistent with your gaming floor procedures, surveillance expectations, and reconciliation records to support audit review.
  • Do not use the template to replace required regulatory forms or cage procedures where a separate record is mandated.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. Set up the template with the exact chip denominations used at the table, the table number, and the required sign-off fields for the dealer and supervisor.
  2. Assign the DRI for each inventory event so it is clear who performs the count, who verifies it, and who records any variance or blocking issue.
  3. Run the checklist at table open, after each fill or credit, and at table close by counting each denomination separately and marking every item yes, no, or N/A.
  4. Record the reason for any discrepancy, note whether it is blocking or non-blocking, and pause the table if the variance requires supervisor review.
  5. Review the completed log at shift end, reconcile it against related fill and credit records, and file any unresolved exceptions for follow-up.

Best practices

  • Count each denomination separately instead of estimating the tray total from memory.
  • Use a supervisor verification step after every fill and credit so the chain of custody stays clear.
  • Mark N/A only when a denomination is not used at that table, not when the count is uncertain.
  • Record variances immediately at the table, before the next transaction makes the trail harder to reconstruct.
  • Keep the checklist item wording atomic so one line covers one verifiable action only.
  • Treat missing chips, mismatched counts, or unexplained tray changes as blocking until a supervisor resolves them.
  • Align the template with your table opening and closing runbooks so the same event is not logged twice in conflicting ways.

What this template typically catches

Issues teams running this template most often surface in practice:

Chip counts do not match the documented float at table open.
A fill is recorded without a matching supervisor verification step.
A credit is processed but the tray denomination breakdown is incomplete.
The same variance appears across multiple events because the discrepancy was not resolved at the table.
The log shows a total value but no denomination-level detail for reconciliation.
Table close counts differ from the last verified fill because the prior event was not updated correctly.
Sign-off is missing or illegible, making the inventory event hard to audit later.

Common use cases

Pit Supervisor Monitoring a Busy Blackjack Table
A pit supervisor uses the log to verify opening float, then checks each fill and credit during a high-traffic shift. The template keeps the count tied to the exact inventory event instead of relying on a single end-of-shift reconciliation.
Dealer Closing Out a Roulette Table
At close, the dealer records the final chip tray count by denomination and confirms the result with a supervisor. This helps separate normal game play from inventory movement and makes the closing handoff easier to audit.
Compliance Review After a Tray Variance
When a discrepancy appears, the completed log provides the sequence of counts, sign-offs, and notes needed to investigate the issue. It gives compliance staff a structured trail instead of scattered verbal explanations.

Frequently asked questions

What does this chip tray log cover?

This template covers denomination-by-denomination verification of a chip tray at the moments that matter most: table open, table close, fills, and credits. It is designed to record the starting float, any changes during the shift, and the final count with supervisor sign-off. Use it when you need a clear audit trail for inventory movement at a gaming table.

When should this checklist be completed?

Complete it at every inventory event, not just at the beginning and end of the shift. A common cadence is open, after each fill, after each credit, and close, with recurrence driven by table activity rather than a fixed clock. If your floor procedures require it, treat each event as a separate checklist run so the count stays traceable.

Who should run the verification and inventory log?

The dealer or table attendant usually performs the count, and a supervisor or pit boss should verify and sign off when the procedure requires a second set of eyes. The DRI should be explicit in the template so there is no ambiguity about who owns the count versus who approves it. If your property uses dual control, keep both roles visible in the log.

Is this template useful for compliance and audit purposes?

Yes, because it creates a time-stamped record of chip movement and a verification step at each inventory event. That supports internal controls, reconciliation, and audit review without relying on memory or informal notes. It is especially useful where documented sign-off is part of the table game control process.

What are the most common mistakes when using this log?

The biggest mistake is combining multiple actions into one vague checklist item, which makes it hard to verify what actually happened. Another common issue is skipping the supervisor sign-off after fills or credits, which breaks the control chain. Teams also sometimes count by total value only and miss denomination-level discrepancies that matter during reconciliation.

Can I customize the denominations and thresholds?

Yes, and you should. The template should reflect the chip denominations actually used at your property, along with any house rules for minimum float, fill triggers, or exception handling. You can also add fields for table number, shift, reason for fill or credit, and variance notes.

How does this compare with an ad-hoc paper note or verbal count?

An ad-hoc note or verbal count is faster, but it is easy to lose detail, miss a denomination, or forget who verified the count. This template turns the process into a repeatable checklist item with clear verification steps and a consistent record. That makes discrepancies easier to investigate and reduces reliance on memory.

Can this be connected to other operational logs?

Yes, it pairs well with table opening and closing checklists, fill/credit authorization logs, and shift handoff records. If your operation uses a broader compliance workflow, this template can serve as the inventory control step that links to the rest of the runbook. Keep the references consistent so the same table event can be traced across logs.

Go deeper on the topic

Related concepts
  • AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
  • Compliance is the practice of ensuring employee behavior meets regulatory, contractual, and internal-policy requirements — and of producing the evidence to...
  • Compliance training automation is the software-driven process for assigning, tracking, and evidencing required training (HIPAA, harassment prevention,...
  • HR case management is a structured system for handling employee questions, requests, and issues — with routing, SLAs, an audit trail, and a knowledge base...

Ready to use this template?

Get started with MangoApps and use Chip Tray Verification and Inventory Log with your team — pricing built for small business.

Get Started