The double booking is the most expensive mistake a rental agency can make: two customers, one car, and a Saturday morning at the counter looking for a replacement vehicle. It almost never happens through carelessness. It happens because the information about availability is scattered.
Why overlaps happen
- Several sources of truth. One reservation noted on WhatsApp, another in the notebook, a third in the manager's Excel file. Nobody sees the whole picture.
- Returns are not dated. A car is "rented" without a reliable return date, so nobody knows when it becomes available again.
- Extensions are not recorded. The customer calls to keep the car two more days; the agent agrees, but the schedule is not updated.
- Maintenance is not planned. The oil change or the technical inspection takes a vehicle off the road that the schedule considers free.
- Two people book at the same time. Without automatic blocking, two agents can assign the same car to two customers within the same hour.
The basic rule: one calendar per vehicle
A car's availability can only be guaranteed if all of its occupations are on the same timeline: current rentals, confirmed reservations, extensions, expected returns and maintenance periods. That is what a calendar per vehicle does. Each row is a vehicle, each bar is an occupation, and a new slot can only be entered if it touches no existing bar.
Five rules to give the counter team
- No reservation outside the software. A call, a WhatsApp message or a customer at the counter always ends with a reservation entered, even a provisional one.
- Every rental has a return date and time. Without a return, no availability can be calculated.
- An extension is a change to the reservation, not a verbal agreement. It is entered before hanging up.
- Plan a margin between two rentals for cleaning and the inspection: an hour or two depending on your organisation.
- Plan maintenance in the calendar, like an internal reservation, so the vehicle is not offered.
The statuses that avoid misunderstandings
A calendar is only useful if the team reads the same thing. Clearly distinguish: request (not confirmed), confirmed (vehicle blocked), in progress (vehicle out), completed (vehicle back) and cancelled. An unconfirmed request must not block a car indefinitely: set a confirmation deadline.
And when the overlap is already there?
Treat it as an operational incident: offer a vehicle of a higher category at no extra cost, note the cause in the file, then fix the rule that let the error through. If the cause is "reservation taken outside the software", the remedy is organisational, not technical.
Reservations and calendar in KriHani · From Excel to software
