> 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/transaction/faq-on-reservation/how-are-department-aids-assigned-to-a-banquet-reservation.md).

# How are Department Aids assigned to a banquet reservation?

To assign Department Aids to a banquet reservation, you must enter them during the reservation creation process under the Transactions menu. The specific steps are as follows:

1\. Navigate to Reservation under the Transactions menu and click New to start a new entry or select an existing one to edit.

2\. Within the reservation screen, click on the Venue tab.

3\. Locate the field labeled Department Aids and enter the specific requirements for the event. This field is typically grouped with other venue-specific details such as the seating arrangement and event start/end times.

4\. Once you have completed all the necessary details across the different tabs (Guest Info, Venue, F\&B, etc.), click the Save button to finalize the reservation and successfully assign the aids.

For these aids to be available for selection, they must first be defined in the Masters menu under Aids, where they are linked to specific Departments and Aids Groups.


---

# 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/transaction/faq-on-reservation/how-are-department-aids-assigned-to-a-banquet-reservation.md?ask=<question>&goal=<user_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.