> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review booking outcomes and timing

> Understand cancellation, no-show, booking lead-time and estimated response-time figures in the mobile app.

Use the booking report to review requests and visit outcomes. The cards count different groups of bookings, so read their definitions before comparing percentages or totals.

## Who can do this?

**Owners and Managers** can open these reports for their shop. Staff access to managing bookings does not include this Analytics report.

## Where to do it

In the mobile app, open **Analytics** and choose **Bookings & Capacity**.

## Read the booking cards

1. Check the shop and select the main reporting period.
2. Read the figure and the counts beneath each card together.
3. Tap the information button for its explanation. Read any additional notes or small-sample warning.
4. Use the definitions below to distinguish bookings created in the period from visits scheduled in the period.

## Cancellation rate

**Cancellation rate** uses all bookings created in the selected period. Its cancelled count includes bookings currently **Denied**, plus requests still **Pending** whose reservation date is before today in the shop’s local time.

The calculation does not automatically cancel those pending requests. It also does not count every cancellation action: cancelling a confirmed booking in the web app archives it, and archived bookings are not included in this cancelled count. Read the [booking-status guide](/en/bookings/manage-booking-status) when checking individual cases.

## No-show rate

**No-show rate** uses reservation dates within the selected period that are before today in the shop’s local time. It divides bookings marked **No show** by past bookings currently **No show**, **Confirmed** or **Archived**. Pending and denied requests are excluded.

A visit earlier today is not yet in this calculation. Archived status does not prove attendance, so review individual booking histories before treating this rate as a complete record of who arrived.

## Booking lead time

**Booking lead time** shows the middle time between creating a booking and its scheduled visit. It uses bookings created in the selected period, excluding walk-ins and bookings entered after their scheduled visit time. It is not limited to bookings whose visit falls in that period.

The count labelled **same-day** means less than 24 hours ahead. It can include a booking made before midnight for a visit the following day. The figure measures advance notice rather than whether the guest attended.

## Estimated response time

**Response time (est.)** uses currently confirmed or denied bookings created in the selected period, excluding walk-ins. It measures creation to the booking’s latest recorded update, then shows the middle duration.

Later edits can increase that duration. Archived bookings are excluded. Treat the value as an estimate, rather than a precise timestamp of the first confirmation or rejection.

## Platform and market notes

These steps describe the mobile report. Booking counts and timing do not depend on currency. The selected period applies differently to each card; the nightly table-duration section uses its own displayed window.

## Troubleshooting

Use retry if the booking figures are replaced by an error. Refresh the report after checking the shop, period and saved booking statuses. A dash is unavailable data, not a confirmed zero; a missing warning does not establish complete records.

If a count seems wrong, check both the booking’s creation date and reservation date. Do not change booking status merely to improve a metric. Contact **Tapp support** if the recorded booking and report remain inconsistent.

## Related guides

* [Review booking capacity and table time](/en/overview/review-booking-capacity-and-table-time)
* [Manage booking status](/en/bookings/manage-booking-status)