> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/other/archived-pages/archive-social-and-community-events-guide/archive-event-role-checklists/archive-host.md).

# \[ARCHIVE] Host

As the host, you are responsible for providing a clean and welcoming space in which to hold the upcoming campaign event.

## Host Checklist

* [ ] **Confirm that you have enough plates, silverware, and space** to host a large number of people
  * [ ] If you don’t have enough plates and utensils, let the organizer know and attendees will be asked to bring their own. Let’s try to avoid disposables wherever possible
  * [ ] You can check on the rough headcount by seeing how many people have signed up to join via the [Volunteer Sign-Up](https://volunteersignup.org/LBJQB) event. Plan on having \~25% more attendees than sign-ups
* [ ] **Provide cleaning materials** for post-event cleanup
  * [ ] Broom or vacuum to clean the floors
  * [ ] Multipurpose spray/disinfectant to wipe down surfaces in the kitchen, common areas, and bathroom(s)
  * [ ] Paper towels or rags
* [ ] **Make sure your space is recreational drug free**
  * [ ] No drugs, drug paraphernalia, or alcohol should be visible
  * [ ] No offers for beers or drinks
* [ ] **Invite a few community members personally**
  * [ ] While promotion is a separate role, personal invites from the host are especially meaningful!
  * [ ] Your message can say something like: “Hey Susie, I’m hosting a social for the pro-animal campaigns at my house next Saturday, I’d love to see you there if you can make it!”


---

# 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://handbook.proanimal.org/other/archived-pages/archive-social-and-community-events-guide/archive-event-role-checklists/archive-host.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.
