> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/banquet/banquet-module/queries/banquet-status.md).
# Banquet Status
The **Banquet Status** menu is used to view and generate banquet booking status reports for a selected date range.
## Steps to View Banquet Status
Step 1: Navigate to the **Banquet** module and select **Queries** menu.
1. Click on **Banquet Status** from the menu list.
* After selecting the menu, the Banquet Status screen will open.
Step 2: Select the required **Date** or **Date Range**.
1. Click on the **Display** button.
* The system will display the banquet status details for the selected date.
Step 3: Use Advanced Search Filters
1. Click on the **Advanced Search** button.
2. The filter section will open.
Step 4: After applying the required filters:
1. Click on the **Display** button.
2. The system will generate and display the report on the screen.
* The report will contain all banquet booking details based on the selected criteria.
Step 5: Once the report is displayed:
* Click on the **Print** button to print the report.
* Click on the **Excel** button to export the report in Excel format.
This allows users to save, share, or print the banquet status report for future reference.
---
# 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://help.rbsgo.com/banquet/banquet-module/queries/banquet-status.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)