ELD & HOS Reference Guide

Total driving = 9 hrs (under 11 ✓)  ·  30-min break taken ✓  ·  Window closes 8 PM regardless

Passenger carriers with a sleeper berth can split their 8-hr rest requirement. The combination must total at least 8 hours:

The cycle is always calculated as a rolling window. On the 70-hr/8-day cycle, the system looks back at the last 8 days. As Day 1 drops off (on Day 9), whatever hours were worked on Day 1 become available again — this is the recap.

1. Ensure any previously active exemption is disabled first — only one exemption can be active at a time.
2. On the main dashboard, locate the Flip icon in the top-right corner and tap it to access exemption settings.
3. Find the "Enable Adverse Condition" toggle switch and tap it to activate.
4. Tap Yes on the confirmation prompt.
5. Enter a valid reason for enabling the exemption (e.g. "unexpected snow on I-80, visibility reduced") and tap Save.
6. You will see an "Adverse conditions enabled" confirmation message. The dashboard will show updated remaining hours reflecting the extension.

Once every 7 days, a driver may use a 16-hr window instead of 14 hrs — if they start and end at the same location, haven't used this in 6 days, and take 10 hrs off before the next shift. Still subject to the 11-hr driving limit.

The ELD automatically calculates HOS in real time. A violation is triggered the moment a rule is exceeded. Here's how drivers and agents see them:

1. Driver opens the ELD app and navigates to Logs
2. Taps the flagged/violation day to open the log detail
3. Selects the driving event in question
4. Taps Review — this opens the review workflow
5. Driver (or agent with approval) makes the correction with a note/reason
6. Change is logged with an audit trail — reason must be documented

Drivers can add or edit non-driving past events directly in the app without agent involvement, as long as the edit does not conflict with auto-detected driving events.

1. Check current duty status — confirm the driver is NOT in PC or YM. If they are, change to On Duty first.
2. Verify the ELD is properly connected via BLE — check indicator lights. Orange + Green = fully connected. Orange only = not connected to driver app.
3. Confirm the cable is firmly plugged into the diagnostic port — no wobble. Use the truck-specific cable provided for that vehicle.
4. Check BT Troubleshoot screen in the app — RPM, speed, and ignition values should appear. If all zeros, the ELD is not reading CAN data.
5. Ignition OFF → wait 10 seconds → ignition ON → drive above 5 mph → monitor status.
6. If still not triggering — check for a competing ELD or adapter on the port. Remove it.
7. If all checks pass and auto-drive still doesn't work — escalate to tech team with BT Troubleshoot screen screenshot.

When a driver tries to certify their daily logs, some events may be flagged with missing data — typically a missing location or odometer value. These appear as yellow-highlighted entries in the Review screen. The driver cannot fully certify until these are resolved or intentionally skipped.

1. Driver taps Review while on the certification screen.
2. Scroll through the day's log — any entry highlighted in yellow has missing data (missing location, missing odometer value, etc.).
3. For each yellow entry, scroll right on that row and tap "Add Missing Data".
4. Tap Yes on the confirmation prompt and enter the missing information.
5. Once all yellow entries are cleared, tap Approve in the top-right corner.
6. Tap Agree on the confirmation page and wait for the success message.

1. On the Review screen, tap Approve without filling in the missing data.
2. Select "Proceed to sign" in the confirmation pop-up.
3. Complete the certification process — the log is certified with the missing data noted.

Log sync issues occur when the app cannot push the driver's HOS data to the Matrack server. This can cause the admin portal to show outdated or missing log data. Most sync issues are caused by poor or no internet connectivity.

1. Check the driver's internet connection — confirm cellular data or Wi-Fi is active and working. Test by opening another app (e.g. browser or maps).
2. Check signal strength — weak signal can cause incomplete sync. Move to an area with better coverage if possible.
3. Open the Matrack ELD Driver App and go to the Dashboard.
4. Tap the Sync button in the top-right corner of the dashboard.
5. Wait for the sync to complete — do not close the app during sync.
6. Once complete, check the admin portal to confirm the logs are now showing correctly.

When a DOT officer stops a driver for an inspection, here is exactly how the driver accesses and uses the DOT Inspection Mode in the Matrack ELD app:

1. Driver launches the Matrack ELD Driver App and logs in.
2. Driver taps the three horizontal lines (☰ menu icon) in the top-left corner of the screen.
3. Driver selects "Roadside Inspection" from the menu options.
4. Driver sees three options — choose based on what the officer needs:
   
   Begin Inspection — primary option for the DOT officer to review logs directly on the device. Shows the last 15 days of driver logs. Officer can browse logs without the driver needing to do anything further.
   
   Data Transfer — transfers the ELD output file to the FMCSA server (telematics) or via USB/Bluetooth (local). Officer receives the data for their own system.
   
   Additional options — compliance details viewer, email to fleet admin, data transfer manual, ELD manual.
5. For Data Transfer: driver taps Data Transfer → selects the method (telematics / web services, or local via USB/BT) → confirms the transfer → officer receives the file.
6. Once inspection is complete, the driver needs their driver password to exit DOT Inspection Mode. This is by design — it prevents the officer from accessing other parts of the app.