Turn a warning into a useful report
Identify the event, report useful details, and verify recovery.
Stop guessing and read the event
A diagnostic flags an inconsistency; a malfunction identifies a defined compliance failure. While safely parked, read the event and check whether required activity is accurate, retained, and available. The effect on the record determines the response.
Record the exact HOS warning and check the affected day’s events. Use the malfunction instructions for the installed IVG version with your carrier’s support team; a vehicle fault alert and an ELD recording failure need different responses.
Give support something it can investigate
At a glance · Follow the sequence
01
Identify
Driver, truck, and device
02
Describe
Exact code, time, and missing events
03
Follow up
What was tried and who received it
An app alert alone is not proof that the carrier received your report.
Send the fault details through the carrier’s configured messaging or reporting channel. If the terminal cannot send, use another written channel and call safety. The IVG sources are dated: verify local menus, DVIR availability, and troubleshooting against your installed version.
For a confirmed ELD malfunction, note the problem and give written notice to the carrier within 24 hours. Include the affected dates and save a copy. Report a truck defect through the vehicle-report workflow too; take login problems to account support.
Verify the affected period
After troubleshooting, check the affected log events and equipment connection. A warning disappearing does not prove that missing activity returned. If required recording is impaired, use the recording fallback described in the next lesson.