The transport KPI dashboard that stops late invoices
What a useful transport KPI dashboard should show a UK haulage firm, which numbers matter daily, and how it helps stop late PODs and invoices.
A transport KPI dashboard should stop money going missing between the job being done and the invoice being raised. In a UK haulage office, that means one thing above all: by the start of the working day, we should be able to see which jobs ran, which ones did not, which PODs are still missing, and which completed work is still not ready to bill.
If a dashboard only gives us attractive charts about last month, it is not doing the job. The useful version is a working screen for the owner or transport manager who has already had the 6am phone call, is covering traffic issues, and needs to know where cash is being delayed today. A good dashboard KPI transport setup is not about more reporting. It is about getting today’s exceptions in front of us early enough to fix them.
What a transport KPI dashboard is actually for
In a small or mid-size haulage business, the dashboard is not there for a board presentation. It is there to run the day.
That matters because most late invoices are not really finance problems. They start in operations. A driver finishes late and the POD stays in the cab. A delivery time is confirmed on a text message but never written against the job. A subcontractor sends a photo that nobody matches to the right load. A container move sits as "done" in someone’s head but not in the system. Two weeks later, accounts are chasing paperwork for work that should already have been billed.
A proper transport dashboard should bring those gaps together in one place. It should answer practical questions.
- What was due yesterday that is still open?
- Which completed jobs have no POD?
- Which jobs have a POD but are not invoice-ready?
- Which customers are waiting because rates or references are missing?
- Which container jobs are at risk of demurrage because milestones were not updated?
- Which subcontractor jobs need cost confirmation before margin disappears?
That is the real purpose of a dashboard in a TMS. It should shorten the time between planning, completion, proof, and invoice.
For UK operators, the useful cut is usually operational first, financial second. We need to see the jobs that are blocking invoicing, not just a month-end debtor number after the damage is done. If one vehicle has finished three jobs and none has a POD attached, that needs attention before breakfast. If a backload was agreed by phone and never priced in the system, we need to catch it while the details are fresh.
This is why we build our software around the daily flow of work, from planning through driver briefing to POD capture and billing. If you want more detail on that link between operations and finance, our guide to transport finance and faster invoice preparation sets out the process.
Which KPIs matter most day to day
Most firms do not need thirty KPIs. They need a short list that reflects how jobs actually move through the office. The best measures are the ones that tell us where revenue is stuck.
For a small to mid-size operator, these are the day to day KPIs that matter most.
1. Jobs due today, jobs missed yesterday
This is the first operational check. We want a count of:
- jobs scheduled for today
- jobs still open from yesterday
- jobs marked complete late
- jobs with no status update
If yesterday’s work is still hanging around at 10am, it usually means one of three things. The job did not happen, the job happened but was not closed properly, or the evidence is missing. All three affect invoicing.
2. Completed jobs with no POD
This is one of the clearest indicators of future cash delay. If the work is done but the POD is missing, billing slows down immediately. The dashboard should show:
- number of completed jobs with no POD
- age of missing PODs
- jobs completed more than 24 hours ago with no POD
- whether the POD is paper, photo, or ePOD
For many operators still using paper, this is where invoices go late. The job is real, the truck has moved, but the office cannot bill confidently because the proof is in a cab, on a phone, or lost in a pile.
3. Completed jobs not invoiced
This is the KPI that joins operations to cash. We should be able to see:
- completed jobs awaiting invoice
- total value awaiting invoice, where rates are already known
- jobs blocked by missing rate, missing reference, or missing POD
- age bands, such as same day, 1 to 3 days, 4 to 7 days, and over 7 days
This measure matters more than broad turnover charts because it tells us what can be fixed now.
4. POD received but invoice not raised
This is a separate exception worth tracking on its own. Once the POD is in, the delay is usually administrative. That can mean rates have not been entered, customer references are incomplete, or someone is waiting for a batch run at the end of the week. If we can identify jobs where all operational evidence exists but the invoice still has not gone, we can remove avoidable lag.
5. Delays, failed collections, and redelivery risk
A useful dashboard should not hide service failures until a customer complains. We need to see:
- failed collection attempts
- delivery delays
- timed bookings missed
- jobs requiring rebooking or redelivery
- customer-impacting exceptions still uncalled
This is not just about service. It affects whether we can bill the original job cleanly, whether waiting time needs adding, and whether extra costs should be charged or absorbed.
6. Subcontractor jobs awaiting paperwork or cost
If we use a subcontractor, the dashboard should show:
- jobs allocated to subcontractors
- completed subcontractor jobs with no POD
- completed subcontractor jobs with no cost entered
- jobs invoiced to the customer before subcontractor cost is confirmed
- margin at risk on subcontracted work
This catches the common problem where the customer invoice is delayed because we are waiting for the haulier’s paperwork, or where the invoice goes out but margin is unclear because the cost was never entered properly.
7. Container milestones and container turnaround
For container transport, the dashboard needs a slightly different shape. It should track milestone events that affect both service and charges. At a minimum:
- import and export jobs by stage
- empty collection completed or not
- loaded collection completed or not
- quay return completed or not
- unresolved booking references
- jobs nearing free time expiry
- container turnaround time by customer or traffic type
If we do container work, we also need visibility on demurrage risk. In the UK, the commercial rules depend on the shipping line, terminal, and customer agreement rather than a single national standard, so the dashboard must reflect the dates and milestones we actually work to. A generic "late job" flag is not enough.
For operators handling boxes every day, our page on container transport workflow and milestone control goes into that side of the operation in more detail.
What the dashboard should show by 10am
By 10am, the morning firefighting is already under way. That is why the dashboard needs to be short, clear, and sorted by action.
The first panel should be yesterday’s unfinished business. Not last week, not a trend line, yesterday. We need a list of jobs that were due to complete but are still open, with vehicle, driver, customer, and last known status. If a job should have finished at 16:00 and there is still no closure, we should not have to dig through messages to find it.
The second panel should be missing PODs. This should show every completed job where no POD has been attached, ideally with age and responsibility. For example:
- driver has not submitted
- paper POD expected back
- subcontractor paperwork outstanding
- POD image received but not matched to job
That distinction matters. If the issue is driver submission, we chase the driver. If the issue is matching, we fix the office process. If the issue is a subcontractor, we chase externally before the day disappears.
The third panel should be unbilled completed work. This is where the dashboard earns its keep. We need to know what is ready to invoice now, what is blocked, and why. A useful list might include:
- completed with POD, invoice can be raised
- completed, POD missing
- completed, rate missing
- completed, customer reference missing
- completed, cost check required
This is the point where a TMS should do more than store jobs. It should help us move work from completed to billed with as few clicks and handoffs as possible. We cover that in more detail in our article on transport planning software that gets invoices out faster.
The fourth panel should be today’s problem loads. These are jobs at risk before they become tomorrow’s exceptions. That includes timed deliveries with no driver assigned, container bookings with missing references, jobs likely to miss a slot, and work where the customer has changed instructions overnight.
For container operations, by 10am we also need a clear view of boxes that could create charge exposure. If a quay return has not happened, if free time is close, or if a container has not moved to the next milestone, that should sit in front of us. Demurrage and storage disputes often start with poor visibility on exactly where the box is in the process.
Finally, the dashboard should show anything that threatens compliance or vehicle use in the real world, without pretending to be a full compliance system. If a vehicle is off road, if a driver has changed, or if a job cannot run as planned because of a workshop issue, that needs to be visible because it affects service and billing. We come from a business that also runs an HGV workshop, so we know how often a day’s plan changes for practical reasons, not theoretical ones.
How to build a dashboard without creating more admin
The quickest way to make a dashboard fail is to base it on data nobody will maintain.
If a KPI depends on someone remembering to fill in three extra fields after every call, it will drift within a week. Then the office stops trusting it, and everyone goes back to WhatsApp, paper, and memory.
The better approach is to build the dashboard from events that already happen as part of the job.
- job created
- job allocated
- driver briefed
- status updated
- POD received
- rate confirmed
- invoice raised
Those are reliable because they are tied to real work. If the system already plans the job, sends the details to the driver, captures the POD, and prepares invoicing, the dashboard can use those same timestamps and statuses without creating extra admin.
That is how we think about a dashboard KPI transport setup. Start with a small number of measures that come directly from the operation. Usually that means:
- open jobs due yesterday
- completed jobs with no POD
- completed jobs not invoiced
- subcontractor jobs with missing paperwork or cost
- container jobs with milestone or free-time risk
That is enough to improve control straight away.
It also helps to decide who owns each exception. A dashboard is only useful if the office knows what happens next. For example:
- missing driver POD, transport follows up
- unmatched POD image, traffic office or admin matches it
- missing rate, owner or accounts confirms tariff
- subcontractor paperwork, planner or accounts chases it
- container milestone issue, container desk resolves it
Without ownership, the dashboard becomes a list of shared concern and no action.
We also recommend avoiding vanity KPIs at the start. Cost per mile, vehicle utilisation, and customer trend reporting can all be useful, but they do not fix a late invoice this morning. Build the first dashboard around workflow blockages. Once that is stable, add broader reporting if it helps.
If you are replacing a spreadsheet-led process, the key is to use a TMS that can be started without a long implementation project. Most firms in this size bracket do not have time for workshops, consultants, and a six-month rollout. They need to get live, run jobs, capture POD, and see the gaps quickly. Our transport management tools for daily planning and job control are built around that reality.
Where AI helps and where it does not
AI helps when it removes repetitive handling of job information that the office is already doing by hand. It does not help if it becomes a vague promise while the basic data is still missing.
The practical uses are straightforward.
It can help read incoming POD images and documents, identify the likely job, and pull out key details that would otherwise be typed manually. It can help sort paperwork arriving from different drivers and subcontractors. It can help flag that a document is missing a signature, date, or reference before we try to bill from it.
It can also help prepare invoice-ready data from completed jobs. If the rate card is already known, the job milestones are present, and the POD is attached, software can move that work much closer to invoice issue without someone rekeying the same details from one screen to another.
For container work, AI can help interpret messy incoming information, such as booking references, container numbers, and milestone updates, then match them back to the right movement. That is useful because the delay often comes from paperwork and message handling, not from the driving itself.
Where it does not help is where the business has not captured the underlying event. If nobody marked the job complete, no tool can confidently know it is ready to invoice. If the rate was agreed on the phone and never entered anywhere, software cannot invent the commercial instruction. If a subcontractor has not sent the POD, there is nothing to process.
It also does not replace sensible operational discipline. We still need drivers to submit paperwork promptly. We still need jobs planned against the right customer and reference. We still need clear statuses that mean the same thing across the office.
That is why we apply AI to the practical parts of the workflow rather than using it as a headline. The useful test is simple. Does it reduce the time between job completion and invoice issue? Does it cut the number of loads sitting unbilled because someone cannot find the POD? Does it reduce the amount of retyping and chasing in the office? If yes, it is earning its place. If not, it is just another feature to admire.
The best transport dashboard is not the one with the most charts. It is the one that tells us, by 10am, exactly which jobs are stopping today’s invoices from going out, and what we need to do next.
What is the most useful KPI on a transport dashboard?
For many small haulage firms, the most useful KPI is work done but not yet invoiced. It shows cash being delayed and usually points straight to missing POD, missing rates or jobs not properly closed.
How many KPIs should a small haulage firm track?
Usually eight to twelve is enough. If the dashboard has dozens of figures, nobody acts on them. Start with job status, POD status, invoice delay, on-time delivery, subcontractor use and any container turnaround or demurrage exposure.
Should a dashboard be for managers or for the traffic desk?
Both, but the same screen does not have to serve both jobs. The traffic desk needs exceptions and today’s problems. The owner or transport manager may also want weekly trends in utilisation, revenue leakage and invoice timing.
Can a KPI dashboard help reduce demurrage?
Yes, if it shows which containers are still out, how long they have been out and which jobs are at risk of delay. A dashboard cannot remove demurrage by itself, but it can make the risk visible early enough to act.
Do you need a full TMS before you can have a useful dashboard?
Not necessarily, but the dashboard is only as good as the job data behind it. If jobs, POD and invoice status are scattered across WhatsApp, paper and spreadsheets, the numbers will be late or incomplete.