Screening integration

Track Checkr background checks with your worker jobs

Link Checkr background checks to chosen worker records in Wingspan. Report status and results flow to the right worker checks. Your team reviews each check under its own rules. See which checks each worker job still needs.

Discuss your integration
Checkr logo Checkr
Wingspan

Connect the work to the payment

  • Checkr

    Candidate

    Wingspan

    Payee (worker record)

  • Checkr

    Report

    Wingspan

    Requirement (worker check)

  • Checkr

    Package

    Wingspan

    Requirement definition (check template)

Choose which records sync and when they move. Your team stays in control of work review and payment approval.

Track worker screening

See Checkr report status next to the chosen worker check. Your team sees which checks need review. Match each result to the right worker. Keep the worker's Contractor or W-2 type on their record.

See what each job needs

Track the required checks for each worker job. One worker check can attach to several jobs. A clear Checkr report still needs your review rules. Each job needs all its required checks before it is ready.

Review screening with the right access

Candidates share private details and consent through the Checkr flow. Your team reviews full reports with the right Checkr access. Report status and references link the review to the chosen worker check in Wingspan.

How Checkr works with Wingspan

Checkr runs background checks and driving record searches. Wingspan tracks workers, required checks, work, and pay. Each worker keeps their Contractor or W-2 type on their worker record.

Your team orders screening in Checkr, where candidates share private details and give consent. A complete report means the searches have ended. Clear and consider describe the result, while Assess applies rules set in Checkr. Your team still owns the hiring choice.

Wingspan links selected candidate IDs to chosen worker records and sends results to the checks your team selects. An engagement is a work template, and an assignment is one worker job under that template. One worker check can attach to several jobs.

Your team applies its own review rules, so a clear report does not pass a worker check on its own. Each job needs all its required checks, with work review and pay approval as separate steps. Full reports need the right Checkr access.

Start with the records you already use

Candidate
A person record in Checkr. It holds contact details and IDs used to match screening records.
Report
A screening report in Checkr. It has search findings, report status, and results.
Invitation
A Checkr invite for a candidate. It links to the form for private details and consent.
Package
A group of searches in Checkr. It sets the checks included in a report.
Assessment
The result of Checkr Assess rules. It is separate from report results and your hiring choice.
Subscription
A Checkr schedule for repeat reports. It runs checks at set times.
Node (Account Hierarchy)
A unit in a Checkr account tree. It groups screening records by branch or team.

Sync options

Choose which tool holds each record. Set the changes that sync between them. Connect your records to the Wingspan workflows below.

Candidate

Payee (worker record)

Reference or reporting

Your team links selected Checkr candidate IDs to chosen worker records. A candidate record does not create a worker. Each worker keeps their Contractor or W-2 type. The match sends screening status to the right worker.

Report

Requirement (worker check)

Checkr to Wingspan

Checkr report status and results flow to chosen worker checks. Complete is a report status. Clear and consider are report results. A clear result does not pass the check on its own. Your team applies its review rules. One check can attach to several worker jobs.

Package

Requirement definition (check template)

Reference or reporting

A Checkr package gives context for a worker check. It lists the searches in a report. Your team chooses the package in Checkr. The work template in Wingspan sets the checks a worker job needs.

Invitation

Screening context

Reference or reporting

Checkr invitations guide candidates through sharing details and giving consent. Invitation records provide context for the linked worker check. Report status updates the chosen check in Wingspan.

Assessment

Screening context

Reference or reporting

Checkr Assess checks findings against set rules and returns eligible, review, or escalated. A report has its own clear or consider result. Your team applies its rules when reviewing the linked worker check in Wingspan.

Subscription

Screening context

Reference or reporting

Checkr subscriptions run new reports on a set schedule. Continuous Check is a separate service that looks for new records. Your team runs these services in Checkr. New report results link to chosen worker checks in Wingspan.

Node (Account Hierarchy)

Screening context

Reference or reporting

Checkr nodes group screening records by branch or team. They give context for your checks. A Wingspan work template holds the checks each worker job needs. Your team keeps those scopes in view when it chooses the worker checks.

Report adjudication action

Requirement (worker check)

Checkr to Wingspan

Your team reviews the report in Checkr. Selected review outcomes link to the chosen worker check in Wingspan. Each attached job needs all its required checks. A passed check leaves work review and pay approval as separate steps.

Integration workflows

01

Track a new worker check

A worker job needs a background check.

Your team orders the package in Checkr. The candidate shares details and gives consent through the Checkr flow. Your team links the candidate to the chosen worker record. Checkr report status and results flow to that worker check. Your team applies its review rules. Each attached job needs all its required checks. The worker keeps their Contractor or W-2 type.

02

Review a report with findings

Checkr has finished the report. The result is consider.

A complete report has finished its searches. A consider result means your team needs to review the findings. Assess is a separate set of Checkr rules. Your team opens the full report with the right Checkr access. It owns the hiring choice and any adverse action steps. Selected review outcomes link to the worker check in Wingspan. Each attached job still needs all its required checks.

03

Track repeat screening results

Checkr returns a new report for a matched worker.

Checkr subscriptions run reports at set times. Continuous Check looks for new records and starts a report when it finds a change. Your team manages both flows in Checkr. New report status and results link to the chosen worker checks. Your team reviews the results under its rules. Each job still needs all its required checks.

Plan your integration

Choose screening scope for each job

Your team chooses the Checkr package for each screening flow. A driving role needs the right driving searches. Wingspan work templates set the required checks for each worker job. One worker check can attach to several jobs. Review the screening scope for each attached job.

Own the report review

Review findings with the right Checkr access and choose which review outcomes link to Wingspan worker checks. Your team owns the hiring decision and any adverse action steps. Passing a worker check leaves work review and pay approval as separate steps.

Keep each worker's type

Contractor and W-2 types belong to the worker record. Keep that type when linking a Checkr candidate. Contractor pay uses invoices and payables. W-2 pay uses pay statements and payroll with taxes. Tax forms and bank details stay on their own Wingspan paths.

How the worker lifecycle fits

Connect worker records from hire to pay. Choose the Contractor or W-2 type and keep the right checks for each.

Workers and worker types
Selected Checkr candidate IDs link to chosen worker records. Each worker keeps their Contractor or W-2 type. The match sends results to that worker's checks.
Engagements and assignments
An engagement is a work template. An assignment is one worker job under it. A Checkr package gives context for the required worker checks. Checkr nodes provide account context for screening.
Requirements and eligibility
Checkr report status, results, and selected team review outcomes link to chosen worker checks. A clear report does not pass a check on its own. One check can attach to several jobs. Each job needs all its required checks.
Work logs and approved work
Work logs track work in Wingspan. Your team reviews the work there. Approved contractor work creates a linked invoice and payable. They are two views of one amount owed. Pay approval is a separate step.
Payables
A worker payable is an amount owed to a contractor for work. Checkr fees are vendor costs for your business. Screening results do not create worker bills.
Client invoices
Client invoices track what your clients owe your business. They are separate from worker bills and Checkr screening fees.
Payments and payouts
Contractor runs pay approved worker bills. W-2 runs pay wages with taxes. A sending bank's processed status does not prove the worker's bank has posted the funds.
Tax forms and reporting
Contractors use W-9 forms and 1099 tax reporting. W-2 workers use W-4 forms and W-2 tax reporting. Checkr collects private screening details and consent through its own flow.

Explore related integrations

Connect Checkr to your worker workflows

Bring worker records, work review, and payments together. We’ll help you set up the flow your team needs.

Discuss your integration