> 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-supplies-checklist.md). # \[ARCHIVE] Event Supplies Checklist This section provides a checklist of the materials that should be brought to each event. It is typically up to the Organizer or Workstation Director to coordinate these with the Campaign Lead. ## **General Supplies Checklist** * [ ] Name tags * [ ] Sharpies * [ ] Extra plates * [ ] Extra silverware * [ ] Laptop and/or tablet (for Zoom participants and shift sign-ups) ## **Work Supplies Checklist** Make sure the appropriate supplies are brought to the event based on the work task you’re looking to accomplish. It’s a good idea to set a goal for what you’d like to get accomplished at the event so you can bring the appropriate quantities (bring extras, just in case!). ### **Petitioner Kits**: * [ ] Petition packets * [ ] Pens * [ ] Staplers * [ ] Staples * [ ] Manuscript covers * [ ] Clipboards * [ ] Printed posters * [ ] Tape * [ ] Laminator * [ ] Laminator sheets ### Buttons: * [ ] Button maker * [ ] Printed button sheets * [ ] Protractor blade * [ ] Button covers * [ ] Button pin backings * [ ] Mylar sheets ### Deep Canvassing Items: * [ ] Phone number lists (for text banking) * [ ] Printed leaflets to fold * [ ] Rulers * [ ] Stencil paper --- # 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-supplies-checklist.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.