The Problem with Static Verification Packages
Traditional background screening works like a menu: you pick a package (Basic, Standard, Comprehensive), hand it to a vendor, and get back a report. This model made sense when verification was a once-per-hire activity. It does not make sense when verification is a continuous operational process with different requirements per role, per geography, and per risk event.
The compliance teams and operations leads who talk to us most often describe the same frustration: they know exactly what they need, but expressing it requires either hacking together multiple vendor products or waiting months for an engineering team to build a custom integration. Profiden Workflow Builder is our answer to that problem.
What Workflow Builder Does
Workflow Builder is a visual configuration tool that lets any user — no programming knowledge required — design multi-stage verification flows using a drag-and-drop canvas. The key capabilities:
Conditional Branching
Define rules that determine which checks run based on data that comes back from earlier in the workflow. Examples:
- If PAN verification returns a name mismatch > 20%, trigger a manual review step before proceeding to employment verification
- If the candidate's declared salary is above ₹15 lakh, automatically add a credit check to the package
- If the employment history check reveals a gap of more than 12 months, add a reference check for that period
Parallel Execution
Checks that do not depend on each other run simultaneously, not sequentially. A workflow can run identity verification, address verification, and EPFO employment lookup in parallel — reducing total turnaround time to the duration of the slowest parallel check, rather than the sum of all checks.
SLA Triggers and Escalation Rules
Set SLA targets per check type. When a check misses its SLA, the platform can automatically: escalate to a senior verifier, switch to an alternate data source, flag the case for ops review, or send a notification to the hiring manager. No manual monitoring required.
Role-Based Packages Built Dynamically
Instead of maintaining 15 different static packages for different role types, define a single rule set that generates the right package for each candidate based on role tier, location, department, and employment type. The package is assembled automatically at case creation.
How It Works in Practice
A typical implementation looks like this:
- An ATS integration (Darwinbox, SuccessFactors, Workday, or a webhook) triggers a new case in Profiden when an offer is accepted
- The workflow evaluates the candidate's role metadata and selects the appropriate check package
- Consent notice is generated and sent to the candidate automatically
- Parallel checks begin as soon as consent is received
- Results are aggregated into a unified report, with any discrepancies flagged for human review
- The final status is pushed back to the ATS or HRMS via webhook
Most customers who implement this flow see time-to-hire impact from background verification drop from 7–10 days to 2–3 days.
What's Coming Next
We are working on two additions to Workflow Builder shipping in Q3 2025:
- Event-triggered re-screening: A workflow that fires automatically when a re-screening trigger event occurs — a role change, a large transaction, or a periodic calendar interval — without requiring a new case to be created manually
- Multi-vendor orchestration: The ability to route specific checks to different vendors within a single workflow, with fallback rules if the primary vendor returns an inconclusive result
If you are a current Profiden customer and want early access to either of these features, reach out to your account manager.