01AUTOMATIC CREATION
HOS violation
Drive limit violation becomes active
Task opens with relevant event details
Response and outcome join the timeline
Documentation · structured issue history
Every issue.
Every action.
Every step documented.
ELD Engine creates structured task records for compliance and operational issues, tracks their progress, records important events automatically, and preserves a clear activity timeline from detection through resolution.
One record for the issue, the response, and the outcome
More than a task
A task becomes the complete record of an issue.
The task is not just something to complete. It is the audit trail: what happened, what was done, who acted, and how the situation ended.
01 / RECORD
Everything relevant, in one place.
Each record can hold the details appropriate to its issue type, alongside the history of its progress.
Issue description
What happened and why the record exists.
Structured metadata
Driver, vehicle, time, issue-specific values, and related context.
Files and comments
Supporting material and human context alongside system activity.
Status and outcome
See where the issue stands and how it was ultimately resolved.
Chronological activity
Changes, decisions, and detected events in the order they happened.
Created as events happen
Some issues document themselves from the moment they begin.
When the monitoring platform detects certain events, it can create a task and preserve the relevant details as the issue unfolds. Documentation is part of the workflow, not paperwork added later.
EXAMPLE · HOS LIMIT VIOLATIONA violation becomes active. Its record already exists.
AUTOMATICEVENT DETECTEDDrive limit violation becomes activeRelevant violation data is available
TASK CREATEDIssue record opens automaticallyThe originating event is preserved
RESPONSEActions and updates are addedPeople add context as they act
OUTCOMEResolution joins the historyReview the full sequence later
For task types configured for automatic creation; coverage depends on the event and workflow.
Automatic activity · Personal Conveyance
The system keeps documenting while the issue is happening.
A PC request can store the requested use, approval information, authorized mileage, and actual mileage. When supported, the platform can add activity as PC is enabled, driving starts and stops, and PC is disabled.
AUTHORIZED20.0 mi
ACTUAL17.6 mi
Completed
Illustrative workflow and values. The product screenshot above shows a real task detail view and its recorded PC activity.
PERSONAL CONVEYANCE REQUESTActivity timeline
PC approvedApproval details recorded
PC enabledSystem event added to the task
Driving detectedActivity begins
Driving stopped · 17.6 miActual distance preserved
PC disabledTask reflects the completed activity
The activity timeline
A complete timeline of what happened.
Instead of rebuilding the story days later from messages, logs, and memory, relevant history is organized chronologically in one place.
A task’s activity may include creation, status changes, human comments, driver contact, detected ELD activity, metadata updates, files, approvals, and resolution events.
A RECORD THAT MOVES WITH THE ISSUE
From first signal to final status.
In this PC Request example, system comments appear in sequence next to the task’s status and issue-specific details.
System activity Task details
People + platform
Automation records what the system knows.
People add the context it doesn’t.
Telemetry and human judgment each tell part of the story. The task brings both into one usable history.
SYSTEM EVENTS
Automatic task creation
Detected ELD and vehicle activity
Field changes and status updates
Automatic resolution events
ISSUE RECORDOne complete
task historyContext + chronology
task historyContext + chronology
HUMAN ACTIONS
Driver requests and explanations
Phone-call outcomes
Management decisions
Files and manual resolution notes
Automatic resolution
When the issue disappears, the record can close itself.
For supported workflows, task status can follow the real state of the issue. When the system detects that the underlying problem is corrected, it can add the event and close the task.
That reduces manual cleanup and keeps status meaningful. Automatic closure applies to certain task types when their resolution condition is detected.
EXAMPLE · MISSING SHIPPING DOCUMENTSIssue detected issue corrected
Shipping documents missingTask created automatically
OPENDocuments addedValue recorded: BOL-583921
DETECTEDTask automatically resolvedRecord preserves what changed and when
CLOSEDDocumentation follows the real state of the issue.
Product evidence
Open one task.
See the whole story.
A task is part of a wider driver history. Find the issue in context, open the record, and review its details and activity.
One framework, many workflows
Different issues.
The same complete record.
The task structure adapts to compliance and operational situations, from automatically detected events to human-reported problems.
Why the record matters
Stop relying on memory, scattered messages, and manual follow-up.
Clear history
See what happened and when, without piecing together separate sources.
Better accountability
Understand what actions were taken and what still needs attention.
Consistent process
Handle recurring issue types through structured workflows.
Less manual documentation
Automatically record the events the platform can detect.
Easier review
Open one task to see the relevant history in context.
Persistent records
Keep the issue history available after the immediate response is over.
Issue coverage
One documentation model.
Many kinds of work.
A sampling of compliance and operational task types the framework can support.
Break, drive, shift, and cycle limit violations · Missing certification · Shipping documents · Trailer ID · Pre-trip inspection · Log optimization
Unassigned driving · Driving without ELD · Disconnected ELD device
DOT inspection
Personal Conveyance and Yard Move · Authorized and unauthorized activity
Problem report · Other
The ELD Engine service loop
Detection. Action. Documentation.
01 / MONITORINGWhat is happening?Detect the issue 02 / RESOLUTIONWhat should we do?Take action
03 / DOCUMENTATIONWhat happened and how did it end?Preserve the whole history
Monitoring detects. Resolution handles the response. Documentation preserves the full record—and can begin updating automatically as events occur.
Structured history, from signal to resolution
If an issue matters,
preserve the full story.
ELD Engine can create, track, and update documentation tasks automatically, while your team adds the human context that makes the record useful.