The calendar and clash guard
Read the availability calendar, stop an accidental double-booking, and put your hires in your own calendar app.
The calendar answers one question at a glance: what is out, what is free, and what is due back. The clash guard stops the mistake that ends with two hirers at the kerb for the same car.
The availability calendar
Go to Bookings, then the Calendar view. You see a strip of dates with each car's hires laid across it, so you can read availability without opening anything. Alongside it is an Upcoming hires agenda listing what is coming up in date order. Only cars from your saved fleet appear on the strip, so pick a saved vehicle when you raise a booking rather than typing a loose name.
Paging through dates
The strip shows a fortnight at a time, starting a couple of days back so you can still see what has just gone out. Page forward and back with the arrows. Once you have moved away from today, a Today button appears to snap you back.
The clash warning
If a car ends up booked on overlapping dates, both hires carry a Clash marker on the agenda. The guard also fires as you work: raising a booking, changing the dates, or swapping in a different car all warn you if the new dates overlap an existing hire.
You can still go ahead when you know the overlap is intentional, for example a same-day return and re-hire. The point is simple: you should never double-book a car by accident. If two hires overlap, KeyProof makes sure it is your decision, not a slip.
Your hires in Google or Apple Calendar
Settings has a calendar feed link. Subscribe to it in Google Calendar or Apple Calendar and every hire shows up alongside the rest of your week: which car, who has it, and the dates. It is one way only, so nothing you do in your calendar app changes a booking.
Treat the feed link like a key. Anyone who has it can see your whole hire schedule with no login, so only paste it into your own calendar app. If it gets out, replace it from the same card: the old link stops working straight away and every calendar subscribed to it has to be pointed at the new one.