> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/delete-voyages.md).

# Delete Voyages

Only voyages of status "Estimate" and "Unallocated" can be deleted. Otherwise you must change the status before you can delete.

1. Find a voyage (i.e through the **Voyages** page).
2. Click to open the voyage you want to delete.
3. At the upper right corner of the panel, click **Delete**<img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/VOOA3uSoa3Xqx4qgh8Wt/delete.svg" alt="" data-size="line">.
4. Click **Confirm** to delete the voyage.

Voyages can be connected to Cargoes and/or Offhires, as well as scheduled voyages if the voyage is a template.

When attempting to delete a **template voyage** that has scheduled voyages either at the Nominated or later stages, an error message will show instead.

The delete-voyage modal will look differently depending on whether it has connected entities:&#x20;

* **No connections:**

<figure><img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/tiXffqO0L2yuuMNaMdnC/image.png" alt=""><figcaption><p>Plain delete modal with no alerts due there not being any connected offhires or cargoes.</p></figcaption></figure>

* **Only Offhire connection:**

<figure><img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/xxIn3MvOJMMVhI46xUX3/image.png" alt=""><figcaption><p>Alert showing that an offhire is connected and will be deleted.</p></figcaption></figure>

* **Only Cargo connection:**

<figure><img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/jtQ4idgMQq0OKiUCSS8d/image.png" alt=""><figcaption><p>Alert showing that an cargo is connected and will be deleted.</p></figcaption></figure>

* **Offhires and Cargoes:**

<figure><img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/GQHDs72cY09h5gg1RRCF/image.png" alt=""><figcaption><p>Alert showing that an offhire and a cargo is connected and will be deleted.</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/delete-voyages.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 `build a script that syncs our docs to a CMS` 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.