> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/business-manager/order-journey/tracking-rider-status.md).

# Tracking Rider Status in the Order Lifecycle

The rider's journey is part of the order's journey. The **Order Lifecycle** tab shows the rider's updates in the **Rider Status** section at the bottom.

## How to Get to the Order Lifecycle Tab

1. Visit login.urbanpiper.com and log in using your credentials.
2. Click on the **Orders** section to view the list of orders.
3. Click on the order you want to explore to open it.
4. Click the **Order Lifecycle** tab.

## Where to Find Rider Status

The rider's lifecycle is shown at the bottom of the **Order Lifecycle** tab. Each event shows the rider status and its timestamp.

1. On the **Order Lifecycle** tab, scroll to **Rider Status** at the bottom.
2. Click **View Details** to see each rider status event.

In this example, the rider events shown are **At store**, **Assigned**, **Out for delivery** and **Delivered**.

![Order Lifecycle tab scrolled to Rider Status, expanded to show the rider events At store, Assigned, Out for delivery and Delivered](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-7c5137a581266f52cdff6d406f7a5a600fc499be%2Forder-journey-08-rider-status.gif?alt=media)

{% hint style="info" %}
**Tip:** To debug delayed-delivery issues, compare the rider timestamps with **Order Ready** and **Order Dispatch** to see where the delay occurred.
{% endhint %}

If the platform does not send rider updates, **Rider Status** appears muted. Learn more in [Understanding Muted Events in the Order Lifecycle](https://help.urbanpiper.com/business-manager/order-journey/understanding-muted-events.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.urbanpiper.com/business-manager/order-journey/tracking-rider-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
