REAL-TIME DATA = REAL-TIME LIABILITY?

Another interesting session at TMC involved the increasing use of in-cab cameras to monitor driver behaviour, but also to help assess fault in the event of a crash.

Rob Moseley, a lawyer with Smith Moore Leatherwood LLP, noted that the real-time data generated by these cameras will soon result in real-time liability responsibility. The courts, Moseley said, will have an expectation that fleets identify a driver who’s having a bad day – maybe he’s departed from his lane a few times – and then intervene to get that driver off the road.

This poses a conundrum for fleets. If you don’t have the resources to manage the data generated by in-cab cameras in real-time, are you better off not having the cameras installed at all? Moseley doesn’t think so.

“If I’m defending an accident case, I want as much information as I can get,” he said. “Where we have video is one place a jury can’t speculate. We want to wall of as many of those areas of speculation as we can, because that’s where these runaway verdicts come from.”

Still, he did warn that we are moving towards an expectation within the hyper-litigious US where it will be incumbent on fleets to manage driver performance in real-time when such data is available to them.

“We’re getting to the point where you’re going to be held responsible for stopping a driver who’s having a bad day,” he said. “We’ve got real-time opportunity, soon we’re going to have real-time liability if we’re not stopping drivers.”

I’ll have more on this topic in an upcoming issue. Stay tuned!

Avatar photo

James Menzies is editorial director of Today's Trucking and TruckNews.com. He has been covering the Canadian trucking industry for more than 24 years and holds a CDL. Reach him at james@newcom.ca or follow him on Twitter at @JamesMenzies.


Have your say


This is a moderated forum. Comments will no longer be published unless they are accompanied by a first and last name and a verifiable email address. (Today's Trucking will not publish or share the email address.) Profane language and content deemed to be libelous, racist, or threatening in nature will not be published under any circumstances.

*