Editing driver logs - Fleet Portal

Permissions and access

Log editing is restricted to authorized roles:

• Access to Compliance → Hours of Service

  

• A role or permission flag that enables Edit Log.

• Training on acceptable and prohibited edit scenarios.

When log edits are appropriate

Edits should focus on correcting factual errors, not reshaping history:

Appropriate reasons:

• Clear mis‑tap (Driving selected instead of On‑Duty while at a dock).

• Device or hardware issues that created duplicate, missing, or obviously incorrect events.

• Documented device swap or outage that needs clarification in the log.

Inappropriate reasons:

• Masking actual non‑compliant driving or duty behavior.

• Backfilling time to force logs into a compliant state for audits.

How to propose an edit

1. Open Compliance → Hours of Service→ Drivers, search for the driver, and open the Daily Log for the target date.

2. Select Edit Log (if enabled for the user and the day).

   

3. Choose the specific event or time range that needs adjustment. Keep the scope narrow to minimize impact.

   

4. Set the correct duty status and adjust start/end times and other required fields (location, vehicle, remark) without creating overlaps or gaps.

5. Add a detailed annotation, such as:

   • “Correcting mis‑tap: driver fueling, On‑Duty not Driving, 10:05–10:15.”

   • “ELD replaced at 14:00; driver remained Off‑Duty in terminal.”

6. Submit the edit. The system creates a pending edit that appears on the driver’s device.

What happens after submission

• The driver receives a pending edit request in the Maven app.

• The driver reviews the change and either:

  • Accepts the edit and certifies the day, or

  • Rejects the edit.

• The audit trail records:

  • Original events and values

  • Proposed changes

  • The admin who submitted the edit

  • The driver’s decision and timestamps