Solutions · HR & mobility

You are accountable for the trip. You should not have to reconstruct it.

HR and mobility teams are measured on safety, experience and adherence — and then handed a roster, a vendor and a spreadsheet to achieve them with. This is what changes when rosters come from the system that already holds them, safety rules are conditions on routing rather than a monthly report, and every trip writes its own record.

What you get

Six things that change on day one.

None of these are reports. Each one moves work out of your team's week or turns an assurance into evidence.

Rosters that come from the HRIS

Shifts, sites and eligibility arrive from the system that already holds them. A joiner becomes transport-eligible on their start date and a leaver stops being allocated a seat on their last — without anyone remembering to tell the transport desk.

Safety rules applied at allocation

Escort requirements, no-first-no-last-drop and gender-composition rules are conditions the router has to satisfy before it produces a route, not a report that tells you afterwards which trips broke them.

Evidence, not assurances

Every trip keeps who was on it, who drove, which escort was assigned, the route actually taken and the times it was taken at. When a safety committee or an auditor asks, the answer is a query rather than a reconstruction.

Self-serve in the employee app

Employees see their pickup, their ETA and their driver, raise an ad-hoc request against policy, and cancel a seat they will not use. Fewer calls to your team, and no-shows that are attributable.

Grievances with a trail

A complaint about a driver, a route or a wait attaches to the trip it concerns. Patterns surface across a vendor or a route rather than living in one person’s inbox, and a resolution has a record.

One console across every site

A programme spread over four cities and three shifts reports as one programme. Policy is set once and varies by site where it has to, rather than being re-implemented per location.

How a shift runs

From roster to audit record, without a handoff.

The compliance record is a by-product of running the trip, which is the only way it is ever actually complete.

  1. Roster

    The shift pattern arrives, not a spreadsheet of names.

    Attendance and shift data syncs from your HRIS or attendance system. Eligibility is derived from employment status and site, so there is no second list to maintain.

  2. Allocation

    Safety rules are satisfied before a route exists.

    Clustering produces routes that already respect escort rules, ride-time ceilings and drop-order constraints. A route that cannot satisfy them is flagged for a decision rather than quietly issued.

  3. In motion

    Employees track their own trip.

    Live ETA, driver and vehicle details in the app. Deviations and prolonged stops raise an alert to your transport desk while the trip is still running.

  4. Afterwards

    The record is already written.

    Manifests, escort assignments, route taken, grievances raised and how each was closed. Nothing has to be assembled at the point someone asks for it.

What you can report on

The numbers an HR review actually asks for.

These are the metrics the platform produces from trip data. We have deliberately not printed target values for them — a vendor page quoting your future escort compliance figure is telling you something it cannot know.

Escort rule adherence

The share of qualifying trips that met the rule, by site and shift — and the exceptions, with the reason each one was approved.

On-time pickup

Measured against the promised window rather than the driver’s own report, because the GPS trail is the record.

Seat utilisation

Occupancy per vehicle class. The number HR and finance can actually discuss together, since it moves both experience and cost.

Grievances per thousand trips

Split by cause and by vendor, so a supply problem is distinguishable from a route-design problem.

No-shows, attributed

A booked seat not taken, tied to a person and a cost centre. The attribution is what gives anyone a reason to cancel in advance.

App adoption

What proportion of employees are self-serving rather than calling your desk. The leading indicator for how much of your team’s week transport takes.

What stays with you

Four things this does not decide.

A platform that claimed these would be overselling what software can do about them.

  • What the policy says

    Eligibility, escort thresholds, how far an employee can reasonably be asked to walk to a nodal point, what happens at 2am when a vehicle does not arrive. We enforce the policy you set; we do not have an opinion on what it should be.

  • Your statutory position

    Night-shift transport obligations in India vary by state and establishment type, and your legal and compliance teams own that reading. What this platform does is make adherence to whatever you have determined provable rather than asserted.

  • Works council and union matters

    Changes to pickup points, shift timings or eligibility are negotiated, not configured. The system will model the impact of a change before you take it to a consultation; it will not conduct one.

  • The vendor relationship

    Scorecards, SLA breaches and acceptance rates arrive as data. Whether an underperforming operator gets another quarter is a commercial judgement that stays with you.

Teams already running on taSki

  • Xiaomi — taSki customer
  • IndiGo — taSki customer
  • bioMérieux — taSki customer
  • Murugappa Group — taSki customer
  • Berger Paints — taSki customer
  • Acko — taSki customer

Questions

From HR and mobility teams

Still unanswered? Our solutions team replies within one business day.

Talk to the team →

Will this integrate with our HRIS?

In the general case yes — rosters and eligibility arrive by scheduled file exchange or API depending on what your system exposes. The specifics matter more than the answer: which system, whether shift data lives there or in a separate attendance tool, and whether site and cost-centre mapping is clean. Those are the first things we look at, and it is worth establishing before a procurement process rather than during one.

We already have a transport vendor. Does this replace them?

No. taSki owns no vehicles. Your operators keep driving; what changes is that allocation, tracking, compliance checks and invoicing stop happening over WhatsApp and email. Most programmes keep every vendor they had — several run their existing operators alongside taSki-sourced supply in cities where they were short.

How do escort rules actually get enforced?

They are constraints on the routing itself. A rule like "no female employee as the first pickup or last drop on a night shift" is evaluated when the route is built, so a route that would break it is not produced. Where no compliant route exists — a single employee in an outlying area at 1am — the system raises it for a decision rather than issuing a non-compliant trip or silently dropping the employee.

What do employees actually see?

Their roster for the week, their pickup point and window, live vehicle position and ETA once the trip starts, driver and vehicle identity, an SOS action, and the ability to cancel a seat or raise an ad-hoc request. Most of the reduction in load on an HR or transport team comes from this rather than from anything on the admin side.

Can we start with one site?

That is the usual way in, and the one we would suggest. One site and one shift pattern is enough to see whether the routing, the app and the compliance record hold up against your own roster, and small enough that it does not need a programme to run. Adding sites afterwards is configuration rather than a second implementation.

How is employee location data handled?

Home addresses are geocoded for routing and the trip trail is retained for the audit record. Access is role-scoped, personal data is masked for roles that do not need it, and the retention period is configurable to match your own policy. taSki holds ISO/IEC 27001:2022 certification; the detail is on our security page.

Start with one site

Bring one roster and one shift pattern.

We will route it against your real addresses and show you the manifests, the escort checks and the audit record it produces. Thirty minutes, and no rate card needed to start.

  • Your roster routed on your own addresses
  • Escort and drop-order rules applied live
  • The audit record a safety review would see

Request a demo

Three details, and we'll call you to arrange a time.

We'll only use these details to contact you about taSki. No newsletter, no list sharing. See our privacy policy.