Maximum ride time as a hard constraint
Route generation treats the ride-time ceiling as a rule, not a target — a chain that would breach it is split rather than accepted.
Employee transport software · Pune, Maharashtra
Pune runs employee transport into a handful of dense IT parks whose approach roads were not built for the volume. Hinjewadi in particular turns a well-planned route into a queue, which is a routing problem, not a driver problem.
Where it runs
Routing is planned around these rather than across a city-wide average.
What breaks a schedule in Pune
These are the local problems a generic routing engine does not know it has.
One approach road into a very large park
Hinjewadi concentrates tens of thousands of employees behind limited access. Peak-hour plans that do not model the queue produce arrival estimates nobody believes by the second week.
Manufacturing shifts do not look like IT shifts
Chakan and Talawade run three-shift patterns with hard start times. A system tuned only for 9am IT logins and night-shift drops handles them badly.
Spread-out residential catchment
Employees live across a wide ring while offices cluster tightly. Pickup chains get long, and long chains are where ride-time limits quietly break.
How taSki answers them
Route generation treats the ride-time ceiling as a rule, not a target — a chain that would breach it is split rather than accepted.
Each site carries its own shift definitions, so a manufacturing site and an IT site on the same contract do not force one compromise.
Where door pickup makes the chain uneconomic, nodal points are planned explicitly rather than negotiated with drivers on the day.
The platform
The same modules run in every city; the routing model is what adapts.
Shift rosters, ad-hoc requests and attendance in one place, so the transport plan is built from who is actually coming in.
Clustering by pickup density, then routing against real road networks — with ride-time ceilings and vehicle capacity as constraints rather than preferences.
Trips are allocated across your operator panel by coverage, rate card and compliance status, with double-assignment blocked at source.
GPS tracking against the planned route, escort compliance, and an in-app SOS that reaches the transport desk rather than a call centre.
Trips, rate cards and vendor invoices reconciled automatically, so disputes are evidenced rather than argued.
Every allocation, escort assignment and exception timestamped and exportable for statutory or internal compliance reporting.
Questions
Still unanswered? Our solutions team replies within one business day.
Talk to the team →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.
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.
One site first. A single Pune 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.
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 Pune roster
A 30-minute review using your own roster and rates, not a generic benchmark.
Hi there. How can we help?
Real people, Monday to Saturday