> This page is for version Staging.
> For other versions, use one of these documentation indexes:
> - Prod (default): https://docs.chrt.com/prod/llms.txt
> - Staging: https://docs.chrt.com/staging/llms.txt
> - Dev: https://docs.chrt.com/dev/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chrt.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chrt.com/_mcp/server.

# Tracking Shipments

> Practical guide to current CHRT tracking workflows and saved-record checks.

## Open the order workspace

Open [Orders](https://chrt.com/orders) and select the shipment. Confirm the order reference and customer before acting. Use **Summary** 1 for the overview, **Timeline** for route and event detail, **Cargo** for shipped items, and **Messages** for coordination. Mark 2 is the **Completed** status and the coordinator, mark 3 is the **Route** card, mark 4 is the **Cargo** section, and mark 5 is the **Progress** | **Live** switch on the map.

![The Summary tab of a completed provider-created order in the shipper workspace, numbered 1 to 5: the Summary, Timeline, Cargo and Messages tabs, the Completed status with the coordinator, the Route card, the Cargo section, and the Progress and Live toggle on the map](/_fern-files/_img/3bcc663a49387b2564c9161dd26f3136cd5fbd5071bed5d316a1bd7be9d2049d.webp)

*Order **Summary** tab in the shipper workspace, for a completed order created by the provider. **1** **Summary**, **Timeline**, **Cargo** and **Messages** tabs, **2** **Completed** status and the coordinator, shown as **by CHRT (forwarder)**, **3** **Route** card, **4** **Cargo** section, **5** **Progress** / **Live** toggle on the map.*

## Read location and route together

The order map can show the route and available tracking sources. Mark 1 is the **Map settings** gear. Use the map controls to select relevant segments and sources such as **Driver** 2, **Cargo (Driver)** 3, and **Cargo with Device**. Mark 4 is **See all pings**, and mark 5 is the **Progress** | **Live** switch.

![Shipper order map settings, numbered 1 to 5: the Map settings gear, the Driver, Cargo (Driver) and See all pings options, and the Progress and Live switch](/_fern-files/_img/09d95f1ba6173ec74ee29e0b949e4657eddb1c5edd2403e1ed59ccfcbf102764.webp)

*Order map settings in the shipper view. **1** **Map settings** gear, **2** **Driver** (on, and dimmed because it is the only source shown), **3** **Cargo (Driver)** (off), **4** **See all pings** (on), **5** **Progress** | **Live** switch. Look at **2** and **3** to see which sources the map is showing.*

Check the last update and selected source before treating a marker as the shipment’s current location. Missing data can reflect source, connectivity, access, or configuration. On the **Summary** tab, the map has a **Progress** | **Live** switch 1. Selecting a point opens a popover 2 with its time and driver.

![Order Summary tab of a completed order with one point selected on the map, numbered 1 and 2: the Progress and Live switch, and the selected point's popover with its time and driver](/_fern-files/_img/a17d2d5b22827d472052ae3cb34446f26b96a31dcd3cfe26b4a80e901e0455ab.webp)

*Order **Summary** tab of a completed order in the shipper view: the ground route in **Progress**, with one map point selected (**10/4 12:22 PDT**). **1** **Progress** | **Live** switch, **2** popover of the selected map point (time and driver).*

## Inspect timeline detail and proof

The read-only timeline lists the **Driver Assigned** 1 node and the **Pickup** 2 and **Deliver** 3 stops. Select the relevant timeline event or stop to open its detail panel. Read the recorded status and timestamps, then inspect the task artifacts associated with that task. Flight segments include flight detail and milestones. An attached document does not by itself establish that a flight booking or airline handoff succeeded.

![The read-only Timeline tab of a completed order in the shipper workspace, with numbers on the Driver Assigned, Pickup and Deliver nodes.](/_fern-files/_img/17688fb74ea1f9a1f64a57a2dfda39ae91d3e79c6dd2ba5c014641a76d4cd217.webp)

*Order **Timeline** tab of a completed order in the shipper workspace. **1** **Driver Assigned** node, **2** **Pickup** node, **3** **Deliver** node.*

![Delivery detail panel for Stop 2, numbered 1 to 3: the Completed time, the Task custody section, and the blank Recipient Name field](/_fern-files/_img/70901a30fc60065eda23af096cf5ae19ead4be327dd6a3978b5077881e64fe18.webp)

*Delivery detail panel for **Stop 2**, **Deliver**, in the shipper **Timeline**. **1** **Completed** time (**12:27 PDT**), **2** **Task custody** section, **3** **Recipient Name** field (blank, disabled).*

The delivery task records completion at **12:27 PDT** 1. In the **Task custody** 2 section, it has a blank, disabled **Recipient Name** 3 field. An artifact's recipient is a separate field.

Scrolled to **Attachments**, an **Image** 1 artifact records its own completion time and proof file 2. Compare artifact and task times separately; an artifact does not fill the task's blank recipient field.

![The Deliver detail of a stop in the shipper Timeline scrolled to Attachments, with number 1 on a completed Image artifact and 2 on its saved proof file.](/_fern-files/_img/a9e0767b54e0b16103f05c5d3d018b01c8dbcec6efd1caa401df4f858b747851.webp)

*Stop **Deliver** detail in **Timeline** for the shipper, scrolled to **Attachments**. **1** **Image** artifact, **2** saved proof file.*

## Understand the shipper view

A shipper view can display **Agent assigned** or **Agent** instead of a third-party executor or driver’s identity. Work with your coordinator when you need dispatch information. The display varies by the organization’s relationship to the segment; do not expect every viewer to see the same names or contact details.

## Use order actions

Open the actions available in your current organization and order state. In the sample **CHRT shipper** profile, the completed fictional order offers **Share tracking** 1. Other roles or states may expose different actions; confirm the actual menu before relying on an option.

![The Actions menu of a completed shipper order open, with number 1 on Share tracking.](/_fern-files/_img/795adb1a170ae44918cb0c422bef2e76eee41da8f48296e37e2b7324cfca5467.webp)

*Order header with the **Actions** menu open. **1** **Share tracking**.*

For public sharing, follow [Public Tracking Links](/staging/shippers/public-tracking) and inspect the recipient’s view.

## Confirm progress

Reload the order and compare the saved task statuses, timestamps, and proof with the work actually completed. A route line is planned travel; a location update is observed tracking; a completed task is a recorded operational event. Check each separately when an ETA or status appears inconsistent.

For billing workflows and rate configuration, see [Billing](/staging/shippers/billing).

## Related guides

* [Getting Started](/staging/shippers)
* [Creating Shipments](/staging/shippers/creating-shipments)
* [Connecting with Providers](/staging/shippers/connecting-providers)
* [Tracking Shipments](/staging/shippers/tracking)
* [Public Tracking Links](/staging/shippers/public-tracking)