Pool Vehicle Booking Systems (PVBS): What They Do and Whether You Need One

A pool vehicle booking system (PVBS) is software that lets staff reserve a shared vehicle, allocates one to them, and records who used it and for how long. It replaces the whiteboard by the key cabinet and the spreadsheet nobody updates.

If you've got two people sharing one car, you've got a pool. Most of the advice online is written for government fleets with 200 vehicles, which is fine if that's you, but the problems start much earlier than that.

The whiteboard problem

Here's what usually goes wrong, and it goes wrong at eight vehicles as readily as at eighty.

Someone books a car for Thursday. The meeting gets cancelled Wednesday afternoon. Nobody rubs the name off the board, so the car sits in the carpark all Thursday while a colleague expenses a rental. Nobody ever counts how often that happens, which is why it keeps happening.

Then people learn. They start booking defensively — a full day when they need two hours, a standing Tuesday slot in case they need it. Contention goes up, actual usage doesn't, and the fleet manager gets asked why we need another vehicle.

Meanwhile a toll notice turns up for the 14th and you're walking around the office asking who had the Hilux.

None of that is a people problem. It's a record-keeping problem, and it's the reason PVBS software exists.

What a PVBS actually does

Four things, roughly in order.

Staff book. Web or phone, pick a date and time, submit. Some setups confirm straight away, others route to a manager for approval depending on who's asking and what they want.

The system allocates. This is the bit that separates a real booking system from a shared Outlook calendar. Rather than letting people choose a specific car, the system assigns one. That sounds like a small thing until you've watched a fleet develop a "good car" that the same three people always get and a "bad car" nobody touches, with a 40,000km odometer gap between them after two years.

The vehicle goes out. If the platform is connected to GPS, this is where it gets useful — geofencing at the depot can pick up the vehicle leaving, close the booking off automatically when it comes back, and flag anything that drove off without a booking at all.

You get a report. Utilisation, booking history, who had what. This is the whole point, and it's the part most organisations don't get around to reading until budget season.

That's the shape of it in Argus Car Pool Management — book, allocate, drive, report.

PVBS or car pool management? They're not the same thing

Worth separating these two, because vendors use them interchangeably and it muddies procurement.

A pool vehicle booking system is the reservation layer. Its job is stopping two people turning up for the same car.

Car pool management is the wider job: booking, plus driver ID, utilisation analysis, fleet right-sizing, FBT records, cost allocation between departments, and being able to prove any of it later.

You can buy pure booking software. Plenty of organisations do, then find eighteen months on that they still can't answer "do we need 20 cars or 14?", because the bookings were never checked against what the vehicles actually did.

The question to put to any vendor: can you tell me the difference between a booked hour and a driven hour? If the answer is no, you're buying a calendar.

Booked hours versus driven hours

This is the number worth chasing, and it's the one nobody calculates.

Say a car is available 45 hours a week. It's booked for 27 of them. That's 60% booked utilisation, which reads like a well-used asset and would survive any budget review.

Check the GPS and the thing moved during 14 hours. Actual utilisation is 31%.

That 29-point gap is cancelled trips, over-generous bookings and reservations nobody released. Two reasons it matters:

It's free capacity. Closing the gap costs nothing — it just needs unused bookings dropped back into the pool, which a GPS-linked system can do on its own.

And it changes the maths on fleet size. You don't size a pool on average utilisation, you size it on peak concurrent demand plus a buffer. If 20 vehicles run at 22% actual utilisation and never have more than 11 out at once, 13 or 14 vehicles will probably do it. Whether you'd want to run that tight depends on your geography and your appetite for a bad Tuesday. But it's now a decision rather than a guess.

Two practical notes. Measure utilisation against core hours on weekdays, not against 168 hours a week — a pool car that's idle at 2am isn't underused, it's parked. And give it a full quarter before you act on it. Two weeks over the school holidays will tell you nothing useful.

Our pool vehicle booking system reports booked and actual hours side by side per vehicle, rolls it up per vehicle group for right-sizing, and tracks peak simultaneous bookings so you can see your real headroom.

Who drove it, though

A booking tells you who reserved the car. It doesn't tell you who drove it, and in a shared fleet those are different people surprisingly often — the EA books it, the keys get handed over at the last minute, someone swaps at the depot.

Driver ID hardware, usually a button or fob tapped at the start of the trip, ties the trip to a person. That matters when an infringement arrives with a nomination deadline, when there's damage nobody's owning, when finance wants the cost coded to the right department, or when travel time is going on a timesheet. It's built into our car pool management platform rather than sold as a separate module.

The related question people forget is whether the person tapping the fob is currently licensed to drive. In a pool, nobody is checking that at the key cabinet. It needs to sit against the user record and be reportable.

Pool cars and FBT

Shared vehicles are one of the more common areas where fleet operators and their accountants end up disagreeing, and it's almost always about records.

In broad terms, fringe benefit tax can bite where a vehicle is available for private use — availability, not actual use, is the trigger. Organisations typically manage pool car exposure with a written restriction on private use, genuine overnight storage at the workplace, and evidence that the restriction is real.

A PVBS produces that evidence as a by-product: bookings, trip times, where the vehicle went, who had it, where it slept. The specific thing to look for is whether the system can isolate bookings that cross a night and record why, rather than making you filter a year of trips by hand every quarter. It won't determine your FBT position and none of this is tax advice — check it with your accountant or against current Inland Revenue guidance. But if the position is ever questioned, you're pulling a report rather than reconstructing a year from memory.

What you should be able to report on

This is where booking platforms differ most, and it's the hardest part to assess from a demo. A sales walkthrough will show you the booking screen, because the booking screen is easy. The reporting is what you'll live with.

As a benchmark, here's the reporting we run in Argus Car Pool Management and the question each one answers:

Whether or not you end up with us, use that as a checklist. If a vendor can't produce something close to each line, work out which question you're willing to keep guessing at.

The ride sharing one is worth a specific mention because it's the least obvious. If two staff travel to the same site in one car, that's a trip you didn't have to run — but only if the system records the passengers and codes them properly. Otherwise carpooling makes your utilisation numbers look worse, not better, and you've quietly disincentivised the thing you wanted.

Who this is for

Any organisation where more than one person shares a vehicle. That's the whole answer.

It shows up most visibly in councils, health providers, government departments, utilities, universities, engineering consultancies and construction firms with multiple sites — they tend to have the largest pools and the most people needing them. But a ten-person surveying firm with three utes and a Corolla has exactly the same problem in miniature, and usually less admin time to throw at it.

The thing that determines whether you need one isn't fleet size. It's the ratio of drivers to vehicles. Eight cars shared by ninety staff is a harder problem than thirty cars shared by thirty-five.

When you don't need one

Not everyone does.

If you've got three or four cars at one site, a small group of regulars who all know each other, and there's never a fight over a vehicle, keep the whiteboard. It works.

You've outgrown it when staff start expensing mileage or renting while pool cars sit idle, when you can't defend a fleet size number, when vehicles move between sites or departments, when nobody can name the driver of a three-week-old trip, or when someone is losing hours a week to running the booking sheet.

If two or three of those landed, it's worth seeing what pool booking looks like set up properly.

Who else offers this in New Zealand

A handful of providers offer pool booking here. Smartrak and FleetWise both run dedicated booking platforms. Teletrac Navman and EROAD approach fleet from the telematics and compliance side. Geotab supports pool booking through third-party add-ins on its marketplace. And if your vehicles are leased, your leasing provider may already bundle a booking tool into the platform you're paying for, so ask before you buy anything.

Rather than take anyone's word on how they stack up, these are the questions worth asking every vendor on your list, including us:

• Is the price published, or do you have to book a call to find out?

• Can you buy booking on its own, or does it require their tracking hardware in your vehicles?

• Is the GPS link native to the platform, or a third-party integration you'll end up supporting yourself?

• Can staff book from a phone, or is it a desktop portal?

• Can it show booked hours against hours actually driven?

• Can it report peak concurrent demand, not just averages?

• Does it track driver licence status and vehicle compliance alongside bookings?

• When was the interface last rebuilt?

• What happens to your booking and trip history if you leave?

Run that list across the market and the answers separate the field pretty quickly.

What ours costs

Argus Car Pool Management is $5 per vehicle per month, excluding GST.

You don't need an Argus Tracking account to use it. It works as a standalone booking system, so if your vehicles are tracked by someone else, or not tracked at all, you can still run it.

Being straight about the trade-off: without GPS, you get bookings, allocation, approvals and utilisation based on what people booked. You don't get the booked-versus-driven comparison, because nothing is confirming the trip. That comparison is the most valuable number in this article, and it needs telematics to exist. If your vehicles are already on Argus, the two link up and you get the lot. If they're not, the booking system still does the job it says on the tin, and you can add tracking later if the utilisation question becomes pressing.

Per-vehicle pricing rather than per-user is deliberate, incidentally. Charging per user penalises you for giving more staff access to shared cars, which is the opposite of what a pool is for.

Two other things we'd point at from that checklist above: the price is on the website, and the GPS integration is native rather than bolted on through a third party. Both are easy to verify and neither is universal in this market.

Questions people ask

What does PVBS stand for? Pool vehicle booking system. It's software for reserving, allocating and tracking shared organisational vehicles.

What's the difference between a PVBS and car pool management? A PVBS handles bookings and allocation. Car pool management covers that plus utilisation analysis, fleet right-sizing, driver identification, cost allocation and compliance records. Booking is one component of car pool management, not a replacement for it.

Do I need GPS tracking to use a pool vehicle booking system? No. A PVBS runs standalone for bookings, allocation and approvals. GPS adds automatic booking close-off, live availability, and the ability to compare booked hours against hours actually driven.

How much does a PVBS cost? Argus Car Pool Management is $5 per vehicle per month, excluding GST. Other providers commonly bundle booking into a wider fleet or telematics contract rather than publishing a standalone rate, so ask for the per-vehicle figure and confirm whether it's GST inclusive before comparing.

Can a booking system reduce my fleet size? Indirectly. It gives you the peak concurrency and actual usage figures to make the case, or to prove the fleet is already right-sized. The data does the work, not the software.

Does a PVBS help with FBT? It produces the records — bookings, trip data, driver attribution, overnight location — that support a pool vehicle FBT position. It doesn't determine the position. Talk to your accountant.

What reports should a pool vehicle booking system produce? At minimum: booking activity with booked versus actual hours, per-vehicle and per-group utilisation, peak concurrent use for right-sizing, late cancellations, overnight bookings for FBT, cost allocation, and driver licence and vehicle compliance status. Booking screens are easy to build; reporting is where platforms differ.

Can staff book from a phone? Yes, on most current platforms including ours. It matters more than it sounds for field staff who need to extend or release a booking without getting back to a desk.

A booking system tidies up your calendar. Connecting it to what the vehicles actually did is what answers the question you'll get asked at budget time.

Argus Car Pool Management — $5 per vehicle per month +GST, no Argus Tracking account required.