Understand duty-status events
A duty-status event records a local date, local time, timezone, duty code, location, truck context, and annotation. The system converts the local timestamp to UTC and stores the original timezone offset so the event can be reconstructed later.
Common statuses include off duty, sleeper berth, driving, and on duty not driving. Professional views may also allow condition, certification, and Canadian extension event types supported by the module.
- Manual events are limited to event types the application is allowed to author.
- Imported-only device, authentication, engine, malfunction, and co-driver event types are not fabricated by the UI.
- Correcting an event requires a meaningful annotation and never overwrites the original event row.
Add events to a daily log
- Open the Daily Log detail page.
- Use Add duty-status event.
- Choose the event type and duty status.
- Enter the local date, local time, timezone, location, odometer, and annotation as applicable.
- Save the event and review the regenerated duty timeline.
Correct a recorded event
Use correction when the original event was wrong. The app marks the original active event as changed and inserts a new active event that supersedes it. This preserves the audit trail expected by Canadian ELD-style recordkeeping and prevents totals from drifting away from the source ledger.
- Open the Daily Log detail page.
- Find the active event that needs correction.
- Choose Correct and enter the corrected values.
- Add the required annotation explaining the correction.
- Save and review the updated timeline and event history.
If something goes wrong
- If an event cannot be corrected, confirm that it is still active and not an imported-only event type.
- If times look wrong, verify the event timezone rather than only the displayed local clock time.
- If totals do not update, refresh the daily log after saving the event; duty periods are regenerated from active events.