> 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/warranty-model.md).

# Warranty Model

## Estimated Replacement Rates

| <p><br></p>                    | VxScan (incl ballot box) | VxAdmin  | VxCentralScan | VxMarkScan |
| ------------------------------ | ------------------------ | -------- | ------------- | ---------- |
| Estimated Replacement Rate     | 10 years                 | 10 years | 10 years      | 10 years   |
| Estimated Cost Per Replacement | $7,500\*                 | $2,500\* | $2,500\*      | $7,500\*   |

\*Costs quoted here reflect 2024 costs. VotingWorks expects prices to increase over time, in line with US inflation rates.

## Estimated Warranty Types and Costs

VotingWorks requires all voting equipment customers to purchase our Technology Repair, Upgrade, Support and Training (“Trust”) Services. TRUST Services will cover warranty for all products purchased. Average annual cost of TRUST Services will not exceed 5% of the equipment purchase price for years 1-10.

## Associated Replacement Policies, Services, and Available Maintenance Agreements

A sample TRUST Services Agreement is available [here](https://github.com/votingworks/docs-vxsuite-v4/blob/main/warranty-model/TRUST_Services_Agreement.pdf).

## Plans for Collecting, Maintaining, and Reporting Data to the EAC to Support and Validate Estimates

VotingWorks will continually collect data on warranty usage at the product level and compile such data into reports. VotingWorks will share this data with the EAC at least every two years.


---

# 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/warranty-model.md?ask=<question>&goal=<user_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.