Blue Ink Tech Blog

Simple Steps to Switching ELD Providers

Oct 26, 2021 11:36:44 AM / by Tiffney Lopez posted in ELDs, business management, DataQ, HOS

0 Comments

There isn't much worse than not getting value out of something you've paid for and are required by law to have. When the Electronic Logging Device (ELD) mandate was implemented it left truck drivers with few options and even fewer ways to deal with it. Selecting the wrong ELD provider is one of the main problems with ELD.

An ELD provider should keep the driver's best interest a priority. Those priorities include making sure their ELD is easy-to-use, there's a knowledgeable support team ready for any questions they have, and there are no hidden or extra costs to any services provided.  

There are a number of reasons carriers and drivers are ready to switch ELD providers. Some of those top stresses include:

1. Equipment malfunctions and failures

2. Poor customer service

3. Costly and lengthy contracts

So what should you do when you’re ready to drop your provider and get a better one?

First things first, plan ahead at least 60-90 days. You want to make sure that you have plenty of time to vet new ELDs before you existing contact is going to end so you can easily make the transition.

Read More

Using DataQ to Correct Inaccurate DOT Citations

Aug 23, 2021 1:50:28 PM / by Tiffney Lopez posted in ELDs, fines, FMCSA, DOT, DataQ

0 Comments

Dave was recently pulled over by an officer with the Department of Transportation (DOT). After the officer completed his inspection, Dave noticed the data on his inspection report was different than the paper version.

Dave at first thought this was one of the problems with ELDs. What stuck out the most is he saw his Hours of Service were recorded accurately on his ELD, but on the report it says Dave violated his HOS by not taking a 30-minute break... The officer was enforcing a rule that has since been changed.

Thankfully, Dave keeps documentation of everything and can easily refute the violation and submit it supporting data.

Read More
Content not found
Content not found