Table of Contents
If you build a background check or screening platform, you live in a constant trade-off:
move fast for clear candidates / tenants / vendors
slow down only when something looks inconsistent
keep decisions explainable and workflows auditable
Identity enrichment (phone / email / name / profiles) can help — but only if you place it in the right part of the workflow. Put it too early and you add friction. Put it too late and you waste investigator time.
This guide shows how screening platforms typically use enrichment without slowing down good cases.
Important: enrichment provides signals and context, not “proof.” Use it to route workflows, not as a single automatic verdict.
The 3 places enrichment fits in a screening workflow
Most screening SaaS products have three moments where enrichment can help:
Intake (pre-check) — right after data is submitted
Before the full check runs — when you decide how deep to go
During adjudication / investigation — when a case needs human review
Each stage has a different goal.
1) Intake (pre-check): keep it lightweight and fast
Goal: catch obvious data issues early — without slowing everyone down.
Good uses at intake:
detect typos / malformed inputs (wrong phone format, impossible email shape)
spot inconsistency signals (example: name/email/phone don’t “fit” together)
pre-route into “clear” vs “needs attention”
What to avoid at intake:
heavy lookups for every case
any “block” decision based on one weak signal
deep profiling before you know you need it
Best practice: intake enrichment should be a triage filter, not a gate.
2) Before the full check: choose the right depth (and save cost)
This is where enrichment often pays off the most in screening products.
Goal: decide “how deep should we go” before running expensive checks or sending a case to manual review.
A simple depth model:
Fast track (low risk / consistent) → proceed with standard package
Standard (normal uncertainty) → proceed normally
Escalate (conflicts) → add verification steps or manual review
This is also where you protect your unit economics:
only run the heavier steps when the case actually needs it
3) Adjudication / investigation: the “explainability” stage
When a case is unclear, enrichment can help investigators answer a practical question:
“Do the submitted identifiers belong to the same real-world person or entity?”
Good uses here:
resolve identity confusion (similar names, transliteration, reused identifiers)
support case notes with consistent signals
reduce time spent switching tools
What to avoid:
treating enrichment as final truth
making irreversible decisions on ambiguous matches
Best practice: in adjudication, enrichment is a support tool for humans.
A simple routing model that works in screening SaaS
Instead of “pass/fail,” use routing tiers:
Green: consistent
Signals generally match the submitted story
→ proceed normally (no extra friction)
Yellow: uncertain
Some signals exist, but uncertainty remains
→ step-up verification or light analyst review
Red: conflicting
Strong mismatches or high ambiguity
→ manual review / escalation workflow
This reduces false positives because you stop forcing a binary decision from incomplete context.
Where most screening products go wrong
Mistake 1: running heavy checks on everyone at intake
This slows down the best candidates and increases abandonment.
Fix: use intake only for triage; go deep only when needed.
Mistake 2: no “uncertainty” bucket
Everything becomes “good” or “bad,” which creates noisy queues.
Fix: use a Yellow tier (step-up) and keep it measurable.
Mistake 3: no audit trail
When clients ask “why was this escalated?”, teams can’t explain.
Fix: store the signal summary + reason codes + request IDs used.
Recommended rollout order (safe and practical)
If you’re adding enrichment to a screening product this quarter:
Start in adjudication (analyst productivity win, low risk to UX)
Add it before full checks (depth selection, cost control)
Add a light intake triage last (careful: don’t add friction)
This order gives value fast and avoids conversion drop.
A quick checklist you can apply this week
Add routing tiers: Green / Yellow / Red
Use enrichment to route and explain, not to auto-reject
Log “why escalated” (reason codes) + request IDs for audit
Only run heavier steps when the case is Yellow/Red
Measure: turnaround time, manual review rate, client disputes
Resources (implementation)
Quickstart (15 min): https://espysys.com/irbis-api-quickstart-15-min/
Tutorial (async job + caching + normalization): https://espysys.com/api-tutorial/