By Danny Roe, Chief Operating Officer at CCT
In the early 1990s, many tribal casinos didn’t look the way they do today.
Operations were smaller, teams were leaner, and processes were still taking shape in real time. Revenue audit departments were built around binders, paper forms, calculators, and spreadsheets that grew more complex month by month. Controls weren’t downloaded from a template. Instead, they were developed through experience, adjusted after audits, and refined during long nights of reconciliation.
The people leading those efforts were building something that didn’t yet exist. There was no mature playbook to inherit.
So how did they do it?
They paid attention. They learned which reports regulators scrutinized most closely and how long documentation needed to be retained — including where it would physically live. They created signature chains, drop procedures, balancing routines, and variance checks long before software automated them. When something didn’t hold up under review, they tightened it. When a process created confusion, they reworked it.
As time passed, discipline became structure. Bingo halls became resorts. Systems expanded. Teams grew. But much of the operational backbone still rested on the judgment of the people who shaped it in those early years.
Thirty years later, many of those same leaders are preparing to retire.
When we talk about generational transition, the focus is usually on staffing. Who will step into the role? How will responsibilities shift? But the more important question is this: what leaves with them?
It goes beyond familiarity with spreadsheets or reports. It’s context. It’s knowing why a specific control exists because of an issue uncovered years ago. It’s recognizing when a variance is routine and when it deserves attention. It’s understanding how a cage delay at 2:00 a.m. can affect accounting by 9:00 a.m.
That kind of knowledge often lives in people more than in documentation.
For years, spreadsheets carried much of this institutional memory. They were flexible and familiar, and they worked because the person who built them understood every formula and assumption behind them. But flexibility has limits. When a spreadsheet is highly customized to one person’s logic, it becomes difficult to transfer that logic to the next generation. When that individual retires, the file remains, but the reasoning behind it can lose clarity.
This isn’t a failure of oversight. Tribal gaming was built by practitioners long before it was formalized by modern software. Growth required adaptability, and experienced operators carried that responsibility well. As those operators begin to step away, the focus shifts from expansion to continuity, ensuring the knowledge behind the work is structured well enough to endure.
Forward-thinking casino leaders aren’t waiting until someone leaves to address this.
They’re asking practical questions now:
—Which processes depend heavily on individual interpretation?
—Where does institutional memory carry more weight than documentation?
—Which controls exist because “that’s how we’ve always done it,” rather than because they’re embedded in the system?
The goal isn’t to remove judgment from operations. Judgment is essential. But it should be applied to oversight and analysis, not to rebuilding foundational workflows from memory.
The first week after a long-tenured leader retires rarely looks dramatic. The office still opens on time. Reports still run. The cage still balances. On the surface, nothing appears broken.
Then a variance surfaces that doesn’t reconcile cleanly. It isn’t large, just unfamiliar. Someone checks the spreadsheet, reviews the drop log, scans the report. The numbers don’t look wrong…but they don’t look right either. And almost instinctively, someone says about the retired teammate, “She would have known what this was.”
This moment is a quiet realization that part of the decision-making process lived in a person who is no longer in place.
Software that is fit-to-purpose can be a solution to this new reality. Taking the opportunity to implement a system like Insight Cash, for example, can reduce the pain in losing key knowledge holders within the organization. It should be viewed not just as an alternative to the spreadsheet system of today, but also as the chance to partner with experts in the field who have been exposed to the variety of operations across hundreds of casinos.
In my time working with casinos, I have found two things to be common across all of them: 1) The security guards have the worst jokes and 2) change occurs at a constant rhythm.
Can the spreadsheets and workflow used today be resilient to the next change the casino ventures into? Would it require the intimate knowledge of the original author to tune it for that change?
Instead of relying on one person to remember why a specific reconciliation step exists, systems can reinforce internal controls, flag anomalies based on established patterns, and create audit trails that reflect years of operational refinement. What once lived primarily in someone’s head can become embedded in the workflow itself.
The leaders who built modern tribal casino operations are used to change; it’s why casinos are able to evolve at such a rapid pace. When the next change is in the retirement of key employees, it should be viewed as both a risk and an opportunity.
When technology is implemented thoughtfully, it reinforces what experienced operators put in place. It provides clarity where memory once filled the gap, and stability where transition might otherwise introduce uncertainty. In doing so, it allows the next generation to lead with confidence, grounded in the discipline that came before them.
Every casino will experience leadership transition. The question isn’t whether it will happen — it’s whether the systems left behind are strong enough to carry forward what was built.
