cabsoft.app
Compliance

The document that expires while nobody is looking

Permit, fitness, insurance and licence run on four cycles. Across thirty vehicles that is 155 dates — and the lapse is always found at the worst moment.

Every operator has had the phone call. A vehicle stopped at a checkpoint, or worse, an incident followed by an insurer asking a simple question about a certificate that lapsed six weeks ago.

Nobody was careless. That is the point worth making about this problem.

The arithmetic nobody does

Four documents per vehicle, each on its own cycle:

  • Permit — renewal by type and state
  • Fitness certificate — its own schedule, shorter for older vehicles
  • Insurance — annual, and a lapse of one day is a lapse
  • Driver licence and badge — per driver, not per vehicle

Thirty vehicles and thirty-five drivers is roughly 155 dates. Fifty vehicles is over 250.

No individual is capable of holding that reliably alongside dispatch, payouts and customers. When it fails, the honest diagnosis is not that someone forgot — it is that the task was never something a person could do.

Why the spreadsheet does not solve it

Most operators have a spreadsheet with expiry dates. It is not useless. But it has one flaw that decides the outcome: it has to be opened.

A spreadsheet is a passive record in a business where nobody has a spare hour. It gets updated after the renewal rather than before, which means it documents history rather than preventing anything. The moment it needs to work is exactly the moment nobody is looking at it.

What is needed is not a better list. It is the list telling you, before the date, without being asked.

The vendor problem, which is worse

If you run contractor vehicles, you are exposed to documents you do not hold and cannot see.

Your client’s contract makes you responsible for the vehicle that turned up. Your vendor holds the paperwork. When a client’s audit asks for the fitness certificate of a vehicle that ran a shift in March, you are making a phone call and hoping.

For a transport desk this is the argument for holding vendor vehicle documents in your own system rather than trusting that the vendor holds them. Not because vendors are dishonest — most are not — but because their filing is not something you can produce on demand, and yours is.

What good looks like

  • Every vehicle and driver has its four dates recorded once, at onboarding
  • Warning at a useful interval — thirty days, not the morning it expires
  • The same discipline for vendor vehicles as for your own
  • An out-of-date vehicle is visible before dispatch, not after a checkpoint
  • The whole picture is exportable, because that is what a client’s audit asks for

That last point converts the exercise from a cost into an asset. An operator who can produce a current compliance file for the fleet within the hour is bidding for work that operators who cannot are eliminated from.

The two-hour job worth doing this week

  1. Count your vehicles and drivers, multiply by four, and look at the number.
  2. Pick three vehicles at random and try to produce all four current documents in ten minutes.
  3. Do the same for one vendor vehicle.

Step three is the one that tends to be sobering, and it is the one your client will eventually ask about.

Our page on safety and emergency response covers expiry tracking across your own and your vendors’ vehicles, and vendor management covers holding a contractor’s records where you can actually reach them.

Bring us the week that went wrong

Tell us how you move people today and we will show you the same week running on one system. Or just email info@qwicksoft.com.

Request a demonstrationAll articles