Pool Car Reservation: Book Shared Vehicles Without the Double-Booking Chaos
Let staff reserve a pool car for a date and time, hard-block every overlap, check eligibility, and capture odometer and condition at key handover — with an admin approving the bookings that need it.
A web tool where staff request a pool vehicle for a time range, overlaps and ineligible drivers are blocked, an admin approves the bookings that need it, key check-out captures odometer and condition, return check-in closes it out, and every trip lands in a usage log you can export as CSV.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A CSV or sheet of your pool vehicles and your staff/driver list
- Claude Code or any AI coding agent
The problem this kills
Two people show up for the same car at 8 a.m. Someone takes the seven-seater for a solo airport run while the team that needed it is stranded. A driver whose license lapsed months ago grabs the keys. The car comes back with a fresh dent that nobody owned up to, and the odometer log has a three-week gap. Right now your "booking system" is a wall calendar, a shared spreadsheet, or a sticky note on the key cabinet — and it quietly fails the moment two requests collide.
The fix isn't a fancy fleet platform with a per-seat license. It's a small, focused tool that does the few things that actually matter: it refuses to let two bookings overlap on the same vehicle, it checks that the driver is allowed to drive, it routes the bookings that need a human (overnight, multi-day, an ineligible driver) to an admin, and it makes the person taking the keys record the odometer and any damage before the car shows as Out. You do not need to be a developer to build that.
What you'll build
A simple internal web app for your team. Staff pick a vehicle and a date/time range and request it. The tool hard-blocks any overlap with an existing booking on that car, and checks the driver's eligibility (valid license on file). Short, same-day bookings by eligible drivers auto-confirm. Anything that needs judgment — overnight, multi-day, or a driver who isn't eligible — goes to a fleet/office admin to approve or decline. When it's time to drive, the admin (or the driver) does a key check-out that captures the odometer reading and the vehicle's condition — and only then does the car flip to Out. On return, a check-in captures the closing odometer and any new damage. Every completed trip lands in a usage log you can filter and export as a clean CSV.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your current booking process, where your vehicles live and how they're typed (sedan, van, seven-seater), the exact fields and naming in your vehicle and driver lists, your typical and peak demand, and your real rules for what needs admin approval versus what can auto-confirm. It reads a short spec back to you for a thumbs-up, then builds the tool around your fleet and your rules instead of a generic template. From there it walks the agent through the data model, the vehicle and driver imports, the conflict-free booking engine, the eligibility check, the admin approval queue, the key check-out / check-in with odometer and condition capture, and the usage-log CSV export. Every step ends with a ready-to-copy prompt.
The governance it includes (this is the point)
This isn't a toy calendar. The plan builds in the controls a real operation needs: login so only your team can book, row-level security so a branch only ever sees its own vehicles and bookings, a complete audit trail of every request, approval, check-out and check-in (who, what, when), a hard human-approval gate so a car never shows as Out until a person confirms the key handover, and duplicate guards so the same vehicle can't be double-booked for an overlapping time. The whole tool exists to make the careful human moments — approving an exception, handing over a key — easy and recorded.
Who it's for
Fleet managers, office and facilities managers, and branch admins who own a handful of shared vehicles and are tired of clashes, lapsed-license surprises, and mystery dents. If you can describe your cars, your drivers, and the bookings that need a sign-off, you can build this.
You've got this — open the plan, paste the first prompt, and you'll be taking your first conflict-checked booking this afternoon.