Screening integration

Track TazWorks background checks in Wingspan

Bring TazWorks check status into Wingspan. Match each screening record to the right worker and check. Your team reviews results under its own rules and report access permissions. See which required checks remain open for each assigned job.

Discuss your integration
TazWorks logo TazWorks
Wingspan

Connect the work to the payment

  • TazWorks

    Applicant

    Wingspan

    Worker records (payees)

  • TazWorks

    Product

    Wingspan

    Check template context

  • TazWorks

    QuickApp

    Wingspan

    Screening invite context

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

Track checks in one place

Bring TazWorks order status to the right worker check. See what is done and what still needs review. Your team tracks progress in Wingspan. Keep each check tied to the jobs it serves.

Keep review steps clear

TazWorks runs the screening checks. Wingspan tracks the linked worker checks and job readiness. Your team reviews the findings under its own rules. A complete report still needs review. Work review and pay approval remain separate steps.

Keep report access scoped

Match screening records to workers using selected IDs, status fields, and report references. Set access rules for screening details and full reports. Worker bank and tax records follow their own onboarding and payment requirements.

How TazWorks works with Wingspan

TazWorks helps screening firms run background checks. Wingspan tracks workers, checks, jobs, and pay. Worker types include Contractor and W-2. A payee is your worker record in Wingspan.

The link brings order status and report references to selected worker checks. Your team matches the TazWorks applicant ID to the right worker. A person being screened is not a worker by default. You create and invite workers in separate steps.

TazWorks products give screening package context. QuickApp collects screening details and consent in TazWorks. A finished report shows that the search is done. Your team still reviews the result.

A check can serve more than one assigned job. Wingspan checks each attached job against all of its required checks. A passed check does not approve work or pay.

Start with the records you already use

Applicant
A person profile in TazWorks. It stores the details needed to screen that person.
Order
A request for a background check in TazWorks. It tracks the searches for one person.
Product
A screening package in TazWorks. It groups search types, such as criminal records.
QuickApp
A TazWorks form that collects screening details and signed consent from the person being checked.
Report
The findings from a screening order. The report has its own access rules in TazWorks.
Client
A TazWorks account for a business that orders checks. It holds the client settings for screening.
Webhook
An event sent by TazWorks when order data changes. The event helps Wingspan track check progress.

Sync options

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

Applicant

Worker records (payees)

TazWorks to Wingspan

Match a TazWorks applicant ID to a selected worker record in Wingspan. A match links the screening data to that worker. It does not create the worker or send an invite. Contractor or W-2 is a type on the worker record.

Product

Check template context

Reference or reporting

A TazWorks product names the screening package used for a check. Your team uses that package as context when setting check rules in Wingspan. Package selection and Wingspan check rules are separate steps.

QuickApp

Screening invite context

Reference or reporting

QuickApp is the TazWorks flow for screening details and consent. Its invite goes to the person being screened. It gives your team context for the linked check. A Wingspan worker invite is a separate step.

Order

Selected background check

TazWorks to Wingspan

Link a TazWorks order ID and status to the chosen check in Wingspan. The order tracks the searches run by the screening firm. Wingspan tracks the check for the matched worker.

Report

Check result and review

TazWorks to Wingspan

Bring report status and an allowed report link to the chosen check in Wingspan. Staff with access rights use the link to review the findings. Keep report status, search findings, and the review decision distinct. Your rules decide how the check is cleared.

Webhook

Selected check update

TazWorks to Wingspan

TazWorks events bring order updates to the linked check in Wingspan. Match the order and person IDs to the right check and worker. Staff see check progress. Each event updates the selected records.

Screening status

Readiness for attached jobs

Reference or reporting

Wingspan tracks readiness for each job attached to the check. The job must meet all of its required checks. One passed check does not clear every job. Work review and pay approval remain separate steps.

Integration workflows

01

Link screening to a worker check

Your team links a TazWorks order to a worker check.

Your team selects the worker and check in Wingspan. It matches them to the TazWorks applicant and order IDs. Order status then appears on the linked check. The worker keeps their Contractor or W-2 type. Screening data does not create a new worker.

02

Review a finished report

TazWorks marks a report complete.

The linked check shows that the report is done. Staff with access rights open the report in TazWorks. Your team reviews the findings under its own rules. A done report does not mean a clear result or an approved check. Your team records the review as a separate step.

03

Check readiness for each job

Your team reviews a check linked to one or more jobs.

A worker check can attach to more than one job in Wingspan. Each attached job has its own required checks. Wingspan tracks readiness based on all of those checks. Worker tax forms stay on their own path. Work review and pay approval follow their own steps.

Plan your integration

Use the right worker type

Worker types include Contractor and W-2. The type belongs to the worker record. Use that type when you match screening records. Contractor tax forms and pay differ from W-2 payroll forms and pay. Background checks do not set or change a worker's type.

Set clear review rules

A completed TazWorks report still needs a review under your rules. Keep the order status, result, and review decision separate. A check can serve several jobs. Readiness applies to its attached jobs and all the checks those jobs require.

Limit shared screening data

Choose the status fields, match IDs, and report references needed for each linked check. Set access rules for full reports and private screening details. Screening fees remain separate from the amount owed to a worker.

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
Match TazWorks applicant IDs to selected worker records. A screening applicant is not a worker by default. A payee is the worker record in Wingspan. Worker types include Contractor and W-2. Creating a worker and sending an invite are separate steps.
Engagements and assignments
A work template holds the shared rules for jobs. An assignment is one worker's job under that template. A worker check can serve several assignments. Screening packages give context for the checks on those jobs.
Requirements and eligibility
Order status and allowed report references link to selected worker checks. Screening packages give context for those checks. Your team sets the check rules in Wingspan. Report completion, search findings, and review decisions stay distinct. All required checks count toward readiness for the attached jobs.
Work logs and approved work
Screening records describe checks. Work items and work logs stay on their own Wingspan paths. Your team reviews work logs separately. Clearing a screening check does not approve hours, shifts, or tasks.
Payables
Screening fees stay separate from worker pay. For contractor work, Wingspan links an approved work log to one amount owed. The contractor sees an invoice. The payer sees a payable. W-2 pay uses payroll and pay statements. Payment approval is a separate step.
Client invoices
Client invoices bill clients for work. Those bills stay on a separate Wingspan path from worker pay. A TazWorks check does not create a client bill.
Payments and payouts
Wingspan handles worker pay on its own path. Required checks, work review, and pay approval are distinct steps. A screening update does not send money. TazWorks screening fees stay separate from pay owed to the worker.
Tax forms and reporting
Contractor tax steps include Form W-9 and Form 1099-NEC. W-2 workers use payroll tax forms and pay statements. Wingspan keeps these tax steps on their own path. A background report does not complete tax setup or a tax filing.

Explore related integrations

Connect TazWorks 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