Background Verification for Contract Workers

Frequently asked questions

What checks are included in the background verification module?+

Aadhaar-based offline identity verification with worker consent, PAN and UAN validation, criminal and court record screening at current and permanent addresses, address verification, employment history, and education or trade-certificate checks where the role requires them. Iddion RegX runs these against the worker's record so results attach to their biometric identity, not a paper file.

What sources are checks run against?+

Government identity databases, court and criminal record databases, EPFO records for employment history, and field verification for physical address checks. Each result carries its source and date, so a report can be assessed on what was actually checked rather than a single pass/fail flag.

How does a verified status translate to gate access?+

Once a worker's background check clears, Iddion RegX writes the result to their biometric identity record — the same identity the gate terminal reads at every entry. A cleared worker enters; a pending or adverse worker is blocked at the barrier without any manual security check. The gate acts on live status, not on a report someone remembered to look at.

What does 'unable to verify' mean for a worker's gate status?+

A record that returns 'unable to verify' is held as pending rather than cleared — the worker's gate pass is not activated until the outstanding item resolves or a manager permits entry under an overridden status with a recorded reason. The system distinguishes all three outcomes — clear, adverse, unable to verify — so security is never making a judgement call on an ambiguous result.

How does re-verification work when a check expires?+

Re-verification schedules are configured per worker category and trigger automatically. When a check nears expiry, Iddion RegX alerts and starts the re-verification workflow. If the check expires before a new result returns, gate access is suspended automatically — the same enforcement mechanism as an expired medical clearance.

How does verification status control site access?+

BGV status is a live gate rule: pending or expired means no entry, enforced at the barrier rather than tracked in a monthly report. Status changes take effect at the next gate attempt without any manual update to security.

Can we set different verification requirements by role or site?+

Yes. A housekeeping worker, a hot-work fitter, and a worker entering a defence establishment carry different requirement sets, configured per category and site. Required checks are hard blocks; informational checks log findings without stopping deployment.

How does this relate to InOps standalone BGV service?+

This module is verification built into the platform — checks run automatically as part of onboarding and results enforce gate rules without a separate process. If you need checks without deploying the full CLMS — per-check pricing, bulk upload, contractor bench packages — see background verification services.

Can verification run in parallel with other onboarding steps?+

Yes — running verification concurrently with medical fitness and induction is how Iddion RegX compresses onboarding from days to hours. Workers are cleared as results return rather than waiting for all steps to complete sequentially. See the onboarding module for how the parallel steps are managed end to end.