> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/booths/booth-statuses.md).

# Booth statuses

Every booth in Vendor Space has a status that tells you its current state at a glance. Statuses help you track availability, manage assignments, and plan your event layout.

## Status Overview

| Status        | Meaning                                                                                          | When It's Used                                                                                                                                     |
| ------------- | ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Available** | The booth is open and ready to be assigned to a vendor.                                          | Default status when a booth is first created. Also returns to this status when a vendor is unassigned.                                             |
| **Reserved**  | The booth is being held for a specific purpose or vendor but has not been formally assigned yet. | Use this when a vendor has expressed interest or you want to hold a booth temporarily while finalizing details.                                    |
| **Assigned**  | A vendor has been assigned to this booth. The space is taken.                                    | Set automatically when you [assign a vendor](/docs/booths/assigning-vendors-to-booths.md) to the booth.                                            |
| **Blocked**   | The booth is unavailable and cannot be assigned to anyone.                                       | Use this for booths that are out of service, reserved for event operations (sound equipment, emergency exits), or otherwise off-limits to vendors. |

## How Statuses Change

Some status changes happen automatically, and others you set manually:

* **Available to Assigned:** Happens automatically when you assign a vendor to the booth.
* **Assigned to Available:** Happens when you remove a vendor from the booth.
* **Available to Reserved:** Set manually when you want to hold a booth.
* **Reserved to Assigned:** Happens when you assign a vendor to a reserved booth.
* **Any status to Blocked:** Set manually to take a booth out of circulation.
* **Blocked to Available:** Set manually when the booth becomes usable again.

> **Tip:** Use the **Reserved** status sparingly and for short periods. Too many reserved booths can make it look like you have less inventory than you actually do.

## Using Statuses to Manage Your Event

### Checking Availability

Filter your booth list by **Available** status to see exactly how many booths you can still sell or assign. This is the quickest way to answer the question "How many booths do we have left?"

### Planning Your Layout

Use a combination of statuses to plan your floor:

* **Blocked** booths mark areas that can't be used (walkways, stages, utility areas).
* **Reserved** booths hold spots for VIP vendors or sponsors who are still confirming.
* **Available** booths are your open inventory.
* **Assigned** booths show where confirmed vendors will be.

### Tracking Progress

As your event approaches, the ratio of statuses tells you how your booth sales are going:

* Mostly **Available**: Still early in the process or more outreach needed.
* Mix of **Assigned** and **Available**: Good progress, keep going.
* Mostly **Assigned** with a few **Available**: Nearing capacity.
* All **Assigned** or **Blocked**: Fully booked.

> **Tip:** Keep booth statuses up to date as things change. Accurate statuses give your team a reliable, real-time view of your event layout and help prevent double-booking or missed opportunities.


---

# 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://vendorspace.gitbook.io/docs/booths/booth-statuses.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.