Straight into the service manual page
WrenchQuarry
More

Fleet tracking: 5 vendor figures to check

WrenchQuarry Editorial Team · Published · 11 min read · How these guides are written

Before buying fleet tracking, check the vendor's fuel savings, satisfaction score, reclaimed hours, safety measure, and idling threshold against your own records. Some of those numbers may be accurate. But the vendor chose which number to show, which customers to count, and which definition to use. Before you sign, you need to know what each figure measures.

Vendor pages also make broad promises. Samsara's GPS tracking page says: "Monitor your fleet, adapt to changing conditions, and keep drivers on schedule with full visibility and extended tracking." That sentence sounds useful, but it gives you nothing to check. Expect to see both kinds of claim: broad promises, and a few precise figures that look like proof. This post covers five precise figures from Motive, and the questions to ask about each one.

Read each figure in three parts: what was measured, what it was measured against, and who was counted. Most of the questions below are those three parts asked in different ways.

Keep your own scope in mind. You run a small HVAC, plumbing, or electrical firm. Your trucks may make fewer stops than a delivery fleet, but your techs spend time at job sites, supply houses, and in traffic. A figure from a large fleet may not match your day. That does not make the figure false. It means you need to test it against your own records.

Gather these before the sales call: three months of fuel card statements, your truck count, a rough count of monthly jobs, and any incident or repair notes you already keep. You will use them to check each figure.

1. Fuel savings up to 13%

Motive's fleet fuel management page says: "How Motive fleet fuel management can help you save up to 13% on fuel."

The words that matter are "up to." That phrase sets a ceiling, not an average. The quote gives a maximum saving of 13%, without showing how many customers reached it. The quote does not tell you the typical result, so ask for it.

Ask three questions:

  • What is the typical saving across customers, and what share of customers reached the top figure?
  • What baseline is used? Last year's fuel for the same trucks, or a different period with different work?
  • How long did the comparison run, and did anything else change, such as new trucks, new routes, or a new fuel policy?

Then run your own numbers. Take your last three months of fuel spend, annualize it, and multiply by 13%. That is the most the vendor's top figure could be worth to you. Compare that number with the yearly cost of the subscription, hardware, and installation. If the ceiling does not clear the cost, the fuel figure cannot justify the purchase by itself, whatever the average turns out to be.

Ask where the savings data comes from, too. Some systems read fuel from the truck's engine data, others depend on fuel card records or driver entries. Ask how each source is matched to your trucks. If your techs fill up at different stations, you want to know whether the report reads that as a saving, a cost, or nothing at all.

Ask also what kind of saving you expect. Savings from less idling, shorter routes, and fewer miles driven each have a different fix. If most of the saving comes from idling, the idling questions in section 5 matter most. If it comes from routing, you need to know whether dispatch can change routes during the day.

Scale matters as well. The same Motive page quotes a customer who says: "Last year we were spending around $110k/month on fuel, and sometimes it's higher." That is a large fleet's spend. A percentage saving on that base produces large dollar figures. The same percentage on your smaller bill produces a smaller number, so the case has to be built on your own spend, not someone else's.

2. A 99% satisfaction score

The same Motive page says: "Read our customer reviews and learn why we have a 99% satisfaction score." That sentence sends you to reviews, but gives no method for calculating the score. Before you give it weight, ask:

  • Who was surveyed? All customers, or only the ones still paying?
  • How many people answered? A score based on a handful of replies and a score based on thousands of replies are different claims.
  • When was the survey run, and what exactly was asked? "Would you recommend us" and "Are you satisfied with support" can produce very different results.
  • How many customers cancelled in the last year, and were they invited to answer?

The last question matters most. Customers who leave may be missing from a satisfaction survey. A vendor can have a high score among the customers who stayed and still lose many who left. Ask for the cancellation count and the renewal rate directly. Ask the vendor to supply both alongside its survey results.

You don't have to be a survey expert to ask for the questions. A score built from a few friendly prompts can sit well above a score built from a longer list that covers billing, hardware, and support. Ask which topics were covered.

Ask for support hours and typical first-response times in writing, too. A tracking system that goes dark on a Monday morning costs dispatch time, and a satisfaction score alone cannot tell you how quickly support responds. Test support during the trial by reporting a problem on purpose and timing the reply.

Then read the reviews yourself, especially the low ones. Look on sites the vendor does not run. Pay attention to the same complaints showing up more than once: installation problems, slow support replies, driver app bugs, camera alerts that fire too often, or billing surprises. A single bad review tells you little. Three reviews from different firms naming the same problem tell you where to look during a trial.

Finally, ask for a trial on your own trucks. A satisfaction score describes other people's experience. A pilot lasting at least a full month on four or five of your vans shows what your techs will actually put up with, and whether the office will keep using the system after the novelty wears off.

3. Reclaims ~10K hours a year

Motive's sustainability page says Cascade improves safety by 50% and reclaims roughly 10K hours a year. The hours figure has a tilde in front of it, which marks it as an approximation. Ask what it is based on:

  • Is 10K hours an average for each customer, or a total across all customers? A total across many fleets says little about one fleet of ten vans.
  • Which tasks count as reclaimed time? Fewer phone calls about locations, less paperwork, automatic mileage logs, or something else?
  • What fleet size sits behind the average? Hours only mean something when calculated for each vehicle or technician.

Hours on their own do not pay bills. An hour saved matters only if it turns into something you can see. Contractor Magazine's webinar page on fleet costs makes this point for field-service businesses: "For field-service businesses, fleet performance is not just an operational issue; it directly affects technician productivity, customer response times, completed jobs and margin protection."

For a dispatcher, time saved on the phone is only worth something if the schedule stays accurate and calls get answered faster. For a technician, time saved on end-of-day paperwork only pays off if the next job starts sooner. Walk through a typical day in your shop and mark where the hours would really come from. If you cannot point to a specific task, the hours figure is not yet a benefit to your firm.

When the vendor says it saves time, ask where that time should show up: faster dispatch to calls, more completed jobs each day, or fewer missed appointments. Then check those measures during the trial. They are harder to dress up than an hours total.

Ask how the hours depend on your people. If the savings rely on drivers or dispatchers using an app, count the time they will spend learning it in the first weeks. That time comes out of the hours total before any gain shows up.

A practical test: ask the vendor to show the hours calculation for a fleet of your size, with every assumption written out. If they cannot produce it, treat the number as marketing rather than a forecast you can plan around.

4. Safety improvement of 50%

The safety claim on Motive's sustainability page needs its own check. Ask the vendor to define "safety," identify the comparison, and give the time period. Ask:

  • Which events were counted? Harsh braking, speeding, rollovers, collisions, or camera alerts?
  • Was the 50% measured against the same fleet before installation, or against a different group of drivers?
  • What were the raw counts before and after? A percentage hides the size of the base.

The raw count matters most for small fleets. A firm with four vans may have only a few incidents a year. If the count fell from two to one, the change is a 50% drop, but the sample is far too small to show that the device caused it. A bigger fleet with more events can show a steadier pattern. Ask for counts, not just percentages, and be skeptical of any safety figure built on a handful of events.

Set your own baseline before the trial starts. Pull your last year's incident, near-miss, and repair notes and write them down. Decide now how you will count near-misses during the trial. Changing the definition in the middle of a trial can make any report look better than the work actually did.

Ask whether any outside party has reviewed the safety results. A vendor's review of its own data can be useful, but it is still the vendor's review. An independent check, even a simple one against your own incident records, tells you more than a polished summary.

Think about how the system will be used, too. Driver-facing alerts can change behavior, and a driver who feels watched may respond in ways a report will not show. Talk with your crew before installation. Explain what the alerts record, who sees them, and what the firm will do with the information.

5. Idling over 2 minutes

The Motive fuel management page also defines a term: "An idling event is recognized when a vehicle is stationary with the engine running for over 2 minutes." That definition is a figure in disguise. Every idling count, every idling-minute total, and every idling-related fuel saving depends on it.

Ask also how idling appears in the dispatch view. A dispatcher should be able to tell a van parked at a supply house from one stuck in a jam without opening a separate report. If the view shows only a count, you will spend time chasing each event to find out what happened.

Consider what a 2-minute threshold does to a van. A tech who parks at a supply house, runs the air conditioning or heat while waiting for a part, and idles for several minutes before going inside may trigger an event at nearly every stop. A tech who shuts the engine off after a minute never triggers one. The same behavior can look bad or fine depending on the threshold, and the report does not show which rule produced its numbers unless you ask.

Ask these questions in writing:

  • Is the threshold fixed, or can we change it?
  • Does the report count idling events, idling minutes, or both?
  • Does the fuel saving claim use the same threshold as the idling report?
  • Does the system count engine-on time for climate control the same way it counts idling in traffic?

Compare vendors on the same definition. If one vendor counts idling at two minutes and another counts it at five, the first will report more idling, and its savings plan may look bigger for reasons unrelated to real fuel use. Ask for the threshold in writing before you compare any two reports side by side.

If you adopt an idling policy, decide what is acceptable before the trial starts. For example, decide whether a tech may run climate control while waiting for a customer to sign off on a job. Write the policy down, so the report measures a rule the crew knows about rather than a surprise.

Before the sales call

Put your questions in writing and send the same list to every vendor. Ask for the answers by email, so you can compare them later without relying on memory from a demo.

  • The typical saving, not just the best case, with the baseline and time period.
  • The survey size, survey date, cancellation count, and renewal rate.
  • The method behind the hours figure, with the fleet size it assumes.
  • The safety measure, the raw counts before and after, and the comparison group.
  • The idling threshold, and whether you can change it.
  • Benchmarks. Motive's page says it can "Compare your fleet performance against the Motive network of 700k+ vehicles." Ask which vehicles are in that group, how they are matched to yours, and whether firms of your size are represented. A comparison to very large fleets may not tell you much about four vans working one metro area.

Then run a trial on your own trucks for long enough to see a full month of fuel and at least a few service calls. Keep a short log during the trial: the date, the truck, what the vendor's report said, and what you saw in your own records. The gaps between those two are where the real questions are.

Set a decision date before the trial starts, and write down two results in advance: the result that would make you buy, and the result that would make you walk away. Vendors are easier to judge when the bar was set before the demo, not after you have seen the best slides.

Compare the trial results against your baseline, not against the vendor's figures. The vendor's numbers tell you what to ask about. Your own numbers, measured the same way before and after, are the only ones that should decide the purchase.

Related guides: 2 heat-stress figures to set before outdoor tech work · Portable ladder setup: 3 figures to check before dispatch · Retainage figures: 3 checks before subcontractor pay.

Sources

More field guides