How to scope a check package by role

The problem with scoping by grade

Most first packages are built from an organisation chart. Junior roles get a small package, senior roles get a large one, and the boundary sits at whatever grade the person building the list happens to be. It feels sensible and it is wrong in both directions.

It over-checks senior people who cannot reach anything. A senior specialist with no budget, no team and no system access is a low-exposure role wearing a high-exposure title. Running a credit check and a directorship check on that person costs money and adds days for no reduction in risk.

It under-checks junior people who can reach a great deal. A cashier handles money. A field technician enters customers' homes. A data entry operator sees every customer record that passes through them. A driver holds a company vehicle and a route full of stock. None of those is senior and all of them carry direct, immediate exposure.

Grade is a proxy for salary and reporting lines. It was never a proxy for what a person can do to you.

The six exposures

Almost every role in an Indian company can be described by which of six things it can reach. Work through them for the role in front of you and the package writes itself.

1. Money

Cash, payments, refunds, procurement, expense approval, payroll, or anything that moves value. This is the strongest single argument for a court record check, and, at the point where a person can authorise or divert significant sums, for a credit check. Note that a credit check is about financial distress as a pressure, not about whether somebody is good with money, and it is not appropriate for a role that simply handles a till.

2. Data

Customer records, employee records, source code, commercial terms, health information. The exposure here is not theft in the dramatic sense; it is the far more common case of data walking out to a competitor or a side business. Employment verification and a moonlighting check do more here than a criminal check does.

3. Customers

Anyone who meets, calls, sells to, collects from or advises a customer is carrying your name. The exposure is reputational and, in regulated sectors, licensable. Identity and court record are the base; for field-facing roles add address, because you need to know where the person actually lives.

4. Premises

Keys, access cards, a client site, a customer's home, a hospital ward, a school. Client contracts frequently make this one contractual rather than optional: many enterprise clients require verified staff on site, which is why staffing firms run verification as standard. Police verification earns its place here more than anywhere else.

5. Goods

Stock, inventory, devices, vehicles, tools, samples. Shrinkage is the most under-scoped exposure in Indian retail and logistics because the roles that carry it are junior and high-volume, which is exactly the combination that pushes an employer towards the smallest package.

6. Signature

Anyone who can bind the company: contracts, statutory filings, board positions, regulatory declarations. This is where directorship and DIN checks stop being optional, because an undisclosed directorship in a competing or struck-off company is exactly the thing a CV will not mention.

Four worked packages

These are illustrations, not a price list, and they are meant to be argued with. The point is the reasoning, not the exact combination.

Notice what is not in any of them. There is no package where every check runs, because a check that does not answer a question about that role is a check you are paying for and waiting on for no reason. The full list is on the all checks page; the discipline is in leaving things out.

Blue-collar and volume hiring is a different problem

Everything above assumes you are hiring one person at a time and can afford to think about them. Volume hiring cannot work that way, and copying a white-collar package onto a hundred warehouse joiners a week produces a process nobody can run.

Two things change. First, the package gets shorter and sharper: identity and address do most of the work, because the exposure is premises and goods rather than credentials. Second, the submission process has to survive candidates who may not have an email address, a laptop or a scanner. A verification programme that assumes a desk and a printer will simply fail at volume, and it will fail in a way that looks like candidates being uncooperative. More on this in blue-collar verification.

Write it down, then apply it consistently

The last step is the one that gets skipped, and it is the one that makes the rest defensible. Put the package in writing against the role, before you have a candidate in front of you.

Doing it this way is faster, because nobody has to decide the package per candidate while a joining date approaches. It is fairer, because everybody considered for the same role gets the same treatment. And it is defensible, because if you are ever asked why a particular candidate was checked in a particular way, the answer is a document that predates them rather than a recollection.

Varying the package candidate by candidate within a role, on the basis of something about the individual, is the one pattern to avoid. It is hard to justify afterwards, and it tends to correlate with exactly the characteristics an employer should not be sorting on.

When to revisit

Packages go stale quietly, because roles change what they can reach without changing their title. A support team gets read access to production. A branch starts holding cash. A category team begins approving vendor payments. None of those turns up in a headcount review, and each is a reason to reopen the package.

The practical trigger is not a calendar. It is any change to systems access, cash handling, site access or approval authority. If you tie the package review to those four events rather than to an annual cycle, you will catch nearly all of it.