Crossing the Chasm
At Pasadena Freight Solutions, a fictional mid-sized carrier in California, there are two people who should talk more often, but don't. Sandra runs safety and compliance. Terry runs the maintenance program. Sandra's world is CSA scores, HOS violations, audit readiness. Terry's world is uptime, repair costs, and a technician queue that is currently two people short. Their responsibilities are treated as different realms, intersecting every once in a while, usually when a vehicle gets into an accident. They're both almost always in firefighting mode; the fires just never feel like they're in the same building.
Pasadena Freight is a fictional company, but the situation - safety and maintenance operating as two siloed functions - is very real and plays out at trucking fleets all over the country. It matters more than most people in the industry have been willing to say directly, because the gap between those two functions is often where the earliest safety signals in the chain get lost.
The Divide
Safety and maintenance are organizationally separate in most fleets above a certain size, usually around 100 trucks. They have separate reporting lines, separate software, separate KPIs. Safety is measured on lagging indicators: what happened, what was reported, what score the fleet got. Maintenance is measured on parts, labor, throughput, and cost. The incentives don't naturally align - often they're actively at odds - and nobody has formally made either function responsible for the space between them.
That space is where a significant amount of operational risk accumulates.
A vehicle defect doesn't start as a CSA violation. It starts as something a driver notices or feels in the cab. This could be a pull, a softness, a sound. It becomes a DVIR and lands in the shop as a work order. A technician looks at it, can't reproduce it, and clears it so it goes back out. Three weeks later it's a roadside inspection failure. Six weeks later it's in the carrier's BASIC score. Six months later it's in a plaintiff attorney's discovery request.
Sandra sees the BASIC score, Terry saw the work order but at Pasadena and beyond, nobody connects the patterns between them.
The DVIR is the Bridge
The DVIR is the one artifact that has to travel between these two worlds. In theory it is the connective tissue; a driver finds a defect, maintenance resolves it, safety has a record. In practice it is a compliance document doing a job it was never designed for.
Most fleets now have the integration. The DVIR, whether done in Samsara, Motive, Whip Around, often flows from the driver's tablet into the shop management system automatically now.
But the DVIR was designed as a loop: report, repair, resolve, move on. It was never designed as a ledger and functionally, has no memory.
What travels: the complaint, in whatever language the driver used at 4:47 a.m. while sitting in a dock in Long Beach. What doesn't travel: that this is the third brake complaint on this unit in sixty days. That the prior two work orders both say "unable to reproduce." That the telematics logged an ABS anomaly the same morning. The technician who replaced a caliper on a similar unit last month mentioned to the shop manager - in passing, not in any system - that the rebuilt parts from the secondary supplier didn't feel right to him. Three brake DVIRs across 45 days on the same tractor should not behave like three unrelated events but in many fleets, they do.
The integration moves the complaint but doesn't move the context. The technician opens a work order, not a case file. He sees today's problem, not the pattern and so the truck goes back out.
The Work Order as a Safety Signal
BASIC scores are built from roadside inspection data. A problem has to make it all the way to a roadside event before it appears in the carrier's public safety profile. By the time it shows up there, it has already happened on the road.
The maintenance record is often weeks or months upstream of that. The DVIR pattern, the recurring complaint, the deferred repair; that is the signal that a vehicle may be trending toward failure. It is earlier than anything the regulator captures. It is earlier than anything a broker checks. It is earlier than anything a plaintiff attorney will eventually find in discovery.
Plaintiff attorneys in nuclear verdict cases pull maintenance records as a matter of course. DVIRs, work order histories, deferred repairs, recurring complaints cleared without resolution. The question they are building toward is simple: did you know, or should you have known?
Three brake complaints in sixty days, each cleared individually, is a pattern that was knowable. The data existed, just never in the same place at the same time, in front of anyone whose job it was to look at it as a safety signal rather than a queue item.
The maintenance department saw the signal first but nobody connected it.
Montgomery Changed the Stakes
On May 14, 2026, the Supreme Court ruled 9-0 in Montgomery v. Caribe Transport II, LLC that freight brokers can be sued under state negligence law for negligently hiring unsafe carriers. The ruling is written about brokers, but follow the chain backward and it lands in the shop.
Brokers now face greater liability around what a carrier's BASIC score showed at the time of dispatch. The vehicle maintenance BASIC, one of the seven categories regulators track, is built directly from roadside inspection failures: brake defects, out-of-service orders, the inspection record of individual vehicles. Which means the legal exposure brokers are now scrambling to document their way around is, at its origin, often a maintenance problem that started in the shop months before any broker touched the load.
The "should have known" standard that Montgomery crystallized for brokers is the same standard plaintiff attorneys have been applying to fleets in nuclear verdict cases for years. The maintenance record, the DVIR history, the work orders, the technician notes, is always in discovery. It has always been the evidence of what the fleet knew and when. The ruling did not change that but it has raised the temperature on the entire environment around it.
For now, the tools brokers use to vet carriers are entirely backward-looking: what the inspection record shows, what the BASIC score reflects, what the crash history says. The carrier that figures out how to make its internal maintenance quality externally legible will be in a very different commercial conversation entirely. That infrastructure doesn't exist yet.
Fixing the Signals
Sandra does not need another dashboard showing her what the BASIC score is. She needs to know what Terry knows. Terry does not need more work orders in a queue. He needs to know which three of the nine actually matter today, and why.
The gap between these two functions has been treated as a communication problem, solvable with better meetings or shared software. It is not. It is a signal interpretation problem. The data exists across both worlds. What is missing is anything that connects it, reads it as a pattern, and surfaces it in a form that either person can act on before the truck is already on the road. The industry digitized maintenance paperwork as step one, but never operationalized the signals inside it as step two.
The maintenance record has always been one of the earliest safety signals in the chain. The industry just hasn't been reading it that way. By the time a safety issue becomes visible to regulators, brokers, or juries, the maintenance department has usually already seen it coming.
Axle Mobility is the system of execution for fleet repair and maintenance, so techs, fleet managers and fleet + service executives can focus on rolling trucks and making money, not mindless admin.