You can't fit hardware to a vehicle you don't own, so cover the driver instead. A smartphone-based system runs on the device the driver already carries, which means subcontracted, leased, gig and motorcycle drivers get the same real-time protection as your owned fleet — with nothing installed and nothing to remove when the contract ends.
The part of the fleet nobody reports on
Ask an operations director how their safety programme is performing and you'll get numbers about the fitted fleet. Ask what percentage of the miles driven under their brand happens in a fitted vehicle, and the conversation changes.
In most logistics networks and every mobility platform, a large share of the moving vehicles are not owned by the company whose name is on the parcel or the app. They are subcontractors, owner-drivers, short-term leases, gig drivers in their own cars, and riders on their own motorcycles. None of them have a camera, because:
- You can't drill into a vehicle you don't own.
- A short lease never amortises the device or the fitting cost.
- A gig driver did not agree to hardware in their personal car, and won't.
- There is nowhere on a motorcycle to fit a cab camera.
- The subcontractor churns before the installation would pay back.
So the safety programme covers the vehicles that were easy to cover. The uncovered group tends to be the one with the least oversight, the least coaching, the most schedule pressure and the highest turnover — which is to say, the group where risk actually concentrates.
Why this is getting more expensive, not less
Two things are converging. Regulators and insurers increasingly look at the operation rather than the asset: who was driving, under whose instruction, on whose schedule. And customers increasingly ask about the whole chain, not just the trucks with your livery on them.
"They were a subcontractor" is a weaker answer every year. If a driver is moving your freight or your passengers, the exposure attaches to you in reputation long before it attaches in law.
Cover the driver, not the vehicle
The change that makes this tractable is simple: stop treating coverage as a property of the vehicle.
Every one of those drivers carries a smartphone. It's already in the vehicle, mounted, running navigation and your dispatch app. A driver-safety system that runs on that phone reaches all of them at once, with no fitting, no ownership question and no asset to recover.
In practice a rollout looks like this:
- Count the gap first. Take total drivers moving under your brand, subtract drivers in fitted vehicles. That number is the business case, and it's usually bigger than expected.
- Put it in the contract. For subcontractors, safety-system participation belongs in the service agreement alongside insurance and licensing, not in a request after the fact.
- Give the driver something. Real-time alerts that keep them safe, rewards for driving well, and explicit control over what is shared. Coverage you impose gets circumvented; coverage that helps gets used.
- Be precise about privacy. State plainly that nothing records continuously, that audio is never captured, that in-cabin capture is triggered by the driver, and that data can be deleted on request. Then hold to it.
- Pair it with an incentive. Adoption is strongest where safe driving is tied to something the driver values — bonuses, preferred allocation, insurance treatment.
- Measure the uncovered group separately. The first weeks are where the surprises are. In our deployments, operators consistently find dangerous behaviour they had no visibility on at all — around two events per mile in the early weeks — and it drops quickly once drivers start getting alerts.
- Subcontracted, leased and gig vehicles are covered on day one.
- Motorcycles and three-wheelers stop being a blind spot.
- Onboarding a new subcontractor is a download, not an installation booking.
- Offboarding leaves no hardware to recover and no stranded asset.
- Seasonal peaks scale up and back down without capital expenditure.
The two objections you'll get
"Subcontractors won't accept it." Some won't, and that's information. Most will, if it's a contract condition rather than a favour, if it's the same requirement for everyone, and if the driver gets alerts and rewards rather than just being watched. The operators who struggle are the ones who introduce it as monitoring.
"It's their personal phone." Correct, which is why the data model matters more here than anywhere else. A system where the driver decides what is shared, that works with nothing shared at all, and where deletion is a right, is a very different proposition from one that quietly uploads everything. More on how we handle that on the Trust & data page.
Questions people ask about this
How do you monitor drivers in vehicles you don't own?
You monitor the driver rather than the vehicle. A smartphone app runs on the device the driver already carries, so it works regardless of who owns the van, the truck or the car. Nothing is fitted, so there is nothing to negotiate with the vehicle's owner.
Will subcontractors agree to it?
It's a commercial conversation, not a technical one. It lands best when it's written into the contract as a condition of work, when the driver gets something back — real-time alerts, rewards, control over what is shared — and when it's explicit that nothing records continuously and no audio is ever captured.
What about data protection when the driver owns the phone?
This is the part to get right. With WingDriver the driver controls what is shared, and the product still functions with nothing shared at all. In-cabin capture is triggered by the driver, never automatic. Any driver can request deletion of all their data. Set the sharing policy before rollout and put it in writing.
Does it work on motorcycles and three-wheelers?
Yes. The phone goes in a standard motorcycle mount and the system runs the same way. This is a segment that fitted cab hardware cannot serve at all.