> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/analytics/order-performance-report/delivery-report-values.md).

# Delivery Report Values

## Calculations

#### Cooking Time

<mark style="background-color:$info;">Prepared at - Start preparing at</mark>

#### Waiting in venue

Time between food being ready and the driver leaving the venue.

<mark style="background-color:$info;">Left venue - Prepared at</mark>

#### Wait to tracked delivery time

Time taken for the customer to see the order tracking.

<mark style="background-color:$info;">Started delivery - Left venue</mark>

> For the first order in a delivery leg, this value is always **0** because *Started Delivery* is automatically set.

#### Tracked delivery time

The duration the customer could view tracking before the driver arrived.

<mark style="background-color:$info;">Waiting for customer - Started delivery</mark>

#### Waiting for customer time

Time taken for the customer to collect their order after the driver’s arrival.

<mark style="background-color:$info;">Completed delivery - Waiting for customer</mark>

#### Delivery time

Time taken to deliver the order once leaving the venue.

<mark style="background-color:$info;">Completed delivery - Left venue</mark>

#### Order completion time:

Total time it took to fulfil the order.

<mark style="background-color:$info;">Cooking time + Waiting in venue + Delivery time</mark>

***

## Order Timestamps

#### Created At

Time the order was created.

#### Start Preparing At

Time the order appears on the KDS.

* If the order is not scheduled or the venue’s internal cooking time equals the cooking time<mark style="color:$primary;">:</mark> <mark style="background-color:$info;">Start Preparing At = Created At</mark>
* If the order is scheduled or the internal cooking time differs from the cooking time: Start Preparing At **may be later** than Created At, as the order will be pushed to the KDS accordingly.

#### Prepare For

Target time for food to be ready.

<mark style="background-color:$info;">Start Preparing At + Preparation Time (from workload mode)</mark>

#### Prepared At

Time at which order was fully cooked, i.e. marked “Prepared” on all KDS screens.

#### Assigned

Time the order was assigned to a driver.

#### Left Venue

Time the driver pressed **Start** in the driver app.

> **Note:** When the "Start" button is pressed, the first order in the delivery leg automatically moves to Started Delivery.

#### Started Delivery

Time the driver began the delivery.

* For the first order in a delivery leg: Left venue = Started delivery
* For subsequent orders in the leg, Started Delivery is set to when the driver completes the previous order (by pressing "Finished").

#### Waiting for Customer

Time the driver pressed **Arrived** on an order.

#### Completed Delivery:

Time the driver pressed **Finished** on an order.

#### ETA

Estimated time of arrival shown to the customer.

<mark style="background-color:$info;">Preparation time + delivery time from workload mode</mark>

***

{% hint style="info" %}
For more information on Workload Modes, please see [Workload](/workload.md)
{% 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.bossithq.com/analytics/order-performance-report/delivery-report-values.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.