How do fleets track vehicles once they enter a repair shop?

A fleet can see a vehicle in perfect detail right up to the moment it needs work. Location, mileage, fault codes, driver behavior — all of it arrives on its own. The vehicle goes into a shop and that stream keeps reporting a stationary vehicle at a fixed address, which is true and useless.

What the fleet needs now is not vehicle data. It is repair data: what stage the job is at, who is waiting on what, what has been approved, and when the vehicle is coming back. None of that is generated by the vehicle. All of it is generated by the shop.

Why does a fleet lose sight of a vehicle at the shop door?

Because the two systems that know the most about the vehicle are not the same system, and the handover between them is a phone call.

Telematics reads the vehicle through installed hardware. It is very good at that and it is the wrong instrument for this: a vehicle waiting three days on a part and a vehicle being actively worked on look identical to a GPS unit. That boundary is not a gap in any one product — it is what the category is. We set it out in detail in FleetOS vs Samsara, which compares a telematics system and a repair-coordination one on exactly this point.

Meanwhile the shop knows everything. It knows the job is waiting on an alternator, that the alternator is two days out, and that the technician who had it is now on something else. That knowledge sits in the shop's management system, or on a whiteboard, and the only route from there to the fleet is a service advisor with a phone.

So the fleet's visibility is not partial. It is intermittent: it exists for the length of a phone call and then stops. For a fleet with vehicles at several shops at once, that means the true state of a meaningful part of the fleet is unknown most of the time, and knowable only by asking.

How do fleets track vehicles in shops today?

Five methods, and most fleets run two or three of them at once.

The first four all share one failure. They report the vehicle, or they report what somebody remembered to write down. None of them is fed by the work as it happens, which means none of them changes when the job changes — and a status that does not change on its own is a status somebody has to chase.

What should a fleet track for a vehicle in a shop?

Six fields answer almost every question a fleet actually has:

• Stage — diagnosing, awaiting approval, awaiting parts, in progress, ready. Not a percentage, a named stage.
• Who the job is waiting on — the shop, the fleet, or a supplier. This is the single most useful field, and the one that is almost never recorded.
• Days in the current stage — not days since drop-off. A job three days into "awaiting approval" is a different problem from one three days into "in progress".
• Quoted versus approved cost — so an approval that has not happened is visible as a number, not just a status.
• Current promised return date, and every previous one — the history is the signal. A date that has moved twice will move again.
• Parts ETA where parts are the blocker — the shop usually knows this and is rarely asked for it.

The second and third of those are the ones that change how a fleet behaves. "Waiting on the fleet" for two days is a problem the fleet can solve this afternoon, and it stays invisible on every dashboard that only records where a vehicle is. How fleets measure maintenance performance makes the wider case for measuring duration rather than counts.

Why is "when is it coming back?" so hard to answer?

Because the return date depends almost entirely on waiting, and waiting is the part nobody is tracking.

The labor hours on a repair are the one number everybody has, and they are a poor predictor of the return date: a job with four hours of work in it can hold a vehicle for a week. The gap is made of an estimate sitting unapproved, a part ordered a day later than it could have been, and a job that lost its slot in the bay schedule and has to be fitted back in. We take that apart in why repairs take longer than the work.

Two of those three have specific, well-understood causes worth reading on their own: the hidden cost of manual repair authorization and why parts delays cost more than parts.

A promised return date that comes from the shop's honest guess, asked for once at drop-off, is a guess about the wrench time. A return date that moves when the job moves is a different instrument, and it is only possible if the job's stage changes are reaching the fleet as they happen.

What does the visibility gap cost?

It costs the days that could have been recovered, priced at whatever a vehicle off the road costs the fleet per day.

The costly part is rarely the repair being slow. It is the fleet finding out late — the approval that sat for two days because nobody knew it was waiting, the replacement vehicle hired for a week when the job needed three days, the route planned around a van that was actually ready. What vehicle downtime costs a fleet works the figure through, and the fleet downtime cost calculator puts your own numbers into it.

How do you get status out of shops you don't own?

By making the update part of the work rather than a favor asked afterwards, and by not requiring the shop to adopt anything.

This is the part fleets usually assume is impossible, because the obvious version of it is. Asking twenty independent shops to buy software, learn it and keep it current for one customer is not a project that finishes. Asking them to log into a portal to update a job they have already written up in their own system is asking them to do the work twice.

The workable version inverts it. The fleet directs the work, so the fleet sends the work order — and it arrives as a link, by SMS or email. The shop opens it, updates the status, uploads photos and answers approvals from that link. No signup, no install, nothing to learn, and it works with the shops a fleet already uses rather than a network it has to move to. Shops that want more can switch on ShopOS free and run their whole business on it, but the work flows either way.

That is why status arrives at all: updating the link is how the shop tells the fleet the job is ready, so the record and the message are the same act. How independent shops win more fleet business covers that shared record from the shop's side, and why a shop takes the arrangement.

How to set this up with your existing shops

1. 1List the shops you actually use, ranked by volume. The top handful will cover most of your repair days.
2. 2Pick the stages you want reported, and keep it to the six fields above. A fleet that asks for twelve gets three.
3. 3Send the next job to your highest-volume shop through the system rather than by phone, and let the link do the introduction.
4. 4Set your approval rules before you need them, so an estimate arriving at 6pm is not waiting until the morning.
5. 5After a month, look at days-in-stage rather than total days. That is where the recoverable time is, and which side it sits on.

For the wider category this sits in — what fleet maintenance software does, what it costs, and how the maintenance-only tools differ from the telematics ones — start with what fleet maintenance management software is.

The short version

A vehicle in a shop is not a tracking problem, it is a reporting one. The information exists and it is in the shop's hands, so the question is not how to observe the vehicle more closely but how to get the shop's own updates into the fleet's system without asking the shop to do the work twice. Do that and the return date stops being a guess.

Key facts

• Telematics reports the vehicle, not the repair — a vehicle waiting on a part and one being worked on look the same to it.
• The information a fleet needs is generated by the shop, so it has to travel from the shop's system to the fleet's.
• Six fields cover it: stage, who the job waits on, days in stage, quoted versus approved cost, return date history, parts ETA.
• "Waiting on the fleet" is the most useful status there is and the one least often recorded.
• A work order sent as a link needs no signup or install from the shop, which is what makes updates arrive at all.