> 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-cleanup-coordinator.md). # \[ARCHIVE] Cleanup Coordinator As the cleanup coordinator, you will be responsible for facilitating the cleanup of the areas used for the event as it comes to a close. ## Cleanup Coordinator Checklist Let's ensure we are giving the host their space back in its original condition. These tasks can be delegated to others at the event, but it’s your responsibility to make sure it gets done. * [ ] **Clean the kitchen** * [ ] Collect dirty dishes from around the space * [ ] Load up dishwasher (if applicable), wash and dry dishes and pans used for cooking * [ ] It may be useful to assign a dish-washer, dryer, and person to put items away * [ ] Wipe down surfaces, stovetop, and sink * [ ] **Check the bathroom** to see if anything needs to be tidied up * [ ] **Tidy up the common spaces** where people were hanging out and/or eating * [ ] Move furniture or items back or original locations if anything was moved * [ ] Wipe down surfaces * [ ] Quick sweep as needed * [ ] **Check with Host to see if anything else needs to be done** --- # 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-cleanup-coordinator.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.