Working With Time In Clovis, New Mexico
Clovis sits squarely in the Mountain Time Zone, which means when the rest of the country is figuring out whether it is EST, CST, or MST, you are just dealing with MT. That simplicity sounds nice until you are coordinating with teams in California or New York and the math stops being obvious. The thing nobody tells you about time in Clovis is that the Mountain Time Zone itself is not one consistent thing year-round, and the overlap periods with adjacent zones cause more scheduling headaches than people expect. I used to run a remote project team spread across six states, and Clovis was our anchor location. The first year, we burned through two weeks of frustrated Slack threads because I did not account for the Pacific Northwest shift pattern correctly. Here is what I learned from actually doing this instead of reading a chart. Clovis follows Mountain Standard Time (UTC-7) during standard time and Mountain Daylight Time (UTC-6) during daylight saving time. New Mexico observes DST, so clocks move forward one hour on the second Sunday in March and back on the first Sunday in November. This is standard, but the practical complication is that Arizona does not observe DST, and the Navajo Nation, which overlaps parts of northeastern New Mexico and adjoins the Clovis area, does observe it. That creates a narrow geographic pocket where neighboring communities are on different time settings despite being close to each other.
When I was booking a field crew out of Clovis for a job near the Arizona border, I ran into a situation where the site foreman in Holbrook was still on Arizona standard time while the equipment delivery in Clovis was running on MDT. The truck arrived at what both parties thought was the same clock time, but they were off by an hour. The fix was straightforward once I caught it: I stopped relying on city names for scheduling and started using UTC offsets in every calendar invite. I also built a simple reference sheet that mapped the specific coordinates of job sites to their current UTC offset so dispatchers could verify without guessing.
The Overlap Windows That Matter Most
The real value in knowing Clovis time comes from understanding when it overlaps with other zones, because that is where your actual working hours live. During Mountain Standard Time, Clovis shares hours with Pacific Time from 8 AM to 11 AM MT, which lines up with 7 AM to 10 AM PT. That is your only window for same-day real-time coordination with California. The overlap with Eastern Time runs from 10 AM to 2 PM MT, corresponding to 12 PM to 4 PM ET, which covers the heart of the East Coast business day. During Mountain Daylight Time, these windows shift. The PT overlap expands slightly because Arizona stays on UTC-7 while Clovis moves to UTC-6, so you effectively gain an hour of overlap with California that does not exist during standard time. The ET overlap shrinks by one hour since Clovis moves away from Eastern Daylight Time, which is still UTC-4. If your team or clients operate primarily in California, scheduling heavy coordination during late spring through early fall is strategically better because those overlapping hours give you more flexibility.
Get the Full Details

Practical Tools For Managing Time In Clovis
You do not need fancy software for this. A few basic setups handle the vast majority of cases. First, keep your computer and phone timezone set to America/Denver, which is the IANA timezone identifier for Mountain Time and covers Clovis accurately. Phone and computer systems often default to this zone for the entire region, so manual adjustment is usually unnecessary unless you are traveling or working with international contractors. For scheduling across zones, World Time Buddy or the built-in clock feature in Google Calendar handles the visual overlap check in about thirty seconds. I prefer World Time Buddy because it shows all major US time zones on a single vertical strip, making it immediately obvious where the common hours are. The downside is that it can be slow to load if you are on a bad connection in rural eastern New Mexico, which happens more often than you would think near Clovis. When the tool does not load, falling back to a simple mental calculation based on the UTC offsets I described above usually takes less than ten seconds anyway. For anything involving payroll, compliance, or legal deadlines where timing matters, double-check using at least two sources. The US Naval Observatory time website and the official NIST time server both confirm current UTC offsets without relying on third-party calendars that may have stale data after a DST transition. I learned this the hard way when a compliance deadline was missed because a widely used scheduling platform had not updated its DST rules for a particular year.
Common Mistakes People Make
The biggest error is assuming that Mountain Time is always one hour ahead of Pacific Time or two hours behind Eastern Time. That relationship holds during the middle of the year but breaks during the four-week windows around DST start and end dates when the zones shift at different times. The United States moved DST start and end dates in 2007, and the misalignment period between when the US shifts and when some international or legacy systems shift can create a one-week window where all the standard rules are wrong. Another mistake is treating Clovis the same as Albuquerque for scheduling purposes. They are in the same timezone, yes, but if you are coordinating with government offices, court filing deadlines, or regional medical appointment systems, some institutions use Phoenix time for administrative purposes even when located in New Mexico. A few county clerk offices in the eastern part of the state operate on this mixed convention, and showing up based on Clovis time when the office is running on AZST can cost you a failed appointment. If you need absolute certainty for time-sensitive work, the workaround I ended up using was to confirm the local office timezone directly in writing before any important visit or deadline. A short email asking "Are you operating on Mountain Time or Arizona Time right now?" solves more problems than any app ever will.
Bottom Line
Time in Clovis is straightforward if you treat it as a practical logistics problem rather than a trivia question. Set your devices to Mountain Time, track the DST transitions carefully, use overlap windows strategically for cross-zone coordination, and verify timezone expectations in writing whenever the stakes are high. The edge cases are rare but expensive when you miss them.
