Yes. Fleet managers must include a note explaining the reason for the suggested edit. The note is visible to the driver and is stored in the log audit trail.
Yes. When a fleet manager submits a log edit suggestion from the Fleet Portal, they must include a note explaining the reason for the proposed change. The note field is required — the suggestion cannot be submitted without it.
Why a Note Is Required
FMCSA regulations require that log edits include an explanation. This ensures: - The driver understands why the change is being proposed before deciding to accept or reject. - The reason for the edit is preserved in the audit trail and visible to DOT inspectors. - There is a documented record of who suggested the change and why.
What the Note Should Include
A good note is specific and factual. Examples: - "Driver was On Duty loading freight from 14:00–15:30, but log shows Off Duty. Correcting to On Duty." - "Pre-trip inspection not logged. Adding On Duty Not Driving from 07:00–07:20."
Vague notes like "fixing error" are technically accepted but provide little value during an inspection.
Where the Note Appears
The note is shown to the driver in the driver app when they review the pending edit suggestion — see how a driver approves or rejects a fleet manager log edit. After the edit is accepted, the note becomes a permanent part of the log record alongside the change — see what happens to the original log entry after a correction.