Industries/ Logistics/ Operations and fleet dashboards
See late and failed drops during the shift, not at month end
One set of numbers for the traffic office wallboard, the depot manager's phone and the directors' weekly review: drops completed, running late and failed, on-time performance by customer, route and depot, and how hard each vehicle is working. Each figure is defined once, so meetings argue about the operation rather than the spreadsheet.

- Used by
- Traffic office, depot managers, account managers and directors
- Takes the place of
- The ops whiteboard, month-end spreadsheets and ringing round depots
- Connects to
- Your transport system, driver app, telematics and accounts
- Built with
- Our live dashboards service
Where it hurts today
A normal week, before it exists
In many firms the operation lives on a whiteboard in the traffic office and in the planner's head. Anyone not standing in that room has to ring someone to find out how the day is going: the depot manager at the other site, the account manager with an anxious customer, the director on the motorway. Each call interrupts the person who is busiest solving the very problem being asked about.
The numbers that do exist arrive late and disagree. On-time performance comes from a spreadsheet someone builds at month end, from exports out of the transport system, with their own idea of what late means. The depot counts a drop as on time if it arrived on the right day. The customer counts it against a two-hour window. By the time the figure reaches a meeting, the week it describes is long gone.
Meanwhile the useful questions go unanswered. Which customers' drops fail most, and why? Which routes run late every Friday? Which vehicles sit in the yard while the firm hires in? A key account review turns into a scramble to prove performance with figures nobody fully trusts, and the recurring problems stay anecdotes, because nobody is counting them the same way twice.
What it does
Operations and fleet dashboards, feature by feature
What the dashboards show and who sees what, built around the decisions people make during a shift and across a month.
- 01
A live wallboard for the shift
A wallboard for the traffic office showing drops planned, completed, running late and failed, by depot and by run, updated as drivers' phones sync. Late runs rise to the top, so the planner can see which van is behind before the customer rings.
- 02
Failed drops counted by reason
Every failed delivery is counted against the reason the driver chose: closed, refused, no booking, access, damaged. Across a month this shows which customers, sites and routes cause the most redeliveries, so a conversation with a customer starts from their own record rather than an impression.
- 03
OTIF defined per customer
We agree with you, in writing, what on time means for each customer: same day, within a booked window, or before a timed deadline. Each customer is measured against their own terms, so the figure in a key account review is one the customer would recognise.
- 04
Fleet utilisation by vehicle and depot
Vehicles and trailers shown by days used, hours out, drops per run and time off the road, drawn from the transport system and from telematics where you have it. Units that sit idle while you hire in, or go back to the workshop week after week, become easy to spot.
- 05
The right slice for each person
A depot manager sees their depot, an account manager sees their customers, and directors see everything with a weekly trend. Drivers' names appear only where someone has a reason to see them, and customers can be shown their own figures in the portal if you choose.
- 06
It says when it is stale
Each panel shows when its data last updated. If a feed from the transport system or driver app stops, the panel is marked stale and someone is alerted, rather than yesterday's numbers sitting on the wallboard looking like today's.
A day with it
How the day runs instead
A normal day and week in a two-depot operation, with the wallboard on and the phone views in use.
- 6.30amTransport planner
The planner checks the wallboard as the first vans leave. Every run is loaded, one van is still in the yard waiting for a driver, and the night trunk reached the south depot late. They move two timed drops onto another run before the morning starts to slip.
- 11.00amDepot manager
On their phone in the yard, the depot manager sees three failed drops at the same retail park, all marked 'no booking'. They call the site's goods-in manager once and agree a booking routine, rather than finding the pattern at month end.
- 2.30pmAccount manager
A key account rings about a missed window. The account manager opens that customer's view, sees two drops running late on a single run held up at the docks, and gives the customer a revised time before they have to ask for one.
- MondayOperations manager
At the weekly meeting the operations manager puts last week's trend on screen: on-time performance by customer, failed drops by reason, and vehicles that sat idle. The discussion goes straight to the two routes that ran late every Friday.
- Month endDirectors
The directors' pack draws on the same numbers the traffic office used all month. Nobody spends two days reconciling exports, and the figure shown to a key customer is the one their account manager has been watching all along.
What it connects to
Works with what you already run
The dashboards are only as good as the data behind them, so we start with where each number comes from.
Transport management system
Runs, drops, delivery windows and customers come from your transport system, through its API where it has one or scheduled exports where it does not, loaded on a schedule we agree with you.
Driver app
Completed and failed drops, reason codes and arrival times come from the driver app as phones sync, which gives the wallboard the freshest picture of the shift.
Telematics and vehicle trackers
Vehicle hours, mileage and time parked can come from your trackers or telematics provider where it offers an API or a data export, so utilisation reflects what the vehicles actually did.
Accounts software
Revenue and cost by customer or route can be added from your accounts package later, so the same dashboard shows whether busy work is also profitable work.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- A traffic office wallboard showing today's drops planned, done, late and failed
- Failed drops counted by reason, by customer and by delivery site
- On-time performance by customer, measured against each customer's own terms
- A phone view for each depot manager showing their own depot
- Stale data marked clearly, with an alert when a feed stops
Once it is in use
- Vehicle and trailer utilisation drawn from telematics, by unit and by depot
- A weekly trend pack for directors and key account reviews
- Performance figures shown to each customer inside the tracking portal
- Revenue and cost per customer and route from the accounts package
Buyer's guide
Before you commission one
Four decisions worth making before you commission logistics dashboards.
- 01
TMS reports, a BI tool or custom
Start with the reports in your TMS and any business intelligence tool you already pay for. If they answer your questions, improve them rather than add another screen. A custom wallboard or data layer earns its place when figures must combine the TMS, driver app and trackers, when each customer is measured differently, or when the shift needs watching live.
- 02
What to gather first
Write down the questions people ring round to answer during a shift, and the figures that go to customers and directors each month. Collect last month's spreadsheet and the definitions behind it, even if they live in one person's head. List every source system and who can grant access to it.
- 03
Who should own it
An operations lead who can settle arguments about what late or failed means, with someone from finance for anything that touches revenue or margin. Each panel needs a named owner who acts when it turns red. A dashboard that nobody is responsible for acting on becomes wallpaper, however good it looks.
- 04
How you will know it is working
Watch whether people stop ringing round to ask how the shift is going, whether weekly meetings start from the screen rather than a spreadsheet, and whether recurring failures get fixed at the source. If nobody opens the phone view, or the wallboard is ignored on a busy morning, it is showing the wrong things.
Terms worth knowing
The words you will meet
- OTIF (on time, in full)
- A delivery counts only if it arrived on time and complete. The detail that matters is on time against what: the date the customer asked for, or the slot you promised. Agree that per customer, or two teams will report two different OTIF figures for the same week.
- Fleet utilisation
- How much of the time, capacity or distance your vehicles could work they actually do. A busy fleet is not always an efficient one, so read utilisation alongside drops per run and cost, and watch for units that sit idle while you hire in.
- Leading and lagging indicators
- Lagging indicators, such as last month's OTIF, tell you what happened. Leading indicators, such as runs behind plan at ten o'clock or bookings with no slot, warn you while there is still time to act. A good wallboard shows both, with the leading ones up front.
Handled with care
The details that matter here
Performance figures end up in customer reviews and in conversations about drivers. These are the details we handle with particular care.
Definitions agreed before building
Late, failed and on time can each be measured several ways. We agree each definition with your operations lead in writing, show it on the dashboard itself, and check the first figures against a month you already know, explaining any difference before anyone relies on them.
Fair to drivers
A failed drop is often the site's fault, not the driver's. We agree with you and your data protection lead whether individual drivers appear on any screen and who can see that view, and we keep driver-level figures off shared wallboards unless you decide otherwise.
Wallboards in shared spaces
A screen in a traffic office or depot canteen is seen by visitors, agency staff and drivers from other firms. We keep customer names and anything commercial off shared screens unless you decide otherwise, and put the detail behind a login.
Usable on a phone in the yard
Depot managers check figures between other jobs, often on a poor connection. We keep phone views light, put the one number they need at the top, and test them on ordinary handsets out in the yard, not only on a large office monitor.
Guides
Worth reading first
Questions
What buyers ask first
Do we need a dashboard if our TMS already has reports?
You may not, and if your system's reports answer the questions you ask, we will say so. Dashboards earn their place when the answer needs data from more than one system, when the office needs to see the shift as it happens, or when each customer is measured differently. Often the most useful work is the layer underneath, joining and defining the numbers.
Can we build logistics dashboards in our existing BI tool?
Yes, and if you already pay for one it is often the sensible choice. The hard part is rarely the charting tool. It is getting runs, drops and tracker data into one place with agreed definitions. We can build that layer and put your BI tool on top, or build a custom wallboard where a general tool would not suit a screen in the traffic office.
Will drivers feel watched by performance dashboards?
They may, if it is introduced badly. We recommend telling drivers what is measured and why before any screen goes up, focusing the wallboard on runs and sites rather than named people, and using the figures to fix causes such as missing booking slots. We agree with you who sees driver-level data, and it stays behind a login.
What if our transport data is messy?
Then the dashboard will show it, which is useful in itself. Missing reason codes, drops never closed and customers recorded three different ways all become visible quickly. We would rather point those out and fix how the data is captured, often in the driver app, than average over the gaps and present a tidy figure nobody should trust.
How live is a live logistics dashboard?
As live as the systems behind it. Drops from the driver app arrive as phones find signal. Figures from your TMS arrive as often as its API or exports allow, which might be every few minutes or once a night. Each panel shows how old its data is, and we agree with you which panels must be current during a shift and which can update overnight.
Tell us the number you ring someone to find out
Name the figure you chase by phone most often during a shift. We will reply within 48 hours with where it would come from and how a wallboard could show it.
More for logistics
What else we build for logistics
Driver and proof-of-delivery apps
The day's manifest on the driver's phone, scanning at load and drop, photo and signature capture at the door, reason codes for failed deliveries, and everything saved safely when signal drops and synced as soon as it returns.
Customer tracking and booking
A portal where customers book collections, follow their consignments live, download proof of delivery and invoices, and see their own history, so the questions they used to phone about are answered before they think to ask.
Paperwork read automatically
Delivery notes, consignment notes, customs paperwork and supplier invoices read as they arrive, with reference numbers, signatures and handwritten notes about damage pulled out and matched to the right job, and anything unclear flagged for a person.
Dispatch and planning tools
Internal screens for your planners: jobs allocated to vehicles and drivers, capacity and delivery windows visible at a glance, and changes pushed straight to the driver's app, replacing the whiteboard and the spreadsheet only one person can read.
Systems that talk together
Orders from customers' systems flowing into your transport software, completed jobs flowing on to your accounts, and every scheduled transfer watched, so a silent failure becomes an alert the same day rather than a month-end surprise.
Everything we build for logistics
The same idea, in other sectors

