Across most Indian states, establishments that require employees — and women employees in particular — to work at night are generally expected to arrange safe transport, along with measures such as escorts, vetted drivers and a means of raising an alarm. The detail sits in state shops-and-establishments rules and in conditions attached to night-work permissions, so it varies by state and by establishment type.
This guide is about the operational side: what "compliant" has to mean in practice, and what an auditor, a regulator or a court would look for after an incident. It is not a substitute for advice on your specific obligations.
What is generally expected
Common threads across states, stated in general terms because the specifics differ.
- Safe transport arranged by the employer for night-shift employees, particularly women
- An escort or security presence for women on the first pickup and last drop
- Verified, background-checked drivers
- A means of raising an alarm during the journey
- Records that demonstrate the above was actually done
- Consent and notice requirements around night work in several states
Where programmes usually fail
Not in the policy. In the gap between the policy and the trip.
- The escort rule exists but is enforced by the transport desk remembering it
- A non-compliant allocation is flagged in a report the morning after
- Driver verification is done at onboarding and never re-checked against expiry
- The SOS routes to a vendor helpline rather than a named internal desk
- Records exist as vendor spreadsheets, not as an auditable trail
- Nobody can reconstruct what happened on one specific trip six months ago
What evidence should look like
The test is whether you can reconstruct a single trip on demand.
- Who was on the route, in what order, and why that order
- Whether the employee was first or last, and whether an escort was assigned
- Which driver, which vehicle, and the verification status of both at that moment
- The actual route travelled against the planned route
- Any exception raised, who approved it, and when
- All of it timestamped and exportable without asking the vendor
Enforce at allocation, not in the report
This is the single change that moves a programme from describable to defensible. If escort rules and no-first-no-last-drop logic are applied when the route is generated, a non-compliant trip cannot be dispatched. If they are applied in a report, the report describes a breach that already happened.
A short self-assessment
- Can you produce the escort record for a named trip three months ago, in under ten minutes?
- If a driver verification expired last week, would a trip have been assigned to them last night?
- Does an SOS reach someone employed by you?
- Is your night-shift rule enforced by software, or by a person remembering?
- Do your records come from your system, or from the vendor being asked nicely?