Contractor Liability at the Gate: Who Carries Risk?

Contractor Liability at the Gate: Who Carries the Risk?

When something goes wrong, the contracting firm is rarely the only one holding the bill.

VizPass team 11 September 2026 6 min read

# Contractor Liability at the Gate: Who Carries the Risk?

Ask most facility managers where contractor liability sits when a worker is injured on their premises and the answer arrives quickly: with the contracting firm. That is what the agreement says, that is what the safety briefing assumed, and that is what everybody has always believed.

Indian law is considerably less generous than that assumption. Contractor liability has a habit of travelling upstream to the organisation whose gate the worker walked through, and it does so in ways that a signed contract does not prevent.

The duty that does not transfer

The principle underneath most of this is that certain obligations attach to the person in control of the premises and the work, and cannot be contracted away.

Under factory legislation, the occupier carries a general duty for the health and safety of everyone working on the premises, and safety inspectorate guidance is published by DGFASLI. The word is everyone, not employees. A worker sent by a labour contractor is working on your premises, under your supervision, in conditions you control.

Under the Contract Labour (Regulation and Abolition) Act, the organisation engaging a contractor is the principal employer, and that status carries duties of its own, including registration, ensuring the contractor holds a licence, and stepping in where the contractor defaults on obligations to their workers. Legislation and rules are published by the Ministry of Labour and Employment.

You can allocate cost between yourself and the contractor through indemnities. That is worth doing. What you cannot do is allocate away the statutory duty, which is why contractor liability keeps arriving at the occupier's door regardless of what the contract says.

Three moments where contractor liability lands on you

The abstract version convinces nobody. Here is where it becomes concrete.

A worker is injured and had no valid induction. The question asked afterwards is not whether the contractor briefed him. It is whether you permitted an unqualified person onto a hazardous site. If your only record is a signature in a register, you have evidence he entered, and no evidence at all that he was fit to.

A licence, medical clearance or insurance had expired. This is the most common failure and the least dramatic. Nothing about the person changed. A date passed, the fact lived in a folder in HR, and the gate had no way to know.

The contractor defaults on wages or statutory dues. As principal employer, the obligation can fall to you, and the evidence of who worked and for how long is frequently the gate record rather than anything the contractor produces.

Notice that in all three the decisive document is created at the entrance, by a guard, in a few seconds, at the busiest hour of the morning.

Why the gate is the control point

Every other control depends on someone remembering. The gate is the only place where the check is unavoidable, because nobody gets in without passing it.

That makes it valuable and fragile in equal measure. Valuable because a check enforced there is enforced universally. Fragile because it competes with a queue.

Three things determine whether the control survives contact with a Monday morning.

It has to be immediate. If verifying validity means phoning HR, it will not happen at six in the morning with fourteen people waiting.

It has to block rather than warn. A warning is a suggestion, and suggestions get waved through. If an induction has expired, entry should stop and require a named person to override it, with the override recorded.

It has to apply at every gate. Validity enforced at the main gate and not the material gate protects the main gate. The weakest entrance sets your real standard, and contractors learn which one that is faster than management does.

The familiarity problem

The highest risk contractor on any site is not the stranger. It is the man everybody knows.

He has come for three years. The guard greets him by name. Nobody is going to stop him to check a date, because stopping him would feel absurd, and because the whole point of familiarity is that it removes friction.

This is precisely why contractor liability controls have to sit in the system rather than in the guard's judgement. A guard who waves through a familiar face is behaving reasonably. A system that permits entry against an expired induction is not.

What a defensible record looks like

Contractor liability is decided on evidence. If an inspector, an insurer or a lawyer asks about a contractor eighteen months from now, the record needs to show four things.

That the person was registered as a contractor of a named firm, not as an anonymous visitor.

That their induction, and any licence or clearance the work required, was valid on that date, with the validity checked at entry rather than assumed.

That entry was authorised by an identifiable person, and that any override of a failed check was recorded with a name against it.

That the exit was recorded, so the hours the person was actually on site are known.

The fourth is the one most sites skip and later wish they had not, because contractor hours at the gate are also the cleanest independent check on what a contractor invoices you for.

Where to start

You do not need software to begin. You need to know, today, how many contractors on your site have documents that have already expired. Most organisations that run this exercise for the first time find between a tenth and a third of their active contractors are out of date on something.

That number is your actual contractor liability exposure, and it is usually more persuasive to a management committee than any argument about process.

VizPass handles contractors as recurring people with dated documents rather than as fresh visitors each morning, checks validity at entry across every gate, and records exits. You can see how that runs in practice on the contractor access page, and what induction means in this context in the glossary entry on contractor induction.

We have also written separately about who vouches for a contractor at the gate, which covers the authorisation side of the same problem.

Frequently Asked Questions

If our contract says the contractor is responsible, are we still liable?

Frequently yes, at least in part. An indemnity allocates cost between you and the contractor, and it is worth having. What it cannot do is remove a statutory duty. Under factory legislation the occupier carries a general duty for the safety of everyone working on the premises, not only direct employees, and under the Contract Labour (Regulation and Abolition) Act the organisation engaging the contractor is the principal employer with obligations of its own. Those attach to your position rather than to the wording of the agreement. In practice a contract determines who ultimately pays, while the statute determines who is answerable, and the second question is usually asked first.

What is the most common contractor liability failure at a gate?

An expired document on a familiar person. Nothing about the individual changed, the guard recognises him, and the fact that his safety induction lapsed some weeks ago lives in a folder in HR rather than at the entrance. It is undramatic, which is exactly why it survives. The failure is structural rather than human: a guard who waves through a face he has known for three years is behaving reasonably, and the only reliable fix is to move the check out of the guard’s judgement and into the entry process itself, where an expired document blocks entry rather than producing a warning that gets waved past.

Should an expired induction block entry or just warn the guard?

Block, with a recorded override. A warning is a suggestion, and suggestions lose to a queue every time. The workable design is that entry stops, and a named person with authority can override it, with that override stored against their name and the reason. This keeps operations moving on the genuine exceptions while making the exception visible. If you look at your override log after a month and it is long, that is useful information: either your documents are chronically out of date, or the threshold is set wrong. Either way you now know, which you did not before.

Why does recording contractor exits matter for liability?

Two reasons. The first is safety: during an evacuation or an incident, the only question that matters is who is inside, and a system that records entries but not exits cannot answer it. The second is commercial. Contractor hours recorded at the gate are an independent record of how long people were actually on site, which is the cleanest check available against what a contractor invoices. Sites that start recording exits for safety reasons often find the billing discrepancy pays for the exercise. Both depend on the same discipline, which is why exit recording is worth enforcing even when it feels like the least urgent part.

How do we find out our current exposure?

Run one exercise. Take the list of contractors currently permitted on your site and check, for each, whether their induction and any required licence, medical clearance or insurance is valid today. Do it manually if you have to. Most organisations doing this for the first time find that somewhere between a tenth and a third of active contractors are out of date on at least one document. That figure is your actual exposure, and it tends to persuade a management committee more effectively than any argument about process improvement, because it is specific, current and about your own site rather than a general risk.