> For the complete documentation index, see [llms.txt](https://docs.voting.works/vxsuite-user-manual-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voting.works/vxsuite-user-manual-v4/checklists/overview.md). # Overview Checklists are provided to help users walk through all of the steps to prepare, conduct, and complete an election. New Hampshire specific checklists can be found here: [New Hampshire Checklists](https://docs.voting.works/nh-checklists)
ChecklistTimeline
Pre-Election Setup ChecklistComplete after the election package has been downloaded or received from VotingWorks and prior to conducting L&A Testing.
L&A Testing ChecklistComplete as soon as possible after receiving the election package and no later than required by law or rule.
Poll Worker ChecklistComplete these tasks during early voting and/or on election day.
Election Night ChecklistComplete these tasks election night or no later than any final certification deadline required by law or rule.
--- # 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://docs.voting.works/vxsuite-user-manual-v4/checklists/overview.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.