Trucksafe LIVE! Virtual EventFree

Trucksafe LIVE! | Ep. 56 - The Great ELD Purge of 2025?

Thursday, December 4, 2025 at 1:56 PM EST
Trucksafe LIVE! | Ep. 56 - The Great ELD Purge of 2025?

About This Event

We break down FMCSA's newly announced overhaul of the ELD self-certification process.

Watch the Recording

Episode Summary

In episode 56 of Trucksafe LIVE!, hosts Brandon Wiseman and Jerad Childress discuss FMCSA's announcement of a major overhaul to the electronic logging device (ELD) self-certification process, joined by special guest Tom Cuthbertson, a former lead for corporate regulatory compliance and industry relations with a large ELD manufacturer and a key stakeholder in the original ELD mandate. The announcement, which came on December 1, 2025, signals a more rigorous vetting process for ELDs before devices are added to FMCSA's registered list — a significant development for fleets that rely on these devices to remain compliant with federal hours-of-service requirements. Tom walks through the history of the current self-certification process, explaining that while FMCSA established a reasonable framework at the outset of the ELD mandate, enforcement of that framework has grown increasingly lax over time. With over 2,400 devices currently on the registered list, Tom notes that a substantial number of entries are incomplete, lack required technical documentation, or represent white-labeled copies of other devices — including some that have already been revoked. He explains that FMCSA has involuntarily revoked approximately 68 devices to date, with roughly 307 total revocations when including self-revocations, and describes the agency's process of notifying non-compliant vendors and providing a 60-day window to demonstrate corrective action before revocation. A major concern raised is the emergence of "chameleon" ELD vendors — bad actors who simply re-register revoked devices under new names, exploiting gaps in the current system that the new vetting process aims to close. The hosts and Tom contrast the U.S. self-certification approach with Canada's third-party certification model, which requires independent lab testing including live vehicle assessments and costs approximately $40,000 to $50,000 per device. While acknowledging that third-party certification in the U.S. could drive up costs and reduce the number of available devices, Tom suggests a practical middle ground: requiring applicants to submit a compliant electronic record of duty status (EROD) file as part of the registration process. He argues that running a submitted EROD file through FMCSA's existing validator would take only a few hours of staff time but would provide a meaningful baseline check on whether a device is actually capturing the required data elements, including malfunctions, unidentified driver segments, and compliant editing records. The episode also touches on several other industry developments, including a federal court agreeing to hold in abeyance a lawsuit challenging FMCSA's interim final rule on non-domicile CDL issuance to foreign-resident drivers while the agency reviews over 8,000 public comments, and a new ATRI report updating its 2020 nuclear verdict study. The ATRI report finds that allegations related to organizational failures — particularly substance abuse — now carry the heaviest financial multipliers in litigation, with substance abuse allegations associated with a 340% increase in total jury awards. The hosts emphasize that missing drug and alcohol testing windows or failing to have a compliant testing program can open the door to those allegations regardless of the circumstances of an underlying accident. Fleet safety professionals should take note of several actionable points from this episode. Carriers should verify that their current ELD appears on FMCSA's active registered list and monitor for any revocation notices, keeping in mind that a revoked device requires replacement within 60 days. Fleets seeking greater confidence in their device's compliance may benefit from independent third-party testing, which the hosts and Tom describe as involving in-vehicle testing, back-office review, and user experience evaluation. On the drug and alcohol side, ensuring that testing windows are met, reasonable suspicion training is current, and policies are fully compliant remains one of the most critical risk management steps a carrier can take to guard against catastrophic litigation outcomes.

Full Transcript

Heat. Heat. [bell] Yeah. Yeah. Oh. Hey. Hey. If you're like us, you're probably tired of flipping through outdated and expensive regulation books and struggling to understand the rule or guidance you're after. E-Riggs is the first web and mobile app version of the federal motor carrier safety regulations, helping fleets of all types and sizes better access and understand their regulatory obligations. Is always upto-date and allows fleet safety professionals to not only read the rules, but also dig into FMCSA guidance and learn more about complex regulatory topics from industry experts. Highlight, bookmark, and take detailed notes right from the app and access them on any of your devices and easily share a digital version of the regulations with your drivers so that they too can better understand the rules. Was developed by safety professionals for safety professionals. app. All right, everyone. Welcome to episode 56 of Truck Safe Live, show where we and our guests tackle the hot button issues impacting highway transportation. I'm Brandon. That's Jared. We're with Truck Safe and Children's Law, both of which are dedicated to helping motor carriers develop and maintain cutting edge safety programs. Jared, what's up? Not much. Thanks everybody for joining. Good afternoon. Yeah, thanks for tuning in. If you're here with us live, say hey in the comments so we know who's around. Um, got a lot in store for this episode. Excited about it. We have a special guest coming on with us to talk about uh this topic. There's been a lot of breaking news this last week or two u from an FMCSA regulatory standpoint. So, a lot to cover uh on this particular show. We're here to talk about EL self-certification electronic logging device and the announcement that came down on Monday of this week, uh early December 2025 if you're watching later. And uh it's it has the potential to kind of change the game when it comes to certification of these types of devices, but maybe not as dramatically as some had hoped. But uh we'll get into the details of that here in a minute. Before we do, first up, want to say thanks to the sponsor of this episode, which is Project 61. It aims to improve the life expectancy of CDL drivers by raising awareness, providing resources, and educating drivers on healthier lifestyle. org. Thanks to those guys. Um, few things going on at TruckSafe and in the industry that we'll kick things off here uh with. First up, if you're not a member of the trucksafe network already, I'd encourage you to join it. com or scan that QR code and download the app in the App Store or the Google Play Store. Uh this is the space we've built for fleet safety professionals to gather together, learn from one another, ask questions, and also access all of our DOT related content. Great resource if you are in fleet safety and compliance. Hope to see you there. Um and then I'll just mention our newsletter. If you need a resource for staying up to speed on all of these developments, uh including those, like I said, that we've seen over the last couple of weeks, our newsletter is a great resource for that. comsubscribe is where you can subscribe to it and uh we'll send you the latest news and our analysis of it and it's also where we send out uh all of our content and um discounts on our in-person conferences and all of that fun stuff. com/subscribe is where you can do that. Um, few things going on in the industry. First up, Jared didn't get to join me, but Rob and I um just finished up our uh we attended the American Toomen Conference in Baltimore, Maryland, largest tow show for towing companies. Um it was it was a pretty good event. next time we uh next time we go go to Baltimore in the winter. You were muted during the whole video, just so you know. Oh, okay. we missed your narration of the clown truck and all that. All right. Well, I I did have a lot to say, but uh yeah, sorry for that. Anyway, to show was great. Got to meet a lot of great people. Um, it's an industry that we don't do a ton of work in. We've got some towing company clients, but um, yeah, if we met you there, it was good to meet you and, uh, yeah, definitely check that out if you are even tangentially involved in in towing or anything like that. Great show to go to. Um, another industry newsworthy article that I saw come through. Uh we've talked about this on a couple of past shows, but uh there has been an update to it. I don't know why that keeps muting me. Um long story short, FMCSA came out with an interim final rule. Folks will remember this uh a couple months ago that cracked down on the issuance of uh these non-domicile CDLs to to [clears throat] uh foreign resident truck drivers. And that got a lot of blowback from certain advocacy groups and also drivers who lost their licenses because of it. And that resulted in a federal lawsuit that was filed. Uh again, we've got a whole show where we discuss that lawsuit, but the latest news on this issue specifically, I thought this was interesting, Jared. So, this just came out uh yesterday. The [clears throat] federal court granted the Trump administration's request to hold that lawsuit in obeyance while the FMCSA goes back and reviews the 8,000 comments that were filed in response to the interim final rule. So the TR so FMCSA itself is asking the court to hold the case in abance. In other words, holding the rule non-effective, ineffective until the agency itself can go review those 8,000 comments and then potentially change the rule based on the comments received. " So, it essentially lands them in the spot they would have been in had they had just gone through the normal rule making process in the first place. Yeah, it it seems like a good chance to temper the rule a little bit and that way the cases should uh turn out a little better in their favor. But reading all those comments, tempering the rule a little bit, hopefully that ends up with a workable result and so we don't end up with 200,000 less drivers out on the road. Obviously, uh depending on what the final rule says, that could still be a pretty drastic number, but hopefully the rules tempered a little bit so it's workable for everyone. Yeah, we'll have to see. We'll uh we'll keep everybody up to date on that as the news develops. Uh a couple more things here. Uh another story I saw come through It keeps muting me. I don't know why. Uh Atri reported a uh issued a new report on nuclear verdicts. So this is a report that we've referenced a lot over the last several years. actually put out a really good report back in 2020 kind of laying out, you know, the statistics on all of these multi-million dollar jury verdict cases rendered against trucking companies and kind of the contributing factors to them. Well, Atri came out recently, more recently, with kind of an update to that report and um I thought some things were worth noting here. Um this is just an article on freight waves. Uh the Atriy report released on Wednesday found that allegations related to a carrier's organizational failures now carry financial multipliers that exceed most on-road infractions, marking a shift in a plaintiff strategy since the 2020 report on nuclear verdicts. For example, substance abuse or driving while under the influence was the most potential most potent financial multiplier identified which is associated with an expected increase in total awards of 340% when controlling for all other forms of negligence according to Atriy. So really no surprise that uh because this is kind of the the whole concept of those reptile theory of litigation cases anyway that they're really an attack on the carrier's reputation more so than the accident at hand. But this study seems to make clear kind of what we already knew, which is that, you know, despite the circumstances of the case at hand, if you get pulled into one of these lawsuits, your entire reputation, your safety scores, uh, that type of stuff is all going to be brought to the forefront and you're going to be tried on those issues as to whether you are a good carrier or not. Essentially, that's what you have to prepare for. and and uh an interesting kind of spin on some of the wording in that article. Um it's substance abuse allegations. So, it's not necessarily driving while impaired. Obviously, we all know that makes a unqualified driver, right? But if you miss your testing windows, that opens the door for those allegations of substance abuse that was not caught. If you miss your alcohol testing window post accident, so making sure those boxes are all checked. You know, do you have folks trained in reasonable suspicion? Is your drug and alcohol policy compliant? things like that. Um, all really important to combat those substance abuse allegations. Yeah, for sure. Uh, and then the last thing I'll mention, this was another article, and we're actually probably going to have another show on this next week or so. Um, folks probably saw the news already, but if you haven't, FMCSA has announced that they are cracking down on not just EL self-certification, but now also uh the entry-level driving driver training providers, ELDT, and the training provider registry, the folks that are listed on there as essentially self-certified training providers, those that offer the required training for folks that are getting, you know, CDL for the first time or looking to upgrade from a class B to class A, for example. U, those folks have to get uh certain training from folks that are listed on the training provider registry. And no surprise with any kind of self-certification process, it turns out that there's quite a lot of fraud um with people listing themselves on the registry and turning out that they're not putting much effort into training these drivers that end up getting a CDL and and not being properly trained. And so FMCSA came out with an announcement again on Monday, this past Monday, saying that they are cracking down on that. They've already removed 3,000 training providers from the registry and they have 4,000 more kind of in the crosshairs. And so pretty significant um you know enforcement action there against non-compliant training providers. So that's a pretty big deal. and [clears throat] Rob and Brian from the Truck Safe team put together a a pretty good article uh breaking all this down and the systemic problems that they see. Both of them have been training providers in the past and that's on the Truck Safe website if anybody's interested in reading that. But like I said, we're also going to try and have a show with those guys next [clears throat] week, so be sure to tune in to that. You surprised by that news, Jared? Uh I'm not surprised. I think it's a long time coming. think the amount of training providers on the registry was a lot more than anyone anticipated. I was shocked by it. I'm sure FMCSA was as well and so obviously that investigation was a long time coming in my opinion. Were you surprised? No. Tens of thousands of training providers on the registry and uh so this is really just a drop in the bucket. The 3,000 that they've removed uh I think it ends up being about 17%. I saw the news story saying it was 40% but I don't think that's right. I think they were FMCSA in their announcement said that they were looking at 16,000 training providers and then they had removed 3,000 of them which would be 40% of of the 16,000 they were looking at but 16,000 isn't the total number in the registry. There are um I think there are like 17,000 or or some No, not 17. I think there are like 35,000 or something like that. yeah, I was thinking it was close to 40. Yeah, something like that. So, um, still a significant number removed, but not as significant as it seemed at first blush. But in any event, that's another news story that we're going to keep, uh, following and we will let you know any developments that we hear. All right, without any further ado, uh, like I said on today's show, we wanted to touch on one of several breaking news topics coming out of the FMCSA this week, which is its announcement that it plans to tighten the vetting process for electronic logging devices. Uh, ELDs have now been the mandated means of tracking drivers hours of service for virtually all regulated truck drivers and bus drivers since 2019. One of the big driving forces obviously behind the ELD mandate was the belief that these devices would help cut down on log falsification. Um, but unsurprisingly, some nefarious actors in the industry, including certain ELD manufacturers, it turns out, have found ways to exploit the system and bypass the baked in checks and balances, which has led to all kinds of new problems for the FMCSA, which it is now starting to address. And so, excited to have on with us uh on today's show, Mr. Tom Cuffbertson, former lead for corporate regulatory compliance and industry relations with a large ELD manufacturer and also heavily involved with the original ELD mandate. Tom continues to consult on ELD issues with manufacturers and carriers and others on uh on these issues. Tom, welcome. Hey, thanks for having me on. I appreciate it. Yeah, appreciate you coming back. You were one of our first guests that we had on uh our show. Oh, I think it was our second show, second ever Truck Safe Live that you came on and and so yeah, we we always appreciate your insight on these topics. It gets pretty technical uh pretty quickly and uh Jared certainly has more experience on the technical side of these things than I do, but you even more so. So, thanks for taking the time to be with us. Um, I was wondering first of all if you could for folks that may not even be familiar with the current or or the historical self-certification process for ELDs. I was wondering if you maybe you could walk us through that certification process and how FMCSA landed on it originally. Sure. Um, the supplier is responsible for creating an account under FMCSA under the ELD under EL registration process. Uh you first you just make the account. Once you're ready to ask for certification, you have to have a a special pneumonic name for the for your device. It must be software release levels. You have to create a document that says here's how I tested how I created this product. Here's how I ensured that it was compliant. You have to make sure you have a driver manual. You have to have pictures that show the the components and devices that you're supposed to register. Uh I've seen very, you know, I I look at the registration account sometimes and see that the pictures are not really what was required early on. They're they don't show how you hooked to the engine. They don't show the cabling. They show images of the screens and and not a full compliance. So I think there's been some getting a little more lax on the registration process. Um but before you you know it was the early ones I registered was vetted pretty good. You know the picture wasn't quite right they made you redo it. You know if they didn't like your write up right they also put out a document that said here's a testing document that was some 400 pages long. And a lot of us in the early stages tried to go by the outline at least of that document to test the product to ensure that on everything was made on the technical specs. the technical specs for folks not familiar with it are in an appendix to part 395 of the safety regulations. Correct. Right. Yes. There's only 122 pages of technical specs. When you go back and look at the AOPD, the entire regulation was only about five pages. Okay. Yeah. right? Because I was involved with the 39516 before it got thrown to the trash. Anyway, um but I think that they had a good outline initially for self-certification, right? But then over the time it got laxed. So, you know, if you take a look right now, there's a,4 registered devices, okay? that that list. Okay. And I've I've download I download this list periodically just to look at it and see what's going on. Um but you'll see on that list that there is missing commentary. It should be there to say the transfer mechanism. So if you here's an outline so you can see you know you have to say how you're supporting your data transfer, what the malfunctions are, the certification statement. You have to have a a driver card that tells the driver what to do. Should he get a malfunction? How should he report it? How is he supposed to transfer? Whether you're using peer-to-peer or you're doing telematics transfer via email or web services. So, it's it's not a bad outline, but it it's very it's not anywhere near the third party certification process that was initially recommended. Yeah. So, in your example, you found several that were on the self-certified list that didn't have didn't say anything about how their devices transfer the information to law enforcement or anything like that. It was it was rather a large number. I was a little bit shocked. It was about 320 that didn't show any commentary on the registration of what methodology. Yeah. And I'll make a note, there were still eight devices out there that were peer-to-peer only. That I thought was h I don't know. And they were they were as current devices. They weren't under revoked side. They were on the current side. So the options for that are peer-to-peer, cloud-based, and Bluetooth. No, it's it's it's a it's a Bluetooth. It's a it's a USB transfer, a thumb drive. Yeah. But it has to be a certain malware protection thumb drive. Gotcha. All right. The other part of the transfer is you can have Bluetooth but enforcement has to supply their communication thing for a web service transfer. The other side is telematics which means you could do email or you could do web service transfer. Okay. Okay. So you have to pick two from each side. You can't pick one from each because the states the regulatory side was to pick one peer-to-peer and one telematics approach. Yeah. So, so Tom, we we have the self-certification regime. " What was their thinking there? And and how many devices have they ended up with on their market with a third party testing? I I think I think it's upwards like 50 to 60 devices on Canada. I was involved um with that process. I was a stakeholder in Canada as well as the US and we we made sure that it was put together that you just don't do simulator testing in the back office of a lab, right? That that the testing it's not it's not inexpensive. It's in that $40 to $50,000 range for the initial certification. But they also included testing in a live vehicle. So you got real world ECM interaction. You were able to generate more testing processes that would show the real world implementation. So I think they did a fairly good job because all the there was three or four suppliers that could test and each one of them had to have an ISO certification process. So, we've kind of set up the problem here in [clears throat] that, you know, as you said, maybe at the start when FMCSA kind of envisioned this, they had a an at least a kind of, you know, good framework for information that they would receive from folks that are going to self-certify that their devices meet the um the technical specifications, but then maybe over time we're starting to see lacks enforcement with even that self-certification structure. And so I guess the question is what have you seen that lead to in terms of uh you know fraud and and that type of stuff that the FMCSA is starting to take notice of? What I what I've seen is u not that I've been engaged in a lot of of those details because I usually just test certification process to make sure compliance devices are compliant but what I've seen is people are they're not paying attention to the engine component and they're having people do different types of editing and and the fraudulent part comes in too much editing of the wrong type of editing. Right. I I I've seen items where somebody was editing from the back office and there was a drive segment being added. Right. Which is a do. Yeah. Right. The only time you know and you know people don't pay attention to things because they would take personal conveyance and turn it in a drive statement and turn it to personal conveyance. Can't do that. Okay. Uh they actually in the last I'd say year or so put very tight guidance together about that. Yeah. like host transfers, making sure that you because you have to supply at roadside on demand. So, how can you supply on demand if you're waiting for a host to respond 10 minutes later? Okay. right? They unplug it in such a a tight fashion that unless you had supplemental reports that aren't identified in the regulation like a a odometer jump report or a better handle on your unidentified report, you don't know that this was disconnected. Yeah. So those kind of fraud situations going on. From my person, I'm sorry to cut you sorry to cut you off. So from my perspective, I think it has the fraud has kind of developed. but uh now you read stories and we were just looking at one before we jumped on here where you've got offshore actors that are editing logs in the back office and then sending communications to the driver of what story they should tell officers if they get caught with a co-driver. And that it's just crazy how the the lengths to which we've seen these bad actors go. And I you know and a lot of these people are people that don't have any regulatory background. They just read 122 pages of technical specs and started writing on an ELD application. They don't know trucking operations and what goes on. And I've seen stuff where the admin is has almost cart launch editing capabilities which is is not correct. Yeah. And part of the problem too is FMCSA investigates problematic devices. They may revoke a device, but then that device reappears under a different name, same software, same everything. They're focused on Chameleon carriers, but we have Chameleon ELD vendors now. right? because there's there's quite a few number of devices out there that what I coin is white labelled and and I think those are the chameleon ones you're talking about. and break that down for folks that aren't familiar with that term. What what do you mean by whitelabeled? Whitelabeled. So, somebody will go out and create a device and they'll they'll write it to the specs, so to speak, right? so it's a copy of the other device it's just they slap their name on it right so if if they if FMCSA is rigorous like you were describing Jared if they start looking at those chameleon and the white labelled ones. They're going to take chunks of ELDs off off that list. Not like one or two. You might take 15 off. They're going to take the the one that's the problem plus all of its copies, right? Yeah. But just like with regular ELDs, there there are reputable white label out there, right? But there's also bad actor white label out there and that could be a cascading problem, which is the point you're making, and I completely agree. Yeah. So, we looked at the list of registered devices and you'd mentioned Tom, you know, that there had been some revoked. I know you looked at the data. How many have been revoked and generally speaking, for what reasons are you seeing them be revoked? Probably there's only two core reasons, right? There's three there's about 308 devices, maybe 307 that are revoked and and 68 were revoked by the agency. The rest were self-revoked. Now, self-revoke could have been there was pressure put on them to fix things and they got their letter, right, and they couldn't do it in 60 days or they felt we can't make this thing compliant in 60 days, so we're just going to take it off the market and self-revoke, right? right? I don't want to I don't want to take shots at everything that's out there, but I think there's a very large portion when you look at a 2014. There's no way, you know, I've been doing this, like I said, forever. And I don't there's no way all those are compliant. There's and and try to go through them is not going to be that simple. Yeah. And I think we've all kind of noticed FMCSA within just even the last year being more aggressive than they had been over the last 5 years when it comes to involuntarily revoking non-compliant devices. Just curious for folks uh that may be curious as well. What's that process look like uh because I know you both have been through it uh for for some folks or looking at it for some folks. What what's the first step to revoking that the FMCSA takes to revoke? What happens is you get you can have different entities that send information to ELD tech. If too many carriers sell it a thing, hey, this isn't compliant. I can't really rely on this stuff. I've been getting written up at roadside. Then they'll send emails to ELD tech with that stuff. You know, enforcement like you know under CVSA, they have a pretty good you know communication link between each other. So states will see certain common problems. They'll supply it to FMCSA through their own web service because they have their own registry where they can send stuff to FMCSA and say, "Hey, I'm seeing this on the road. " Blah blah blah. Right. And then the other one is that that people don't look at and I and I know Jared and I have have counseledled people to do this is when you register your e-rod files being transferred, you have a section under your account that you can look at the performance of the rod files and see if you're getting errors or failed or rejects, right? And if people don't pay attention at the supplier, when it gets to a certain level, it's like a red flag for FMCSA to go, "Wait a minute. This thing is not working right. I can't get E-ROD transfers. " And one thing that FMCSA did it two maybe three years ago, up until a certain point, if you could you couldn't transfer E-Rods at roadside, there was no infraction. They've changed that. So it's a three-point severity now. Yeah. Unable to transfer. Yep. Right. And if you and even if you transfer and the transfer doesn't doesn't make it through, that's a failed transfer. And you get the if you get error too many errors, which also this registry within your own account tells you and they get that highlight. They're going to look at stuff like invalid sequence numbers, right? Missing powerups, missing engine data, right? Yeah. You can still have a log and be a be submitted to E-Rods, but if you have too many gaps in that data, that's a red flag and they're going to start peeling the onion back to take a look at it. So, for folks who aren't familiar, what's [clears throat] electronic record of duty status transfer? So it and that's where the the technical spec is really built to I would say probably 60 pages of it is dedicated to identifying the file structure and the content of the file that is eight days of logs to be transferred to enforcement at roadside. right to enforcement and they've been doing off-site audits on that that ros. But this is a very detailed file. It shows every duty status, every power up, every login, every malfunction, every unidentified. It'll show how many different trucks the driver drove that day, right? What's what's the entity do number? personal conveyance use? Yard yard move use. Okay. Um edits, edits from the administrator, edits from the driver. Does it show the original and then the edited status? It'll show the file, but if if they want [clears throat] it, you have to show the inactive records. So the inactive records will show what the file what the record looked like before it was edited. Yeah. So all that information is there. It's not necessarily transfer the roadside, but you have to maintain it. Yeah. Because if they wanted to come in and peel the unknown all the way back, it's a lot of data. Yeah. Right. Yeah. And and with some of these bad actors that we've been talking about, I mean, that edit history is there. And so if enforcement decides to dig into edit history and log history and changes that were made, that's how they're going to be able to find it and they'll find it every time. Right. Right. So let's say that one of these complaints gets made or several of these complaints either from law enforcement or from, you know, competitors or drivers or whoever. What's [clears throat] the next step you're seeing FMCSA take once they start to accumulate those? They have a group of x number of people that I've have both both Jared and I have interaction with. And what they will do is they will call the carrier. " Right? Many times, you know, they're caught cold. It's just a cold call. Yeah. And many times the suppliers, they're like stuttering, oh my god, what am I doing? And you know, it'll be a followup and it should be a letter that specifically calls out, I see sequence numbers, power up, missing, this missing, this missing, your incorrect data, uh, engine data missing, and they'll call it out. And it and it typically it says in the regulation, you got 30 days to make it whole, right? Or else. Now, what I've also seen is if you if the supplier shows improvement over that 30-day period, it might need a little more time, they'll allow them a little more time, but it's not a forever, right? You may get to 60 days, but if you can't show market improvement and correction within that 60 days, you're going to get a revoke letter. And that's when we see FMCSA publish these, they send them out via email and also on their social media of, hey, we've revoked five devices. Yeah. See you later. you're all gone and they and they tell you you got 60 days to find a replacement, right? Yeah. And that number you said is around 68 or so at this point of Yeah. from FMCSA. Yeah. Okay. And then from time to time, you'll also see during that 60-day period where the all of the users of that ELD are looking for a new ELD, you'll see the actual vendor trying to demonstrate corrective actions during that 60-day period so they can keep their customers as best as possible to get reinstatement. You see reinstatement much it's much less common to see reinstatement, but every once in a while you will see devices get reinstated. Yeah. Yeah. And then yeah, I mean that leaves the carriers and the drivers in a bad position obviously once a device gets revoked. And that's where we're starting to see the issue you raised, Jared, which is these Chameleon devices that, you know, they say, "Okay, well, that one's revoked. " It's kind of a play on the Chameleon carrier issue that we're having with motor carriers getting shut down and coming back. Same thing with EL. And so, at least from the DO's or from FMCSA's announcement of their proposed changes here, we'll get to those here in a second, but it looks like that was a big driving force for them to take some uh action here was these Chameleon ELD manufacturers. So, Tom, what did you see? Or maybe let's just pull up the announcement here. We'll read it together and then we can uh we could talk about it. Let me pull it up and then I'll have to unmute myself. All right, here it is. Okay, [clears throat] so this is the announcement that came out on Monday, December 1st, 2025. Trump's Department of Transportation streamlines vetting process for ELDs used by truckers. Says the FMCSA today announced a complete overhaul of the vetting complete overhaul of the vetting process for ELDs, helping to ensure non-compliant devices are blocked before they ever reach FMCSA's registered ELD list. ELDs, it kind of describes what they do. The new more rigorous vetting process is part of a broader department initiative to strengthen road safety for American families. Um then here's a quote from administrator Bars from uh FMCSA's newly uh installed administrator. He said, "American families deserve to feel safe sharing a road with semi-truckss and we want truck drivers to have the best tools to maximize those safety precautions. by strengthening our review process for ELDs. We're ensuring the industry can rely on trusted equipment. Uh and then the the announcement, it's not much longer than that, but then it it u provides a little bit of additional information. It says that under the previous system, it was easier to register non-compliant devices or reregister devices that had been revoked, leading to repeated revocations and costly inconvenient replacement for carriers. FMCSA's updated process closes this loophole, giving carriers and drivers a greater peace of mind that the ELDs they purchase are accurate, reliable, and compliant. Then it says, "Keatures of the new and improved vetting process include an initial review which involves verification of contact information, technical specifications, and device images. some of the topics that Tom already mentioned. Then it involves fraud detection, cross-checking new applications against active, inactive, revoked, and in process list. And then application categorization. Uh there's four categories they're setting up. One is approved, meaning the device has met all necessary requirements. Category two is information requested when FMCSA asks for additional information from the applicant. Further review is a category three which is the application requires additional internal assessment and may require additional documentation from the applicant and category 4 would be denied if it doesn't meet the standards. So I mean that's all the details that we have uh from the announcement. I don't know if FMCSA is planning to publish anything else. Uh probably not if I had to guess but um so what are your thoughts on that Tom just reading that? Well, when I looked at it is when they say they want to look at a vetting process and and see that it meets compliance. I'm not sure how they're going to do that. Uh if I had a suggestion to make it would be why don't you supply a comprehensive 8day e-rods file for a entity or several drivers because if if the rods file successful you know and it takes about 5 seconds to put it through the validator to say that it has all the correct data and if you look at rods is is what enforcement sees at roadside and what FMC can look at and and I don't think it's insurmountable for a supplier to supply that eight days, but make sure it has the key components. You know, when you brought up that registration process, make sure it shows malfunctions. Make sure it shows unidentified drivers. Make sure it shows edits from the driver and edits from the back office that they're compliant. Because if you fill in all the other data, sequence numbers, check sums, all the other things that are in the technical specs to create a US file, you have a better view of whether the thing's compliant or not. Yeah. Because a lot of these, and you know it yourself, not every carrier, depending on your size, gets pulled over for a roadside audit. So they may not even they may have an ELD, but nobody's looking at it, right? you have a good idea that this thing is compliant and it's captured all the correct data. Yeah, it's crazy to me. Right. It's crazy to me that that hasn't been required. Just an initial sanity check. Did am I correct? Did Rod's It came out after the ELD mandate came. Oh, it came out at the same time. Yeah. I the reason I know about it is um I gave test data to Vulpi. Yeah. So so they so they could have actual carrier test data of what an EOS file would be because but it came out now I think what you're referring to public access to it. Enforcement well enforcement held off for four months. Okay. All right. So December of 2017 the actual regulation got released. Right. I see. Yep. And it CVS held off for four months of doing it because they still needed training on how do I get this e-rods file? What am I going to look at? I mean, I I know personally I probably helped test or train about 20 different states on what rods is going to look like, right? Because with that - concept was all developed in the mix subcommittee. I got you. So Tom, um I mean great point on the - file and that sanity check. Keeping in mind how small of a team they're going to have, are the resources there to even do a base level of rigor like this? Well, let's put it this way. If they're going to do what they think they're they're saying they're going to do, even if it's only four categories, they better beef up the manpower because they won't be able to do that, right, with a limited amount of people. Well, the reason I even say E-RODs is I, you know, as you well know, I use E-RODS when I'm testing for people. I look at the validator and the web servers E-RODS. I know how long it takes to go through an ERODS file, right? Yeah. And I can tell you by looking at it whether somebody's compliant, whether there there's some gray area, right? And I can do that probably within an hour. Yeah. " No. I do some testing and some vetting, right? I think I think that if you put that into place, you're probably talking about three to five hours of concerted effort to look at this. I don't think that's too much time to help guarantee that you're putting stuff out this complaint. It's not going to be the perfect world. It's not third party certification, right? I foresee another FMCSA RFP process here, Jared. Yeah, there you are. And [snorts] Tom's gonna apply for it. Hey, wait. I remember I used to be 6'4 before I started a regulatory. I'm 5'9. join the club. Hey, hey, [clears throat] Tom. I wanted to camp out on the fraud component of that announcement for just a minute. So, if if I'm a revoked device, how difficult is it going to be to detect that I've renamed my revoked device and tried to resubmit another self-certification? Is that going to be as easy to detect as I think it will be? No, it won't because it's a new name. So, how are they going to go through the list and figure out which ones are are the same one? Because you don't have to register who made it. You just you're the entity that's using it now as a business, right? " Right? right? right? Yeah. The only way they could This is just me and putting a screw ball technical hat on. If somebody gave me source code, I could compare source code and tell you if it was the same stuff. Yeah. Right. That's a file comparison. That's not magic. Right. But then you have to get the source code from all those other ones. And then you then unequivocably you could tell it was the same stuff. That's where I was going. It's yet another resource that needs to be there that probably isn't there at this point. That's right. because it's the same issue with Chameleon carriers, right? get new addresses, email addresses, and stuff and slip right through the cracks. Yeah. Yeah. Yeah. Not that we're giving a playbook here to anybody that's wanting to do this. Yeah. But I I just think that some of that stuff is very difficult. That's why I'm trying to give what I think is the stuff that's lowhanging fruit that can help you catch problems. Yeah. Okay. And not and not be manpower, you know, like, oh, I got to have to add another 100 people to the source. Right. Yeah. Yeah. Well, let me ask you about this because you said it's not, you know, full-scale thirdparty certification. Do you foresee FMCSA ever moving to that? I I guess give us some insight because I know you were heavily involved in the original uh ELD mandate. I assume third party certification was brought up at the time. What What's your sense of the thoughts on it currently in the US? I think the thought was when they when we talked about it because we had a bunch of suppliers on there were like five suppliers on that mixup committee with OIDA with enforcement with industry right and we brought it up and said look if you're going to do that you almost have to look something like TIA like a standards committee right and you have to have enough entities because what they were looking at first off you know what do we have with three to four million drivers that require BLDS, right, or logs. Okay. So, FMCSA was all concerned at the time about having enough devices out there that could satisfy three to four million drivers. you know, they got they got into the engagement of cost, right? Yeah. Now, if if the cost is is low, fine. right? Drive the cost up, then you're going to drive the cost up and you're not going to have these other suppliers to satisfy. I was curious about that. Do you have a sense of the cost differential between Canadian devices and US devices? Is it a significant difference? Do either of you know? I I think I think what happened when a lot of the suppliers, if you look at the list, they're suppliers that have been in that marketplace forever. Okay? let's call it this way, they want to make sure they maintain and protect their customers because I know what that was like because the same guys that are doing the work in here have big customers in Canada. So, they're going to invest that money to protect their customers in Canada. I got you. they don't have that kind of money to self-ser to reertify for $40 or $30,000. Yeah. And I can't imagine that there would be a huge cost variance there because you're dealing with a lot of crossber fleets. A lot of fleets that want the ELD certified device in Canada. Yeah. It's going to be a crossber fleet most likely or one that wants to be a crossber. That's right. That's right. Yeah. right? And I think they did. I mean, do I think it's as good as it could have been, but I think Canada did a representative job to harmonize between the co countries. They had to put their own thumbrint on it. So that's fine. That's their country. They can do that, right? Yeah. We've kind of hit on it bits and pieces here, but I know both of you guys spend quite a bit of time doing essentially thirdparty certifications, more of kind of an independent review of US-based ELD devices. Just I think people would be interested to know generally speaking, what's that involve when you when you guys go in and you're testing these devices? You want first? Yeah. Tom, you're the guest. Go ahead. Well, basically I when I do that, um, you know, I want to look at five days of logs before I go out in the truck. I'm going to spend probably 24 to 30 hours in a vehicle creating things that I know will break the device, right? I will generate malfunctions. I'll take things like a Faraday bag, right? And I'll I'll I'll compromise GPS. I'll compromise clocks. I'll I'll pull the ECM component off. Oh, some of the M components have GPS in them. So, I'll put a Faraday card on them and plug them back into the ECM, right? So, since we know how to break them, we in we try to break them. You're exploiting the the potential gaps. Yeah. Because we know where the holes would be, you know, we do editing. We try every kind of edit we can have. Do you do I do personal conveyance? Can I turn personal conveyance into a drive segment? Sure, that's not a problem. Can I turn drive segment into personal conveyance? Oh, you have that, we got a problem. You know, I we I know Jared and I, we hound on people to make sure that they have a correct unidentified segment report that you can categorize them because that is one unproductive report for a carrier. But if you don't capture all that data and you don't do something with it, then that audit's going to be a disaster, right? So we we also check the host side. Do we test anything from the admin? Can they do this? Can they do that? You know, we we'll try unplugging the the the thing and making sure that it gives the right warnings to the driver. Pull over and plug in. You didn't you didn't authenticate yourself. Does it have because there could be ver visual audi because if it's not plugged into the table or to the tablet, you're not going to have a message. But there should be some kind of blinking light. So we we go through that whole process of what is it six or seven different malfunctions to try and break them. Okay. Yeah, you captured it really well. I mean, essentially it comes down to an in truck testing component that probably is going to last uh a couple days most likely. And that involves like Tom said going through those test cases that have been published by FMCSA but also customized test cases that we've built in our experience areas where we can actually try to break the device and find non-compliance. And then also like Tom said that back office component which is really detailed and technical um and that that can last uh a week two weeks depending on how quickly everyone wants to move with that. But, you know, we do this testing not only for ELD vendors. Early on with the ELD mandate, it was much more focused on vendors. Now, we're looking more at testing for larger motor carriers that really want to ensure that the device is compliant, right? Because really, I mean, the the whole point of the ELD mandate in essence is to make it easier for drivers to stay in compliance, to make it easier for motor carriers to stay in compliance. And then you have the benefit of reduced crash risk, reduced crash risk, uh reduced fatigue, etc. Um, and so if the device isn't making it easier for drivers and motor carriers, that's your red flag right there that you need to take a look at the device itself and potentially move on from that device. Yeah, that's what I was going to say because I know some carriers are also having you test like user experience just to see if this is a intuitive device or not. right. Yeah, that's that's another aspect of our testing is user experience. And Tom H obviously has tons of experience in actually, you know, designing ELDs. And so understanding what drivers are going to hate and what, you know, back office administrators are going to hate and this isn't workable. Making this report is a huge pain. It's just not workable. We need to fine-tune this. That's also a huge part of it as well. Yeah. All right. There you go. Sales pitch for these guys. If you're a ELD manufacturer, you're a carrier that wants to test your device, give these guys a call. They're the they're the experts. All right. Well, anything else, guys, that we haven't hit on? We're about out of time here. I think we hit on quite a bit, but let me know if I missed anything. No, I Tom, I think I'm good, too. You know, I think I think just, you know, reiterating if they want to do something like a Neod's file or multiple Lero's files, I think that can help them plug a whole lot of holes. Yeah. So, I'd be interested to see if they publish anything that says what they're going to do. Yeah. Yeah, I would just say I mean this is I think this is a really positive sign with this administrator that he's willing to come in and start doing dirty work right off the bat. I mean these are two things that are a long time coming. Uh the training registry working on that and then trying to police ELDs. I mean it's it's dirty work that needed to be done. So kudos to the agency for doing that. Yeah. Right. There was also Go ahead. I was going to say there was also a leaked memorandum. I don't think they published the official one yet, but some more crack files. No, not that kind of like on chameleon carriers. Not quite as Yeah, not quite as exciting, but anyway. All right, Tom. Well, uh, as always, we really appreciate you joining us, taking some time out of your day to talk with us about these topics and, uh, we'll look forward to having you you on a a future show. So, thanks for being with us today. Great. Thanks for having me. Appreciate it. All right. All right. Well, that's going to wrap things up uh for this show. Appreciate everybody tuning in. Uh you can watch prior episodes and read guest bios and get in contact with us over at Truck Safe Live. If you're interested, stay tuned for announcements about future shows. Again, subscribe to the newsletter. We post uh uh all kinds of articles in addition to announcements about future shows. com. Anything else I missed there, Jared? Uh, we've got exciting news coming on the 2026 Trucks Safe Boot Camp. So, that'll be coming. Uh, keep your eyes peeled for that. that is in the works and uh always look forward to that. So stay tuned and uh yeah, I think that's it. Appreciate you being here with us. We'll catch you next time. See you.

Event Completed

Thursday, December 4, 2025 at 1:56 PM EST

Watch on YouTube