EVP – Operations Transformation — Fleet-Operations Network

The mandate

Several states are introducing materially different obligations for commercial fleet aggregators: local control rooms, vehicle and driver verification, incident retention, permit evidence and auditable service records. The fleet network currently runs national processes with depot-level exceptions managed through email and spreadsheets. Compliance has been achieved case by case, but the approach will not survive simultaneous implementation or regulatory inspection. The operations transformation leader must build one federated model that respects local rules without creating a different company in every state.

The operating perimeter covers approximately 900 employees and partners across control towers, depots, fleet scheduling, maintenance coordination and partner support. Vehicles include company-controlled and third-party capacity serving enterprise and consumer contracts. Product and legal teams interpret requirements; this EVP owns the operating design, adoption and evidence that controls work on an ordinary shift.

Success is not a larger compliance department. It is a front-line operation in which a vehicle cannot be dispatched without valid evidence, incidents move through known escalation paths and local regulatory differences are configured rather than improvised. Service continuity matters: controls that strand compliant vehicles or create queues at shift change will rapidly lose legitimacy.

Why this seat is open

The board approved this planned new role when the regulatory horizon showed multiple implementation dates within the next year. Existing operations leaders remain accountable for daily service and cannot redesign the network while meeting current contracts. Creating the seat now allows sequencing, piloting and workforce consultation rather than emergency remediation after an adverse inspection.

What you will own

• Translate every applicable obligation into a process, control owner, evidence record and service-impact assumption; resolve conflicts through legal rather than local custom.
• Design the target relationship between national control tower, state compliance lead and depot manager, with unambiguous incident and dispatch authority.
• Establish master data for vehicle, driver, permit, training and insurance status, including third-party validation and expiry prevention.
• Pilot shift-start and dispatch controls under peak load, measure queue and rejection causes, and fix usability before national deployment.
• Standardise incident intake, preservation, escalation and regulatory notification while protecting personal data and fair investigation.
• Reconfigure third-party fleet contracts to provide evidence, audit access and remedy rights without transferring non-delegable accountability.
• Build a field implementation team that can coach depot managers and then withdraw, leaving durable line ownership.
• Maintain a regulatory-readiness view for the executive committee, separating confirmed requirements from assumptions and lobbying positions.

The first 12 months

The first 90 days should produce an obligation map, control baseline and implementation sequence across all active states. Observe dispatch at six depots, sample failed verifications and rehearse one serious-incident path. Select two contrasting pilots and agree service guardrails with customer operations. Any critical evidence gap affecting lawful dispatch should receive an interim control immediately.

By month six, pilots should demonstrate reliable verification at peak shift change, auditable incident records and clear local-national escalation. Begin staged deployment in the highest-risk states, supported by accredited training and daily defect management. Amend priority third-party contracts and create a controlled exception process with expiry, approval and after-action review.

At year end, 98% of dispatches should carry complete, current evidence; permit-expiry failures should decline by 80%; serious events should reach the accountable executive within 30 minutes; and regulatory submissions should meet every statutory deadline. Control-related dispatch delay should remain below two minutes at the 90th percentile. Independent testing should find no repeated critical exception across two review cycles.

What the board will measure

• Legal readiness by state and obligation, supported by operating evidence rather than programme self-certification.
• Service continuity while new controls are introduced, particularly during shift peaks and seasonal demand.
• Completeness and accuracy of vehicle and driver master data across owned and partner fleets.
• Incident response that is fast, fair, privacy-conscious and capable of regulatory scrutiny.
• Third-party adherence without fictional transfer of the platform's responsibilities.
• Line ownership after implementation teams leave, demonstrated through depot self-correction and internal assurance.

The person

You have 18–22 years in distributed operations transformation and have implemented regulation where front-line work, technology and third parties meet. Suitable experience could come from mobility, aviation ground services, logistics, payments operations or regulated field infrastructure. You have personally carried service levels through control change and can distinguish a policy statement from a workable shift procedure.

Your relevant scale includes at least 650 employees and a multi-location network with significant partner capacity. The board will examine an implementation that initially failed, how quickly the defect became visible and whether you altered design rather than blaming adoption. You are confident with regulators and legal counsel but remain grounded in depot observation, queue data and incident records.

The appointment is onsite in Mumbai with substantial state travel. It reports to the Group Chief Executive or designated sponsor and will work closely with legal, risk, product and regional operations.

Compensation and terms

Fixed compensation is ₹2.2–3.0 crore plus performance variable linked to regulatory readiness, service continuity, data quality and embedded ownership. This permanent onsite Mumbai role reports to the Group Chief Executive or appointed committee sponsor and entails frequent travel. Notice up to six months can be considered against the regulatory implementation timetable.

Confidentiality

Client identity, state sequence, inspection history and fleet partners remain restricted. Candidates who establish relevant experience will receive fuller information under a mutual undertaking and after conflict review. The composite description is not a clue to a named operator; speculative contact with regulators, depots or fleet providers is prohibited.