Notices forwarded by the lease company
Leasing companies forward notices for the vehicles they own, often with their own admin fee. Councils and parking operators write to you directly for others. Each notice has to be matched to a client, then to the driver who had the vehicle at that time, then handled the way that client wants: some want the liability transferred to the driver, some want you to pay and recharge, some want the notice sent to their own fleet team.
The driver on the fleet system is the current driver. The vehicle was swapped between two drivers last month, and the notice is from last month.
Why driver identification is slow
The problem is not the notice. It is knowing who had the vehicle on a given day, weeks ago.
- Fleet systems often store the current driver, not the history.
- Pool vehicles and shared vans have no fixed driver.
- Clients have different rules on who pays and whether to transfer.
- Notices arrive from lease companies, councils, private operators and the police, each with its own route.
- Deadlines are short, and forwarding from the lease company eats into them.
What slow handling costs
Notices that escalate because the transfer window passed, and costs that land on the client or you. Admin time spent emailing clients to ask who was driving. Drivers who receive a notice weeks late and dispute it. And clients who expect their fleet manager to handle this cleanly.
The notice desk we build
- Notices from every source are scanned or forwarded into one intake, and the registration, date, time, issuer and deadlines are read from them.
- The vehicle is matched to its client, and the driver is found from the allocation history for that date and time, including pool bookings and temporary swaps.
- Where the allocation is unclear, the client's fleet contact is asked through a link that shows the vehicle, date and possible drivers, with the deadline visible.
- The client's rule is applied: transfer to the driver, pay and recharge, or pass to the client's own team, with any admin fee under their contract recorded for rebilling.
- Transfers and responses are prepared for each issuer's route and checked by a person before sending.
- Every notice has a status and deadline, and escalations and follow-up letters are matched to the original.
| Client rule | What the desk does |
|---|---|
| Transfer to the driver | Prepares the transfer with driver details |
| Pay and recharge | Records for payment and adds to the rebill |
| Pass to the client's fleet team | Sends the notice with vehicle and driver details |
| Driver unclear | Asks the client's contact before the deadline |
Allocation history is the foundation
The desk is only as good as the record of who had which vehicle when. If your fleet system does not keep that history, we add it: a driver change is recorded with a date whenever a vehicle is reallocated, and pool bookings are recorded as allocations. That history is also what clients need for fuel exceptions and accidents, so it pays back in several places.
Notices handled while the deadline is still comfortable
Notices for vehicles in transition are the trickiest: a car between drivers, a van at a supplier for repair, or a vehicle already returned to the lessor. The allocation history includes those states, so a notice issued while the van was at a garage goes to the supplier handling it, not to the last driver, and a notice after return goes back to the lessor with the collection date.
Most notices are matched to a driver on the day they arrive. The desk works through a queue sorted by deadline, and clients are only asked about the ones that genuinely need them. Admin fees are rebilled as the notices are handled. The overdue pile disappears.
Signs this is your desk
- You cannot easily say who had a vehicle on a past date.
- Notices escalate because the transfer deadline passed.
- Clients are emailed about every notice to ask who was driving.
- Each client's rule is remembered by one person.
- Admin fees for notices are not always rebilled.