Back to BlogCompliance

Police Verification of Contract Workers: A Factory Guide

10 Nov 2026 10 min read

Sooner or later every factory that uses contract labour asks the same question: who exactly is on our floor? A theft from the stores, an incident at the gate, or a client audit that asks for proof of worker verification usually brings it up. The first answer is often 'get police verification for everyone', which sounds thorough and usually turns out to be slow, uneven and not quite what the factory needed. This post explains what verification can and cannot tell you, whose job it is when the worker is on a contractor's payroll, how to handle identity documents without creating a data-protection problem, and how to set up a process matched to the risk of each role, so that a new worker is not left waiting for weeks. It is a practical guide, not legal advice. The data-protection rules in particular are still being phased in, so confirm the specifics with your counsel.

What verification can tell you, and what it cannot

It helps to separate three questions that tend to get bundled together. The first is identity: is this person who they say they are? The second is history: is there a criminal record or pending case against them that matters for this job? The third is reliability: will they turn up, do the work and stay? Identity checks are quick and dependable when done properly. Police verification goes some way towards the second question, but it reports only what the police records it searches contain, usually for the address given, and a clean report is not a guarantee about the person. No check answers the third question. Attendance, supervision and how the first month is handled tell you far more about reliability than any certificate does. Factories that expect police verification to screen out unreliable workers are usually disappointed, and the delay it causes can push away exactly the steady workers they wanted. Be clear about which question you are trying to answer for each role before deciding how much checking it needs.

Whose job it is when the worker is not on your payroll

For a contract worker, the contractor is the direct employer and is the natural party to collect documents and run checks. The factory is still the one with a stranger on its premises, and it carries real exposure if something goes wrong, so it cannot simply assume the checking has been done. The clean answer is to put it in the manpower agreement. The agreement should state what verification the contractor will complete for each category of role, by when, and in what form you will receive confirmation, and it should say what happens if a check comes back adverse. It should also say who bears the cost. Do not let the cost fall on the worker through a 'verification fee' deducted from the first wage, which is both unfair and the kind of deduction that causes trouble later. For roles where a specific law already requires checks, follow that law. Security guards are the main example: the Private Security Agencies (Regulation) Act, 2005 requires a private security agency to verify the character and antecedents of the guards it employs, so ask your security vendor for evidence that it has done this rather than repeating the exercise yourself.

Identity first, done properly

Most of what a factory needs comes from a careful identity check, and this is where shortcuts cause the most problems. Accept a recognised photo ID, check that the face matches the person in front of you, and check the details against the worker's bank account and the name used for PF and ESI registration, because a mismatch there will surface later as a payment or claim problem. Aadhaar is the document most workers carry, and it comes with rules. The Aadhaar Act and the regulations under it restrict how the number can be used and shared and prohibit displaying it publicly, so think about why you need the full number before you keep it. In most cases a masked Aadhaar, which shows only the last four digits, is enough for an identity file. Where you want to confirm the card is genuine, UIDAI supports offline verification through the secure QR code on the card or the downloaded e-Aadhaar, which confirms the details without your keeping the full number. Never keep a worker's original documents. Hold copies, give the originals back the same day, and if a contractor or hostel operator is holding originals 'for safe keeping', treat that as a serious warning sign.

How police verification works in practice

Police verification of an employee is generally a request to the police to check their records for a named person at a given address and report back. Many state police departments, Telangana's among them, offer some form of employee or tenant verification through their citizen services, and the route, form and fee vary and change over time, so check what is currently offered before you build a process around it. Two practical points matter most for a factory employing migrant workers. First, the address that counts is often the worker's permanent address in their home state, which means the check may have to go through the police in that district, and turnaround can be long and unpredictable. A check against the worker's local address in Hyderabad, where they may have lived for a week, tells you little. Second, verification needs the worker's knowledge and cooperation. Explain what is being checked and why, get written consent, and give them a copy of what they signed. A worker who discovers that the police came asking about them at home, without being told, is unlikely to stay long, and their family will be anxious about it too.

Previous employment and references

For many factory roles, a short conversation about where the person worked before, combined with a document that confirms it, tells you more than a police report. Workers who have been in formal employment will usually have a UAN, and their EPF passbook shows previous employers and contribution periods. Ask the worker to show you the history, rather than trying to get it some other way. Experience certificates from previous factories, skill certificates and training records are useful for operator and technician roles. A reference call to a previous supervisor is fine when the worker has given you the contact and agreed to the call. What you should avoid is informal checking: calling around other factories or contractors to ask whether anyone knows this person. It produces rumour rather than information, it can amount to an informal blacklist, and it is the kind of thing a worker would reasonably object to. If a contractor tells you a worker is 'known to be a problem', ask what is documented and treat anything undocumented with caution.

Handling the data: the DPDP Act applies

A verification file is personal data, and the Digital Personal Data Protection Act, 2023 governs how it is collected and used. The Rules under the Act were notified in November 2025, with most obligations phased in over the following months, so confirm with counsel which obligations apply to you now. The principles are worth adopting immediately, because they are good practice anyway. Tell the worker, in a language they understand, what you are collecting and why. Collect only what the stated purpose needs: a photo ID copy and a verification result, not a full photocopy of every document the worker owns. Keep the file where access is restricted, not in an open shared folder or a supervisor's phone gallery, and do not circulate ID copies on WhatsApp groups. Decide how long you keep records after a worker leaves, and then delete them, subject to any statutory retention period for employment records. Because the contractor usually collects the data, the agreement should also say how the contractor stores and shares it with you, and that it will not use it for anything else.

What not to do

A few practices are common and should stop. Do not ask for caste, religion or similar information as part of verification; it has no bearing on the job and creates obvious risk of discrimination. Do not treat workers from a particular state, district or community as needing heavier checking than others doing the same job. Base the level of checking on the role, not the person. Do not keep workers waiting without pay while a police report is pending, and do not let a worker start and then deduct a verification fee from their wages. Do not reject someone on the strength of an unverified rumour, and if a report does come back adverse, look at what it actually says and whether it is relevant to the work before deciding. A pending complaint from years ago is not the same as a conviction for theft. Finally, do not gather the documents and then file them unread. A verification process that nobody looks at gives a false sense of security, which is arguably worse than having no process at all.

A process that matches the check to the role

A workable approach is to sort roles into tiers. For general production and helper roles, the standard is a proper identity check, bank and PF/ESI details that match, any previous employment the worker can document, and written consent on file before they start. For roles with access to cash, stores, finished goods, data or the main gate, add police verification, and decide in advance whether the worker can start under supervision while it is pending or must wait for the result. For security, rely on the PSARA obligations of your security agency and audit the evidence. Write the tiers into the manpower agreement, with a stated turnaround for the contractor's part and a simple monthly confirmation that every deployed worker has a complete file. Then sample it, just as you would sample wage registers: pick five names a month and look at the actual files. When you evaluate a new manpower vendor, ask how they verify workers, what a typical file contains and how they store it. A vendor who can answer clearly and show you a redacted example is probably running a real process.

Verification works best when it answers a specific question for a specific role: identity for everyone, police records where the role justifies it, and documented history where skill matters. Put the responsibilities and timelines in the agreement, keep the data to what you need and protect it, and treat workers fairly throughout, because migrant workers in particular notice how they are checked and will remember it. If you are setting up or reviewing verification for contract workers at your site, FactoryForce can explain how worker records are documented for our clients; request a quote or reach us on WhatsApp. The Aadhaar rules, the DPDP Act and Rules, police verification procedures and fees, and PSARA requirements are set by statute, notification and state practice and change over time, so confirm current requirements with your counsel before relying on anything here.

Ready to Get Started?

Need workers for your factory?
Let's talk.

Tell us your requirement — role, quantity, site. We'll have workers on your floor within 48 hours.

Looking for work instead? हैदराबाद में काम चाहिए →