Employee Cab Scheduling: The Complete Guide for Indian Companies

Every evening, somewhere in a corporate admin office, a transport coordinator is reconciling a shift roster against a spreadsheet of home addresses, a list of available cabs and a stream of WhatsApp messages about leave, late logins and changed pickup points. By the time the plan is final, some of it is already out of date. Employee cab scheduling is the discipline of making that process reliable, safe and economical — and, increasingly, automated.

This guide is written for HR, admin, facilities and transport teams at Indian companies that run shift-based employee transport, whether you operate ten cabs at one site or several hundred across a city. It covers the full scheduling lifecycle: collecting the right data, planning routes, assigning vehicles and drivers, handling day, night and overlapping shifts, keeping employees safe, reacting to last-minute changes and measuring the results. It ends with a practical checklist, the mistakes we see most often and a framework for evaluating software.

What is employee cab scheduling?

Employee cab scheduling is the process of converting a company's shift roster and employee location data into a set of pickup and drop trips for a given day or shift. For each trip, the schedule answers five questions:

• Who is travelling — which employees, for which shift login or logout.
• Which vehicle carries them — sized for the group, available and compliant.
• Which driver operates it — verified, on duty and within working-hour limits.
• In what order pickups or drops happen — the stop sequence.
• At what time each employee should be ready, so the cab reaches the office before the shift starts (or leaves after it ends).

Scheduling sits inside the broader category of employee transport management software, which also covers fleet and vendor management, billing, safety and reporting. But scheduling is the part that runs every single day, and it is where most of the cost, punctuality and safety outcomes are decided.

Scheduling, routing and dispatch — what is the difference?

The three words are often used interchangeably, but separating them helps you diagnose problems:

• Scheduling decides which trips need to exist and who is on each one, based on the roster.
• Routing decides the path and stop order for each trip — the sequence of pickups or drops.
• Dispatch assigns the trip to a specific vehicle and driver and releases it for execution.

A late cab can be a scheduling problem (the employee was on the wrong trip), a routing problem (the stop order made the route too long) or a dispatch problem (the assigned vehicle was still finishing a previous trip). Good tooling keeps all three connected so a change in one flows into the others.

Common corporate transportation challenges

Most transport teams face a familiar set of problems. Naming them precisely is the first step toward fixing them.

Roster churn

Shift allocations change weekly or even daily — rotations, project moves, new joiners, exits, leave and hybrid office days. If the transport plan is built from last week's roster, employees get missed, double-booked or assigned to the wrong shift window.

Inaccurate or outdated addresses

Free-text addresses ("near the temple, second lane") are hard to plot, and many employees move without informing the transport desk. A single wrong pin can add ten minutes to a route and push every later pickup out of its window.

Under-filled and over-scheduled vehicles

Without systematic clustering, some cabs run with one or two passengers while others are full and running long. Both outcomes cost money — the first in wasted seats, the second in long ride times and complaints.

No live visibility

Once a cab leaves the parking bay, many teams lose sight of it until an employee calls to ask where it is. "Where is my cab?" calls are a symptom of a schedule that is not connected to live tracking.

Night-shift and women-employee safety

Late-night drops carry heightened duty-of-care obligations. When safety steps — check-in calls, escort rules, drop-order rules — depend on a coordinator remembering them for each trip, they are applied inconsistently.

Multiple vendors and manual billing

Many companies rely on two or more cab vendors. Reconciling their trip sheets and kilometre claims against what was actually scheduled is slow, dispute-prone and often done at month-end when the details are hard to verify.

Constant exceptions

Cancellations, no-shows, late shift extensions, vehicle breakdowns and traffic disruptions happen every day. A plan that cannot absorb change without being rebuilt from scratch will always feel fragile.

Manual scheduling versus automation

Manual scheduling — spreadsheets, maps and phone calls — can work for a small, stable operation. As headcount, shifts and sites grow, the number of possible groupings and stop orders explodes, and a human planner cannot re-optimise them every shift. The table below summarises the practical differences.

Automation does not remove the transport team. It moves their time away from rebuilding the same plan every day and toward handling exceptions, managing vendors and improving service. If you are weighing that shift, our companion answer on how companies automate employee cab scheduling walks through the end-to-end automated workflow step by step.

When manual scheduling is still reasonable

If you run a single day shift at one site, with fewer than a handful of fixed routes and very little roster change, a well-maintained spreadsheet plus a tracking app may be enough. The tipping point usually arrives with the second shift, the second site, night operations or the second vendor — each multiplies the coordination work.

Collecting employee location and shift data

The schedule can only be as good as the data it is built from. Before investing in optimisation, invest in data hygiene.

The minimum dataset

Keeping data current

• Connect to the source. Pull roster and employee data from your HRMS or workforce system rather than re-keying it. Where an integration is not available, use a scheduled bulk CSV import with a fixed template. See roster integration and HRMS-integrated transport for how this works.
• Geocode once, verify once. Convert addresses to map pins when an employee opts in, and have the transport desk confirm any pin that lands far from the declared locality.
• Set a cut-off time. For example, roster changes for the next day must be submitted by a fixed hour; later changes go through an ad-hoc request. This protects the plan without blocking genuine emergencies.
• Sync leave and hybrid days. Employees on leave or working from home should drop out of the schedule automatically. Attendance sync covers this.
• Audit monthly. Compare scheduled employees against boarded employees; repeated no-boards often point to a stale address or a changed commute need.

Pickup and drop route planning

Route planning turns a list of employees per shift into efficient trips. A practical sequence that works for most operations:

1. Group by shift window. Everyone logging in at 9:00 is planned together; 9:30 is a separate group unless your policy allows combining adjacent windows.
2. Cluster by geography. Within a shift window, group employees who live along the same corridor or in the same residential zone. Zone-based routing keeps clusters compact and predictable.
3. Size each cluster to a vehicle. Match cluster size to the capacity of the vehicles you have (4-seat sedan, 6–7-seat MUV, tempo traveller, bus).
4. Sequence stops. For pickups, the first stop is usually the farthest from the office; the route works inward. For drops, it is the reverse. Apply any drop-order rules your safety policy requires.
5. Check constraints. Validate each route against maximum ride time, pickup window and detour limits before you lock it.
6. Back-calculate pickup times. Work backward from the shift start, subtracting travel time between stops plus a realistic buffer for boarding.

Set ride-time limits before optimising cost

The cheapest plan almost always packs vehicles fully and runs long routes. Employees experience that as a 90-minute commute. Decide your service rules first — maximum ride time, earliest acceptable pickup, maximum detour per added rider — and let optimisation work inside them. This is the single most important design decision in employee cab scheduling, because it sets the balance between cost and employee experience.

Nominated pickup points

Door-to-door pickup is common for night shifts and for women employees after dark, but for daytime shifts many companies use nominated pickup points on main roads. They shorten routes, reduce turns into narrow lanes and make ETAs more reliable. Define them per zone and review them periodically with employee feedback.

Vehicle capacity and driver assignment

Choosing the right vehicle mix

A fleet of only sedans is flexible but expensive per seat; a fleet of only large vehicles is economical on dense corridors but wasteful on scattered ones. Look at the cluster sizes your routes actually produce over a typical week and match the mix to them. If most clusters are five to seven employees, 7-seat MUVs will usually fill better than a mix of sedans and buses.

Capacity rules worth writing down

• Usable seats, not registered seats. Many companies do not seat a passenger in the front seat, or reserve a seat for an escort on night routes. Plan to usable capacity.
• Luggage or equipment. Operations such as healthcare or manufacturing may need space for bags or tools.
• Target occupancy band. A target such as 75–90% of usable seats gives room for an ad-hoc addition without forcing a new vehicle.

Driver assignment

Driver assignment is a compliance step as much as a logistics step. Before a driver is assigned to a trip, confirm that:

• Licence and background verification records are on file and current.
• Vehicle documents (registration, permit, insurance, fitness, pollution certificate) are valid for the trip date.
• The driver is within your duty-hour and rest-period policy, especially across back-to-back night trips.
• The driver has the driver app installed and logged in, so the trip can be tracked and verified.
• For vendor-supplied vehicles, the vehicle and driver are mapped to the right vendor for billing.

Driver verification with document-expiry alerts prevents a lapsed document from being discovered only after the trip.

Day, night and overlapping shift scheduling

Day shifts

Day shifts carry the highest volume and the worst traffic. Prioritise reliable ETAs: use nominated pickup points, plan with peak-hour travel times rather than off-peak estimates, and add a buffer on corridors with known congestion. Review on-time arrival by route every week and re-cluster the routes that consistently run late.

Night shifts

Night operations change the priorities from speed to safety and accountability. Common practices include door-to-door drops, rules on the order in which employees are dropped, escort or security-guard requirements for certain trips, check-in calls after the last drop, and closer monitoring by a control room. The exact requirements depend on your company policy and the state rules applicable to your location — confirm them with your legal and HR teams. Our article on night-shift employee transport compliance explains the documentation many organisations now expect to keep.

Whatever your rules, encode them into the schedule so they apply automatically to every qualifying trip rather than relying on a coordinator to remember them at 2 a.m.

Overlapping and staggered shifts

Overlapping shifts — for example 9:00, 9:30 and 10:00 logins, or a logout at 18:00 coinciding with a login at 18:30 — create both risk and opportunity.

• Combine adjacent windows carefully. If your policy allows, an employee with a 9:30 login can ride a 9:00 trip, arriving early, when that fills a vehicle that would otherwise run half empty. Make this an explicit, opt-in rule, not a silent planner's choice.
• Chain trips. A vehicle that completes a 9:00 login drop at the office can often start a nearby logout pickup or a later login run. Chaining reduces dead mileage — the kilometres driven with no passenger.
• Protect the handover. When one shift's logout and another's login overlap at the same gate, stagger vehicle arrival slots to avoid congestion at the pickup bay.

Rotating shifts and roster patterns

Teams on rotating patterns (for example, a week of mornings, a week of evenings, a week of nights) need shift templates in the scheduling system so the next rotation's trips are created automatically, not re-entered every week.

Shared rides and pickup sequencing

Shared rides — several employees in one vehicle — are what make employee transport economical. Doing them well comes down to sequencing.

Sequencing principles

• Farthest-first for pickups, nearest-first for drops, modified by any safety rules on drop order.
• Avoid backtracking. A route that passes a stop, goes further out and then returns is a sign the cluster is wrong, not just the order.
• Use anchor stops. A predictable first pickup point makes the whole route's timing more stable.
• Cap detours. Adding one more rider should not add more than a defined number of minutes to everyone else's ride.
• Balance ride times. The first person picked up has the longest ride. If that is consistently the same employee, rotate or re-cluster.

Communicate the plan clearly

Employees should know their vehicle, driver, pickup time and pickup point before the trip, and see the cab's live position on the day. That single change removes most status calls. An employee app with trip notifications and live ETAs is the most reliable way to do it. For a deeper look at day-to-day pickup and drop operations, see how to manage employee pickup and drop efficiently.

GPS tracking, ETA updates, geofencing and trip alerts

A schedule describes what should happen. Tracking tells you what is happening, while there is still time to act.

Live GPS tracking

Every scheduled trip should be visible on a live map from the moment the driver starts it until the last employee is dropped. Live tracking is the foundation for everything else in this section. See GPS tracking for employee transport.

ETA updates

Planned pickup times are estimates; live ETAs update them using the vehicle's actual position. Sharing ETAs with employees reduces waiting at the roadside — which matters for both experience and safety, especially at night.

Geofencing

A geofence is a virtual boundary around a location — an office campus, a pickup point or a high-risk area. Entry and exit events can confirm arrival at the office, flag a vehicle that stops unexpectedly, or alert the control room when a cab enters an area your policy marks as sensitive. Geo-fencing for employee transport explains the common configurations.

Trip alerts worth configuring

Alerts are only useful if someone owns them. Assign each alert type to a role, define a response time, and review missed alerts in your weekly operations meeting.

OTP verification, employee safety and SOS procedures

OTP boarding verification

With OTP boarding verification, each employee shares a one-time code with the driver at pickup (or the driver enters it) so the system records who actually boarded, where and when. The result is a verified trip record that supports safety audits, attendance reconciliation and vendor billing — and it makes no-shows visible instead of anecdotal.

Safety practices to build into the schedule

• Only verified drivers and compliant vehicles can be assigned to trips.
• Drop-order and escort rules apply automatically to qualifying night trips, as defined by your policy.
• Employees can see vehicle and driver details before boarding.
• A post-drop safety confirmation (for example an automated call) is made after the last drop on applicable routes.
• Employees can share their live trip with a trusted contact, where your process allows it.
• Every safety event is logged against the trip for audit.

For a complete view of safety workflows, see women employee transport safety.

SOS procedures

An SOS button is only as good as the process behind it. Write down, test and rehearse your escalation matrix:

1. Trigger. Employee or driver presses SOS in the app; the live location is shared with the control room.
2. First response. The control room calls the employee and driver within a defined time, typically a minute or two.
3. Escalation. If unresolved, escalate to the security lead, then HR and, if needed, emergency services — each tier with a named owner and backup.
4. Closure. Record what happened, actions taken and time to resolution.
5. Review. Every SOS — including false alarms — is reviewed weekly to improve the process.

SOS and emergency alerts covers the tiered escalation approach in more detail.

Last-minute changes, cancellations and no-shows

Exceptions are where schedules break. Design for them.

A simple change policy

• Before cut-off: changes flow into the next schedule automatically.
• After cut-off, before dispatch: the affected trip is resequenced; other trips are not touched.
• After dispatch: the driver and remaining employees receive updated ETAs; the control room decides whether to add, merge or cancel a trip.

Cancellations

When an employee cancels, the route should be recalculated to remove the stop rather than leaving an empty detour. Dynamic routing recalculates routes for cancellations, added riders and traffic and updates ETAs for everyone on the trip.

No-shows

• Define a wait time at each stop (for example, a few minutes after the scheduled pickup) and what the driver does next.
• Require the driver to mark a no-show only after attempting contact, so there is a record.
• Use boarding records to identify repeat no-shows and address them with the employee and their manager.
• For night drops, never leave an employee without transport because of a missed slot — have a defined fallback.

Ad-hoc and emergency trips

Late meetings, client visits and shift extensions generate one-off trips. Handle them as ad-hoc requests with an approval step, so they are tracked and billed like any other trip instead of being arranged over the phone.

Fuel costs, fleet utilisation and operational efficiency

Transport is usually one of the larger facilities cost lines. Most of the controllable cost comes from three things: how full vehicles are, how many kilometres they drive empty, and how many vehicles you need at peak.

The main cost levers

• Seat occupancy. Raising average occupancy reduces the number of trips needed for the same headcount.
• Dead mileage. Positioning a vehicle from its parking point to the first pickup, and returning after the last drop, costs fuel and driver time without carrying anyone. Assigning vehicles based on where they actually are, and chaining trips, reduces it.
• Peak vehicle count. Staggering shifts or combining adjacent windows (where policy allows) lowers the number of vehicles you must contract for the busiest slot.
• Billing accuracy. Paying vendors from verified trip data rather than self-reported trip sheets avoids paying for kilometres that were not driven.

Cost per employee per trip

The most useful single cost metric is cost per employee per trip:

The Fleet Optimization Handbook goes further on fleet-level formulas, maintenance and a 30-day improvement plan.

KPIs for employee transportation

Pick a small set of KPIs, define them precisely and review them on a fixed rhythm. The table below is a solid starting set.

Avoid setting targets for a KPI before you have measured a baseline for a few weeks. Then improve one or two at a time, and watch the counter-metric: pushing seat occupancy up should not push average ride time beyond your limit. Fleet analytics covers dashboards and scheduled reports for these metrics.

A practical implementation checklist

Use this checklist when setting up or overhauling employee cab scheduling, whether or not you use software.

Policy and rules

• Eligibility: who gets transport, for which shifts and distances.
• Service rules: maximum ride time, pickup window, wait time at stops, detour limit.
• Night-shift and safety rules: drop order, escorts, post-drop confirmation, as per your policy.
• Change and cancellation cut-off times, and the ad-hoc request process.
• No-show policy and fallback for night drops.

Data

• Roster source identified and connected (HRMS sync or scheduled import).
• All employee addresses geocoded and verified.
• Nominated pickup points defined per zone.
• Leave and hybrid-day data flowing into the schedule.
• Emergency contacts captured.

Fleet and vendors

• Vehicle directory with usable capacity and document expiry dates.
• Driver directory with verification status.
• Vendor rate cards and allocation rules recorded.
• Driver app installed and tested on every vehicle.

Operations

• Control-room roles and shift coverage defined.
• Alert ownership and response times documented.
• SOS escalation matrix tested with a live drill.
• Employee communication: app onboarding and a help contact.
• KPI baseline measured for at least two weeks.

Rollout

• Pilot one site or shift alongside the current process.
• Compare schedules, timings and costs before full cut-over.
• Go live in phases; review daily for the first two weeks.
• Collect employee feedback and adjust clusters and pickup points.

Common mistakes and their solutions

How to evaluate employee transport software

If you are considering software, evaluate it against your own operation rather than a generic feature list. A structured approach:

Questions to ask every vendor

1. Data in: How does roster and employee data get into the system — HRMS integration, bulk import or both? How are changes after cut-off handled?
2. Scheduling logic: Can it cluster by shift and zone, respect maximum ride time and detour limits, and handle rotating and overlapping shifts?
3. Exceptions: What happens on a cancellation, an added rider or a vehicle breakdown? Does it resequence one trip or rebuild the plan?
4. Tracking: Is every trip tracked live with ETAs, geofences and route-deviation alerts? What do employees see in their app?
5. Safety: How are OTP boarding, SOS escalation, drop-order rules and post-drop confirmation configured? Are events logged per trip?
6. Fleet and vendors: Does it check driver and vehicle documents before assignment? Does it support multiple vendors and rate cards?
7. Billing: Can vendor invoices be reconciled against verified trip data?
8. Reporting: Can you get the KPIs listed above by route, zone, vendor and shift without exporting to a spreadsheet?
9. Rollout: What does a pilot look like, and how long does onboarding take for a site of your size?
10. Security: How is employee location and personal data protected, and who can access it?

Insist on a pilot with your data

Ask the vendor to generate schedules from a real (anonymised if needed) week of your roster and addresses, and compare the output with your current plan on ride time, vehicle count and occupancy. A demo with sample data proves the interface; a pilot with your data proves the outcome. Our Q&A on choosing the best employee transport management software in India includes a full evaluation scorecard.

How Track My Tour supports employee cab scheduling

Track My Tour's Employee Transport System is built for the workflows described in this guide. Specifically, it provides:

• Roster-based trip generation — shift timings, pickup locations and vehicle capacity generate daily trip schedules automatically, with ad-hoc trips for one-off needs. See employee cab scheduling software and trip scheduling.
• HRMS and roster sync — employee data, shift timings and pickup addresses sync from your HRMS or a bulk CSV import, with shift templates, rotation patterns and roster-change alerts.
• Attendance sync — leave and in-office days flow into scheduling so trips are planned around who is actually coming in.
• Route clustering and optimisation — employees are grouped by shift and residential zone, with AI route optimisation for stop sequencing.
• Dynamic routing — routes recalculate for cancellations, added riders and traffic, with configurable pickup windows and detour limits and live ETA updates.
• Live GPS tracking and geofencing — every trip is visible on a live map with ETAs, route-deviation alerts and geofence entry/exit alerts.
• OTP boarding verification — a verified record of who boarded each trip.
• Safety workflows — one-tap SOS with tiered escalation, an automated last-female-drop IVR call, configurable escort rules, guardian alerts and an optional buddy system.
• Driver and vendor management — licence and police verification status, document-expiry alerts, vendor directory, SLA tracking, rate cards and GST-compliant vendor reconciliation.
• Employee and driver apps — trip details, live tracking, ETAs, OTP boarding, SOS and trip notifications on Android and iOS.
• Analytics — utilisation, cost, safety and driver-behaviour dashboards, with a custom report builder and scheduled reports.

Configuration — service rules, safety rules, alert thresholds — is set to match your policy during onboarding, and rollout typically starts with a pilot on a subset of routes so you can compare results before switching over.

Next steps

Start with the data: connect or clean your roster and addresses, write down your service and safety rules, and measure a two-week KPI baseline. Then decide where automation will save the most time. If you would like to see how these workflows look in practice with your own shifts and sites, book a demo with the Track My Tour team.