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

# Bookings on the handset

> Your own bookings, read live — what is coming up, what each one holds, and releasing or deleting one.

The **Bookings** screen lists the bookings you made and the ones somebody made for you, so you can check from the floor that what you booked is still held, and release or delete a booking you no longer need.

> [!NOTE]
>
> If you don't see this in your navigation, your administrator can switch the module on under **Administration → Modules**, or it may not be included in your plan. You also need permission to see bookings.

Open it from **Home → Bookings**. Bookings are made in the web app; see [bookings](https://docs.assetinfinity.ai/assets/bookings.md). The handset does not make new ones.

## The list

The heading says **Made by you, or made for you.** Bookings are split into two groups:

| Group | What is in it |
| - | - |
| **Coming up** | Bookings whose window has not ended yet, soonest first. A booking you are in the middle of still counts as coming up |
| **Earlier** | Bookings whose window is over, latest first |

Each row shows the booking's title (or its number where it has no title), then its number, site and window, then its status and what it holds. What it holds is drawn as a count beside an icon for each kind of line: tools, assets, places and people.

The status uses the same words as the web app's register:

| Status | What it means |
| - | - |
| **Awaiting approval** | Requested and waiting for somebody to approve it |
| **Booked** | Booked |
| **Confirmed** | Confirmed |
| **Out** | Issued — what it holds has been handed out |
| **Back** | Returned |
| **Settled** | Closed off |
| **Released** | Released before it was used |
| **Never collected** | Nobody came for it |
| **Created by mistake** | Released because it was made by mistake |

The refresh button reads the list again. You see your most recent 200 bookings; past that, the screen says **Only your most recent bookings are shown. The rest are in the web app.** With no bookings it says **You have no bookings**.

## One booking

Tap a booking to open it. The panel shows its status, **When**, **Site**, and how many **Tools**, **Assets**, **Places** and **People** it holds. A released booking also shows **Released** with when and why. **← Bookings** goes back to the list, and the refresh button reads the booking again.

Two buttons appear under it where they apply:

| Button | When it is offered | What it does |
| - | - | - |
| **Release this booking** | You may edit bookings, and the booking is not already released, settled or never collected | Opens **Release this booking?** — see below |
| **Delete booking** | You may delete bookings, and nothing on the booking has been checked out or recorded against it yet | Opens **Delete this booking?** |

### Releasing a booking

**Release this booking?** asks:

| Field | What it means | Notes |
| - | - | - |
| **Why** | The reason you are releasing it | Required |
| **Created by mistake** | Tick it when the booking should never have been made | **No short-notice fee and no release notice. Left out of the utilisation and cancellation figures.** |

**Release it** sends it. Without the tick, the booking stays on your list as **Released** with your reason, and your organisation's release rules apply, which may include a release notice or a short-notice fee. With the tick, you go back to the list.

### Deleting a booking

**Delete this booking?** explains that **The booking and its lines will be removed. Reserved stock goes back into what's available. There's no fee and no notice.** Choose **Delete booking** to remove it, or **Keep it** to leave it. Once a booking is deleted it is gone from the list.

If the server refuses either one, the sheet shows the reason in its own words.

> [!NOTE]
>
> **Bookings need a connection.** Bookings are read live, because what is held for you can change while you are on your way. Nothing is kept on the handset, so without a signal the screen says **No signal** and offers **Try again**. Releasing and deleting are not queued for later either. Without a signal both buttons stay on the screen, greyed, with **Needs a connection** under them. If the signal drops while you are sending, the sheet says **No signal, so nothing was changed. Try again when you have one.**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.