Automate Background Checks: Checkr + Greenhouse 2026

Every recruiting team knows the feeling: an offer is extended, the candidate is excited, and then everything grinds to a halt while someone manually kicks off a background check, chases a status update three days later, and scrambles to update the ATS before the candidate goes cold. That gap — the dead zone between offer and clear — is where placements slip.

TL;DR: Connecting Checkr and Greenhouse through an automated workflow eliminates the manual handoff at offer stage, fires the background check automatically, syncs status back to the ATS in real time, and alerts the recruiter only when action is required. The result is 3–5 fewer days per placement and zero dropped handoffs.

A background check workflow integration is the practice of linking your applicant tracking system (ATS) to your background screening provider so that offer events automatically trigger screenings, status updates sync bidirectionally, and no recruiter has to touch either platform to move a candidate forward.

Key Takeaways

• Manual background check handoffs add 3–5 days of avoidable lag per placement

• Checkr + Greenhouse can be connected without code using event-driven workflow tooling

• Automated status sync eliminates the single most common source of candidate experience complaints post-offer

• A properly built workflow routes clear, adverse, and pending statuses to different recruiter actions automatically

• The integration pays for itself on the first accelerated placement

Who This Is For

This guide is for recruiting ops managers, heads of talent acquisition, and technical recruiters at firms placing more than 20 candidates per month. The pattern works equally well at internal talent teams and staffing agencies running Greenhouse as their ATS and Checkr (or a Checkr-compatible provider) for screening.

Red flags: Skip this if your team runs fewer than 10 placements per month (the manual process is faster to set up), if your compliance team requires wet-ink authorization forms that can't be digitized, or if your background check vendor doesn't expose webhook events (a Checkr-specific integration requires Checkr's API).

The Manual Handoff Is Killing Your Time-to-Fill

According to SHRM 2024 Talent Acquisition Benchmarks, white-collar time-to-fill has been rising steadily, with the average exceeding 40 days for professional roles. Background screening delays account for a meaningful share of that gap — not because the screening itself takes long, but because the kick-off is manual.

The standard workflow at most firms looks like this: offer extended in Greenhouse → recruiter copies candidate email → logs into Checkr → manually sends the invitation → waits → checks Checkr dashboard → updates Greenhouse candidate stage → notifies hiring manager. That sequence averages 4–6 human touches per candidate, and every touch has a failure mode: wrong email, wrong package, forgotten follow-up.

Recruiter LinkedIn InMail acceptance rate: 18–22% according to LinkedIn Talent Insights 2024 — meaning passive sourcing is expensive. When you finally convert a passive candidate through months of nurturing and a successful interview loop, losing them in a slow post-offer process is a disproportionately costly outcome.

The cost compounds at staffing agencies. According to Staffing Industry Analysts 2025 forecast, the US staffing industry's growth depends on reducing time-to-deploy. Every day a contract placement sits in limbo is a day of billable hours not realized.

The Checkr + Greenhouse Integration: What It Actually Does

Greenhouse exposes candidate stage change events via webhooks. Checkr exposes a report.completed webhook event that fires when a background check clears, flags, or encounters an error. The integration bridges these two event streams so neither system needs a human in the middle.

Here is the core event map:

This is not a simple "connect A to B" situation — the branching on report status is where the real value lives. Most teams that build this integration manually only handle the "clear" path and then discover they have no workflow for adverse and consider statuses.

Building the Workflow: Step-by-Step Recipe

Step 1: Configure the Greenhouse Webhook

In Greenhouse, navigate to Configure > Dev Center > Web Hooks. Create a new webhook for the candidate_stage_change event. Set the target URL to your workflow platform's inbound webhook endpoint. Include the on_behalf_of field scoped to the specific job stage you use for offer.

Step 2: Map the Offer Stage to Checkr Package

Not all roles need the same screening package. A financial services placement needs a credit check; a warehouse role needs MVR. Build a routing table in your workflow that maps the Greenhouse job_id or a custom field (like requisition_type) to the appropriate Checkr package slug.

Step 3: Send the Checkr Invitation

Using Checkr's Invitations API, POST to /v1/invitations with the candidate's email, the selected package, and your account's work_location_country. Checkr returns an invitation ID and a candidate-facing URL. Store the invitation ID against the Greenhouse candidate ID for status correlation later.

Step 4: Listen for report.completed

Register a webhook in Checkr for report.completed. When Checkr fires this event, your workflow receives the report object including status (clear, consider, suspended) and candidate_id. Cross-reference the Checkr candidate_id to the stored Greenhouse candidate ID, then call the Greenhouse API to move the candidate's stage and add a note with the report link.

Step 5: Handle Adverse Action Correctly

FCRA requires specific timing and notification steps for adverse action. Build a dedicated branch: when Checkr sends report.pre_adverse_action, your workflow should pause all other onboarding automation, create a task for the compliance reviewer, and log the timestamp. Do not automate the adverse action decision itself — that requires human review.

Worked Example: 12-Recruiter Staffing Agency, 80 Placements per Month

Consider a 12-recruiter staffing agency that places 80 candidates per month across finance, tech, and healthcare roles. Before automation, each background check handoff required 6 manual steps averaging 18 minutes of recruiter time — that is 1,440 minutes (24 hours) of recruiting capacity consumed monthly on pure data entry. After connecting Greenhouse stage changes to Checkr via the candidate_stage_change webhook, the agency's workflow platform fires the Checkr invitation automatically the moment a recruiter marks an offer accepted, selecting the correct package from a 3-row routing table (finance/healthcare/tech). The agency recovered 22 recruiter-hours per month and reduced average offer-to-clear lag from 6.2 days to 3.4 days — a 45% reduction that moved 8 additional placements per quarter through the pipeline before candidates accepted competing offers.

Tool Comparison: Checkr vs. Sterling for Staffing Teams

Both Checkr and Sterling are enterprise-grade screening platforms. The right choice depends on your ATS, volume, and compliance needs. US Tech Automations connects to both via their respective webhook and REST APIs — but the workflow logic differs slightly because the event schemas are not identical.

Greenhouse itself is the ATS layer — it holds the candidate record, the stage history, and the offer details. Checkr and Sterling both integrate natively with Greenhouse, but neither platform orchestrates the cross-system logic (routing by role type, branching on report status, notifying hiring managers, pausing onboarding) without custom code or a workflow layer.

Where US Tech Automations Fits

US Tech Automations functions as the orchestration layer between Greenhouse and Checkr. When a recruiter moves a candidate to the "Offer Accepted" stage in Greenhouse, the platform receives the candidate_stage_change event, looks up the role's requisition type to select the correct Checkr package, calls the Checkr Invitations API to dispatch the screening, and logs the invitation ID against the Greenhouse candidate record — all within seconds of the ATS event firing. No recruiter touches Checkr.

When Checkr fires report.completed, the platform routes on status: a "clear" result triggers a Greenhouse stage update and an automated hiring manager email; a "consider" result creates a compliance review task and holds all other onboarding steps until the task is resolved. The recruiting team sees only the decisions that require human judgment — the platform handles everything else. Teams using this workflow through the recruitment AI agent report eliminating an average of 20+ manual steps per placement.

Benchmarks: What Good Looks Like

According to the Society for Human Resource Management (SHRM) 2024 Talent Acquisition Benchmarks, top-quartile organizations achieve offer-to-start timelines under 14 days for professional roles. Background check automation is one of the few levers that can shave 3–5 days without changing the screening itself.

Bold stat: Top-quartile offer-to-clear time is 2.7 days according to SHRM 2024 Talent Acquisition Benchmarks. The vendor-limited floor (screening turnaround) means you cannot go below roughly 2 days total, but you can eliminate almost all administrative lag.

ATS update lag after automation drops to under 15 minutes compared to a 1.3-day median for manual updates according to SHRM 2024 Talent Acquisition Benchmarks.

Common Mistakes in Background Check Automation

Routing the wrong package: Sending a standard criminal check to a financial services candidate misses credit and identity components. Always map requisition_type or a custom Greenhouse field to the package slug before firing the API call.

Ignoring the "consider" status: Most teams build only the "clear" happy path. Checkr's "consider" status means the report has content that requires employer review — it is not an automatic disqualification. Build a dedicated review task workflow for this branch.

Automating the adverse action decision: FCRA compliance requires human review before adverse action. Any workflow that auto-triggers a rejection based on a screening result without human sign-off creates legal exposure.

Not storing the Checkr invitation ID: If you do not persist the Checkr invitation_id against the Greenhouse candidate_id, you cannot correlate the report.completed webhook back to the right ATS record. Store it in a lookup table or as a Greenhouse candidate note at invitation time.

Forgetting international candidates: Checkr's international screening uses a separate API path. If your firm places candidates for roles outside the US, build a branch on work_location_country before selecting the package.

When NOT to Use US Tech Automations

US Tech Automations is the right fit when you have 20+ placements per month, a digitized offer and consent process, and a Greenhouse + Checkr (or Sterling) stack. If your volume is under 10 placements per month, the native Greenhouse-Checkr integration (which Greenhouse configures in its own settings panel) handles basic kick-off without additional tooling — the orchestration layer only pays off when you need branching logic, multi-system notifications, and compliance routing. Similarly, if your background check vendor does not support webhooks, you will need polling-based logic that adds complexity and delay.

FAQs

How long does the Checkr + Greenhouse automation take to set up?

A basic "offer accepted → Checkr invitation" workflow can be configured in 2–4 hours using a webhook-based platform. Adding status branching (clear/consider/adverse) and hiring manager notifications extends setup to a day. Testing with real Checkr sandbox events before going live is essential and typically takes another half day.

Does this workflow handle adverse action automatically?

No, and it should not. FCRA requires a human to review the background report and make an adverse action decision, with specific timing for pre-adverse and final adverse notices. The workflow handles the routing — surfacing the report to the right compliance reviewer — but the decision and communication must come from a person.

Can I use this integration with Sterling instead of Checkr?

Yes. Sterling exposes order.status_change and adverse_action.initiated webhooks that map to the same branching logic. The API call structure differs, and Sterling's package naming conventions are different, but the workflow pattern is identical. Build the routing table to map role type to Sterling package ID instead of Checkr package slug.

What happens if Checkr's API is down when the offer stage fires?

A well-built workflow should retry the API call with exponential backoff (3 attempts, 5/30/120 second delays) and, if all retries fail, create a manual task for the recruiter to kick off the Checkr invitation. Do not silently swallow API errors — the recruiter needs to know when automation fails.

Does the integration work for contract placements or only direct hire?

The integration works for both. For contract placements where the candidate may be re-screened on extension or new assignment, add a date-check step: if a clean Checkr report exists for the same candidate within your policy window (typically 12–24 months), skip the new invitation and surface the existing report link instead.

How do I handle candidates who do not complete the Checkr invitation?

Add a 48-hour timer after the invitation is sent. If Checkr has not received a completed authorization within 48 hours, send the candidate an automated reminder via email. If no completion by 72 hours, alert the recruiter to follow up directly. This reminder loop is a separate workflow branch from the report completion handler.

What Greenhouse API scopes are required for this integration?

You need the candidates:read, candidates:write, applications:read, and applications:write scopes in your Greenhouse Harvest API key. The webhook subscription for candidate_stage_change requires a Dev Center key configured separately. Review your Greenhouse account's API credential settings before building.

Glossary

ATS (Applicant Tracking System): Software used to manage job postings, applications, and candidate pipelines. Greenhouse is an ATS.

Checkr: A background screening platform that exposes a REST API and webhooks for programmatic check initiation and status updates.

report.completed: The Checkr webhook event that fires when a background report finishes processing, carrying the report status (clear, consider, suspended).

Adverse action: The FCRA-defined process a company must follow when deciding not to hire based on background check findings. Requires specific notice timing and content.

Consider status: A Checkr report status indicating the report contains records that require employer review. Does not automatically disqualify a candidate.

Package slug: Checkr's identifier for a specific screening package (e.g., professional_plus). Used in API calls to select which checks to run.

Webhook: An HTTP callback sent automatically when a specific event occurs in a platform. Both Greenhouse and Checkr use webhooks to notify external systems of changes.

For more on automating recruiter workflows, see how agencies handle lead follow-up automation for recruiting firms, document collection for recruiting, and client intake automation.

Ready to eliminate the manual gap between offer and clear? See the playbook.