> 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/mark-results-as-official.md).
# Mark Results as Official
{% hint style="info" %}
The following steps must be completed by an election manager.
{% endhint %}
When you are ready to certify election results, you can mark VxAdmin results as official to print official reports.
{% hint style="warning" %}
Make sure that you've imported all CVR files, completed all adjudication, and added all manual tallies before proceeding.
{% endhint %}
To mark results as official, select *`Reports`* from the side menu and select *`Mark Election Results as Official`.*
Confirm by selecting *`Mark Election Results as Official`.*
All references to unofficial results in VxAdmin will be changed to official.
If you become aware of a mistake after marking results as official (say, you forgot to import one machine's CVRs), you can revert the results to unofficial as a system administrator. Log in as a system administrator and use the *`Revert Election Results to Unofficial`* button.
Log out and log back in as an election manager to make the necessary edits and be sure to remark the results as official once done.
---
# 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/mark-results-as-official.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.
