If you use time logging or timesheets for your technicians in ServiceBridge, the logged duration will be affected at the beginning or end of Daylight Savings Time. This article outlines what can be expected for each scenario.

What To Expect at the Start of Daylight Savings Time 

In the spring, when we lose an hour due to the start of Daylight Savings Time, the logged duration of a job may appear shorter than the actual time a technician spent at the job. This is because the system recognizes that the day is only 23 hours and the 2AM hour does not actually exist. Below, we have listed scenarios and what you can expect. 

Scenario A - Accurate Recording

If a user starts a job at 11:30PM the day before Daylight Savings Time and ends it at 1:30AM on the day of Daylight Savings Time, the logged duration will be correctly recorded as two hours. 

Scenario B - Inaccurate Recording

If a user starts a job at 11:30PM the day before Daylight Savings Time and ends it at 3:30AM on the day of Daylight Savings Time, the logged duration will be counted as four hours instead of the actual three hours the technician was on site. 

Scenario C - No Recording

If a user starts a job between 2AM and 2:59AM on the day of Daylight Savings Time, the time will not be logged as this time does not exist when we "spring forward."

What to Expect at the End of Daylight Savings Time 

In the fall, when we gain an hour due to the end of Daylight Savings Time, the logged duration of a job may appear longer than the actual time a technician spent at the job. This is because the system recognizes that the day is 25 hours and the 2AM hour occurs twice. Below, we have listed scenarios and what you can expect. 

Scenario A - Accurate Recording 1

If a user starts a job at 11:30PM the day before Daylight Savings Time and ends it at the first 1:30AM on the day of Daylight Savings Time, the logged duration will be correctly recorded as two hours. 

Scenario B - Accurate Recording 2

If a user starts a job at 1AM on the day of Daylight Savings Time and ends it at 1:30AM on the day of Daylight Savings Time, the logged duration will be correctly recorded as 30 minutes. This is true whether the job is started in the first 1AM hour or the second 1AM hour on that day.

Scenario C - Accurate Recording 3

If a user starts a job at the second 1AM on the day of Daylight Savings Time and finishes at 2:30AM the time will be accurately recorded as 90 minutes. 

Scenario D - Accurate Recording 4

If a user starts a job at 2AM or any time after on the day of Daylight Savings Time, the correct amount of time will be recorded. 

Scenario E - Inaccurate Recording 1

If a user starts a job at 11:30PM the day before Daylight Savings Time and ends at the second 1:30AM on the day of Daylight Savings Time, the time will be recorded as two hours instead of the actual three hours spent on the job. 

Scenario F - Inaccurate Recording 2

If a user starts a job at 11:30PM the day before Daylight Savings Time and ends at 2:30AM on the day of Daylight Savings Time, the time will be recorded as two hours instead of the actual three hours spent on the job. 

Scenario G - Inaccurate Recording 3

If a user starts a job at the first 1AM on the day of Daylight Savings Time and ends at the second 1:30AM, the time will be recorded as 30 minutes instead of 90 minutes. 

Scenario H - Inaccurate Recording 4

If a user starts a job at the first 1AM and finishes at 2:30AM on the day of Daylight Savings Time, the time will be recorded as 1.5 hours instead of 2.5 hours. 


Did this answer your question?