"Do you do police verification?" is one of the first questions security-conscious clients ask, and the honest answer needs more nuance than a yes or no, because what "verification" means varies a lot depending on the role and the site.

What Verification Typically Covers

Why This Isn't One-Size-Fits-All

A pharmaceutical cleanroom and a general warehouse don't carry the same risk profile, and treating verification as an identical checkbox for both either over-delivers (wasting time and cost where it isn't needed) or under-delivers (skipping checks that a sensitive site genuinely requires). The right approach is matching verification depth to the role's actual risk and to what your specific client contracts or certifications require.

Woman reviewing receipts and using a calculator
Verification depth should match the role's actual risk, not a single blanket policy.

A supplier that promises full police verification on every worker, instantly and at no extra cost, is telling you something about their standards, just not the thing they think they're telling you.

What to Ask Your Supplier

Ask specifically which checks are standard for every placement, which are role-dependent, how long each takes, and whether verification records are available to you on request. A supplier who can lay this out clearly, rather than giving a single blanket assurance, is one whose process you can actually trust.

Need to know what verification applies to your site?

Tell us your sector and role types and we will explain exactly what checks are standard versus role-specific.

Talk to Prarambh

What a Client Audit Actually Looks For

For factories supplying into pharmaceutical, export, or certain FMCG supply chains, client audits increasingly extend beyond the factory's own practices to the manpower supplier's verification standards. An auditor representing a global pharma brand, for instance, may specifically ask to see the verification documentation for contract workers, not just direct employees, because the brand's own compliance standards hold them responsible for their entire supply chain's labour practices, not just their direct payroll.

This means the verification standard that matters isn't just what the law strictly requires, it's often what your most demanding client contractually requires, and those two things aren't always the same. A factory supplying a domestic customer with no specific verification clause in its contract might have a genuinely lighter obligation than one supplying an export-oriented pharmaceutical client whose own compliance team audits contractor verification as a standard part of vendor review. Knowing which category your business falls into, and communicating that standard clearly to your manpower supplier, is part of getting this right.

Documentation That Actually Holds Up

Verification that exists only as a verbal assurance from your supplier doesn't survive an audit. What holds up is a dated, retrievable record for each worker, what was checked, when, and by whom, kept in a form that can be produced quickly rather than reconstructed from memory when an auditor asks. This is a small operational habit that separates suppliers who talk about verification from suppliers who actually practise it consistently.

Balancing Thoroughness Against Practicality

There's a real tension worth naming honestly: more thorough verification takes more time, and factories under pressure to deploy workers quickly sometimes push back against anything that adds days to a hiring timeline. The answer isn't to skip verification under pressure, it's to build the standard verification steps into the maintained talent pool discussed elsewhere on this blog, so the depth of checking a role needs has already happened before the urgent request arrives, rather than being rushed or skipped once it does. A supplier who can explain how they resolve this tension, rather than pretending it doesn't exist, is one whose verification standards are more likely to hold up under real-world time pressure rather than only on paper.

What We Actually Do, By Role Category

For standard factory-floor roles, picking, packing, general production line work, we run identity and address verification as a baseline for every placement, with employment history checks where a prior work record exists. For roles involving security, restricted-access areas, or explicit client mandates, we extend this to full police verification before deployment, not after. We share the specific verification record for any worker on request, because a client shouldn't have to take our word for what was checked, they should be able to see it. This tiered approach means we're not over-verifying low-risk roles at unnecessary cost and delay, and we're not under-verifying the roles where it genuinely matters.

If a supplier can't describe their approach in this level of specific, role-by-role detail, that vagueness is itself worth treating as a signal.

Frequently Asked Questions

No. It's typically required for specific categories, security roles, sensitive-access positions, or where a client contract mandates it, rather than being a blanket requirement for every factory-floor placement.
At minimum, identity verification against a government ID and address confirmation are standard practice for any placement, regardless of role or site sensitivity.
Yes, a transparent manpower supplier should be able to provide verification records for any worker on request, as part of normal compliance documentation.