Night shift cab rules for women employees: what to evidence

If your organisation moves staff outside daylight hours, and particularly if you employ women on those shifts, you carry obligations that go beyond booking a cab. Most companies we speak to can describe a safe process. Far fewer can produce evidence that it was followed on a specific night, months later.

That gap is where the risk sits.

Requirements differ by state and by establishment type, and they change. This describes the pattern that recurs across Indian states, not the statute where you operate. Confirm what applies to your organisation with your legal counsel before relying on it.

What is generally expected

Across states, the expectations that recur are consistent enough to plan around:

• Transport provided or arranged by the employer, rather than left to the employee to sort out and claim back.
• Vehicles that are tracked while carrying staff.
• Drivers who have been verified, with a record of which driver was on which trip.
• A way for someone in the vehicle to raise an alarm, and a named person who has to respond to it.
• A record afterwards that survives the contract with whoever drove.

Note how much of that is about evidence rather than about the vehicle. A safe arrangement you cannot demonstrate is, from an auditor’s point of view, an arrangement.

The six records to be able to produce

Take a specific journey from three months ago. Can you produce these?

1. Who travelled. Not who was rostered — who actually boarded. A trip started against a one-time code answers this; a roster does not.
2. Who drove, and in what vehicle. As assigned on the night, not as currently assigned.
3. The route the vehicle took. Live tracking answers where a car is now. After an incident, the question is where it went.
4. The timings. When the vehicle reported, when the journey started, when each person was dropped.
5. Any alert raised, and who owned it. An alarm that appeared on a screen and was swiped away is worse than no alarm, because it documents that you were told.
6. That the vehicle was legal to be on the road. Permit, insurance, fitness and licence, current on that date.

If any of those live in a vendor’s WhatsApp history, you do not have them. You have access to them, at that vendor’s discretion, until the contract ends.

Ad-hoc reimbursement is not transport

A pattern worth flagging because it is common and it is weak: reimbursing employees for a ride-hailing trip is not the same as providing transport. You did not choose the vehicle, you did not verify the driver, you cannot retrieve the route, and you have no record beyond a receipt for money.

It is administratively easy and evidentially close to worthless. If it is what you do today, it is the first thing to change.

Alerts that nobody owns

The most common design failure we see is an alert that surfaces somewhere and then stops. A notification is not a safety system. What matters is escalation: the alert keeps going until a named person acknowledges it and takes ownership, and that acknowledgement is itself on the record.

Ask your provider — or your own operations team — a simple question: what happens to an emergency alert raised at 02:00 that nobody clicks? If the answer is “it stays on the screen”, you have found something to fix this week.

Where to start

You do not need to solve everything at once. Start with the shift that worries you most, get the six records above working for that shift, and extend from there. Most organisations find the exercise of trying to produce them for one past journey is clarifying on its own.

Our longer employee transport compliance guide sets out an eight-point checklist, and the safety and emergency response page covers what escalation looks like when it is built properly.