> 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-night-guides/manual-tallies.md).
# Manual Tallies
{% hint style="info" %}
The following steps must be completed by the Election Manager.
{% endhint %}
To enter tallies manually, select *`Tally`* from the side menu and then select the *`Manual Tallies`* tab.
Enter the Ballot Style, Precinct, and Voting Method of the ballots being added and select *`Enter Tallies`*. This step will be repeated for any additional ballot styles, precincts, and voting methods.
Start by entering the manual tally ballot count. By default, the manual tally ballot count is the same for all contests but can be overridden on a per-contest basis.
Then enter vote tallies for the first contest, entering undervotes and overvotes in addition to votes cast for each candidate or option. If a vote is for a write-in candidate, select *`Add Write-In Candidate`* to enter the name found on the ballot and add a tally. Select *`Save & Next`* to proceed to the next contest and repeat steps for all contests. Select *`Finish`* after entering vote tallies for the last contest.
---
# 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-night-guides/manual-tallies.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.
