Client Login

Common Pitfalls of Selecting Background Screening Companies

Choosing a background screening vendor looks like a commodity decision until inaccurate records, hidden fees, or poor integrations stall hiring and create compliance exposure. This guide cuts through marketing claims to show the common pitfalls HR teams make when evaluating the best background screening companies for speed, accuracy, compliance, and total cost of ownership. Read on for concrete red flags, contract language to insist on, and a practical vendor evaluation checklist you can use in RFPs and pilots.

Overlooking FCRA, EEOC, and State Level Compliance

Hard truth: compliance failures are almost always vendor selection failures. Choosing one of the best background screening companies on price or speed alone is how organizations end up with inaccurate reports, botched adverse actions, and state-level lawsuits that the HR team has to manage.

What to require from vendors before you buy

  • Written FCRA program: a documented consumer reporting agency or furnishers policy showing how they obtain candidate consent, reinvestigate disputes, and handle reinvestigations.
  • Adverse action pack samples: provide redaction-ready pre-adverse and final adverse action notices with the underlying report attachments your team will send to candidates.
  • State law matrix: a country and state-by-state summary showing how the vendor applies ban the box, sealing/expungement, and lookback restrictions.
  • Audit evidence: recent third-party SOC 2 Type II or a compliance audit and client references that have similar regulatory exposure to your business.

Practical insight: faster turnaround can mask compliance shortcuts. Vendors that hit very low TATs often rely on commercial databases rather than direct courthouse or DMV retrievals. That improves speed but increases the chance of stale or incomplete records and makes accurate adverse action harder — a tradeoff you must accept consciously, not accidentally.

Concrete example: a mid-market hiring program used a low-cost provider that aggregated commercial criminal data. A candidate received an adverse action based on a misattributed conviction; the vendor could not produce source documentation or a county court pull and refused to support a full reinvestigation. The company faced a contested hire, legal engagement, and a damaged candidate experience.

Red flags that indicate real compliance risk: vendors that refuse to produce sample adverse action notices; vendors that will not commit to a data retention timeline; and vendors that decline indemnification for FCRA violations or limit indemnity to narrow, rare scenarios.

Sample contract language to insist on: Vendor will indemnify and hold Client harmless from any claims, fines, or damages resulting from Vendor's failure to comply with the Fair Credit Reporting Act (15 U.S.C. 1681 et seq.) or applicable state employment screening laws. Vendor will provide timely assistance and documentation for pre-adverse and adverse actions, and supply a full export of supporting source documents within 10 business days of request.

Judgment: prioritize vendors that can operationalize compliance, not just claim it. Insist on demonstrable processes and contractual tools that make compliance auditable. If you must accept commercial database reliance for speed, require stronger indemnities, faster source-delivery SLAs, and a tested dispute workflow before you go live.

Reference compliance guides from the FTC and EEOC: FTC FCRA overview and EEOC guidance on arrest and conviction records.

Frequently Asked Questions

Straight talk: the questions HR teams ask most often reveal where vendor selection fails in practice: operational gaps, surprise costs, and weak evidence trails. This FAQ answers the pragmatic items procurement and hiring teams ask when narrowing down the best background screening companies.

How do I confirm FCRA processes are operational and not just marketing copy

Request evidence, not slogans. Ask for written procedures for consent capture, dispute handling, and reinvestigation timelines; request recent dispute logs with redacted PII; and require client references that operate in your regulated vertical. Limitation: vendors will redact source documents for privacy, so insist on a commitment to deliver unredacted source records to your legal team under a controlled process when needed. For baseline legal context see FTC FCRA overview.

What hidden costs do teams most often miss after signing

Watch operational surcharges. Beyond per-search fees, vendors commonly bill for CSV or API exports, custom report templates, change requests to workflows, priority processing windows, and extra charges for legacy or manual data cleanup. These fees compound during seasonal spikes and create a gap between forecast and actual spend. Negotiate caps and require an explicit fee schedule in the statement of work.

Which SLA metrics actually reduce time to hire

Measure tail latency and integration reliability. Median turnaround time is useful but misleading. Require median and 90th percentile TATs by search type, API acknowledgement latency, webhook delivery success rates, and mean time to resolve high severity issues. Expect tradeoffs: tighter SLAs raise vendor cost and may push them toward commercial data that is faster but less defensible.

Can I validate coverage and accuracy before a full rollout

Yes, do a controlled verification pilot. Commission a 50 to 100 record pilot composed of real candidate locations and job roles. Require the vendor to deliver raw source documents and permit your team to compare results to ground truth. Concrete example: a retail operator ran a 60 record pilot across three counties; the vendor missed 11 misdemeanor records that required manual court pulls. The pilot forced contract language changes requiring direct court retrievals for priority geographies.

How do I preserve portability if I need to switch vendors

Make portability a precondition. Insist on a contract clause for scheduled full data exports in a documented CSV schema, a one time test export during onboarding, and a maximum 15 business day delivery for ad hoc exports. In practice, vendors will try to charge for complex exports; counter that with an export flat fee in the SOW.

Minimum precontract asks: API sandbox access with sample calls; the vendor's last 90 day SLA report showing percentile TATs; two client references that use comparable volumes and geography; a sample pre and final adverse action pack; committed fee schedule for the first 12 months.

Next actions: request the documents in the info box, run a 50 100 record pilot focused on problematic jurisdictions, require a test data export during onboarding, and add explicit caps on operational surcharges to your contract.

article blockquote,article ol li,article p,article ul li{font-family:inherit;font-size:18px}.featuredimage{height:300px;overflow:hidden;position:relative;margin-top:20px;margin-bottom:20px}.featuredimage img{width:100%;height:100%;top:50%;left:50%;object-fit:cover;position:absolute;transform:translate(-50%,-50%)}article p{line-height:30px}article ol li,article ul li{line-height:30px;margin-bottom:15px}article blockquote{border-left:4px solid #ccc;font-style:italic;background-color:#f8f9fa;padding:20px;border-radius:5px;margin:15px 10px}article div.info-box{background-color:#fff9db;padding:20px;border-radius:5px;margin:15px 0;border:1px solid #efe496}article table{margin:15px 0;padding:10px;border:1px solid #ccc}article div.info-box p{margin-bottom:0;margin-top:0}article span.highlight{background-color:#f8f9fb;padding:2px 5px;border-radius:5px}article div.info-box span.highlight{background:0 0!important;padding:0;border-radius:0}article img{max-width:100%;margin:20px 0}