Tracking vehicle and driver document expiry for an Indian fleet

Why an expired document costs more than the renewal fee

A missed renewal rarely costs the government fee. It costs the days the vehicle sits idle, the penalty that builds up while nobody notices, and the claim that an insurer refuses to pay after an accident. Each of these is larger than the fee itself, which is why the tracking problem belongs to operations and not only to the office clerk.

Start with the penalty math for commercial vehicles, because it grows every day. Fleet and vehicle portals widely report a late fee of Rs 50 per day for a transport vehicle that runs on an expired fitness certificate, with no cap in the rules as they are described online. A vehicle that is 60 days late therefore adds about Rs 3,000 before the inspection fee is paid. Those figures come from secondary sites, so confirm the current rate with your regional transport office before you put it in a budget.

The fee is not the whole loss. Your own cost per idle day is the number that matters. Take the revenue one vehicle earns on an average working day, add the driver wage you pay while it sits, and multiply by the number of days a missed renewal typically takes to fix. That is the figure to put in front of the owner who decides how much attention this problem deserves.

Driver licences add a different kind of risk. A transport licence can be renewed from one year before expiry to one year after, and a renewal inside the window without a fresh test is the normal path. After that window, delay fees rise, and some drivers face a re-test. A driver who cannot legally drive is a driver you cannot put on a route, so the cost lands on dispatch, not on the office.

The documents to track, the alert windows and the owner for each

Most fleets track two or three documents and forget the rest. The list below covers the six that matter for a mixed fleet of trucks, vans and passenger vehicles. The alert windows are our practical suggestion for lead time, not legal deadlines. Adjust them to how long your local office takes to process each renewal.

• Registration certificate (RC): check the validity date on the card and in the Vahan record. Owner: the fleet administrator. Alert at 60 days.
• Motor insurance: the policy end date, which is usually the earliest date to fail. Owner: the finance lead who pays premiums. Alert at 30 days and again at 7 days, because insurers may ask for a valid PUC and fitness record before they quote a renewal.
• Fitness certificate (FC): the date shown on the certificate, which is the one that changes most often for commercial vehicles. Owner: the workshop or fleet manager who books the test. Alert at 30 days so the test slot can be booked 15 days before expiry, a lead time that at least one fitness guide recommends.
• PUC certificate: the validity printed on the certificate. Owner: the driver or depot supervisor who takes the vehicle to a test centre. Alert at 14 days.
• State permits: the permit end date. Owner: the operations head who files routes and inter-state movements. Alert at 60 days, because permits often need paperwork from the owner and sometimes a physical visit.
• Driver licences: the expiry of each driver's transport licence, and the medical certificate if the rules ask for one. Owner: the HR or driver supervisor. Alert at 90 days, which leaves room for the medical test and the one-year window.

Give each renewal one owner, not a team. When two people are responsible, both assume the other one has booked it. The owner is the person who is paid, measured or disciplined if the renewal is late. Write the name next to the document in the register. If the person leaves, the register should show who takes over the same day.

Manual way and automated way compared

The table below compares how a typical fleet handles expiry tracking today with an automated setup. The automated column does not remove the RTO visit or the portal booking. It removes the search for dates, the missed reminder and the chase by phone.

How to automate it, step by step

The set-up does not need a new system on day one. You can run the first version with the tools you already have and add the rest after the first month of reminders. Work through these steps in order.

1. Build the vehicle and driver list. Write one row per vehicle and one row per driver, with registration number, chassis and engine numbers, driver licence number and the owner for each renewal. Keep this list in a shared cloud database such as Zoho Creator or Airtable, or in the vehicle module of your ERP if you already run one. Do not use a loose spreadsheet as the master, because a spreadsheet does not send reminders on its own.
2. Collect the expiry dates once. For each vehicle, use the validity dates on the RC, insurance policy, fitness certificate, PUC and permit. For each driver, use the licence card and the medical certificate. Where paper is the only copy, photograph it and let an OCR engine such as Google Cloud Vision or Amazon Textract read the date fields. Have a person confirm every date the OCR reads, because a misread digit causes the whole alert schedule to be wrong.
3. Confirm the registration status on the official portal. Use the Parivahan Sewa portal to check the vehicle record for each registration number, as described below. Record the result in the register. Treat this as the baseline. The portal does not offer a reminder service that we could confirm, so the reminders must come from your own system.
4. Set the alert windows and the message templates. Use the windows from the list above. In WhatsApp, use a utility template for reminders because the message concerns an existing obligation. Marketing templates cost more and can be rejected if they are written as promotions. A short template with the vehicle number, the document name, the expiry date and one action is enough.
5. Connect WhatsApp through an official provider. Meta's WhatsApp Business Platform charges per message in India. Meta's current India rate card lists a utility message at Rs 0.115, and a marketing message at Rs 0.8631, both before 18 percent GST, and from 1 October 2026 utility templates sent inside an open 24-hour window also carry the utility charge. A business solution provider adds its own platform fee on top, so compare the total per message before you choose one. Add email alerts through your existing Gmail or Microsoft 365 account for the owner's records.
6. Connect the register to your accounts. Once a renewal fee is paid, the expense goes into Tally Prime or Zoho Books against the vehicle. Recording it in the same place keeps the cost per vehicle visible for the owner. If you already use Zoho, the link is simpler, but Tally works through an export or a connector your accountant can set up.
7. Run the escalation rule. If an owner does not confirm a booking within the first window, the message goes to the owner's manager. If the document is still open at the last window, it appears at the top of the weekly review, and the operations head sees it. This is where the chasing happens, and it no longer depends on memory.

Checking registration status on the Parivahan portal

The Parivahan Sewa portal, run by the Ministry of Road Transport and Highways, is the place to confirm what the government record shows. Open the portal and go to the online services menu. Choose vehicle-related services, select the state where the vehicle is registered, then choose the regional transport office and proceed. Enter the registration number to see the vehicle details, including fitness, insurance and registration information where the record holds it.

The same details are available in the mParivahan app, which many drivers already have. Check each vehicle at the start of your set-up and once a quarter after that. Any mismatch between the portal and your register is a sign that a renewal was done but not logged, or that a document was entered wrongly. Resolve the difference before you rely on the alert schedule.

Do not treat the portal as a substitute for the physical certificate. Carry the original documents or the digital copies that the transport department accepts, and keep scans in the register. Do not rely on a third-party site that shows vehicle details unless your team has checked it against the official portal first.

What breaks and how to prevent it

The most common failure is a wrong date. Someone enters the issue date instead of the expiry date, or the OCR reads a 3 as an 8, and every alert for that document fires at the wrong time. The fix is a second check on every date at entry, and a monthly comparison of the register against the portal for a sample of vehicles.

The second failure is an owner who leaves. The register still names them, the messages go to a dead number, and nobody notices for weeks. Keep at least two people on every renewal, with the second person copied on the alert, and review the owner list every time someone leaves.

The third failure is a message that never arrives. WhatsApp templates can be paused or rejected, and a phone number can change. Check the delivery status of each reminder in the provider's dashboard, and send the first alert of each window by email as well. If a message shows as undelivered, the worker should call the owner's number through a person, not wait for the next window.

The fourth failure is a rule change. Fitness testing rules changed when automated testing stations became the route for commercial vehicles, and driver licence and PUC validity periods are described differently across sources. Confirm each validity period with the regional transport office or the official portal before you set a window, and review the register when the rules change.

The fifth failure is a booking that cannot be made. Some renewals depend on other documents being valid first. A fitness test, for example, may need current insurance and a current PUC before the slot can be booked. Set the alerts in the order the documents must be renewed, not in the order they expire, so the owner has time to fix the dependency.

When not to automate

Automation is not worth it for a very small fleet, such as two or three vehicles with one owner who checks the papers every week. A calendar entry on the owner's phone is cheaper and clear enough. Set up the register when the number of vehicles or drivers grows past the point where one person can hold the dates in their head.

Do not automate a renewal that needs judgement. A vehicle that has failed a fitness test, or a driver whose licence was suspended, needs a decision about repair, replacement or reassignment. The worker can flag it, but the decision belongs to a person.

Do not automate the chase if your drivers do not carry a phone that receives WhatsApp messages. In that case, the alert has to reach a supervisor who can speak to the driver, and the design should follow that route.

Automation cannot book the government slot, pay the fee, sign the form or make the physical visit. It cannot read a certificate that is torn or faded without a person checking it. It can tell you that a date is coming and who is responsible. The renewal itself still happens at the RTO, on the portal or at a testing station.

What it takes in time

For most fleets the first version takes a few weeks of part-time work from an operations person, plus a day or two from whoever manages the WhatsApp provider. The first week goes on the vehicle and driver list and the document dates. The second week goes on the Parivahan checks and the alert windows. The third week is a trial with three or four vehicles, and the fourth week rolls the process out to the rest of the fleet. These are our working estimates, not a published benchmark, and a fleet with many documents in paper form will take longer.

After the set-up, the ongoing work is small. Someone reviews the weekly list, checks the portal once a quarter, and updates the register when a renewal is done. The effort shifts from remembering dates to confirming outcomes. Plan for that review to take a short slot each week, not a full day.