How to Evaluate and Choose a Professional Background Screening Provider 

Choosing a background screening provider is a decision about the quality of information an organization will use, the experience of the people being screened and the support available when something goes wrong. A useful evaluation connects those outcomes to evidence: defined search methods, demonstrated workflows, credible security review, comparable pricing and clear commitments.

Parts I through IV explained the industry, screening operations, compliance and specialized capabilities. Part V turns that knowledge into a practical selection process for HR, Talent Acquisition, Procurement, Compliance, Legal, IT and business leaders. It explains what to ask, what to verify and how to compare providers without allowing a persuasive demonstration or a low package price to decide the outcome prematurely.

The best provider is the one that can substantiate its ability to meet your organization's actual requirements. Size, software ownership and brand recognition can inform the evaluation, but none independently establishes accuracy, service quality or suitability for a particular program.

This chapter is an educational procurement guide, not legal advice. Its scorecard, examples and recommended workflows are tools to adapt to your organization. Legal requirements and contract terms need appropriate review for the services, locations and populations involved. Source review does not represent approval by legal counsel.

Contents

Key takeaways

1 Define what a better screening program would accomplish

2 Build an organizational requirements profile

3 Separate mandatory requirements from preferences

4 Understand who will provide each part of the service

5 Compare provider models without assuming the outcome

6 Define the screening package precisely

7 Evaluate sources and research resilience

8 Ask how accuracy is achieved and corrected

9 Examine compliance support without transferring the decision

10 Treat consumer disputes as a core service

11 Verify accreditation and distinguish it from membership

12 Read security evidence at the correct scope

13 Examine practical security privacy and continuity controls

14 Test the integration you intend to use

15 Evaluate the candidate experience directly

16 Compare turnaround using consistent definitions

17 Define customer service and escalation commitments

18 Confirm specialized and international capability

19 Ask what AI and automation actually do

20 Assess reporting and the evidence available after launch

21 Check references and organizational resilience

22 Compare total expected cost

23 A worked example of comparable pricing

24 Use an RFP when it will improve the decision

25 Score only after checking mandatory requirements

26 Run a demonstration based on your workflow

27 Use a controlled pilot for critical uncertainties

28 Negotiate the commitments that matter

29 Plan the transition before ending the existing service

30 Manage the relationship after selection

31 Warning signs that deserve follow up

32 Final selection checklist

33 Frequently asked questions

The central principle of Part V

Related SimpliVerified resources

Source review and maintenanc

------------------------

Key takeaways

• Define the problems and requirements before comparing providers.
• Evaluate the CRA, its technology and its research network as connected but distinct parts of the service.
• Compare equivalent search scope, verified capabilities and total expected cost.
• Treat accuracy, compliance, consumer support and security as substantive evaluation areas.
• Use demonstrations and controlled testing to verify important claims.
• Resolve mandatory requirements before allowing weighted scores to determine the shortlist.
• Put material service, pricing and implementation commitments into the agreement.
• Package names are offered without a clear account of search scope.
• Accuracy or turnaround claims lack definitions and supporting evidence.
• The provider describes membership as accreditation or presents another entity's security report as its own.
• Important functions are on a roadmap but priced or scored as available today.
• Consumer disputes are treated only as an employer customer-service issue.
• Integration responsibilities and failure handling remain unclear after the demonstration.
• Variable charges, minimums or renewal terms cannot be explained in writing.
• The provider promises to assume the employer's entire legal responsibility.
• A monitoring or AI score cannot be connected to understandable evidence and review procedures.
• The requirements profile reflects the roles, locations, volume and workflows in scope.
• Mandatory requirements have been verified or explicitly resolved by authorized reviewers.
• Search specifications and pricing assumptions are comparable across finalists.
• Accuracy, consumer support, security and compliance evidence have been reviewed.
• The required integration and candidate workflow have been demonstrated.
• References and any pilot findings support the proposed service.
• Scoring reasons are documented and the decision explains material tradeoffs.
• Legal, security, HR, procurement and financial reviews are complete as applicable.
• The agreement contains the important service, pricing and transition commitments.
• Launch ownership, acceptance criteria and treatment of existing cases are clear.

1 Define what a better screening program would accomplish

Start with the reasons for evaluating a provider. A team might need better visibility into delayed reports, stronger support for candidates, reliable integration, broader country coverage or clearer billing. Those are different problems and may require different solutions.

Document the current situation with examples and available data. Replace “turnaround is terrible” with an account of which searches are delayed, how often delays occur, what causes them and how recruiters learn about them. Replace “support is poor” with the unresolved issue, elapsed time and business effect.

Set a small number of measurable outcomes. Examples include reducing duplicate recruiter entry, providing an owner for every escalated report and making variable charges predictable. Do not invent performance targets without a baseline or assume that the current provider controls every delay.

Changing providers is one possible remedy. Package configuration, candidate instructions or internal approval practices may also contribute to the problem. A useful selection process identifies those factors so they are addressed during implementation instead of carried into a new relationship.

2 Build an organizational requirements profile

Describe annual order volume, seasonal peaks, locations, worker types, job categories and expected growth. Include screening after hiring, such as promotion-related checks or monitoring, if those services are in scope. Distinguish the number of candidates from the number of individual searches purchased.

Inventory the current packages and their components. Record the ATS or HRIS, candidate workflow, user roles, legal review process, reporting needs and current contract dates. Note where different business units use different policies or purchase services independently.

Involve the teams that will operate or approve the program. HR can describe hiring workflows; Procurement can establish a fair evaluation; Legal can address applicable obligations and contract allocation; IT and Security can assess systems and data; Finance can validate cost assumptions. Identify one person who owns the final requirements record.

Use a written profile rather than relying on a vendor to infer your needs during a sales call. The same profile should go to every shortlisted provider. This creates a common basis for questions, demonstrations and pricing, and makes later changes visible to the evaluation team.

3 Separate mandatory requirements from preferences

Classify each requirement as mandatory, preferred, optional or requiring an internal decision. Mandatory should mean that the organization cannot proceed without it, not simply that a stakeholder would like it.

A mandatory item might be a lawful service required for a regulated role, an approved security control or a demonstrated integration needed for launch. A preferred item might be a convenient dashboard view. An unresolved policy choice should be assigned to an internal owner rather than sent to providers as though it were settled.

Define acceptance evidence alongside each requirement. “Supports our ATS” is difficult to evaluate. “Demonstrates ordering, candidate invitation, status return and corrected-report access in our supported ATS configuration” describes an observable result. Include dependencies, fees and availability dates.

Keep the same standard for each provider. If a requirement changes during evaluation, record why it changed and give all remaining providers a fair opportunity to respond. Otherwise the process can quietly favor the last demonstration or the most familiar vendor.

4 Understand who will provide each part of the service

The contracting company, CRA, screening platform, court researcher, verification supplier and laboratory may be different organizations. Ask the bidder to map the service chain and identify which entity prepares the report, supports the customer and handles consumer disputes.

A proprietary-technology CRA develops some or much of its own software. A platform-powered CRA uses shared infrastructure and adds its own operations, research relationships and service. A hybrid provider combines approaches. A large integrated provider may operate across multiple products, countries or acquired systems. These descriptions overlap; they are not exclusive rankings.

Shared platforms are an established part of the industry. TazWorks describes infrastructure and integrations for CRAs, while Accio Data describes screening software and connections used by its CRA partners. Their product descriptions establish the platform model, not a guarantee of any particular customer's implementation. TazWorks TazCloud and Accio Data platform overview

The buyer should understand the chain well enough to know who responds when a source fails, who approves a workflow change and whose controls protect the information at each stage.

5 Compare provider models without assuming the outcome

Software ownership can support product control, while a shared platform can spread infrastructure investment across many CRAs. Neither model guarantees better service or lower cost. Evaluate the capabilities available in the proposed service today.

 

Do not assume that every independent provider delivers personal service or that every large provider is impersonal. Ask for the staffing model, support channels, escalation process and references relevant to your size and needs.

Likewise, two CRAs using the same platform can differ in package design, source selection, quality procedures, verification effort and consumer support. Similar screens do not establish identical services. A meaningful comparison follows a report through the work behind the interface.

6 Define the screening package precisely

A package name such as standard, national or comprehensive does not define its contents. Ask for a component-level specification that identifies sources, geographic scope, identifiers, applicable research periods and rules for additional searches.

For criminal research, clarify the relationship between database discovery and source research. Ask how counties are selected, how aliases are handled, what triggers further verification and whether federal court research is included. Distinguish search scope from legal reporting limits; looking at a source and reporting information from it are different questions.

For verifications, specify the number of employers or credentials, contact attempts, escalation rules and treatment of nonresponsive sources. Determine which charges are included and which arise from a particular source. Ask how candidate-provided documents are labeled when independent confirmation is unavailable.

Compare these specifications before comparing price. A lower-cost package that omits a required verification is not an equivalent offer. Conversely, paying for additional searches that do not address an identified need can increase cost and delay without improving the program.

7 Evaluate sources and research resilience

Ask how the provider obtains information and maintains coverage. Useful answers describe the types of sources, qualification of researchers, review of suppliers and alternatives when a normal route is unavailable. A statement about the number of records in a database provides little evidence about currency or suitability for your package.

Request a sample explanation of a source outage. Does the provider identify affected orders, offer an appropriate alternative and explain any difference in scope? Is additional cost approved before work proceeds? Who tells the recruiter that the expected completion date has changed?

Redundancy has value when it preserves an appropriate research route. Ordering from multiple aggregators that rely on the same underlying source may not provide independent confirmation. Ask how the provider understands dependencies and reconciles duplicate or conflicting results.

Providers may reasonably protect confidential commercial relationships. Seek enough evidence to understand methodology and accountability without demanding unnecessary trade secrets. A redacted procedure, coverage specification or controlled demonstration can be more useful than a long supplier list without context.

8 Ask how accuracy is achieved and corrected

Accuracy should be evaluated through procedures and evidence. The FTC explains that CRAs must maintain reasonable procedures directed at maximum possible accuracy and identifies problems such as duplicate offenses and records that have been sealed or expunged. FTC guidance for employment background screening companies

Ask the provider to explain a difficult identity match, an amended court disposition and conflicting records from different sources. What information supports the match? When is a case escalated? How does a reviewer preserve uncertainty? How are later corrections applied to the report?

Request the definitions behind accuracy metrics. A claimed accuracy percentage may measure audited fields, reports, searches or only disputed records. Those denominators are not interchangeable. Ask how samples are selected and whether testing includes common names, missing identifiers and difficult sources.

Also assess the response to an error. A credible provider should be able to describe correction, notification, root-cause review and follow-up. An assertion that mistakes never happen provides less usable evidence than a documented process for finding and resolving them.

9 Examine compliance support without transferring the decision

A provider may supply forms, notices, workflow controls and educational resources. Determine who maintains them, which jurisdictions they address and what review the employer must perform. Ask how changes reach existing customers and how version history is retained.

The FTC describes employer responsibilities before obtaining covered employment reports and before and after adverse action. It also explains that the CRA supplying the information does not make the employer's unfavorable decision. A provider's software does not remove those responsibilities. FTC guidance for employers using consumer reports

Demonstrate the proposed process for the locations in your requirements profile. Check whether ordering can be held until an appropriate hiring stage, whether permissions restrict sensitive decisions and whether notices and response opportunities can be configured correctly. Avoid treating a default waiting period as a rule that applies everywhere.

Ask the vendor to separate CRA reporting review, comparison against employer-defined criteria and the employer's final decision. The term adjudication can refer to different functions. The contract and demonstration should make those functions explicit rather than leave responsibility inside an ambiguous status label.

10 Treat consumer disputes as a core service

Disputes affect the person screened and the organization relying on the report. Ask to see the consumer's route to assistance, including contact information, identity verification, submission of supporting material and communication of results.

The FCRA provides reinvestigation rights and duties for disputed information. The provider should be able to explain its process under the applicable requirements, not merely describe how the employer opens a support ticket. Fair Credit Reporting Act

Use a fictional case in which a report appears to contain someone else's record. Ask what the candidate sees, what the employer sees and how the case moves to the appropriate team. Establish how corrected information reaches an ATS, downloaded reports and authorized users who relied on the original result.

Measure service with care. A short average resolution time does not establish that complex cases are handled properly, and few disputes do not prove few errors. Ask about accessibility, unresolved cases, communications and how recurring problems lead to procedural improvement.

11 Verify accreditation and distinguish it from membership

PBSA operates accreditation programs with defined standards and an accreditation process. Membership in the association is different from accredited status. Individual training certificates are also different from organizational accreditation. PBSA accreditation programs

Ask which legal entity and program are covered, verify the current status and determine whether the scope is relevant to the services you are buying. If an application is pending, record it as pending rather than treating an intended future designation as an existing credential. PBSA accreditation information and resources

Accreditation can provide useful evidence about organizational practices. It is not government approval, a guarantee that every report will be correct or an exemption from reviewing the service. Continue to evaluate actual procedures, references and contractual commitments.

Apply the same discipline to any badge or credential. Ask who issued it, what was examined, which entity was evaluated, when it was assessed and what remains outside its scope. The answer is more important than the number of logos on a proposal cover.

12 Read security evidence at the correct scope

Background reports and candidate records can contain sensitive personal information. Include security professionals early enough to review the actual service, not only a questionnaire delivered after the commercial choice has been made.

SOC 2 is an independent assurance reporting framework used by CPAs for controls relevant to specified trust services categories. It should be described as an examination and report, not a government certification or a guarantee against incidents. AICPA overview of SOC services

Review the system and entity covered, report date or period, applicable categories, auditor's opinion, exceptions and relevant customer responsibilities. A Type 1 addresses an as-of date; a Type 2 includes examination of operating effectiveness over a period. Examine how relevant subcontracted services are treated. AICPA SOC 2 report review checklist

A platform or hosting provider's report does not automatically cover the CRA's personnel, local processes or every supplier. Ask for evidence that addresses those parts of the service too. Handle restricted reports through an appropriate confidential review process.

13 Examine practical security privacy and continuity controls

Ask how the proposed service manages user access, multifactor authentication, administrative privileges, encryption, activity logs and removal of departed users. Determine who can download complete reports and whether access can be limited by role, location or business unit.

Map the candidate information shared with researchers and other vendors. Address permitted use, storage locations, international transfers, retention, deletion and assistance with privacy requests. Ask how backup copies and legal holds affect deletion rather than accepting a simple statement that everything is erased immediately.

Review incident communication and continuity arrangements. A useful plan identifies contacts, recovery priorities, dependencies and a tested route for restoring service. Ask what happens to open orders and candidate communications during an outage, and which functions remain unavailable even if the portal is restored.

PCI DSS addresses payment account data security. It can be relevant to a payment environment, but it does not substitute for reviewing protections for screening records across the service. PCI Security Standards Council overview of PCI DSS

Require security evidence proportionate to the service and your approved requirements. A collection of credentials with unrelated scope should not outweigh a material gap in the process you will actually use.

14 Test the integration you intend to use

An integration listing establishes a starting point for discussion. It does not establish that your subscription, software version, business-unit configuration or required workflow is supported.

Request a demonstration from the recruiter's starting screen. Show package selection, candidate invitation, required documents, status updates, report access and any separate drug-testing or occupational-health workflow. Verify what happens after a corrected report is issued and whether a failed connection creates an alert.

Identify which system controls each important step. For example, determine whether a hiring-stage change triggers an order automatically, whether duplicate orders can occur and how cancellation is communicated. Establish who supports problems involving the ATS, integration provider and CRA.

Document setup work, customer responsibilities, testing requirements and recurring fees. If a feature requires custom development, record the scope, acceptance criteria and delivery commitment separately. A product roadmap is not evidence that a capability is available for launch.

15 Evaluate the candidate experience directly

Invite evaluators to complete the candidate journey using fictional data. Try a phone as well as a desktop. Review instructions, upload requests, error messages, language support, accessibility and the route to a person who can help.

Focus on the work the candidate must perform. Are they asked repeatedly for the same information? Can they save progress? Is it clear why another document is requested? Does the portal explain what the screening company can resolve and what must go to the employer?

Test an exception, such as an unsupported document, a name change or a source that needs additional information. The process should help the person resolve the issue and should distinguish incomplete information from a negative finding.

Clarify responsibility for communications. A provider may support candidates only for technical issues while expecting the employer to answer every status question. That division can be acceptable if it matches your needs and staffing; it should not be discovered after implementation. Include candidate support in the commercial scope and performance review.

16 Compare turnaround using consistent definitions

Ask when the measurement begins and ends. Does it start when the employer places the order or when the candidate completes the invitation? Does completion mean the first search result, all ordered components or a report awaiting employer review?

Separate product categories and relevant jurisdictions. A pooled average can conceal the difference between a fast electronic source and a manual verification. Request the median, the time by which most comparable orders finish and the age of open work, where reliable data are available.

Identify excluded time and cases. Candidate delays, closed courts and nonresponsive institutions may be outside the provider's direct control, but buyers still need to know their effect on the hiring process. Ask the provider to report both end-to-end elapsed time and the portions it controls.

Use realistic expectations. A promise that every report will finish immediately deserves examination of scope and review practices. A stronger commitment explains expected ranges, exceptions, update frequency and escalation when a case exceeds the agreed threshold.

17 Define customer service and escalation commitments

Clarify whether support is pooled, assigned or tiered. A named account manager can be useful, but the buyer should know who handles a time-sensitive report when that person is unavailable and whether the account manager has authority to resolve the issue.

Distinguish acknowledgment, meaningful response and resolution. An automated receipt does not answer a research question. Ask for support hours, channels, severity definitions and escalation owners. Record any additional charge for premium service.

Use a realistic scenario: an important hire is waiting on a delayed county search and the expected start date is approaching. Ask what the recruiter receives, how often it is updated and who decides whether another research route is appropriate. Avoid rewarding an unsupported guarantee over a clear account of what can actually be done.

Service-level agreements should define measurement, exclusions, reporting and remedies. Commercial service credits can encourage accountability, but they do not replace correction of a reporting problem or eliminate legal responsibilities. Review both the promised service and the process for addressing repeated failures.

18 Confirm specialized and international capability

Use Part IV's role and country approach to define the services that matter. A provider that performs well for domestic office hiring may need additional partners or workflows for regulated drivers, healthcare, international verification or ongoing monitoring.

For each important service, request the source or method, eligibility limits, geographic availability, required candidate steps, expected timing and support owner. For international work, clarify languages, local research partners and data handling. For drug testing or occupational health, check practical collection-site availability in the locations where candidates will use it.

Monitoring requires its own specification: roster enrollment and removal, source update frequency, alert review, correction and employer response. A broad claim of continuous coverage should not replace those details.

Consolidation may simplify administration, but a single portal does not prove a single support process. Compare a consolidated proposal with the practical responsibilities of using specialist services. Choose the arrangement that meets requirements and assigns clear ownership across the full workflow.

19 Ask what AI and automation actually do

Request an inventory of consequential automated functions. The provider should distinguish scheduling, data extraction, identity matching, research summaries, reporting review and decision recommendations. A general claim that the service is AI-powered is not an evaluation answer.

For functions affecting report content or candidates, ask what evidence supports the output, how uncertainty is handled, which cases receive review and how errors are corrected. Determine whether material model changes are tested and communicated. Ask how candidate data are used, retained and protected by any AI suppliers.

Evaluate the result with difficult examples. A tool that extracts a charge but overlooks a later dismissal can mislead without producing an obviously fabricated statement. A demonstration should preserve original source context and show the review route when evidence conflicts.

NIST's AI Risk Management Framework provides a voluntary structure for governing, mapping, measuring and managing AI risk. It is a useful reference for questions, not proof that a vendor complies with consumer-reporting or employment law. NIST AI Risk Management Framework

20 Assess reporting and the evidence available after launch

Ask to see reports that the operations team will actually receive: order volume, aged pending work, turnaround by component, service performance, disputes, corrections and invoices. Confirm that relevant data can be filtered by location, package or business unit without exposing unnecessary candidate information.

Definitions should be documented. An outcome labeled review, eligible or complete can mean different things across systems. Distinguish the CRA's reporting status from the employer's decision, and avoid interpreting a screening status as an assessment of a person's character.

Check export access and scheduled delivery. A dashboard available only to the vendor may not support your audits or business reviews. Determine which history can be retrieved after a report is corrected or an account closes and how access is restricted.

Use a sample invoice to reconcile actual components against the price schedule. If the buyer cannot connect a charge to an order, source fee or agreed service, the quoted rate may be difficult to manage even when it appears competitive.

21 Check references and organizational resilience

Seek references with similar order volume, industry needs, geography and technology. A prominent customer using a different service tier may tell you little about the experience your organization will receive.

Ask consistent questions about implementation, difficult cases, unexpected charges, responsiveness and changes over time. Ask what the reference would negotiate differently and what work still falls to its own team. Note the limits of a reference supplied by the vendor rather than treating it as an independent audit.

Review the contracting entity, ownership, relevant operating history, insurance and continuity arrangements to the extent appropriate for your procurement process. Where regulatory or litigation disclosures are requested, distinguish allegations, findings, settlements and remedial actions. The useful question is what the evidence says about the proposed service and controls.

Consider what happens after an acquisition, platform migration or significant staffing change. Ask how customers are notified, whether contractual commitments continue and how a service transition is tested. Organizational scale matters most when it produces resources and continuity relevant to your program.

22 Compare total expected cost

Request a common pricing schedule that includes base packages, incremental searches, source access fees, verification charges, aliases, international work, testing, monitoring, setup, integration, minimums and recurring account costs where applicable. Require the bidder to identify what is included, excluded, variable or subject to markup.

Build the comparison from your expected mix of orders rather than multiplying every candidate by the cheapest advertised package. Geography, number of searches, source fees and specialized services can materially change the result. Use historical aggregate information when available, without distributing candidate records.

Separate one-time and recurring costs. Compare the first year and a normal operating year, and examine the contract period if prices or minimums change. Include the organization's estimated internal administration costs separately, using explicit assumptions rather than hiding them inside vendor fees.

Run sensitivity cases for changes in hiring volume, verification use and high-fee jurisdictions. A proposal that is economical at one volume may be expensive if a minimum commitment remains in place when hiring falls. Clearly label estimates and obtain a written explanation of any line item that cannot be priced reliably.

23 A worked example of comparable pricing

The following fictional example illustrates the method. It is not a market price estimate or a quote from any provider. Assume 1,000 orders, identical required package scope and equivalent verified service. Variable charges have been normalized to the same annual workload. Taxes and employer labor are excluded.

 

Provider B has the higher base price but the lower modeled total. The first-year difference is 4,000 dollars. The recurring difference is 2,000 dollars if scope, workload and prices stay unchanged. Neither result establishes that B is the better provider; quality, mandatory requirements and implementation still need evaluation.

Confirm that the verification and source-fee assumptions reflect each proposal's inclusions so costs are not counted twice. If a fee is genuinely unknown, show it as an unresolved item and test a reasonable range. Treating unknown charges as zero makes the comparison look more certain than it is.

24 Use an RFP when it will improve the decision

A formal Request for Proposal is useful when several teams need to compare substantial requirements or when the service is complex. A smaller purchase may use a structured questionnaire, demonstration and written quote. The essential discipline is consistent requirements and evidence, not document length.

The SimpliVerified AI Background Screening RFP Builder Toolkit is designed to support discovery, a requirements profile, an RFP, a response matrix and a weighted scorecard. Its intended sequence aligns with this chapter: understand the organization first, approve the requirements, then ask providers to respond. AI-generated procurement material still requires human review before distribution.

Use approved tools and organizational information appropriate for sharing. The requirements exercise does not need candidate SSNs, background reports or medical information. Describe volumes, packages, workflows and problems in aggregate.

Require responses to identify whether each capability is available now, partially supported, dependent on another service or planned. Ask for evidence, limitations and cost alongside the answer. Give providers a common question deadline and share material clarifications consistently so all proposals address the same request.

25 Score only after checking mandatory requirements

Begin with a separate gate for mandatory items. Record pass, fail or unresolved, the evidence and the responsible reviewer. An unresolved mandatory item is not a pass. A provider should not compensate for a material security or required-service failure by receiving more points for price.

After the gate, use a weighted scorecard to compare qualified providers. The example below totals 100 points. It is an editorial starting point, not a legal standard or a universal weighting. Approve weights before proposals are scored and adjust them to reflect actual priorities.

 

Use a common zero-to-five scale. Zero means unsupported or unavailable; one means major gaps; two means partial fulfillment; three means the requirement is met with adequate evidence; four means a useful improvement is demonstrated; five means a substantial relevant advantage is supported by strong evidence. Define category-specific examples before scoring so evaluators interpret the scale consistently.

Calculate weighted points as category weight multiplied by rating divided by five. For ratings of 4, 4, 3, 4, 5, 4, 4, 3 and 4 in the table's order, the points are 16, 12, 9, 12, 10, 8, 4, 3 and 4, totaling 78 out of 100.

Each evaluator should record an evidence reference and reason before the group reconciles scores. Do not count the same advantage repeatedly across categories. If prices are to receive a formula-based score, define that formula and comparable cost basis in advance rather than switching methods after seeing the bids.

26 Run a demonstration based on your workflow

Give finalists the same demonstration scenarios and explain what evaluators will observe. Allow reasonable preparation, but distinguish a live supported function from a mockup, a manual workaround and a promised enhancement.

Begin with an ordinary order, then introduce a difficult case. Ask the team to show missing candidate information, a delayed search, a disputed record, a corrected report and an integration failure. Include a role-specific service if it is material to the contract.

Request a demonstration of permissions and reporting as well as the attractive ordering screens. A recruiter, administrator and reviewer may need different access. Show how an administrator prevents an inappropriate package from being ordered and how the organization retrieves a record of important actions.

Record the outcome of each scenario, unresolved questions and commitments for follow-up. A demonstration is evidence about the demonstrated configuration; it should not be treated as proof that all locations or products behave identically. Verify important exceptions before contracting.

27 Use a controlled pilot for critical uncertainties

A pilot should resolve a defined question, such as whether an integration works in your environment or whether candidate support handles a particular workflow. Agree on the scope, duration, responsibilities, acceptance criteria and cost before beginning.

Start with fictional or appropriately de-identified cases wherever possible. If real consumer reports are necessary, establish the proper authority, notices, authorization, security and other applicable requirements. Do not run duplicate live checks merely to stage a race between vendors without considering those obligations and candidate impact.

Measure the same outcomes for each test case. Record start and completion events, manual effort, exceptions and support interactions. A small pilot can validate workflow, but it cannot establish a statistically reliable accuracy rate for the provider's entire operation.

When pilot results differ, investigate scope and methods before deciding which result is better. More reported information is not automatically more accurate or more appropriate. Close the pilot with a written decision about what passed, what needs correction and what must be retested before launch.

28 Negotiate the commitments that matter

Make sure the agreement reflects the service evaluated. Identify the contracting entity, scope, pricing schedule, implementation deliverables, support model, service measurements and change process. Record important proposal commitments in the binding documents rather than leaving them in a presentation.

Review term, renewal, notice periods, minimum commitments, fee increases and termination provisions. Clarify how pass-through charges are defined and disclosed, whether custom work is reusable, and what assistance and cost apply if the relationship ends.

Legal, privacy and security reviewers should address responsibility allocation, confidentiality, permitted data use, incident reporting, subcontractors, insurance and other relevant terms. Contract language cannot by itself remove statutory duties that apply to the parties. Avoid assuming that a broad compliance warranty answers every operational question.

Confirm how future changes will be handled. A new source, platform migration or AI function may affect service, data use or risk. Establish notice and approval mechanisms appropriate to those consequences. The goal is a workable agreement that both teams can administer, not a collection of promises no one measures.

29 Plan the transition before ending the existing service

Work backward from a realistic launch date and current contract obligations. Assign owners for package configuration, form review, integrations, permissions, candidate communications, training, billing and acceptance testing. Identify dependencies that could delay launch.

Decide what happens to open reports and disputes at the old provider. Candidates should know which organization is handling their case, and recruiters should know where to find the authoritative status. Avoid automatically recreating every unfinished order with the new vendor.

Determine which historical records need continued access or transfer, what the organization may lawfully retain and how permissions and corrections will be managed. Migration is not simply copying every available report. Use a defined scope with appropriate safeguards and retention requirements.

A phased launch can reduce operational risk when there are many locations or packages. Establish go-live criteria, a support schedule for early issues and a fallback plan. Do not cancel needed access to the old service until the transition obligations and records requirements have been resolved.

30 Manage the relationship after selection

Selection establishes a starting point. Schedule an early review after implementation and a recurring review appropriate to volume and risk. Compare actual results with the assumptions and commitments used to select the provider.

Review unresolved reports, changes in turnaround, support performance, consumer complaints, corrections and charges. Look for patterns by source or package rather than treating every problem as an isolated ticket. Agree on corrective actions, owners and dates.

Reassess requirements as the organization changes. Entering a new country, adding regulated positions or adopting a new ATS may require a revised service design. Likewise, changes in provider ownership, systems or suppliers may justify renewed diligence.

Keep an exit plan current even when the relationship works well. Know the renewal window, access options, export limitations and treatment of open cases. A well-managed provider relationship makes responsibilities understandable throughout the contract, including at its conclusion.

31 Warning signs that deserve follow up

These signs call for clarification and evidence. Some may be resolved by a more precise response; others may reveal a substantive gap. Record the distinction. A provider that clearly discloses a limitation can be easier to evaluate than one that claims every requirement is already solved.

32 Final selection checklist

The final decision record should identify the selected provider, why it fits the requirements, known limitations, agreed remedies and the conditions that must be satisfied before launch. A numerical score supports this judgment; it does not replace it.

33 Frequently asked questions

Is a large provider always the best choice

No. Scale may support capacity and geographic breadth, but the buyer must verify the specific service, account support and implementation resources being offered. A smaller provider may also meet demanding requirements when its operations and infrastructure support them.

Does using the same screening platform make two CRAs equivalent

No. Research methods, package scope, verification effort, quality procedures and support can differ. Evaluate both the shared technology and the CRA's own work.

Is the lowest package price the lowest cost

Not necessarily. Source fees, additional searches, verification charges, minimums and integration costs can change the total. Compare the same expected workload and separate one-time costs from recurring costs.

Does a SOC 2 report cover every part of the provider

Only the defined scope should be relied upon. Review the actual system, entity, period, categories, exceptions and treatment of other service organizations. A hosting or platform report may leave important CRA operations outside its scope.

Does PBSA membership mean the company is accredited

No. Membership and organizational accreditation are distinct. Verify the applicable accreditation program and the current status of the entity providing the service.

Can a provider guarantee that an employer is compliant

A provider can support a lawful process, but the employer retains duties of its own. Evaluate the division of responsibilities, current forms and workflow controls rather than rely on a general guarantee.

Do we need an RFP for every purchase

No. Use a process proportionate to the complexity and risk. Even a smaller selection benefits from consistent requirements, evidence, demonstrations and a written cost comparison.

Should the highest score automatically win

No. Mandatory gates, unresolved findings, contract terms and documented business judgment remain important. If the selected provider does not have the highest score, record the substantive reasons rather than quietly changing the scoring method.

The central principle of Part V

A strong provider evaluation makes the service understandable before the organization depends on it. The buyer should know what will be searched, how information will be reviewed, how candidates can obtain help, what the program will cost and who will respond when the ordinary process breaks down.

The complete guide has followed the screening system from industry structure through research, compliance, specialized capabilities and provider selection. Across each part, the same standard applies: relevant information, reliable methods, clear responsibilities and decisions supported by evidence.

Related SimpliVerified resources

Parts I through IV provide the background for this evaluation framework. Background Screening for Employers addresses the employer's operating responsibilities. The guides to Pre-Adverse and Adverse Action, Background Check Disputes, and Fair-Chance and Ban-the-Box Laws explore important workflows in more detail. Housing providers should use the Tenant Screening guide for the differences relevant to their decisions.

The AI Background Screening RFP Builder Toolkit supports conversion of organizational needs into procurement documents. Use this chapter to assess the resulting requirements and evaluate provider responses. The toolkit is designed for a vendor-neutral process, including proposals from providers other than SimpliVerified.

To discuss how SimpliVerified could support your organization's requirements, contact SimpliVerified. Apply the same evidence and evaluation standards to every provider you consider.

Source review and maintenance

Primary-source links appear beside the relevant claims. Sources were reviewed on September 23, 2026. Vendor product pages are used only to illustrate the existence of platform-based service models, not as independent validation of comparative performance. The scorecard, cost model, examples and recommended buying process are editorial tools rather than legal requirements or market benchmarks.

Recheck accreditation status, security-report scope, product capabilities, legal sources and commercial terms during an actual procurement. The evaluation should use current evidence from the entity and service being considered.