Verifying a contractor or a gig worker once, at onboarding, is a good start — but a lot can change after day one. Roles end, clearances lapse, and the person who onboarded isn't always the person who shows up months later. Periodic re-verification keeps a one-time check from going stale.
Why once isn't enough
- Long-running contractors whose status may have changed.
- Distributed and gig workforces you don't see daily.
- High-assurance sites where stale clearance is a real risk.
- Regulated contexts that expect ongoing, not one-off, assurance.
What re-verification looks like
It's the same source-verified check — Aadhaar or a document, with liveness — run again on a schedule or trigger: a set interval, a return after a gap, or a change in role. The point is to confirm the person is still who they claim and still cleared, not to re-onboard from scratch.
Keep it proportionate and consented
Re-verify where the risk justifies it, capture consent each time, and keep it minimal — the same DPDP principles as the first check. Don't turn assurance into surveillance.
Fits distributed workforces
For driver and delivery or contractor workforces, periodic re-checks are exactly the pattern — field-friendly, and offline-capable where connectivity is poor.
Re-verification with Certopact
Run re-verification through Certopact Entry or embed it via Certopact Verify on your own schedule. This is general information, not legal advice.