I Just Got Fired

I do background checks, I see these and don’t care, my insurance company doesn’t care. They only care with at fault accidents, which matter and have to be reported, everything else doesn’t count

 

Good point.

 

you gave someone this information in a private message, and then that person came here and told everyone?

Sad.

 

There are different types of background checks. When you hire the volume of people that Roehl hires, you don't want to start the expensive one until they actually show up to orientation. I don't like it, but I also understand that it's cheaper to fork out $500 in transportation costs to bring out someone you're going to immediately fire than $1,000 on someone who will just ghost you. You, me, and the two very nice ladies who do on boarding for my company object to this line of thinking, but I have to admit it is cost effective.

Then you have how long the background checks take. The major disqualifying things tend to pop up quick and fast, but some of the more subtle red flags take some time to find. I have a VERY common name and any troll through any database is going to pop up a bunch of bad leads. Last spring I was kibbitizing with some of our training office staff end of day on Friday when an SFI rep came bustling over in a panic about needing to get a truck back from the hotel because the background company had just sent over a revised report with SOMETHING BIG on it and we NEEDED TO GET THE TRUCK BACK RIGHT NOW. Sometimes things don't get found until after the fact.

Then when they're found, someone needs to act on it. I doubt Roehl was holding it in their back pocket, more likely the driver manager was sent an email saying "deal with this", and the driver manager didn't. DMs are very good at 'hiding' issues until they are no longer issues. Sometimes they do it to protect their drivers, sometimes because they are lazy/incompetent, sometimes because they want to protect themselves. A couple years ago I had to 'retrain' a driver. He'd been hired as a system driver out of different operating center, then transferred to a dedicated account that ran out of my OC. His previous DM had managed to close out a bunch of incidents without properly documenting them, so he was free to transfer when we should have been firing him. To a point I can see the logic of the DM, and for a lot of new drivers it would have been a solid choice - guy dun f'd up, but owned it, so slap him on the wrist and send him forth to sin no more. Long story short, dude dumped the trailer in a ditch pulling out of a customer's lot but we couldn't fire him because we had no documentation. Our local Chief Safety Critter was pooping out solid tungsten rods when he dug into this guy's record.

That's what I would guess happened here. Someone looked at the deep background check and said "so what?" and just stuck it in the file. When the workman's comp claim hit someone's desk and they looked through the whole file the smelly stuff started towards the fan.

From the facts presented this could have and should have been handled differently, but I can see how internal processes can lead to a bad outcome that looks malicious but isn't.

 

Any accident where any insurance company pays anyone generates an entry in the CLU database, IIRC. It allows any insurance company to verify if a new customer's claim of a clean record is accurate.

 

Its not to hard to figure out who it was just look through the posts in the last couple pages ..
Lesson... never trust a stranger with info you don't want shared
The sad part is they came on here telling everyone like a little school boy

 

37 months of service on mine, and all are intact.