> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/how-to/how-to-mark-a-proposal-as-lost.md).

# How to Mark a Proposal as Lost

When a customer decides not to proceed with a proposal, follow these steps to update the status and record the reason for marking a proposal as lost.

1. In **EKR**, from the Proposal section, open the **Proposal**.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FCYF1hwV9eNhYuultfoZI%2Fimage.png?alt=media&amp;token=ee3cc265-eeac-4857-bf8f-5b2ecbacabda" alt="" width="563"><figcaption></figcaption></figure>

2. Ensure all current line items and customer details are correct before changing the status.
3. Click the button to begin the cancellation process.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FXlPz1QS0wM9z8ziGyEvF%2Fimage.png?alt=media&amp;token=724b5d98-1b32-4d58-b75b-c1c3fa0d88e7" alt="" width="563"><figcaption></figcaption></figure>

4. A Reason dialog box will automatically appear. Click on the **Please enter a reason...** field.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FM86ppDyba6v0OIxE2OQY%2Fimage.png?alt=media&amp;token=2c20cd54-72ea-4f01-8a81-aed20a9d31a6" alt="" width="563"><figcaption></figcaption></figure>

5. Type in an explanation for why the proposal will not be converted to an Agreement.
6. Click the **Submit Reason** button to continue.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FMMGI8N3YnLABWPwJzmSH%2Fimage.png?alt=media&amp;token=5a289f87-7c92-4088-b259-a8e7585aadbb" alt="" width="563"><figcaption></figcaption></figure>

7. Once submitted, a red Lost badge will appear in the proposal header, displaying the reason provided.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FPiDzb9Iuc1zuCHlxRf7k%2Fimage.png?alt=media&amp;token=6f0d483a-865b-44bd-a5f4-894024726453" alt="" width="563"><figcaption></figcaption></figure>

7. A confirmation message stating "Successfully saved proposal" will appear in the top-right corner.


---

# 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.biscit.com/ekr-user-guide/how-to/how-to-mark-a-proposal-as-lost.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.
