> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/platform/overview/control-tower/live-network-report.md).

# Live Network Report

## Use Case

Using this report, you can view how many parcels are being delivered, are in transit or have been announced they are ready to be picked up. You can also check how the delivery process changes hourly and identify possible abnormal behavior from the average performance of the last seven days. Additionally, you can identify delivery issues per carrier on the fly by checking if they are underperforming from what is expected.

## <code class="expression">space.vars.Report\_CTLiveNetwork</code> Report Features

This report is based on the current day and at which time the last refresh of the data occurred.

The top-level row shows the core metrics of this report. This gives you an overview of the status of parcels for today, including the total number of parcels in progress, still at the warehouse, and delivered.

<figure><img src="/files/DNsr5rZdnX8cSotMlMlt" alt="Core metrics for Live Network report"><figcaption></figcaption></figure>

More detailed charts are included in the <code class="expression">space.vars.Report\_CTLiveNetwork</code> report to help you monitor how well your business is performing on the current day.

<figure><img src="/files/vrb2X0oJTSmLifS5c6Bj" alt="Live Network report charts"><figcaption></figcaption></figure>

{% hint style="info" icon="book" %}
**Check out the parcelLab guides**

For further information on using the report and metrics, see our [user guide documentation](https://how.parcellab.works/guides/trackings/control-tower/live-network-report).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parcellab.com/docs/platform/overview/control-tower/live-network-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.