Fleet Analytics: See Drops Done, Fails, and Who Ran

When you just need the numbers, not a dashboard degree

You finished the week and someone asks: how many drops actually got done? Who was on the road? How many stops failed? If you're running a fleet, you know the feeling — you have a rough sense, but no quick way to prove it without chasing drivers or digging through texts.

That's the problem Analytics solves. It's a simple scoreboard for the last few days, not a full business-intelligence suite. It shows what got delivered, what failed, and which phones were actually running.

This article walks through what you'll see, how to use it, and how to turn those numbers into a quick conversation with your team.

What Analytics actually shows

Analytics sits inside your fleet login. Open it, pick a window — 7, 14, or 30 days — and you get four summary cards plus a table.

The cards are:

• Drops done — stops marked Done in the driver app.
• Failed — stops marked Failed in the driver app.
• Phones that ran — devices that actually ran at least one route in that window.
• Active seats — phones currently approved and active on your account.

Below the cards is a per-phone table. Each row is a phone, and you can see who is finishing the most stops, who is failing the most, and who barely ran at all.

That's it. No charts you have to interpret, no drill-downs you'll never use. Just the numbers a fleet controller needs at the end of a shift or the start of a Monday.

How it works — in plain terms

Every time a driver marks a stop Done or Failed in the app, that action is recorded. Analytics counts those actions and groups them by phone over the period you choose.

A few honest notes about the counts:

• They only include stops marked after Analytics was turned on for your fleet. Older routes won't appear.
• API usage (if you use planning API keys) also shows up in the summary when it's present.
• For live vans on the map, use Overview or the live map. Analytics is history, not live GPS.

So think of Analytics as the scoreboard after the game, not the play-by-play during it.

Step-by-step: your first look at the scoreboard

1. Open your fleet login and go to Analytics.
2. Choose 7, 14, or 30 days. Start with 7 if you want a recent picture; go to 30 if you're reviewing a month.
3. Read the four cards. Drops done and Failed give you the headline. Phones that ran tells you how many devices were actually used. Active seats tells you what you're paying for.
4. Scroll to the per-phone table. Sort by drops done or by failed stops to spot patterns.
5. If something looks off — a phone with zero runs, or a spike in fails — check the driver's run sheet or give them a quick call.

That's the whole workflow. It takes about a minute.

What the driver sees vs what the office sees

The driver sees their run: a numbered list of stops, the next address, and buttons to mark each stop Done or Failed. That's their whole world during a shift.

The office sees the rolled-up picture: total drops done, total fails, and which phones contributed. You don't see the driver's screen, and they don't see the scoreboard. Each side gets what they need.

This split matters because it keeps the driver focused on the road while giving the controller the numbers without interrupting anyone.

Worked example: Monday morning review

It's Monday. You open Analytics and pick 7 days.

• Drops done: 412
• Failed: 18
• Phones that ran: 6
• Active seats: 8

The per-phone table shows one phone with 3 runs and 9 failed stops. Another phone ran every day and finished 96 stops with zero fails.

Before Analytics, you might have guessed the quiet phone was just doing short runs. Now you can see it barely ran, and when it did, a third of its stops failed. That's a conversation worth having — maybe the driver needs help with the app, or maybe that seat doesn't need to be active.

You also notice two active seats that never ran. If they stay unused, you can remove them and stop paying for seats you don't need. That's fleet pricing per driver working in your favour.

After the conversation and a quick seat cleanup, next week's numbers look different: fewer fails, fewer idle seats, and a clearer picture of who's carrying the load.

What about live tracking?

Analytics is history. If you want to see vans moving right now, use the live map in Overview. That shows current positions, not past counts.

Both have their place: live map for today's dispatch, Analytics for the week's review.

FAQ

How far back does Analytics go?

You can pick 7, 14, or 30 days. Counts start from when the feature was turned on for your fleet, so the earliest days may be incomplete if you've just enabled it.

Do failed stops count against the driver?

They count as failed stops, full stop. Whether that's a performance issue or a one-off is a conversation for you and the driver. Analytics just gives you the number.

Can I see which stops failed, not just how many?

Analytics shows counts per phone. For the specific stops, you'd look at the driver's run or ask them directly. The scoreboard tells you where to look.

Does API usage show up?

Yes, if you use planning API keys, API usage appears in the summary when present. It's a separate line, not mixed into the stop counts.

Where to go next

If you want the full walkthrough with screenshots, the in-product guide is here: Analytics guide.

To see how fleet pricing works — including the cost per extra phone — head to pricing. And if you're still deciding whether StopSorted fits your operation, how it works gives you the plain-language version.

Analytics won't replace your judgement. But it will save you a few phone calls and give you a straight answer when someone asks how the week went.