Onboarding a valeting supplier without disrupting a single shift comes down to four steps, and none of them require a vehicle to leave its bay: add the fleet, sign in by magic link, book the first service, then let condition data accumulate from visit two. There is no software to install, no password to remember, and no multi-year commitment to sign before the first car is cleaned.
What onboarding a valeting supplier actually looks like
The Fleet Insight Platform reduces the whole onboarding sequence to four steps, each designed to sit around a working fleet rather than interrupt it:
- Add the fleet — the fleet is created with a slug and a manager email. No uploads, no CSV mapping, no vehicle specification sheet to chase.
- Sign in by magic link — the manager opens the dashboard from a link. No password, no app install, no IT ticket.
- Book the first service — the first visit is scheduled from the portal at pre-approved pricing, so procurement sees the number before the car is touched.
- Read the data from visit two — post-visit condition records populate the platform and start to trend, so the picture grows without any extra effort.
For a fleet manager who is defending a budget rather than buying a service, the point of the sequence is that none of it needs a vehicle to stop work. The manager view is shown in full on booking/acme, a worked example of the dashboard.
Step one: add the fleet with a slug and an email
Onboarding starts with two fields: a slug for the fleet and a manager’s email address. There is no import to run, no file to clean and no legacy data to reconcile. The fleet exists as a live dashboard at /<slug>?view=manager from the moment it is created, and every module — overview, condition inspections, ROI, ESG, reports, booking, procurement and toolkit — is available from that one page.
The slug is a naming layer, not a technical dependency. A fleet of five vehicles and a fleet of 500 enter through the same door; the only variable is how many registrations sit behind the slug.
Step two: sign in with a magic link
There is no password to set and nothing to install. The manager receives a magic link, opens it and is signed into the dashboard. This matters more than it looks: a valeting supplier is competing for a share of a fleet manager’s day, and the quickest way to lose that share is to hand over a stack of credentials, an app-store approval and an IT onboarding queue before the first car is cleaned.
Because sign-in is a link rather than an account, the person who signs off on the supplier does not have to become the person who administers it. The manager can be in the portal in the same sitting in which the fleet was added.
Step three: book the first service from the portal
The first visit is booked from within the platform through a multi-vehicle wizard with pre-approved pricing. The numbers are visible before the booking is confirmed, which is the detail that matters to someone defending a budget: procurement sees the cost before the work, not after.
Payment terms are set up for a finance function — BACS, bank transfer and purchase order are all accepted — and the supplier carries £1 million in public liability with DBS-checked technicians on site. The first service is the moment the platform stops being a promise and starts being a record.
Step four: read the data from visit two
The first visit creates the baseline. The second visit starts the trend. After each service, per-vehicle condition records populate the dashboard, and the fleet-level rollup aggregates urgent and advisory counts by registration alongside vehicle history and CSV export. A manager reads that history back over time: the platform stores dated photographs for anything flagged, and the manager reviews them — it does not perform the comparison for you.
This is where the difference from a conventional supplier shows. A typical supplier leaves a receipt. This leaves a running record: what was flagged on which vehicle, whether it recurred, and how the fleet’s condition moves between visits. Downtime reduction is not achieved by cleaning faster; it is achieved by catching the advisory before it becomes the urgent, and the urgent before it becomes a vehicle off the road.
Why this maps to Downtime Reduction
The value pillar here is Downtime Reduction, and the mechanism is inspection rather than cleaning speed. A 20-point Vehicle Health Check is bundled into the Fleet Plan at no extra cost, scored per point as OK, Advisory or Urgent, and reported on the day by email, WhatsApp and the portal, with technician notes and photographs for anything flagged.
The 20 points sit across four groups — tyres and visibility, under bonnet, interior and controls, and exterior condition — and the framework aligns with BVRLA Fair Wear and Tear. That alignment turns the inspection from a checklist into evidence: when a vehicle comes back off lease with a fair-wear question, the dated condition record is the answer.
For a fleet manager, the downtime equation is straightforward to defend in a budget meeting. An advisory caught and fixed at a routine service is cheaper than an urgent discovered at the roadside or at an MOT — the platform surfaces the advisory while the vehicle is still on the road, not after it has been pulled off. That is what Downtime Reduction means in practice: fewer vehicles leaving the schedule unexpectedly.
Works at 5 vehicles or 500, with no lock-in
A pilot is available, and there is no multi-year lock-in. A fleet of five vehicles and a fleet of 500 use the same platform, the same four-step onboarding and the same condition framework; the difference is volume, not architecture.
Because the process is waterless, it is designed to avoid trade effluent from the service site — a detail that reads as an afterthought until it lands in a facilities or ESG conversation, where it removes a negotiation rather than starting one. Condition records are GDPR-compliant and exportable, so the data belongs to the fleet, not to the supplier. For procurement and compliance documentation, the Toolkit carries COSHH, RAMS and the equipment list, and common questions are answered on the fleet FAQ.
How the record compounds over time
From visit two onward, the platform does something a spreadsheet cannot: it accumulates per-vehicle history with dated photographs, technician notes and urgent/advisory counts, aggregated by registration and exportable as CSV. Nothing is entered twice and nothing is chased from a technician’s notebook.
We have watched the same advisory recur across staff car parks in Surrey and south-west London — a tyre flagged as borderline one visit and still borderline the next — which is exactly the pattern a per-vehicle record turns into an early catch instead of a roadside stop.
The same dashboard carries the ROI & Financial Impact and ESG Impact modules — driver hours saved against a £25/hour productivity value, and Scope 3 Category 1 (purchased goods and services) figures alongside litres conserved and CO2e, reported against a documented ESG method — each downloadable as PDF and emailable to finance. Operating and environmental figures are reported as planning estimates unless confirmed in writing, which is how a budget holder wants them framed: honest about the estimate, precise about the method.
The waterless system that runs the fleet is the same one behind mobile car valeting in Esher and mobile car valeting in Guildford, so the process a manager sees on the portal is the same process already run across Surrey and Greater London.
Fleet managers can map site access, compliance documents and pilot scope through a Fleet Readiness Audit.