Eligible users have access to the Work Hours feature in their MentorSM app. Typically, all trips completed will default to Driver and will contribute to your FICO® Safe Driving Score. Work Hours is designed to remove the hassle of logging trips by separating drives taken during Work Hours and those taken during personal time, eliminating the need to adjust your trips later.
Work Hours is easy to set up and allows your trips to default to Driver when taken between your set Work Hours. Trips taken outside of Work Hours will not be visible on the Trips page and will not be counted toward your FICO Safe Driving Score, behavior risk ratings, or Rewards.
Set Up
To set up Work Hours, go to the More menu and select Work Hours in settings. Toggle Activate Work Hours and confirm your time zone.
Your time zone is automatically updated from your device settings. If your time zone is correct, select Yes. To change your time zone, select No when prompted and change your location settings.
From the Work Hours screen, you can set your hours by selecting the days and times that you are scheduled to work. Simply select the day and then use the slider to adjust the start and end times of your shift. This will allow all drives taken during your shift to default to Driver and will exclude all drives taken outside of Work Hours. Select Save to activate your newly set Work Hours.
Note: all updates will take effect the next calendar day. Work Hours for current and historical days cannot be edited.
Changing Hours
To change your hours, go to the More menu and select Work Hours in settings. Select or deselect the days and use the sliders to adjust your scheduled Work Hours. Select Save to update your set Work Hours.
Once your Work Hours are set, all trips taken during your shift will default to Driver. Trips taken outside of Work Hours will not be displayed on the Trips page and will not count toward your score, risk ratings, or Rewards.
Changing Trip Status
Trips taken during your set Work Hours will default to Driver status under the Trips page while trips taken outside of your Work Hours will not be displayed in your Trips and will not count toward [towards] your FICO Safe Driving Score, behavior risk ratings, or Rewards.
To change the status of a trip recorded during Work Hours, tap the Driver icon and change it to Personal.
Partial Trips
Some trips may be partially captured while Work Hours are set:
- If your trip starts before your scheduled shift begins and ends after your set shift starts, the portion of your trip taken during Work Hours will appear on your Trips page. The portion taken outside of Work Hours will be excluded from your trips.
- If your trip starts before your scheduled shift ends and ends after your set shift ends, the portion of your trip taken during Work Hours will appear on your Trips page. The portion taken outside of Work Hours will be excluded from your trips.
Trips taken during Work Hours will default to Driver. To change the status, select the status icon and choose the appropriate category. Although you can change the status of the recorded trips, you cannot view or change the status of a trip taken outside your work hours. Note: the portion of the trip taken outside of Work Hours will NOT be visible or scored and will not reflect in your FICO Safe Driving Score, behavior risk ratings, or Rewards.
Note: Within the app, trip data is initially captured when a driving event occurs and sent to the backend for processing. Once the trip data has been transferred, the app deletes any locally stored raw trip information, leaving no persistent cache on the device. On the backend, all trips are evaluated, with those occurring outside Work Hours flagged as Outside Work Hours (OWH). These trips are processed and retained under the same protocols as Work Hours trips but are categorized differently. Notably, OWH trips are excluded from user-facing metrics, such as in-app trip statistics, reported mileage, eLearning engagement, and Rewards contributions. This ensures that users only see trip data aligned with designated Work Hours, while backend processing maintains comprehensive trip records for operational purposes.