> 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.

# Orders, Task Groups, Segments, and Stops

> How chrt models a shipment — the order, the task groups (segments) it's composed of, the tasks (stops) inside each task group, and the cargo that flows through them.

An **order** organizes a shipment's cargo and work. A **task group** organizes related work within that order, and a **task** records an action or event within the group. **Segment** and **stop** are useful operational labels, but always follow the labels and relationships shown for the current workspace.

## Order

Open an order by its reference. The workspace can show a draft or staged 1 order and has **Summary**, **Timeline**, **Tasks**, **Cargo**, **Bookings**, **Messages** 2 and **Audit Log** sections where your access permits them; an order reference alone does not prove readiness or assignment.

![Timeline tab of a staged example order, with numbers pointing at the Staged badge (1), the tab row (2), the Segment 1 — Ground task group (3), the executor chip (4) and the Driver Assigned row (5), above the Stop 1 Pickup and Stop 2 Deliver rows](/_fern-files/_img/8d23e3a5a817ac2c779856b391339592aa844a04ab746a19ea61800829374719.webp)

*Order workspace, **Timeline** tab, of a staged example order, with the **Stop 1** **Pickup** and **Stop 2** **Deliver** rows below the driver. **1** **Staged** badge, **2** Section tabs, **Summary** through **Messages**; further tabs such as **Audit Log** sit to the right, outside the picture, **3** **Segment 1 — Ground** task group, **4** Executor chip, **5** **Driver Assigned** row with **Change**.*

## Order states

A draft is work being prepared. **Stage order** asks the service to validate readiness and stage it. If the order is not ready, CHRT lists the requirements that are not met, such as **Stops are missing cargo** or **The order has no coordinator**, and you can fix them and stage again. A shipper operator can edit and stage a draft their own organization created, after choosing a coordinator with **Select coordinator…** in the header. After the action, refresh/reopen the order and inspect its saved state. If staging succeeded but refresh failed, resolve the refresh before repeating the action or concluding that nothing was saved.

Later status reflects the configured task groups and execution. Do not infer live tracking, locked editing or automatic completion solely from a status label.

## Task group

A task group 3 identifies a unit of configured work, such as a ground movement, flight-linked cargo or on-board courier work. Its executor 4, driver 5 and task sequence must be checked separately. One order can include several groups and handoffs.

## Task

Tasks describe the configured pickup, delivery, airline handoff, flight or handling events. A task can have instructions, timing, proof and custody requirements. Complete or report the actual event; a flight departure does not by itself prove cargo loading or customs clearance.

## Cargo

Cargo records describe what is moving. Check quantity, measurements and handling instructions, then review which task groups or legs the cargo is associated with. Selecting a type is not evidence that a carrier has the required qualification or that a handling rule is enforced.

On an editable provider order, **Add cargo** creates a row immediately and grid edits submit automatically. Reopen **Cargo** to confirm what saved; the order's staging action is separate.

## Visibility and handoffs

The creator/coordinator, executor, shipper and assigned driver can have different access. Do not assume a provider sees the entire order or that reassignment removes all prior visibility. Confirm the applicable saved assignment and sharing settings with the parties involved.

For billing setup, see the existing [billing guide](/staging/docs/concepts/billing-primitives).

See [Create and assign an order](/staging/help/getting-started/create-and-assign-order), [Cargo types](/staging/docs/concepts/cargo-types), [Tracking](/staging/docs/concepts/tracking) and [Driver proof](/staging/app/proof-of-delivery).