Crossings modelled as the chokepoints they are
Bridges are treated as constraints in route generation rather than averaged into a city-wide speed, so a plan that depends on one is costed honestly before it is published.
Employee transport software · Kolkata, West Bengal
Employee transport management software in Kolkata.
Kolkata runs the most night-weighted employee transport programme of any Indian metro — the floors in Salt Lake and New Town keep western business hours. That makes the night rules the operating model rather than a compliance report, and it makes the river the constraint everything else is planned around.
Where it runs
The Kolkata corridors employee transport actually moves on.
Routing is planned around these rather than across a city-wide average.
What breaks a schedule in Kolkata
The constraints that decide whether a plan survives contact.
These are the local problems a generic routing engine does not know it has.
-
The river is a handful of fixed crossings
Employees living across the Hooghly reach Sector V over a small number of bridges. A model that treats the river as open road produces timings that fail on the first attempt, and a restriction on one crossing applies to the whole plan at once rather than to a single leg.
-
Night-weighted demand concentrates the risk
When most of the volume sits in the hours after public services thin out, escort rules and vehicle checks stop being something to audit and become the thing being operated. Reviewing them the next morning describes a breach you have already had.
-
Older neighbourhoods do not take every vehicle
Much of the residential catchment is narrow and congested. A plan that sends a coach down a street it cannot enter gets corrected by the driver, off-system, and the pickup point quietly moves without anyone recording that it did.
How taSki answers them
Built for the way Kolkata actually moves.
Night rules as the default for the whole plan
Where the programme runs mostly after dark, escort assignment and no-last-drop logic apply to every route at generation rather than being flagged on a subset afterwards.
Pickup points planned where access is tight
Where a street cannot take the assigned vehicle, the nodal point is planned and published to the employee rather than negotiated at the kerb on the morning.
The platform
Everything between the roster and the invoice.
The same modules run in every city; the routing model is what adapts.
Rosters and attendance
Shift rosters, ad-hoc requests and attendance in one place, so the transport plan is built from who is actually coming in.
Route generation
Clustering by pickup density, then routing against real road networks — with ride-time ceilings and vehicle capacity as constraints rather than preferences.
Multi-vendor allocation
Trips are allocated across your operator panel by coverage, rate card and compliance status, with double-assignment blocked at source.
Live tracking and SOS
GPS tracking against the planned route, escort compliance, and an in-app SOS that reaches the transport desk rather than a call centre.
Billing and three-way match
Trips, rate cards and vendor invoices reconciled automatically, so disputes are evidenced rather than argued.
Audit trail
Every allocation, escort assignment and exception timestamped and exportable for statutory or internal compliance reporting.
Questions
Employee transport software in Kolkata
Still unanswered? Our solutions team replies within one business day.
Talk to the team → Does taSki operate vehicles in Kolkata?
No. taSki is software and owns no vehicles. Your existing transport operators run the trips on the platform. Where you would rather contract once, taSki can also be your transport vendor — in which case taSki holds the agreements with the empanelled operators and you contract only with taSki.
Can we keep our current vendors in Kolkata?
Yes, and most programmes do. Operators onboard onto the Partner Suite in days, usually without changing their commercials. There is no supply lock-in, and no requirement to retender before you can use the software.
How long does implementation take?
One site first. A single Kolkata location, one shift pattern and one roster is modelled against your current spend, so the business case uses your data rather than a benchmark. Most programmes run four weeks from first site to steady state.
Does it handle night-shift safety compliance?
Escort assignment, no-first-no-last-drop logic, driver vetting and in-app SOS are enforced when the route is generated rather than reviewed afterwards, and every decision carries a timestamped record for statutory and internal reporting.
See it on your Kolkata roster
Bring one site and we will model it against your current spend.
A 30-minute review using your own roster and rates, not a generic benchmark.