Most dealer mobile service programs are reviewed quarterly, usually when someone in a management meeting asks whether the van is still worth keeping. By that point the review is a verdict rather than a correction, and three months of fixable problems have already compounded.
The fix is not a bigger report. It is four numbers, checked on the same day every week, by the person who can actually act on them.
Here is what to watch, what each number tells you, and what to do when it moves the wrong way.
This is the throughput number, and it is the one most directly tied to whether the asset pays for itself. Count completed repair orders, not appointments booked and not stops made. A stop that did not produce an RO consumed the same fuel, the same time and the same technician.
Watch it per van rather than in aggregate. A program with several vans will average its way past a single underperforming asset, and the average is the number that hides the problem you can actually fix.
When it moves the wrong way, resist the instinct to look at the technician first. In most cases the cause sits upstream in job mix or scheduling. A day loaded with appointments spread across a wide geography will produce fewer completed ROs than a day of geographically-clustered appointments, with the same technician working the same hours. Look at what was booked and where before you look at who was driving.
The share of appointments finished on the first visit, with no return trip and no handoff back into a fixed bay.
This is the quietest of the four but often the most expensive. An unfinished job consumes your capacity twice, consumes the customer's patience once, and frequently produces a service experience worse than if the customer had simply driven in. It rarely shows up in a revenue report, because the work eventually gets done somewhere.
When this number slips, the cause is almost always one of three things: the van is not equipped to finish the job that was booked, the inspection that preceded the appointment was incomplete, or the appointment was written without the parts confirmed. All three are process problems, and all three are solvable without buying anything.
There is a correlative relationship worth internalizing: first visit completion moves in the opposite direction from your return trip costs and in the same direction as customer retention. When it rises, both of those improve at once, which is why it deserves more attention than it usually gets.
Average drive time divided by completed repair orders. This is a measure of route density, not of how fast anyone drives.
Mobile service economics live or die on how much of the day is spent working versus traveling. Every minute of drive time is a minute of fully loaded technician cost producing nothing, and unlike most costs in a service department, this one is almost entirely a scheduling decision rather than a staffing one.
When it climbs, the answer is geographic clustering and real time availability. Block scheduling makes this worse by design. If you offer a customer a four hour window, you have given yourself no ability to place that appointment near the one before it, and the route fills in whatever order the bookings arrive. Real time availability lets the system offer the customer times that happen to be efficient to serve, which is how density gets built without anyone being told to hurry.
Pressure on the technician is the wrong lever here and it tends to cost you the technician.
Of the work a technician identifies and recommends in the driveway, what share comes back as a booked appointment.
This is the number that separates a mobile program that performs maintenance from one that builds a pipeline. A van puts a trained set of eyes on vehicles that have sometimes not been in your drive in a year or more. Those vehicles accumulate deferred maintenance, open recalls and wear items, and the inspection that happens during an oil change in a customer's driveway is often the first honest look that vehicle has had in a long time.
If that work is being found and not captured, the program is leaving its best economics on the table. The causes are usually mundane: the recommendation was never documented in a form the advisor could follow up on, nobody owned the follow up, or the customer was given an estimate and no appointment.
When it moves the wrong way, look at the handoff. Capture is an advisor process and a system process, not a technician one.
None of these four is the headline number. Gross profit per van is the headline, and is the product of all four. Throughput sets how many repair orders you get. First visit completion determines how many of those cost you a second trip. Drive time determines how much of the day was available to produce them. Capture rate determines what the next month looks like.
That is precisely why you watch the inputs weekly and the output quarterly. Gross profit per van tells you whether the program worked. These four tell you why, and early enough to change it.
Pick a day. Monday works because the week is still shapeable. Put the four numbers on one page, per van, with last week beside this week. Give the review to the fixed ops director because the decisions that move these numbers are scheduling and process decisions and they belong to the person who runs the department.
Spiffy is twelve years and four million services into running mobile service and the pattern we see is consistent. The dealers whose programs work are not the ones with better technicians or newer vans. They are the ones who looked at the operating numbers early enough to fix what the numbers were telling them.
How often should a dealer review mobile service performance?
Weekly for the operating numbers, quarterly for profitability. The four numbers in this article are inputs and they can be corrected inside a week. Gross profit per van is an outcome and it needs a longer window to read accurately. Reviewing only the outcome is what turns a fixable problem into a decision about whether to keep the asset.
Who should own the weekly review?
The fixed ops director. Every lever that moves these four numbers is a scheduling, routing or process decision inside the service department. Routing the review through accounting produces a report nobody can act on.
What if we only have one van?
The four numbers matter more with one van, not less. A single asset has no fleet average to hide behind, which makes the weekly read cleaner. It also means every scheduling decision is visible in the next week's numbers, so corrections show up fast.