Logistics Reporting: Why On-Time and Cost Per Drop Disagree

Most logistics reporting is too agreeable. On-time delivery sits at 96%, cost per drop is trending down, and everyone walks out of the Monday ops meeting happy. Here's the problem. Those two numbers almost never improve together for long. When they both look great, one of them is usually being measured in a way that flatters it.

The better approach is to stop reporting them as separate wins and start reporting them as a trade-off. Put them side by side, at the same level of detail, and let the tension show. That's where the useful decisions live.

Why your two favourite KPIs pull against each other

Think about what it takes to hit a tight delivery window. You send a second truck half full. You pay overtime. You book an express carrier because the regular run won't make it in time. Every one of those choices protects on-time delivery and pushes cost per drop up.

Now flip it. To cut cost, you consolidate routes, fill trucks properly and stretch runs a little further. Fantastic for the cost line. But a fuller truck leaving an Acacia Ridge or Larapinta depot at 6am and battling the Gateway Motorway is going to miss a few windows on the Sunshine Coast. Sound familiar? We see the same pattern with Brisbane mining-services contractors shipping parts to the Bowen Basin, where one urgent charter flight can wipe out a month of route savings.Neither number is wrong. They're just answering different questions.

Where the numbers quietly stop matching

Even before the trade-off kicks in, most businesses have a measurement problem. On-time delivery usually comes from the transport management system, refreshed daily. Cost per drop usually comes from finance, calculated at month end from the general ledger. They were never built to line up. Here are the gaps we find most often in Brisbane operations:

• "On time" means the customer's requested window in one report and the promised window in another
• Failed deliveries count once in on-time figures but twice in cost, because the truck went out twice
• Express and third-party carrier costs land in a different cost centre and never reach the drop-level number
• Regional drops to Toowoomba or Bundaberg get averaged in with metro drops, hiding what each really costs
• Proof of delivery timestamps come from driver apps that sync late, so some drops look late when they weren't

Fix the definitions first. If your team can't agree on what a single drop cost and whether it was on time, no dashboard will save you.

Putting both numbers on the same page

So what does good look like in practice? Start with one record per drop. Each drop carries its delivery status, its promised window and an allocated cost, including fuel, driver time, tolls and any carrier charges. Once both metrics share that same grain, you can slice them by route, customer, depot or day of week and see exactly where the trade-off is happening.

Our favourite view is a simple scatter chart. Plot each route or customer by on-time rate against cost per drop. The top-left corner is where you're winning. The bottom-right is where you're paying a premium and still disappointing people. That one visual tends to start better conversations than ten pages of tables. It's the kind of thing we build regularly through our Power BI dashboard development work, and it's a core part of how we approach supply chain and logistics reporting for clients across South East Queensland.

If your logistics reporting still lives in two spreadsheets that never quite reconcile, that's the place to start. Roar Data works with Brisbane distributors, transport operators and field-services businesses to join their TMS, finance and driver data into one honest view. Have a look at how we approach Power BI for Brisbane businesses, or book a chat about Power BI consulting in Brisbane. Bring your current on-time and cost figures, and we'll show you where they disagree.

If the question is who should do the work, how we scope and price a Power BI engagement in Brisbane covers the diagnostic, the fixed price, and what is agreed before a build starts.