> 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/election-day-guides/closing-polls.md).
# Closing Polls
* [ ] Insert the poll worker card
* [ ] Select *`Close Polls`*
* [ ] One copy of the polls closed report will print
* [ ] Tear to remove the report
Insert poll worker card
Select Close Polls
* [ ] Select *`Reprint Polls Closed Report`* to print more reports as necessary
* [ ] Remove the poll worker card
Select Reprint Polls Closed Report
Remove the poll worker card
* [ ] Unseal and document the poll worker door seal as required
* [ ] Open the poll worker door
* [ ] Remove the USB drive from the poll worker door and secure as required
unseal and document interior panel
remove the USB drive
The polls are now closed. Below is an example of the polls closed report.
---
# 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/election-day-guides/closing-polls.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.
