Fleet maintenance & fuel tracking for Indian fleets

If you manage a corporate fleet in India — whether it's owned employee-transport cabs, vendor-supplied vehicles, or driver-cum-owner (DCO) partners — maintenance is where profit quietly leaks. A missed service triples repair cost. An untracked fuel bill hides pilferage. And a paper logbook can't tell you which vehicle is burning the highest cost-per-km. This guide walks through a modern maintenance setup, tuned for Indian corporate fleets.

Why "spreadsheet maintenance" fails at scale

Beyond ~20 vehicles, an Excel-based service tracker becomes read-only in practice: the person maintaining it can't keep up with odometer readings, service invoices, insurance and PUC expiries, fuel receipts, and driver-side complaints. The symptoms are always the same:

• Vehicles going into breakdown between services because service was calendar-based, not km-based.
• Fuel bills that don't reconcile with kilometres driven — no cost-per-km visibility.
• Expired insurance / PUC / permits caught by a traffic stop, not by a reminder.
• DCO invoices that can't be validated against actual usage.

Set the right service cadence — km-first, calendar-fallback

Indian OEM service intervals are typically 10,000 km or 12 months, whichever is earlier, with oil, filter and tyre-rotation checkpoints in between. In a corporate fleet you should run two parallel schedules per vehicle:

1. Odometer-based: engine oil (every 10k km), transmission (30k km), coolant (40k km), brake fluid (40k km), tyres (every 40–50k km).
2. Time-based fallback: air-con service (annual), battery health (annual), wiper blades (annual), AMC checks (semi-annual).

Whichever hits first triggers the service. Software should compute this from continuous odometer + last-service state and raise a work-order automatically.

Fuel tracking that actually catches leaks

The right unit is km per litre per vehicle per week, not a single fleet-wide average. Two habits close 80% of the leak:

• Capture odometer + litres + amount at every fill (not just amount).
• Flag vehicles whose weekly KMPL drifts more than 15% below the rolling 4-week baseline.

On DCO vehicles, tie the fuel entry to the driver's app so a "fill" event is time-and-location stamped — that alone eliminates the classic reimbursement padding.

The document-expiry stack you must automate

Every vehicle carries four running documents in India:

• RC book — 15 years, then renew.
• Insurance — annual; comprehensive for corporate use.
• PUC certificate — 6-monthly for BS-VI, quarterly for older.
• Permit (contract carriage / all-India tourist) — annual, state-specific.

Driver docs matter equally: DL renewal, badge, police verification for corporate tie-ups (especially for female-employee night shifts). A good system alerts at T-30, T-14, T-7, T-1 days before any expiry — SMS to driver, email to Ops, and a red flag on the vehicle card.

Cost-per-km: the one number that matters

Compute per vehicle per month:

Cost/km = ( Fuel + Service + Repair + Tyres + Insurance ÷ 12 + Permits ÷ 12 ) ÷ km driven

Track the trailing 90 days. When cost-per-km rises 25% above the vehicle's own baseline, that unit is either driving less (utilisation problem) or costing more (maintenance problem) — both fixable, but only if visible.

What "good software" looks like for Indian fleets

When choosing fleet maintenance software for the Indian market, evaluate these:

• Multi-vendor model: own, vendor and DCO vehicles in one system without duplicate data.
• GST-compliant invoicing with HSN codes and place-of-supply logic.
• Female-employee safety compliance — geofence, night-shift escort rules, SOS.
• Offline-tolerant driver app for weak-network areas.
• Rate cards: per-trip, per-km, monthly, and 8/80 duty slabs.
• Document expiry alerts across vehicle and driver stacks.

A 30-day rollout plan

1. Week 1 — Master data: import vehicles, drivers, vendors, clients, rate cards.
2. Week 2 — Live tracking: get every active driver on the driver app; verify GPS pings.
3. Week 3 — Service backlog: catch up on overdue services and load document expiries.
4. Week 4 — Billing dry-run: generate a full month of invoices in parallel with your current process; reconcile line-by-line.