Las Vegas operates on Pacific Time, but that creates headaches most people don't expect until they're already missing a call or a payout window.
Las Vegas sits in the Pacific Time Zone, which means it is one hour behind Mountain Time and three hours behind Eastern Time for most of the year. That sounds simple enough. It is not simple when you are running a multi-state operation, scheduling live dealer streams, or coordinating with international gaming regulators. The real problem is daylight saving time, because Nevada follows it, but Arizona does not, and that single fact breaks more business workflows than any amount of timezone math. Here is what actually matters for people running business from or around Vegas. Pacific Standard Time is UTC-8. Pacific Daylight Time is UTC-7. Nevada switches to DST on the second Sunday in March and falls back on the first Sunday in November. Arizona stays on Mountain Standard Time all year, which means for roughly six months of the year, Las Vegas is actually one hour behind Phoenix instead of being in the same timezone. I learned that the hard way in 2019 when I was coordinating a live broadcast with a production company based in Scottsdale. We had been using the same clock for months during standard time, and nobody flagged the DST switch. The stream went live an hour early for the Vegas team. Every feed was misaligned, teleprompters were off, and we lost about forty-five minutes before we could recover. The fix was not complicated, but it should have been obvious: I started using a shared calendar system that pulls from actual timezone databases instead of relying on the assumption that both cities stayed locked together year-round. If you are dealing with Europe, Las Vegas is typically nine hours behind London during British Summer Time, or eight hours behind during standard time. Paris and Berlin follow similar patterns with their own DST rules, which means the offset can shift by an hour depending on when the EU switches compared to the US switch. They rarely stay perfectly synced. The EU moved its spring forward date a few years ago, and now there is a brief window in March where the two regions are off by an hour from what you would expect. Most scheduling tools handle this, but if you are building something custom or working with legacy systems, you need to account for that gap explicitly.
Asia is another layer. Las Vegas is sixteen hours behind Japan Standard Time and seventeen hours behind China Standard Time, with no daylight saving complications on the Asian side. This creates some genuinely awkward overlap windows. The only time of day where a Las Vegas business person can reasonably join a live call with someone in Shanghai without either of them staying up past midnight or waking before dawn is roughly between 8 AM and 10 AM Pacific Time, which translates to midnight to 2 AM in Shanghai. That is not ideal for either party. I recommend async communication as the default for Asia-Pacific operations and reserve live calls for the narrow window I mentioned. It saves a lot of resentment. For gaming and entertainment operations specifically, there are regulatory implications. The Nevada Gaming Control Board requires certain reporting to happen within strict windows, and if you have licensees or partners in other jurisdictions, you need to make sure your internal clocks are synchronized properly for audit purposes. I once audited a property where the surveillance system timestamps were logged in UTC but the financial reconciliation was done in local time, and nobody had bothered to verify the conversion was consistent across all terminals. It created a discrepancy that took three people two full business days to trace. The solution was straightforward: standardize everything to UTC at the point of data capture and do all display conversions at the presentation layer only. Nobody likes hearing that their compliance process has a timezone bug. Online sportsbooks and fantasy platforms operating out of Las Vegas face another practical issue. Betting cutoffs are tied to game start times, and those start times shift when DST changes. A Sunday Night Football bet cutoff that has always been at 8 PM Pacific becomes 7 PM Pacific when the rest of the country falls back but Nevada springs forward, or vice versa. The oddsmakers know this and adjust, but if you are running a syndicate or a betting group with people in multiple timezones, you need to be tracking the actual game clock, not your local clock. I keep a simple reference sheet on my desk that lists the DST shift dates for the current year and flags any weeks where the usual cutoff times will be off by an hour. It takes about five minutes to update each March and November and has saved me from missing at least a dozen deadlines over the years.
There is also the question of what happens when you are physically in Las Vegas but working with teams across multiple timezones simultaneously. The worst setup I have seen is someone trying to run a morning standup with New York, an afternoon session with Las Angeles, and an evening call with London all in the same day while based in Vegas. It is possible, but it usually means the Vegas-based person is working from 6 AM to 10 PM and missing the middle of their day entirely. A better approach is to stagger your core collaborative hours. Do your New York calls in the morning, your local work in the early afternoon, and your European wrap-up calls in the evening. It is less glamorous but it keeps your actual working hours reasonable. For people who travel frequently between Las Vegas and other cities, the biggest mistake is assuming your body clock will adjust quickly. Pacific Time is close enough to Mountain and Central that jet lag is mild for most domestic routes, but it is real enough to affect decision-making. I have seen dealers, pit managers, and even executives make costly errors on the first day back from an East Coast trip because they were operating on a mindset that was still three hours ahead. The standard advice of getting sunlight exposure and avoiding caffeine after noon is correct, but the most practical tactic I use is to set all my devices to the destination timezone the night before I leave and gradually shift my meal times. It reduces the adjustment period from two days to roughly one. One counter-intuitive thing about Las Vegas time that most people miss: the city itself is huge and spread out, but it is all in the same timezone. The Strip, downtown, Henderson, North Las Vegas, and the airport are all within about twenty miles of each other and share the same clock. This means there is no excuse for internal confusion within the metro area, unlike cities that span multiple timezones. Use that to your advantage when scheduling anything local. If you can coordinate it within the Vegas valley, you do not need to think about timezones at all.
Get the Full Details
For international business with Las Vegas-based partners, always confirm whether DST is currently active before setting up recurring meetings. A lot of scheduling software defaults to the sender's timezone or uses ambiguous labels like "Vegas time" without specifying PST or PDT. I always ask for the UTC offset explicitly, and I double-check by converting it to my own timezone before confirming. It adds thirty seconds to the process and eliminates the vast majority of scheduling errors. If you need a practical tool for managing these conversions, most people end up relying on world clock apps or browser-based converters, but the ones that actually work well are the ones that pull from the IANA timezone database and handle DST transitions automatically. Avoid anything that hardcodes offsets or relies on manual adjustment. The ones that do will break you in March or November without warning. The bottom line is that Las Vegas being on Pacific Time is straightforward until it is not. The DST shifts, the Arizona exception, the regulatory clock requirements, and the international overlap constraints are all real operational factors. They are not difficult to manage, but they require explicit attention rather than assumptions. Once you build systems and habits around the actual mechanics instead of the rough approximation, you stop losing time to preventable errors and can focus on the actual work.
