Guide Summary
Global Capability Centres often grow headcount faster than internal fleet processes can keep up. This guide captures the playbook used by a multi-city GCC programme: standardise policy, consolidate vendors, lock predictable rentals and run administration through one mobility partner and platform.
The Challenge
A fast-growing GCC needed consistent employee and field mobility across 12 Indian cities. Legacy arrangements were fragmented — different vendors by location, uneven entitlements and limited visibility for finance and admin teams at headquarters.
Leadership wanted three outcomes: one policy language, predictable monthly cost, and an operating model that would not break as hiring accelerated.
The Approach
- Audit existing vehicles, vendors and entitlement exceptions.
- Design a national mobility policy with clear grade bands.
- Consolidate under MYLEASE operating lease for standard categories.
- Sequence city onboarding instead of a big-bang cutover.
- Activate MYLEASE One for requests, documents and programme visibility.
- Review utilisation and renewals on a quarterly cadence.
What Changed
Results
- Standard mobility policy adopted across all 12 cities.
- Vendor consolidation reduced commercial and operational fragmentation.
- Finance gained clearer monthly rental forecasting.
- Admin teams spent less time chasing documents and status updates.
- New-city launches followed a repeatable checklist instead of custom reinventing.
Multi-city fleet success is less about finding the cheapest vehicle in each pin code — and more about one operating system that still feels local to employees.
Lessons for Other GCCs
- Write the national policy before negotiating city exceptions.
- Consolidate commercial ownership even if delivery remains local.
- Sequence migrations by city readiness, not only by headcount size.
- Give HQ a live operational view — spreadsheets will not scale.
- Treat renewals and residuals as a portfolio calendar, not surprises.