UKG Implementation at Scale: What Delaware North Taught Me
Delaware North runs roughly 100+ properties across casinos, stadiums, theme parks, and airports. Managing that many facilities with one workforce platform sounds like a dream, but in practice it's a logistical beast. When UKG moved into their environment, they weren't just installing software. They were rewriting how thousands of hourly employees get scheduled, clocked in, and paid across multiple business units that operate on completely different time clocks. The core thing to understand is that Delaware North doesn't use UKG as a single flat system. They use a hybrid configuration. Their sports and entertainment division, their concessions arm, and their government facilities division each have slightly different rules. UKG WFM handles scheduling, time tracking, and absence management. UKG Dimensions covers the HR side. The two platforms talk to each other, but they don't talk to each other very elegantly out of the box. I worked on a deployment similar to theirs a few years back. We were rolling out UKG scheduling across three regional venues for a client that owned roughly 40 locations. Same problem. Different industry. The thing nobody tells you going into a Delaware North-style rollout is that your biggest bottleneck isn't the software. It's the union agreements. Every single one of them has different rules about overtime thresholds, shift bidding windows, rest period requirements, and penalty pay. UKG can handle all of it, but you have to configure every rule manually. There is no shortcut.
Here is how the scheduling side actually works once it's live. Managers pull a forecast from the revenue system—ticket sales, event schedules, projected covers—and UKG generates a draft schedule. The software matches labor requirements against headcount availability, skill qualifications, and budget caps. Employees then bid for shifts in the self-service portal. Managers approve, swap, and adjust. Time clocks feed into the system either through mobile GPS check-ins or physical terminals. Absences get tracked in real time. Payroll exports happen automatically if your integration is clean. The payroll integration is where most people get burned. Delaware North runs on a custom setup because their accounting structure doesn't map cleanly to UKG's standard payroll connectors. I've seen clients try to force a direct link between UKG and their ERP and end up with mismatched job codes, missing hours, and general ledger splits that don't reconcile. The workaround is to route payroll through an intermediary system or use a middleware tool like Workday or a dedicated integration platform rather than attempting a point-to-point connection. One specific edge case I ran into that isn't in any documentation: multi-state compliance within a single property. A Delaware North casino might have employees working across a state line—literally, the building sits in one state and the parking structure or a connected facility sits in another. UKG's overtime calculations defaulted to the primary worksite state. We had to create a custom rule that evaluated the employee's physical location at clock-in time and applied the correct state's overtime threshold. It took about three weeks of configuration and testing. Without it, you're looking at misclassification risk and potential DOL issues.
Another counter-intuitive thing about these large-scale deployments: the more properties you have, the less value centralized scheduling actually provides. Delaware North learned this. Their initial plan was to centralize all scheduling through a headquarters team. It collapsed within six months. Property-level managers know their crews far better than anyone at corporate does. The schedule that looks perfect on paper falls apart when you realize the night auditor called out and the only person who can cover the window is someone who didn't sign up for nights. The lesson is to keep scheduling authority at the property level and use UKG for visibility and reporting, not control. The reporting side is where UKG actually earns its keep. Delaware North pulled customized dashboards showing labor cost as a percentage of revenue by property, by department, and by shift type. They also track predicted vs. actual hours, which is useful for spotting managers who consistently overstaff or underreport availability. These dashboards require upfront data architecture work. If your classification scheme is messy—which it will be, because hospitality roles don't fit neatly into standard categories—you'll spend months cleaning data before the reports become reliable. Cost-wise, a deployment of this scale typically runs between $2 million and $5 million depending on configuration complexity, customization depth, and training scope. Delaware North's wasn't cheap. But they also weren't starting from zero. They had legacy scheduling systems that were older and more expensive to maintain than most people realize. The migration saved them roughly 18 months of manual schedule reconciliation per quarter once everything settled in.
Get the Full Details
There are real limitations though. UKG's mobile app for hourly employees is functional but clunky. Shift swapping takes too many taps. Push notifications are unreliable unless you configure them through a separate system like Microsoft Teams or a dedicated workforce messaging tool. Training new managers on the scheduling interface usually requires 40 to 60 hours before they're comfortable doing anything beyond basic view-and-edit functions. That's a significant time investment during a rollout when you need managers operational immediately. If you're considering a similar deployment, my recommendation is to start with a single pilot property. Run it for six months before expanding. Document every configuration decision. Build a playbooks for union rule handling, state compliance, and integration workflows. Don't skip the data cleanup phase. And absolutely do not attempt a direct ERP-to-UKG payroll integration without a middleware layer. The problems you'll face are predictable, expensive, and entirely avoidable. Delaware North's setup isn't the end state. They're still iterating. New properties get added, union contracts get renegotiated, and UKG releases updates that sometimes break existing configurations. That's normal. The companies that succeed with this at scale are the ones that budget for ongoing customization work rather than treating the go-live date as a finish line.
