AI ELD
Apr 27, 2026
.webp)
Team driving is one of the most productive operating models in trucking. Two drivers, one truck, continuous movement. When the compliance side runs cleanly, a team can cover 1,000 miles in a single operational day without either driver approaching a violation. When it does not run cleanly, the same setup generates more ELD errors per mile than almost any other configuration.
The reason is straightforward. A solo driver is the only person interacting with the ELD. A team operation has two drivers, two sets of HOS counters, one device, and a handoff sequence that must be executed correctly every time one driver stops and the other starts. The errors that result from a missed step are not always visible on the day they occur. They surface during a roadside inspection, a log audit, or a compliance review, and at that point the fleet manager is looking at a violation record that could have been prevented with a login step that took thirty seconds.
This article covers what the FMCSA regulations and ELD technical specifications actually require for team operations, what specifically goes wrong during co-driver handoffs, what an inspector sees when reviewing a two-driver log, and how the 2026 HOS pilot programs interact with team driving schedules.
Every driver in a team operation must have a separate, authenticated ELD account. This is not a procedural recommendation. It is a technical requirement under the FMCSA ELD rule. The device must maintain individual records for each driver linked to their specific credentials, and those records must be separable for roadside inspection and data transfer purposes.
At any moment during a team operation, the ELD recognises two driver states: the active driver and the inactive driver. The active driver is the one currently logged in as driving or on-duty. The inactive driver is the co-driver who is resting, typically in the sleeper berth. Both drivers are authenticated on the same device simultaneously, and both are generating records during that time, which is the detail most solo-driver ELD users find counterintuitive when they first encounter team operations.
The regulatory basis for how automatic driving detection works in a team operation is in the FMCSA ELD technical specifications. Under a standard solo operation, the ELD must automatically change the driver's duty status to driving when the vehicle exceeds the 5 mph threshold. In a team operation, that automatic trigger has a specific exception: when the inactive driver has logged into the ELD and is in sleeper berth status, the ELD does not automatically switch them to driving when the vehicle moves. Instead, the device records intermediate location and movement data against the inactive driver's log without attributing driving time to them.
This exception is the entire foundation of legal team driving under the ELD mandate. If the inactive driver is not correctly logged in with sleeper berth status before the vehicle moves, the exception does not apply. The ELD then processes vehicle motion according to its standard rules, either attributing driving time incorrectly or generating an unassigned driving event. Both outcomes require administrative correction and both appear on the carrier's compliance record.
The co-driver handoff is the moment of highest compliance risk in a team operation. Both drivers need to complete their portion of the status change before the truck moves under the new active driver, and the sequence must happen while the vehicle is stationary.
FMCSA rules and ELD technical specifications confirm that drivers cannot switch driving roles on the ELD while the vehicle is in motion. The handoff requires the vehicle to be stopped, the outgoing active driver to change their status to sleeper berth or off-duty, and the incoming active driver to log in and set their status to driving before any movement begins. Co-drivers can make entries and edits to their own records while the vehicle is moving, but the role switch itself must happen at a stop.
In practice, the handoff sequence that generates violations is almost always a timing failure rather than an intentional shortcut. The outgoing driver parks, the incoming driver gets settled, and one of three things goes wrong. The incoming driver starts moving before completing the login sequence, generating unassigned driving from the moment of first movement. The outgoing driver falls asleep without switching to sleeper berth status, so the device records them as on-duty while the other driver is also on-duty, producing a dual on-duty overlap that flags as a potential log falsification. Or the inactive driver's sleeper berth status is not set before the truck moves, removing the automatic driving exception and creating an erroneous driving record against the resting driver.
The ELD unidentified driving guide covers what happens when handoff errors result in unassigned driving events across the fleet and how the resolution process works when those events accumulate. For team operations specifically, the pattern is almost always the same vehicle generating repeated unassigned events during the same driver transition window, which points to a procedural problem at the crew level rather than a device problem.
Understanding what the ELD records for both drivers simultaneously is what allows a safety coordinator to audit a team operation effectively and what allows an inspector to identify problems during a roadside check.
The active driver's log records driving time, duty status changes, location at each status change, and the full HOS counter state throughout their shift. This is identical to a solo driver log in structure.
The inactive driver's log records something more nuanced. During the period when the inactive driver is in sleeper berth status and the vehicle is moving, the ELD records intermediate data against the inactive driver's log: location at the start and end of the sleeper period, total miles accumulated during the sleeper berth period, and the engine hours recorded during that time. These intermediate records appear in the data file that transfers to an inspector. They document the inactive driver's whereabouts and confirm that the sleeper berth exception was properly applied during the period when the other driver was actively driving.
The sleeper berth provision that makes team driving work under HOS regulations is covered in depth in the complete guide to HOS rules for truck drivers. For team operations specifically: when a driver uses the sleeper berth correctly, their 14-hour driving window pauses for the duration of that rest period. This allows a team truck to run continuously while each driver accumulates compliant rest time in the berth. The AI ELD logbook tracks both drivers' HOS counters simultaneously, showing each driver's remaining hours in real time regardless of whether they are currently active or resting.
When a team truck is stopped for inspection, the ELD display and data transfer requirements differ from a solo operation in one specific way that affects how the inspection proceeds.
The inspection header on the ELD display must show the current co-driver's information, not just the active driver's. If a co-driver has been active during the record retention period being reviewed, they appear in the user list of the data transfer file. An inspector reviewing a team operation has access to both drivers' logs simultaneously from the same transfer file, and they are looking at the relationship between the two logs rather than each log in isolation.
For full detail on what the transfer process looks like and what inspectors specifically request at a Level 1 inspection, the ELD roadside inspection guide covers the standard sequence. For team trucks specifically, inspectors look for three things beyond the standard solo-driver checks.
First, whether both drivers' on-duty periods overlap at any point. An overlap suggests either a handoff error or deliberate log manipulation. Second, whether the inactive driver's sleeper berth periods are recorded with the corresponding intermediate movement data, which confirms the automatic driving exception was applied correctly. Third, whether the handoff locations correspond to plausible stopping points given the trip pattern. A handoff that appears at a location where no fuel stop, rest area, or facility exists draws scrutiny in the same way an implausible solo driver log stop does.
For fleets running team drivers, the fleet compliance dashboard shows both drivers' logs side by side rather than requiring the safety coordinator to pull each record individually. Seeing the two logs together makes handoff sequence errors visible immediately, before they become inspection findings. A coordinator who reviews team logs the morning after each run can catch and annotate errors within the 7-day editable window, which eliminates most compliance exposure before any inspector reviews the same records.
The FMCSA launched two HOS pilot programs in spring 2026 as part of its Pro-Trucker Package: the Flexible Sleeper Berth pilot, which expands available split options to include 6/4 and 5/5 combinations in addition to the existing 7/3 and 8/2 splits, and the Split Duty Period pilot, which allows drivers to pause the 14-hour window by taking off-duty breaks that do not count as sleeper berth time.
Both programs affect team operations, and the compliance implications for team trucks are more complex than for solo drivers. The Flexible Sleeper Berth pilot changes the minimum sleeper period for participating drivers from 7 consecutive hours to 5 consecutive hours under the most flexible configuration. For a team operation where the inactive driver's sleeper berth period determines when their 14-hour window resumes, a shorter minimum sleeper period changes both the scheduling flexibility and the compliance verification burden. The ELD must be configured to recognise the pilot-specific duty status combinations, and the carrier must be enrolled in the program before any driver uses the new splits. Using a 6/4 split on an ELD that is not configured for the pilot generates a false violation automatically.
The Split Duty Period pilot cannot be combined with sleeper berth periods. A driver using the sleeper berth as part of a team operation cannot simultaneously use the Split Duty Period provision to pause the 14-hour clock. The two provisions are mutually exclusive within the same duty cycle. Teams where one driver attempts to combine them create a compliance error that the ELD records accurately and that an inspector identifies without difficulty.
Both programs require formal enrollment through the FMCSA pilot program portal. For team operations evaluating whether the scheduling flexibility justifies the enrollment and ELD configuration overhead, confirming that the ELD platform supports the new duty status combinations before any driver attempts to use them is the first step.
The fleets that run team operations without recurring ELD violations are not doing so because their drivers are more careful in isolation. They are doing it because the dispatch and scheduling process accounts for the handoff sequence and builds enough time into each stop for both drivers to complete their status changes before the truck moves.
When a team operation generates the same handoff error repeatedly on a specific route, the fix is almost never additional driver training. It is a dispatch scheduling change that extends the handoff window, or a route adjustment that places the handoff at a location where the stop can be completed properly rather than at a roadside point where one driver is rushed into the seat.
For fleet managers overseeing team operations across multiple trucks, the AI ELD monitoring plan covers overnight and weekend periods when no one in the office is watching the dashboard. When a handoff generates an unassigned driving event at 3 in the morning, the monitoring team flags it for the safety coordinator before the driver reaches the delivery and before the error solidifies into a compliance record that cannot be corrected. For team operations that run continuously, that coverage interval is the one that matters most.
If you want to see how AI ELD handles co-driver account setup, the dual HOS counter display, and the automatic handoff prompts before committing to a full fleet rollout, start a free 14-day trial and run both drivers through a complete operating cycle on real trucks.
FMCSA. ELD Technical Specifications, Section 4: Functional Requirements. Primary source for the inactive driver exception to the 5 mph automatic driving trigger in team operations: the ELD must not automatically change an inactive driver's status to driving if they are logged in and in sleeper berth status during a team operation. Source for intermediate recordings on the inactive driver's log during sleeper berth periods, and the inspection header co-driver requirement. https://eld.fmcsa.dot.gov/Developer
FMCSA. "Frequently Asked Questions: ELD Technical Specifications." Source for the specific rule that co-drivers cannot switch driving roles on the ELD while the vehicle is in motion, that co-drivers can make entries and edits to their own records while the vehicle is moving, and the co-driver header requirement in the inspection display and data transfer file. https://eld.fmcsa.dot.gov/FAQ/Topics?name=ELD_Technical_Specifications
FMCSA. "Hours of Service of Drivers: Pilot Program to Allow Commercial Drivers to Split Sleeper Berth Time." Federal Register, September 2025. Primary source for the Flexible Sleeper Berth pilot program introducing 6/4 and 5/5 split options, the enrollment requirement before any driver uses new configurations, and the mutual exclusivity of the Split Duty Period and sleeper berth provisions. https://www.federalregister.gov/documents/2025/09/17/2025-17939/hours-of-service-of-drivers-pilot-program-to-allow-commercial-drivers-to-split-sleeper-berth-time
FleetRabbit. "FMCSA HOS Pilot 2026: Flexible Sleeper Berth and Split Duty Guide." March 2026. Source for spring 2026 launch of both pilot programs under the Pro-Trucker Package, confirmation that the two provisions are mutually exclusive within the same duty cycle, and the ELD firmware update requirement before implementing new split configurations. https://fleetrabbit.com/blogs/post/fmcsa-flexible-sleeper-berth-split-duty-period-pilot-hos-2026
FMCSA. "What Rest Periods Qualify for the Split Sleeper Berth Provision?" Regulatory guidance confirming the 7/3 and 8/2 split options under 49 CFR 395.1(g)(1) and the 14-hour window pause mechanic during both qualifying sleeper periods in team operations. https://www.fmcsa.dot.gov/regulations/hours-service/what-rest-periods-qualify-split-sleeper-berth-provision
FTSGPS. "ELD Resource Center: HOS, AOBRD, FMCSA, DOT." Source for the specific rule that co-drivers cannot switch driving roles while the vehicle is in motion, and that drivers may make entries and edits to their own records while the vehicle is moving. https://www.ftsgps.com/eld-resource-center/
HOS247. "ELD for Team Drivers: Rules, Top Providers and Best Practices." May 2025. Source for the characterisation of driver handoffs as the most common compliance challenge in team operations, and the confirmation that each driver must have their own login credentials in a team ELD configuration. https://hos247.com/resources/eld/eld-team-drivers/