Why this trips up good shops
You want to know who you’re putting in someone’s home. Fair enough. A tech works alone in a stranger’s kitchen, near their kids, next to the drawer where the jewelry lives. Screening isn’t paranoia. It’s part of the job.
The trouble starts with the how. Employers rarely get sued for running a background check. They get sued for the way they ran it, or for what they did with the result. The mistake usually isn’t checking. It’s skipping a step in some paperwork you didn’t know existed.
Background checks: the rules that bite
The second you pay an outside company to pull someone’s record, a federal law kicks in: the Fair Credit Reporting Act. FCRA for short. Doesn’t matter that there’s no credit involved, the name is just misleading. If a third party runs the check, you owe the applicant a few things. A clear written notice, on its own page, that a background check is coming. Their written permission. And if that report is the reason you’re passing on them, a specific notice process before and after you make the call.
That last part is where shops get burned. You can’t just read a report, decide no, and ghost the guy. The law makes you send what’s called a pre-adverse action notice first, with a copy of the report attached, and give him a real chance to say “that’s not me” or “that charge got dropped years ago.” Reports have errors in them. People get confused with somebody who shares their name. Only after that do you send the final notice. Skip the dance and you’ve handed a plaintiff’s lawyer an easy afternoon.
There’s a second layer, too: what you’re even allowed to ask, and when. Plenty of states and cities now have “ban the box” rules that push the criminal-history question later in the process, or off the application sheet entirely. And a blanket “no felonies, ever” policy is riskier than it sounds. Federal guidance leans hard toward weighing the actual offense, how long ago it happened, and whether it has anything to do with the work. A 15-year-old possession charge on a guy who’s been clean since is a weak reason to pass on a solid plumber.
Tell the applicant, on its own page, that you're going to run a check. Not buried in the application fine print.
Their signature giving permission, before you pull anything. No signature, no report.
If the report is why you're saying no, send it first with a copy of the report and time to dispute it.
The formal no, sent after the waiting window. Keep a copy of every step.
Drug testing: legal, but with new landmines
Private employers can drug test in most states, and for safety-sensitive trade work most of them can require it. Nobody wants a guy running a torch or wiring a live panel while he’s high. If you run trucks that need a CDL, you’re in a separate federal system altogether: DOT testing is mandatory, with its own rules on when and how it happens. That one is not up to you.
The ground shifted under marijuana, though, and a lot of owners haven’t caught up. As more states legalized it, some passed laws protecting workers who use cannabis off the clock on their own time. In those places, a positive THC test on its own, with no sign of impairment on the job, might not be legal footing to fire someone or turn them down. THC also lingers in the body for weeks, so a test can flag a guy who last used days ago and is stone sober standing on your job site. This is the corner of the law changing fastest. It’s exactly where you want to know your own state’s rule before you write your policy, not after you’ve already fired somebody.
“You rarely get sued for running the test. You get sued for testing one guy and not the others.
Write it down and apply it to everyone
Whatever you land on, the thing that keeps you out of court is boring old consistency. Pick your policy, put it in writing, and run every candidate through the same door. The lawsuit is hardly ever about the test itself. It’s about testing the one guy and waving the others through, because that’s where a discrimination claim comes from. If you test, test everybody for that role. If you check backgrounds, check them all the same way.
Then keep the paper. The signed consent, the policy your new hire acknowledged, the notices you sent and the dates you sent them. It’s dull filing right up until the day you need it, and on that day it’s the whole case. Same habit that keeps a job from turning into a he-said-she-said: write down what happened, and keep it somewhere you can actually find it again.
Where the habit carries over
None of this is what ToolbagCRM does. We run your jobs, not your HR file, and we’re not going to pretend to store drug-test results. But the discipline is the same one we built the product around: write down what happened, keep it where you can find it, run every job and every customer through the same process. On the hiring side that habit keeps you legal. On the job side it’s the difference between a warranty callback you can prove you handled and an argument you lose.
One thing worth knowing while you’re hiring: we don’t charge per seat. Every tech you bring on after that background check comes back clean gets added to the system at no extra cost. Founders pricing is $99/mo for the first three months, then $150/mo locked for the life of the account, for the whole crew, however big it gets.