Fleet Compliance Checklist: RC, Insurance, Fitness, PUC (India 2026)

Compliance is the most boring topic in fleet management and the most expensive one to get wrong. A missed insurance renewal turns a ₹300/year premium into a ₹10 lakh liability the moment a vehicle is in an accident. A missed fitness certificate turns a trip into an impoundment and a lost customer. A missed PUC turns a routine check into a ₹10,000 fine.

This is the compliance checklist we would hand to an operations manager taking over a 500-vehicle fleet on day one. It is India-specific, operator-focused, and it is the playbook that keeps a fleet in the clear as it scales.

The six mandatory documents

Every commercial vehicle in India must have all six of these current at all times:

Each has its own renewal cadence, issuing authority, and penalty structure. Missing any one is a fineable offence and — in most cases — a ground for vehicle impoundment.

Document 1: Registration Certificate (RC)

Validity: 15 years from date of first registration for personal vehicles, renewable for 5-year blocks thereafter. For commercial vehicles, the RC is linked to the fitness certificate — effectively renewed every 2 years (first 8 years) then annually.

Issuing authority: The RTO (Regional Transport Office) of the state where the vehicle is registered.

Renewal process:

1. Form 25 submission to the RTO.
2. Updated fitness certificate (for commercial).
3. Updated insurance and PUC.
4. Vehicle inspection (physical) for commercial vehicles.
5. Road tax dues cleared.

Penalty for lapsed RC: ₹5,000 + registration cannot be transferred, insurance claim can be denied, vehicle cannot be legally sold.

Fleet gotcha: If you operate a vehicle in a state different from registration, you may need a state-specific "NOC" and re-registration after 12 months. Leasing companies often miss this when a lessee moves the vehicle inter-state.

Document 2: Motor Insurance

Validity: 1 year typically. Long-term policies (3–5 years) available for new private vehicles; not for commercial.

Types:

• Third-party — mandatory under the Motor Vehicles Act. Covers damage to third parties.
• Comprehensive — covers own-damage + third-party + theft. Optional but strongly advised for commercial fleets.
• Commercial vehicle liability packages — bundle IMT 23 (legal liability to paid driver) and goods-in-transit cover.

Issuing authority: Any IRDAI-licensed insurer.

Renewal cadence: 30 days before expiry is the safe window. Do not let it lapse — if it lapses for more than 90 days, you need a fresh inspection before renewal, which takes time and adds cost.

Penalty for lapsed insurance: ₹2,000 (first offence), ₹4,000 (subsequent), plus full liability for any accident that occurs during the lapsed period. Impoundment is common.

Fleet gotcha: Claim Bonus (NCB) resets if the policy lapses for more than 90 days. On a 500-vehicle fleet, NCB erosion across even 2% of vehicles is a material cost — could be ₹5–15 lakh in extra premium next year.

Document 3: Fitness Certificate (FC)

Validity:

• 0–2 years: valid at purchase (issued with RC)
• 2–8 years: renewed every 2 years
• 8+ years: renewed annually

Issuing authority: RTO, after a physical inspection at an authorised testing centre.

Renewal process:

1. Form 38 submission.
2. Physical inspection (brakes, steering, lights, emissions, structural integrity).
3. Fee payment.
4. New FC issued on same day for a pass; re-inspection for fail.

Penalty for lapsed FC: ₹10,000 and impoundment. This is the most commonly caught compliance failure at interstate checkpoints.

Fleet gotcha: Fitness inspection fails ~10–15% of first attempts in most states. Budget 5 days between the expiry date and your target renewal to handle a re-inspection. Do not leave renewal to the last week.

Document 4: PUC Certificate

Validity: Varies by vehicle age.

• 0–1 years: 12 months
• 1–3 years: 6 months
• 3–10 years: 3 months
• Diesel, 10+ years: 3 months or less (state-specific)

Issuing authority: Any authorised PUC testing centre (most petrol pumps).

Penalty for lapsed PUC: ₹10,000 and impoundment in most states. Delhi, Mumbai, and Bangalore enforce actively; smaller cities less so.

Fleet gotcha: PUC has the most renewals per year of any document. For a 500-vehicle fleet with mixed age profile, that is 1,200–1,800 PUC renewals annually — roughly 5 per working day. Cannot be managed from a central inbox; needs per-depot ownership.

Document 5: Road Tax

Validity: Depends on state. Typically paid as one-time (on registration) in most states; annual in a few states for commercial vehicles.

Issuing authority: State RTO.

Special note: If a vehicle operates in a state different from its registration for more than 12 months, the operator must pay road tax in the operating state too (after obtaining NOC). This is the single biggest compliance exposure for interstate leasing.

Penalty for unpaid road tax: Varies by state, typically ₹1,000 to ₹5,000 per month of default. Interstate enforcement has become stricter with the VAHAN 4.0 inter-state data sharing.

Document 6: Permit

Validity: Depends on permit type.

• Local permit — for use within the issuing state (typically 5 years)
• National permit — for interstate commercial use (5 years, renewable)
• All-India Tourist Permit — for tourist passenger vehicles (5 years)
• Contract Carriage Permit — specific to lessor-lessee arrangements
• Goods Carrier Permit — for trucks

Renewal: Form PCA + fees. Often bundled with fitness renewal.

Penalty for operating without permit: ₹10,000 + impoundment + permit cancellation risk. For commercial operators, this is existential — a cancelled permit is a revoked licence to operate.

The compliance calendar for a 500-vehicle fleet

Here is what a realistic monthly compliance load looks like for a mid-size fleet:

Total: roughly 170–240 renewals per month, across multiple depots, with per-document lead times ranging from 7 to 45 days.

This cannot be run from a spreadsheet once you cross 100 vehicles. The arithmetic does not work.

The automation playbook

A well-run compliance function has four layers:

Layer 1: Single source of truth

Every document expiry date lives in the fleet platform, against the vehicle record. No parallel spreadsheets, no "the insurance guy has a list". If it is not in the platform, it does not exist.

Layer 2: Automated alerts

Each document type has a cadence:

• 30 days before expiry — first alert to the responsible region/depot manager
• 15 days — escalation to operations lead
• 7 days — escalation to fleet head + CC finance
• 1 day — red-alert to everyone

Alerts must route by region. A Pune depot manager does not care about Nashik expiries. The volume makes central routing impractical.

Layer 3: Status dashboard

A compliance dashboard that shows, at any moment:

• Overall compliance rate (% of vehicles with all six documents current)
• Red, amber, green breakdown by document type
• Top 10 vehicles needing attention this week
• Disposed vehicles excluded (critical — alerts on scrapped vehicles destroy operator trust in the system)

Target: 98%+ green at all times. Below 95%, you are at material risk.

Layer 4: Historical audit trail

When a vehicle is audited, sold, or involved in a claim, you need the full history of every document, every renewal, every receipt. Retention should be 7+ years (matches most statutory limits).

What good looks like in a compliance report

A monthly compliance report should answer three questions:

1. Are we compliant? Percent of fleet with all documents current. Target: 98%+.
2. What is coming up? Count and list of renewals in the next 30 days, by region and document type.
3. Where did we fail? Any vehicle that has lapsed, for how long, and why.

The third question is the most important. Compliance lapses are almost never random — they reveal process gaps. A consistent PUC lapse in one depot means that depot is not checking; a fitness fail in a specific sub-fleet means those vehicles need more maintenance; a claim that was denied because of an insurance lapse is a process failure, not bad luck.

The three common mistakes

1. Central-only ownership — "compliance is a central team function" works up to ~50 vehicles, not beyond. Scale requires regional ownership with central oversight.

2. Alert fatigue — if every user gets every alert for every vehicle, they will ignore all alerts. Route precisely: the Pune manager gets Pune alerts, the fleet head gets escalations only.

3. Disposed vehicle noise — if your compliance list includes scrapped, sold, or transferred vehicles, the reported compliance rate is wrong in both directions. Your platform must exclude them automatically, and it must be easy to mark a vehicle as disposed the day it leaves the fleet.

How FleetoFi handles compliance

FleetoFi's compliance module covers all six mandatory document types:

• Per-vehicle expiry tracking for Insurance, Fitness, PUC, RC, Road Tax, Permit
• Configurable alert cadences — 30/15/7/1 day defaults, customisable per document type
• Region-based alert routing — each region has a named responsible recipient
• Compliance dashboard with overall % green and red-amber-green breakdown
• Automatic disposed-vehicle exclusion — vehicles in Inventory status post-disposal do not generate alerts
• Historical audit trail — every renewal, receipt, inspection, stored against the vehicle record

The operational target we recommend: 98%+ compliance rate, max 2-day window between expiry and renewal completion, zero lapses > 7 days.

Compliance is the least exciting and most consequential operational discipline in fleet management. The operators who run it well never feature it in a dashboard presentation — they run quietly at 99% and their insurance claims get paid and their permits get renewed. The operators who run it badly feature it in their finance reviews every month, under "unexpected fines" and "impoundment recovery costs."

The playbook is simple. The execution is the discipline.