Freight Visibility KPIs: Dashboard Definitions and Review
Quick overview
A freight visibility KPI dashboard measures the availability of shipment information and the team’s response to exceptions. Define eligible shipments, required milestones and reporting periods before calculating results. Keep data quality separate from transport performance so missing updates are not automatically counted as late shipments.
Define the eligible shipment group
Select modes, services, branches and reporting dates. Specify which milestones are required and when they become due. A new shipment should not count as missing a delivery event that is not yet expected.
| KPI | Definition | Clarification needed |
|---|---|---|
| Due-milestone coverage | Received required milestones divided by required milestones due by the cut-off | Expected events differ by workflow |
| Active-shipment freshness | Active shipments with a usable update inside the defined window divided by eligible active shipments | Set realistic windows by source and service |
| Assignment time | Case creation to accepted ownership | State elapsed or business hours |
| Resolution time | Case creation to confirmed resolution | Report unresolved cases separately |
| Open-case age | Time since creation for unresolved cases | Segment by owner and exception type |
| On-time delivery | Deliveries meeting the agreed commitment divided by eligible deliveries due in the selected cohort | Preserve the baseline and disclose missing outcomes |
Multiply ratios by 100 for percentages. Explain exclusions instead of silently removing incomplete records.
Separate transport delay from data delay
An event can occur on time but reach the tracking feed later. Store event time and receipt time where available.
Investigate the source or connection when information is delayed. Assign an operational response when a shipment delay is confirmed. Both problems matter, but they require different action.
Example: coverage is not punctuality
In a hypothetical report, 100 milestones are due and 90 have been received. Coverage is 90%. This does not mean 90% of shipments are on time: several milestones may belong to one shipment, and received events can report delays.
Do not substitute an easy data metric for a different service outcome.
Make the dashboard actionable
Show the metric definition, cut-off and owner beside the result. Let reviewers inspect its underlying records.
Review old open cases alongside resolved-case averages. Otherwise the dashboard can appear faster while difficult cases remain unresolved.
Use median and a high percentile for response times where the sample supports them, and state the number of observations.
Connect measurement with operations
End each review with an assigned action: repair a feed, clarify a milestone, resolve an old case or correct ownership.
Explore the Operations Tower for task coordination and TMS integration for connected data. Confirm available reports in your implementation; these definitions are a measurement framework, not a list of guaranteed built-in dashboards.
Related Articles
