How Automated Trucking Differs From Robotaxi Development

An automated truck cruising a highway and a robotaxi navigating downtown traffic can look, from a distance, like the same technology pointed at two different markets. Up close, the bet each one is making is different.

Automated trucking developers generally aim for a highway-only operating domain: limited-access roads, on-ramps and off-ramps, far fewer intersections and virtually no pedestrians compared to a city street. That narrower domain cuts out a large share of the hardest problems in urban perception and planning, unprotected turns, crosswalks, cyclists, double-parked delivery vans, simply by not attempting to operate where those problems live. A truck merging onto an interstate is dealing with a much smaller and more predictable set of possible situations than a robotaxi turning left across three lanes of city traffic with a cyclist filtering up alongside it.

The cost of that simplification shows up at both ends of the route. The tradeoffs cut both ways. Many proposed trucking models still need a human driver for the "last mile" legs, getting a trailer off the highway and into a depot or yard, because that portion of the trip reintroduces exactly the kind of complexity the highway-only design was built to avoid. Every proposed fix for that gap, a relief driver waiting at a transfer hub, a separate short-haul carrier, a fully automated yard, adds its own cost and its own operational complexity back into a business case that looked simpler when it was confined to the highway portion alone.

Trucking has also produced technology proposals distinct from full autonomy that don't have a clean robotaxi equivalent. Platooning, multiple trucks travelling in a tight, computer-coordinated line so trailing vehicles draft off the lead truck's wake and burn less fuel, was pitched years ago as a lower-risk, incremental step that didn't require solving driving end to end at all. It has not become the industry's dominant approach, partly because the fuel savings depend on maintaining a following distance many drivers and regulators are uncomfortable with at highway speed, and partly because it addresses a narrower problem, fuel cost, rather than the labour cost that full automation targets. It remains a useful example of how trucking's technology roadmap has branched in directions urban robotaxi development never needed to consider.

Jurisdiction adds a wrinkle that a metro-confined robotaxi service doesn't face in the same way. A long-haul truck routinely crosses state and sometimes national lines in the course of a single trip, which means its automated-driving permit, or the patchwork of rules it has to satisfy, needs to hold up across multiple regulatory regimes rather than one city's or one state's framework. A robotaxi service can grow its footprint by adding one metro area at a time, negotiating with a single regulator per market. A cross-country automated truck route doesn't have that luxury; it has to satisfy every jurisdiction it passes through on the same trip.

That's a structurally different bet from point-to-point urban robotaxi development, which has to solve the harder problem end to end rather than handing off the messy parts to a human. It's part of why trucking-focused programmes and urban robotaxi programmes have ended up on different regulatory and deployment timelines rather than converging toward the same milestones on the same schedule. Volvo AB, a D20 constituent with a long-haul trucking business, has taken this highway-first approach directly, an approach detailed further in the look at Volvo's truck-autonomy programme.