Insights

The work between two bookings

Between two bookings sits the work that decides availability. How Lanterne turns it into tasks – and where the limits are.

Roland Kainbacher – Porträt Roland Kainbacher 6 min
Illustration: Statistiken und Kennzahlen im Dashboard

One booking ends, the next begins. In between sits the work nobody puts on a website: the car is dirty inside, the charge won't cover the next trip, someone reported a chipped windscreen, and one station suddenly holds four vehicles instead of two. With five cars, somebody keeps this in their head. With fifty, it lives in a WhatsApp group, and half of it is lost at the change of shift.

Why operations is the hard part

A booking platform knows exactly what state a vehicle is in: charge, mileage, location, reported faults. What it does not answer is the next question – who drives out today, with what job, and can it be done before the next booking?

In most operations that question gets answered on the side. In the group chat, in the inbox, in the head of whoever has been there longest. It works for a surprisingly long time and then fails at a predictable point: when several people work in shifts, when external service partners are involved, or when someone goes on holiday.

The damage is rarely dramatic. It consists of vehicles standing idle half a day longer than necessary, and of trips to cars where there was nothing to do.

What Lanterne does

Lanterne is a platform for exactly that part – operations, not booking. The company is based in London and describes itself as "intelligent fleet operations you can manage on the go".

Lanterne watches the systems that are running anyway and works out from them where something needs doing. That turns into tasks: created, sorted by urgency and assigned to the right person. The team gets an alert instead of having to go and look.

On top of that come the operational figures nobody usually keeps: availability, utilisation and – the most revealing one – how long it takes from a problem appearing to it being resolved. That single number says more about a fleet operation than most others.

Two things matter enough to Lanterne that they say them explicitly. First, decisions stay with people: the system suggests and reminds, it does not act on its own. Second, nothing is meant to be replaced – Lanterne sits on top of the tools already in use, from telematics through the booking platform to the WhatsApp group where the cleaner can be reached.

What changes day to day

  • Tasks survive the change of shift. What needs doing isn't in a message that scrolls away, but in one place the next shift actually looks at.
  • Targeted trips instead of inspection rounds. The team drives to vehicles where something was actually reported.
  • Urgent things first. A car booked in two hours is treated differently from one that is due at the weekend.
  • One figure for operations. How long a problem stays open on average can be tracked – and with it, whether a change to the process achieved anything.

Working with Zemtu

Zemtu and Lanterne have been working together since 2024. Lanterne connects directly to Zemtu, so the state of the fleet and the booking situation feed into operations without a detour. For operators that mainly means: no second system to maintain, and no change to what already runs today.

The division of labour is clear. Zemtu holds vehicles, users, rates, bookings and billing – all described under Administration. Lanterne starts where that data turns into work, and organises it. Lanterne is listed with the other connected services on the Integrations and API page.

What Lanterne does not do

An honest assessment belongs here. Lanterne cleans no car and charges no battery. It makes sure the right person knows at the right time what is due – the work itself stays undone if there is nobody to do it. A tool does not make up for a team that is too thin, it only makes the bottleneck visible.

It also replaces neither a booking system nor fleet management. And it depends on usable data: what no vehicle and no person reports, no system can detect either. If you have no reliable feedback on the state of your vehicles today, solve that problem first.

Who it pays off for

The threshold sits where operations stop fitting into one person's head. With a handful of vehicles at one location a list is enough, and every extra system costs more time than it saves.

It gets interesting at a few dozen vehicles across several locations, especially when several people work in shifts or external service partners are involved. At that point the bottleneck is no longer the technology but the coordination – and that is exactly where Lanterne comes in.