Freight Visibility KPIs: Dashboard Definitions and Review

Quick Overview

A freight visibility dashboard measures whether eligible shipments have usable tracking information, whether teams respond to exceptions and whether verified deliveries meet their commitments. Define the shipment group, required events, time window and reporting cutoff before calculating a KPI. Report missing information separately from a confirmed transport delay: a milestone that has not reached the tracking feed does not, by itself, prove the shipment is late.

Define The Eligible Shipment Group

Choose the modes, services, branches and shipment states included in the report. Specify which milestones each workflow requires and when those milestones become due. An active shipment should not be counted as missing a delivery event that is not yet expected.

Use a consistent reporting time zone and show the period start, period end and data cutoff beside every dashboard. A reporting period selects the relevant shipments or events; the cutoff determines which updates were available when the report was produced.

A milestone-level percentage and a shipment-level percentage answer different questions. For example, one shipment may have several required milestones. Do not describe 90% milestone coverage as “90% of shipments on time.”

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.

Reporting Rules And Data Checks

Store the event time and the time the update entered your system where both are available. A vessel arrival may have happened on schedule even when its tracking message arrived late. Investigate late receipt as a data issue; investigate a verified late event as a transport issue.

For each report, record:

• The eligible modes, services, branches and shipment states.
• The event or shipment cohort used for each metric.
• The time zone, period dates and data cutoff.
• The required milestones and freshness window for each service.
• The source of each event and whether its timestamp was verified.
• Missing outcomes, unassigned exceptions and cases still open.

Review these exclusions and incomplete records beside the headline percentage. If no eligible denominator exists, show “n.a.” rather than 0%.

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.

Visibility KPIs And Sales KPIs Answer Different Questions

Visibility KPIs begin with a shipment, milestone or operational exception. Sales KPIs begin with an enquiry or quote opportunity. Keep quote response time, quote follow-up, win rate and quote-to-book conversion in the freight sales and quoting KPI guide. Use this page for tracking coverage, update freshness, exception handling and verified delivery performance.

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.