Factory Gate Entry Rules for Contract Workers: The 19 Checks That Should Run Before Anyone Walks In

Most factory gates answer one question: is this person who they claim to be? Identity, verified by a card, a fingerprint or a face.

Compliance requires answering nineteen. Whether the contractor supplying this worker holds a valid licence. Whether the establishment is within its permitted headcount. Whether this worker's safety induction is still current. Whether their medical fitness certificate has expired. Whether they are cleared for the zone they are heading to, on the shift they are entering, on a day they are legally permitted to work.

A gate that checks identity alone will admit a correctly-identified worker whose contractor's licence lapsed three weeks ago. That is not an attendance problem. It is a compliance failure that an inspector will find in your own records, because your gate created the evidence. This is the compliance layer a purpose-built contract labour management system enforces at the barrier — before entry, not after audit.

Below is the full set of checks, grouped by what they protect. Score your own gate against them: for each, ask whether it happens automatically at entry, manually sometimes, or not at all.

Family 1 — Statutory checks (CLRA and Factories Act)

These protect against the compliance findings that carry penalties and, in serious cases, prosecution.

1. Contractor licence validity. Is the contractor's CLRA licence current on the date of entry? A lapsed licence means every worker they deploy is unlicensed labour on your premises. The contractor management module tracks licence expiry and flags approaching renewals before they become a gate event.

2. Establishment headcount cap. The licence permits a maximum number of workers. Is this entry within it? Most plants discover a breach only when an inspector counts.

3. Form V registration currency. Is the contractor properly registered against your establishment for the work being performed?

4. Continuous attendance threshold. Has this worker attended continuously without a weekly off? See the 9-day continuous attendance rule for why this specific count creates liability.

5. Work order validity. Is the worker being deployed against a live work order, or one that closed last month?

6. Statutory age verification. Is the worker above the legal minimum age for the work and the establishment?

Family 2 — Safety checks

These protect people. They are also the family most often absent entirely, and the one an HSE head will react to first.

7. Safety induction completion. Has this worker completed site induction? Not "has induction been conducted" — has this individual completed it, with a record.

8. Induction validity period. Inductions expire. Is this one still within its refresh window?

9. Medical fitness certificate. Is a current fitness certificate on file for the work being performed?

10. Job-specific certification. Hot work, confined space, working at height, electrical work — does this worker hold the certification the task requires?

11. PPE issuance record. Has the worker been issued the protective equipment their zone requires?

As one HSE head put it: if a non-inducted person can walk past the gate, the induction is documentation, not a control.

Family 3 — Shift and deployment checks

These protect operational integrity and prevent the quiet accumulation of unauthorised time.

12. Shift window. Is the worker entering during their rostered shift, or three hours early?

13. Zone authorisation. Is this worker cleared for the area they are heading into? A housekeeping worker in a hot-work zone is a safety incident waiting for its trigger.

14. Site authorisation. Multi-plant employers: is this worker authorised for this site, or another one?

15. Overtime pre-approval. If entry extends beyond permitted hours, has the overtime been approved before it starts accruing?

Family 4 — Identity and integrity checks

These protect against the fraud that quietly drains contractor spend.

16. Background verification status. Is BGV cleared, pending, or expired? At defence and PSU sites this is a precondition, not a preference. The background verification module holds this status per worker and surfaces it at the gate.

17. Blacklist status. Has this worker been blocked for a safety violation or security incident? Critically — does that block survive the worker being resubmitted by a different contractor next month?

18. Duplicate identity detection. Is the same person enrolled twice under different worker IDs, drawing two sets of wages?

19. Biometric match confidence. Did the reader actually match this worker, or accept a low-confidence read at a crowded shift change?

Score your own gate

Run through the nineteen. For each, mark:

• A — checked automatically at entry, entry refused on failure
• M — checked manually, sometimes, by a person who may or may not be at the gate today
• N — not checked

Most plants score A on one to three of nineteen: identity, sometimes shift window, occasionally licence validity. The rest sit in M or N — which means they are policies rather than controls.

The distinction matters because an inspector does not ask whether you have a policy. They ask for evidence it was applied to a specific worker on a specific day.

Hard, soft, and override — why this is deployable

The objection to gate-level enforcement is always the same, and it is a fair one: we cannot stop production because someone's medical certificate expired at 6am.

Which is why rules should not run as a single mode. In practice a workable configuration has three:

• Hard block — entry refused outright, no override. Typically statutory checks and critical safety items: lapsed licence, missing induction, expired hot-work certification.
• Soft warn — entry proceeds, the exception is logged and escalated for follow-up. Typically documentation gaps that don't create immediate risk.
• Supervisor override — a named authoriser permits entry with a recorded reason and timestamp. The override itself becomes the audit record.

The third mode is what makes the system survivable in a real plant, and it produces something paper never does: a log of every exception, who authorised it, and why. During an audit, that log is often more valuable than the entry record.

What a rejection record is worth

The counterintuitive part: for compliance purposes, the denials matter more than the entries.

An entry log proves people came to work. A denial log — worker, contractor, gate, timestamp, the specific rule that failed, any override and its authoriser — proves the control was operating. It demonstrates that when a lapsed licence appeared, the system caught it. That is the evidence an inspector, an OEM auditor, or a CVC review is actually looking for.

Plants that run gate compliance properly find the denial rate drops sharply within the first few weeks — not because the rules relaxed, but because contractors start arriving compliant once they discover the gate is checking.

Where the checks come from

Everything above runs on data the plant already has — contractor licences, induction records, medical certificates, verification status — but which normally sits in files nobody consults at 6am when 800 workers arrive in twenty minutes. Automated gate compliance is not new information. It is the existing information, applied at the moment it matters.

If you want to know how your current gate scores, a CLRA compliance audit includes gate enforceability as one of its assessment areas — not just whether the records exist, but whether they can stop anyone.

This article is general information about contract labour compliance in India and is not legal advice. Requirements vary by state, industry and establishment; confirm your obligations with qualified counsel.