Overview
The Dispatch Board shows every visit and event in the time zone of the computer you are using, not in a fixed company time zone. When scheduled times look an hour early or late, the cause is usually a time zone mismatch on a device, or events that were saved under an earlier company time zone.
This article is for dispatchers and admins. It explains how the board chooses what time to show, how to check your settings, and how to correct events that are already off.
How the Dispatch Board decides what time to show
The board converts each saved event into the time zone your browser reports. Your browser gets that time zone from your computer's operating system clock settings.
Non-visit events, such as recurring Load Up and End of Day (EOD) events, are saved as a single moment in time (UTC). That moment does not change when someone views it from a different time zone, but the clock time on screen does. For example, an event saved for 14:30 UTC shows as 7:30 AM on a computer set to UTC-7 and as 8:30 AM on a computer set to UTC-6.
Two users in different time zones can therefore see the same event at different clock times. The event itself has not moved.
Why scheduled times can look an hour off
Three situations account for most reports of times that are an hour early or late:
The browser and the computer disagree. The browser reports a different time zone than the computer's clock, so the board shifts every event.
The computer is set to the wrong time zone. This often happens when automatic time zone is off, or when a region changes its daylight saving rules and the device is not updated.
Events were saved under an earlier company time zone. Recurring events are calculated using the company time zone when they are created. Changing the company time zone later does not move events that already exist, so a recurring Load Up created under the old zone can display an hour off.
How to check your time zone settings
Start with the computer, then the browser, then compare against a second device.
Check the computer's time zone. On Windows, go to Settings > Time & language > Date & time. On Mac, go to System Settings > General > Date & Time. Confirm the time zone matches your location, and turn on the automatic time zone option if it is off.
Check that the browser matches the computer. Some browser settings, extensions, or IT policies can report a different time zone than the computer's clock. If the two differ, ask your IT team to correct the browser's time zone.
Refresh BuildOps. After any change, refresh the page. If times still look wrong, clear the browser cache and restart the browser.
Compare with another computer. Open the same day on a second computer. If it shows a different time for the same event, the difference comes from the device settings, not from the event.
How to fix events that are already off
Correct your computer's time zone first, then fix the events themselves from the Dispatch Board.
A single visit or event: drag the card to the correct time, or click the card, open the Scheduling section of the Visit Side Panel, update the time, and click SAVE. A visit cannot be rescheduled once the technician has tapped Travel or started work.
A recurring Load Up or EOD series: delete the series and recreate it at the correct local time. To recreate it, click blank space on the Dispatch Board, select the event type, fill in the details, and set the recurrence over the date range you need.
Many events at once: contact Support. Do not rebuild a large schedule by hand before Support has looked at it.
When to contact Support
Contact Support if times are still wrong after your computer and browser both show the correct time zone, or if many events are affected. Include the following so the team can trace the event end to end:
A screen recording or screenshot of the event on the Dispatch Board
The job, visit, or event name, the date, the time shown, and the time you expected
The time zone shown by your computer and by your browser
Whether other users see the same time for that event
Whether the event is recurring, and whether it was created before or after a company time zone change.
