Date Published

"Who drove the pool car on 14 March?" Public sector and university fleets without the logbook at reception

Imagine you work in town hall, it is Thursday morning. An auditor asks a simple question: who drove the car on 14 March, and why? The answer is in the logbook at reception. Or it would be, if someone hadn't torn out the page.

Why a shared calendar isn't enough

Cars are shared by several departments, buildings or faculties. Each has its own rules, budget and approvers, and every trip has to be traceable a year later. The usual setup looks like this:

  • bookings go through a logbook, email or calendar,
  • keys hang at reception with no record,
  • nobody checked the driving licence,
  • departments "borrow" cars outside the rules.

Then during an audit you spend a whole afternoon hunting for one signature.

Questions every pool fleet manager gets asked

Who can book a car?

  • Only the people you allow, by role, department, building or campus. Employees request a car through a portal and upload their driving licence.

Who approves it?

  • You set approvals to match your own rules. The fleet manager only handles exceptions.

How does handover work?

  • The employee scans a QR code or plate, checks the car's condition, signs and records mileage and fuel from a phone.

What if someone brings the car back late?

  • The system sends a return reminder and alerts the fleet manager once a time limit is exceeded.

Who drove on 14 March?

  • Every event is logged with time, user and action, so the auditor gets an answer in seconds.

One trip in 4 steps

  1. The employee asks for a car, and permissions and approvals apply automatically.
  2. At pick-up they scan a code, confirm the car's condition, sign and go.
  3. During the trip you see status and mileage and get alerts for time limits.
  4. At return, condition, fuel and mileage are recorded. History and reports update automatically.

Data security

For public institutions this is often the first question. Camasys states TLS 1.2+ encryption in transit and AES-256 at rest, automated encrypted backups across multiple regions, WAF/DDoS protection and continuous monitoring. Each person sees data according to their role and location, and sensitive actions can require approval.

Management gets the same rules for every department, fewer emails about keys, and better use of the cars it already has.

How to start

  1. Start with one department and 5 to 10 cars.
  2. Set up approvals and booking rules.
  3. Retire the reception logbook only after a month of running both.

When public money is involved, it pays to have records you can defend in any audit. We'll show you Camasys for fleet owners in a demo.

Share

Explore

Get in touch to see how we can help

Book a demo