Time zone handling for multi-region dispatch teams

Question

We're expanding our operations to cover three regions: Eastern, Central, and Mountain time. From an operational perspective, I want to ensure our dispatchers in each region aren't creating scheduling conflicts when coordinating cross-regional technician assignments.

Specifically, I'm trying to understand:

1. How FieldPulse handles time zone display — is it user-local, or tied to a company default?
2. When a dispatcher in Eastern time schedules a job for a technician in Mountain time, which time zone drives the calendar and notification timing?
3. Are there safeguards to prevent double-booking when the "same" time slot spans different actual hours across zones?

We've identified this as a potential friction point before our January rollout and want to establish clear protocols now rather than troubleshoot in production. Any guidance on current behavior or recommended configuration would be appreciated.

Priya Nair (Staff) · Accepted Answer

Hi Nadia — happy to help with this! Great question as you're scaling across regions.

FieldPulse handles time zones in a specific way that impacts exactly the scenarios you're describing:

**Company Default Time Zone**
Your account has a single company time zone set at Settings → Account Preferences → Time Zone . This drives:
 
 The dispatch board and scheduler display 
 Internal notification timing 
 Report date/time stamps

**User Display vs. Stored Time**
Individual users see times converted to their local browser/device time zone, but the underlying data is always stored in company time. This means when your Eastern dispatcher creates a 9:00 AM appointment, a Mountain technician sees it as 7:00 AM — both refer to the same moment.

**Cross-Regional Scheduling**
The scheduler does not currently block bookings based on "business hours" per region. FieldPulse validates against technician availability windows set in their profile, but those windows are interpreted in company time, not local time. So a technician with an 8:00 AM–5:00 PM availability in Mountain time needs their profile configured to 10:00 AM–7:00 PM if your company is Eastern.

**Recommended Protocol**
1. Standardize on a single company time zone (often the headquarters location)
2. Configure technician availability profiles offset for their actual local working hours
3. Train dispatchers to verbalize times with time zone notation when confirming cross-region assignments

Does this align with what you were expecting? I can also connect you with implementation resources if you'd like to review this setup before go-live.

Josh Mercer · Answer

Pro tip from someone who's lived through this: we put the local time in the work order title. Not elegant, but it saved us more than once when dispatchers were looking at a board full of appointments and losing track of which tech was where.

"HVAC install — 7AM MT / 9AM ET" — something like that. Your technicians see their local time in notifications, but dispatchers need the mental anchor.

Another thing: if you're using customer notifications, double-check your templates. The default SMS doesn't include time zone, and customers absolutely notice when you say "technician arriving at 9:00" and they meant their 9:00, not yours.

Sylvia Chen · Answer

Ray's not wrong, but UTC training scales poorly past ~15 people. We've got 40+ dispatchers and field techs across four zones.

What actually worked for us:
 
 Dedicated dispatch boards per region (saved views, not separate accounts) 
 Technician profiles with "local working hours" noted in the bio field as a visible reference 
 One person who owns the "time zone sanity check" before any multi-region job gets scheduled

The last bullet is the important part. Someone needs to catch it before it becomes a problem.