ELD systems can generate a steady volume of unassigned driving time records every month, particularly at fleets with active shops and yards. These records originate from vehicle telematics when the engine is running and the truck is moving without an active driver duty status. Left unresolved, they create compliance risk under FMCSA Part 395, distort HOS calculations, and trigger unnecessary violations during audits.
Strong Tower Consulting designs automated reconciliation architectures that correlate geofence events, maintenance work orders, yard move authorizations, and personal conveyance declarations. The goal is to resolve automatically only the records the evidence supports, route the rest to a reviewer, and produce defensible audit trails that reference specific SQL records across your TMS, telematics platform, and shop system. Each carrier should measure its own automation rate and reviewer workload against a manual-review baseline during a pilot.
- Unassigned driving time distorts HOS, driver settlement, and IFTA reporting when left unresolved.
- Hierarchical geofences separate shop zones, yard areas, fuel islands, customer facilities, and personal conveyance corridors.
- Shop movements match to open work orders by vehicle number, timestamp window, and technician badge.
- Every automated assignment records its source data, confidence score, and reference IDs.
- Unified reconciliation views join TMS, telematics, and shop systems on standard vehicle and driver identifiers.
The Business Impact of Unassigned Driving Time
Unassigned driving time creates multiple operational and financial problems. It inflates apparent on-duty not-driving time, distorts driver settlement calculations, and complicates IFTA fuel tax reporting. When an ELD records movement without a linked driver log, the carrier has to review it and either assign it to the correct driver or annotate why it cannot be assigned. Records left unresolved can surface as audit findings or be misattributed to a driver's hours.
Common sources include:
- Mechanics moving trucks between service bays
- Yard jockeys and hostlers performing internal moves
- Drivers using personal conveyance without proper annotation
- Technicians performing pre-trip or post-trip movements
- Terminal staff repositioning equipment
| Category | Resolving Evidence | Compliance Risk |
|---|---|---|
| Maintenance Shop Moves | Open work order on the unit, shop geofence, technician badge | Low |
| Yard Repositioning | Yard move authorization in the TMS, terminal geofence | Medium |
| Personal Conveyance | Driver PC declaration in the ELD, written carrier PC policy | High |
| Unknown / Unresolved | None found automatically; routed to a reviewer | Critical |
Geofence Event Correlation Architecture
The foundation of automated reconciliation is precise geofence management. Strong Tower designs hierarchical geofence sets that distinguish between shop zones, yard areas, fuel islands, customer facilities, and personal conveyance corridors. These geofences are stored in a normalized SQL schema and cross-referenced with telematics pings in real time.
When a vehicle begins moving without an assigned driver, the system evaluates:
- Current geofence membership at ignition-on
- Duration and path of movement
- Cross-reference to open maintenance work orders in the shop system
- Recent yard move authorizations from the TMS (Truckmate, McLeod, or TMW)
- Driver personal conveyance declarations from the ELD API
Maintenance Work Order Cross-Referencing
Integration with shop management systems is critical. Our architecture pulls mechanic work orders via SQL views or API and matches them to unassigned driving segments using vehicle number, timestamp windows, and technician badge data. When a mechanic logs a repair on a specific unit, all subsequent movements within the shop geofence during the repair window are automatically assigned to that work order.
assign segment s to work order w when
s.vehicle = w.vehicle
s.start >= w.repair_start and s.end <= w.repair_end
s.geofence = shop zone
This eliminates the common problem where a technician test-drives a truck after service and the ELD records unassigned driving time that later appears as a violation on the driver's record.
Automated Assignment Heuristics for FMCSA Part 395
Our decision engine applies layered heuristics designed to support FMCSA audit review. Each assignment records the source data, confidence score, and reference IDs from the originating systems. The resulting audit trail includes direct links to:
- EDI 214 status updates when applicable
- Driver settlement records
- Maintenance work order IDs
- Yard move authorization logs
- Geofence definition versions
Rules are configurable by fleet and can incorporate business-specific logic such as detention time calculations, fuel surcharge validation, and driver escrow accounting considerations.
Do
- Store hierarchical geofences in a normalized SQL schema
- Match shop moves on vehicle number, timestamp window, and technician badge
- Record source data, confidence score, and reference IDs on every assignment
Avoid
- Leaving unassigned records unresolved until an audit
- Personal conveyance without proper annotation
- Assignments with no link back to the originating system
Metrics to Track in a Reconciliation Pilot
Capture a baseline month of manual review before automation is switched on, then compare each metric against that baseline.
| Metric | How to Measure | Source System |
|---|---|---|
| Automation rate | Records resolved automatically divided by total unassigned records in the period | ELD unassigned driving report, reconciliation log |
| Reviewer hours per month | Staff time spent reviewing and assigning records, before and after | Time tracking or review queue timestamps |
| Override rate | Automatic assignments later reversed by a reviewer divided by automatic assignments | Reconciliation log audit trail |
| Unresolved at month end | Count and total duration of records still unassigned and unannotated | ELD unassigned driving report |
| Audit packet completeness | Resolved records carrying every required source reference divided by resolved records | Reconciliation schema, shop and TMS reference IDs |
Implementation Considerations for Common TMS Platforms
The architecture applies to Truckmate, McLeod Transportation Management, and TMW Suite. Each requires specific SQL schema knowledge and understanding of how these systems store driver logs, movement records, and settlement data. For carriers running multiple systems, we create unified reconciliation views that join across disparate databases using standardized vehicle and driver identifiers.
Frequently Asked Questions
How does the system distinguish between yard moves and personal conveyance?
The engine uses both geofence membership and driver intent signals. Yard moves are typically short duration movements that begin and end within terminal geofences and are often linked to a yard move authorization record in the TMS. Personal conveyance declarations are explicitly entered by the driver through the ELD and must comply with the carrier's written policy. The system records the exact matching criteria used for each assignment.
Can this integration work with our existing ELD and telematics provider?
Yes. Our architecture is provider-agnostic and works with Samsara, Geotab, Omnitracs, KeepTruckin, and most major ELD platforms through their respective APIs or data exports. The key is establishing reliable vehicle and timestamp alignment between the telematics feed and your internal operational systems.
What audit documentation does the automated system produce?
Every reconciled record generates a permanent audit packet containing the original telematics ping data, the matching criteria (geofence, work order, yard authorization, or driver declaration), confidence score, and direct SQL references to source records in your TMS, shop system, and ELD database. The packet is designed to support the carrier's supporting-document and unassigned-driving review obligations under Part 395; confirm specific retention requirements with your safety manager.
How does this affect driver settlement and fuel tax reporting?
Proper classification prevents unassigned time from incorrectly appearing in driver on-duty calculations, which protects both driver pay accuracy and IFTA state mileage allocation. The system can also feed corrected records to your transportation accounting integration for accurate fuel surcharge and detention calculations.
Our independent systems architecture and technology advisory services help motor carriers, freight brokers, and private fleets implement robust, audit-ready solutions without vendor lock-in.
Clear unassigned driving time before the audit.
Strong Tower Consulting provides independent systems architecture, feasibility audits, and engineering roadmaps for motor carriers and freight brokers. Contact our advisory team or call 763-244-1373 to discuss your operational data and evaluate practical implementation paths for your fleet.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Founded in Minnesota in 2008 by Scott Elliott, we have been serving the transportation industry for more than 18 years.