Print this list, or save it on your phone, and take it into your next vendor call. These ten questions get you real answers instead of a pitch, and asking them before you sign is a lot cheaper than finding out the hard way what a bad contract costs.
I sat through more of these calls than I can count over almost 30 years running background checks for a manufacturing company in Ohio. A vendor is good at answering the questions you ask and quiet about the ones you don't. These ten are the ones that actually matter.
A quoted "per report" price almost never means the final number. Add-on searches, a monthly platform fee, and court costs the vendor passes through can all show up later.
Ask for a real itemized quote on one specific county search before you sign anything. If they won't give you one in writing, that's your answer right there.
An "average turnaround" number hides exactly the searches that'll blow up your start date. A database check clears in a day. A county court pull or an employment verification call can run a week or more.
Ask for turnaround by search type, not one blended number. And ask what they do when a report runs late. Do they flag it, or do you find out by calling them.
PBSA stands for the Professional Background Screening Association. Their accreditation means an outside auditor actually reviewed the vendor's data accuracy, security, and compliance process. It's not a rubber stamp, and most screening companies don't have it.
Not having it isn't automatically disqualifying, especially for a smaller regional vendor. What matters is whether they can explain why, plainly, instead of dodging. PBSA keeps a public list. Check it yourself rather than take a sales rep's word for it.
Federal law generally expects a background check company to acknowledge a dispute fast and finish reinvestigating within about a month, though exact numbers shift, so verify the current rule rather than trust mine.
Ask who owns a dispute internally, and how you as the employer get looped in while it's open. If they can't describe their own process off the top of their head, they don't really have one.
A real, built integration means a status change in your applicant tracking system triggers the check automatically. That's different from a generic API your team has to build against, which is a project, not a feature.
Ask about the candidate's side too. A clunky consent form nobody wants to finish on their phone slows your hire down just as much as a slow report does.
Multi-year terms that auto-renew, early-termination fees, minimum-volume requirements. These are the clauses that make a bad vendor expensive to escape, not just annoying to deal with.
Ask them to read you the cancellation and renewal terms out loud, right there on the call. Reasonable ones look like a short initial term and no penalty if you give proper notice.
You're handing this company Social Security numbers, addresses, and criminal history for every person you consider hiring. Ask how long they keep that data, where it's stored, and what their breach notification process actually looks like.
A vendor who answers this fast and specifically has clearly been asked before. One who gets vague hasn't thought about it much either.
Some vendors hand you blank disclosure forms and adverse-action letters at onboarding and call it done. No guidance, no state-specific templates, good luck.
Here's the part that matters. When the paperwork's wrong, you're usually the one who gets sued, not them. Ask exactly what support they give you through the pre-adverse notice, the waiting period, and the final notice, and get specifics, not "we'll help."
A vendor proud of their work will show you a redacted sample report with no fuss. Look at whether it's actually readable by someone who isn't a lawyer, and whether it says which court or database each record came from.
If a rep stalls, or only offers a sample after you've already signed, that's not confidentiality. That's them not wanting you to compare it to anyone else's.
You'll recieve plenty of sales emails promising a dedicated account manager. Ask what that actually means. A named contact who answers, or a shared support inbox with a generic reply time.
Ask specifically what happens when their mistake costs you a candidate. Refund, re-run, a real escalation path. If they dont have a clear answer, that tells you something too.
Print this part if nothing else. It's built to hand to a vendor mid-call, not just read once and forget.
| Question | Good answer sounds like | Red flag sounds like |
|---|---|---|
| What's included, what costs extra? | A written, itemized quote by county | "It depends, let's talk pricing after the demo" |
| Turnaround by search type? | Specific ranges per search, with delay alerts | One blended "average" number |
| PBSA accredited? | Yes, or a clear reason why not | Confusion about what PBSA is |
| Dispute process? | A named owner and a real internal timeline | "We handle it case by case" |
| ATS integration? | A named, built connector for your system | "Our API is very flexible" |
| Contract lock-in? | Short term, no penalty with notice | Hesitation before answering the term length |
| Data security? | Specific retention period and breach process | "We take security very seriously" |
| Adverse action support? | State-specific templates, active guidance | Blank forms, "that's on your legal team" |
| Sample report? | Shown to you before you sign, unprompted | "It's proprietary" or shown only after signing |
| Support responsiveness? | A named contact with a stated response time | "Submit a ticket" |
Ask all ten on the same call, back to back. A vendor with good, confident answers won't mind the list. One that gets cagey by question four already told you what you need to know.