> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/quotes/why-cant-i-edit-a-quote.md).

# Why can't I edit a quote?

Quotes can be edited only while they're in Draft. Once a quote has been sent for signature (Unsigned), signed, expired, or voided, its contents are locked.

To change an Unsigned or Expired quote, choose **Revert to Draft** from the ... menu. The confirmation warns that this immediately makes the customer link unavailable and stops pending follow-ups. After making your changes, send the quote again.

For a Signed quote, choose **Void** from the ... menu first, then use **Revert to Draft**. (If a send fails to go out, the quote drops back to Draft on its own so you can fix it and try again.) The customer and property can never be changed, so if either is wrong, void the quote and create a new one.

> **Where to find it:** Open an Unsigned, Expired, or Void quote, then choose Revert to Draft from the ... menu at the top.

## Related guides

* [Generate a quote draft with AI](/revenue/quotes/generate-a-quote-draft-with-ai.md)
* [Quote statuses and lifecycle](/revenue/quotes/quote-statuses-and-lifecycle.md)
* [Why can't I save a quote?](/revenue/quotes/why-cant-i-save-a-quote.md)
* [Why can't I send a quote?](/revenue/quotes/why-cant-i-send-a-quote.md)
* [Add a line item to a quote](/revenue/quotes/add-a-line-item-to-a-quote.md)


---

# 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://learn.withessential.com/revenue/quotes/why-cant-i-edit-a-quote.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.