> For the complete documentation index, see [llms.txt](https://docs.voting.works/vxsuite-tdp-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-tdp-v4/readme/vxadmin-results-exports/ballot-count-reports.md). # Ballot Count Reports Ballot count reports contain ballot and ballot sheet counts, not contest results. If there are multi-sheet ballots in the election, the sheet counts (e.g. "Sheet 1", "Sheet 2") can be added to the report in the ballot count report builder by selecting "Sheet" as a `Report By` dimension. The total ballot count is always defined as the first sheet count. If there are manual results, the manual ballot count will always be displayed separately from the scanned ballot count, and the total of the two will also be displayed. When grouping is applied in a ballot count report, each group corresponds to a row in the table. In the following example, the ballot counts are grouped by both precinct and voting method:

The following metadata columns may appear in a ballot count report table in order to specify groupings:

Header	Values
Precinct	The name of the precinct
Ballot Style	The internal identifier of the ballot style
Party	The short name of the party, e.g. "Democrat". Included by default if the ballot style is included, in a primary
Voting Method	"Precinct", "Absentee", or "Provisional"
Scanner ID	The serial number of the scanner. Included by default if the batch is included
Batch	The label for the batch, or "Manual Tallies" for manually entered data

Filters apply to the entire report. Simple filters are shown in the title, while complex filters are listed in a box below the title.

Ballot count report with a complex filter

--- # 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-tdp-v4/readme/vxadmin-results-exports/ballot-count-reports.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.