Designing an India-first screening policy

Most India hiring programmes fail policy design in the same place: they copy a global template, then discover state-level court workflows, candidate communication, and retention rules need local decisions.

Start with purpose. For each check family (identity, employment, education, court), write why it is required for the role tier—not why it is available in a catalogue. If you cannot defend the check to a candidate or auditor, remove it from that package.

Next, define consent and notice. Candidates should understand what will be verified, who will see outcomes, and how long evidence is retained—before they upload documents. Keep language plain; reserve legal detail for the employer agreement and privacy notice.

Map geography deliberately. Court and address programmes behave differently across metros and smaller towns. Set package SLAs by region, and train recruiters to set expectations early.

Finally, close the loop with documentation. Store who ordered the package, which evidence supported each decision, and who signed off. That trail is what makes screening usable in disputes and audits—not just “completed” status in an ATS.