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

# Control Tower

Use the Control Tower dashboard to get a snapshot of your brand's performance today, highlighting parcels delivered, communications sent, and any potential issues that have surfaced.

## Overview

Specific reports on your current performance are available in the <code class="expression">space.vars.Report\_ControlTower</code> dashboard.

You can use the reports and advanced filters available to track the status of your parcels and monitor the success of your communications and trackings that are experiencing issues.

## Purpose of the Reports

This section provides some example questions and how specific reports can help you answer them to give insights into your data.

An example question is: *Which parcels are still not delivered?*

This can be answered by going to the [Exceptions report](/docs/platform/overview/control-tower/exceptions-report.md) and viewing the "Parcels in progress" table. By using the filter above the table, you can set the minimum number of days a parcel has been stuck. If you set the minimum time stuck to one day, this will show you all orders that are still open (that is: created during the last 15 days). Additionally, if you want to check a particular order, you can check its tracking number in the table and see its current position.

<figure><img src="https://1156682959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LPf1Lv1YUuLYva6LrXQ%2Fuploads%2FDhVRWb7Z6gLHU17G5Z2j%2FExceptionsReportChart1.png?alt=media&amp;token=139b9d7b-f6b1-4341-8a78-3b310009a3c4" alt="Parcels in progress table"><figcaption></figcaption></figure>

## <code class="expression">space.vars.Report\_ControlTower</code> Reports

Each of the reports in the <code class="expression">space.vars.Report\_ControlTower</code> dashboard are described in the following pages.

{% content-ref url="/pages/Q0PyeARYy7cwbhkLIBsu" %}
[Live Network Report](/docs/platform/overview/control-tower/live-network-report.md)
{% endcontent-ref %}

{% content-ref url="/pages/NpI96C8IcdJxOwOAbKWH" %}
[Communications Report](/docs/platform/overview/control-tower/communications-report.md)
{% endcontent-ref %}

{% content-ref url="/pages/wLxPDdFpnU4An2PZDLtB" %}
[Exceptions Report](/docs/platform/overview/control-tower/exceptions-report.md)
{% endcontent-ref %}

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

For further information on using the dashboard and metrics, see our [user guide documentation](https://docs.parcellab.com/guides/trackings/control-tower).
{% 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 by asking a question.

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

```
GET https://docs.parcellab.com/docs/platform/overview/control-tower.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.