One policy engine
Grade, city, shift and cost centre are defined once. They govern a flight, a hotel, an airport transfer and a night-shift drop identically, because it is the same rule set.
One platform · Travel and ground
Corporate travel and employee transport, on one platform.
Most enterprises run business travel in one system and employee transport in another. Two policies, two approval chains, two invoices, and no single answer to what it costs to keep a team mobile. taSki runs both on one policy engine.
Trusted by leading enterprises
The split stack
What running two systems actually costs.
None of these are software faults. They are what happens when the same employee is governed by two sets of rules.
-
Two policies that disagree
A travel policy in one tool and a transport policy in another drift apart within a quarter. The grade that entitles someone to a cab at 11pm is not the grade that entitles them to a flight, and no one notices until an exception is escalated.
-
Two approval chains
The same manager approves the same person twice, in two systems, against two thresholds — and finance reconciles the result by hand.
-
Two invoices, two formats
Air and hotel arrive as a GST invoice from a travel desk. Ground arrives as a spreadsheet from each operator. Matching them to one cost centre is a monthly exercise rather than a report.
-
No single view of spend per employee
The question "what does it cost to keep this team mobile" needs two exports and a join. It is usually answered once a year, for a budget, and never checked.
One platform
Defined once, enforced everywhere.
The same rule set governs a flight to Delhi and a 2am drop in Whitefield.
One approval chain
Multi-level approvals with the same thresholds and the same delegation rules, whatever is being booked. An out-of-policy request looks the same to the approver either way.
One audit trail
Who booked, who approved, what it cost and what actually happened — captured the same way for every mode, and exportable for statutory or internal reporting.
One invoice, one reconciliation
Travel and ground consolidate to a single monthly invoice with three-way match against the rate card, rather than arriving as separate documents to be joined by hand.
One number per employee
Total mobility cost per person, per team, per site — without an export. That is the figure a CFO asks for and the split stack cannot produce on demand.
One vendor relationship
One contract, one SLA and one support path. Where taSki acts as your transport vendor, taSki holds the agreements with the empanelled operators — you sign with taSki and nobody else.
How the switch runs
One site first, then the rest.
No big-bang cutover. The first site proves the numbers against your own spend before anything else moves.
-
Week 1
Bring one site
One office, one shift pattern, one roster. taSki models it against your current spend so the comparison is your data, not a generic benchmark.
-
Weeks 2–3
Onboard the operators you already use
Existing vendors move onto the Partner Suite, typically without changing their commercials. No supply lock-in, and no service gap during the switch.
-
Week 4
Switch travel onto the same policy
Air and hotel join the policy engine the ground programme already runs on. The approval chain does not change — it just covers more.
Questions
What buyers ask before consolidating.
Still unanswered? Our solutions team replies within one business day.
Talk to the team → Do we have to buy both travel and employee transport?
No. Most programmes start with one — usually employee transport, because that is where the spend and the safety obligation sit — and add corporate travel later. The point of one platform is that adding the second is configuration, not a second implementation.
We already have a travel desk or a TMC. Does taSki replace it?
Not necessarily. taSki can run the policy, approval and reporting layer over your existing travel arrangements, or provide booking directly. What changes is that ground and air stop being governed by two different sets of rules.
How is this different from an employee transport tool plus an expense tool?
Two tools give you two policies, two approval chains and two datasets that have to be joined before anyone can answer a question. One platform means the rule is defined once and the report exists without an export.
Does taSki own vehicles?
No. taSki owns no fleet. Trips run either on the operators you already use, or on taSki-empanelled vendors across India. In the second case the vendor contract is between taSki and the vendor — you have no agreement with them, no rate negotiation and no paperwork. You contract with taSki alone, and taSki carries the SLA.
See it on your own data
Bring one site's roster and one month of travel spend.
A 30-minute review, modelled on your programme rather than a generic benchmark. No obligation and no rate card required to start.