> 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-7.8/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/voyage-functionalities/change-voyage-status.md).

# Change Voyage Status

From the voyage drawer it is possible to change the status of the voyage by using the status chip next to the reference no at the top of the drawer.

### **From Estimate to Allocate:**

When changing status from estimate to Allocate, the following modal will show, where you have to select the vessel, and if you want, you can manually change the position. It will by default be put last.

<img src="https://content.gitbook.com/content/x9ICCwvAr5T5HIPaqMYk/blobs/S83B28zHepApMXyVsaZa/Screenshot%202022-08-26%20at%2008.49.16.png" alt="" data-size="original">

### **From Estimate to Nominated:**

When changing status from Estimate to Nominated, the following modal will show. If it is a TC voyage with missing laycan on the TC, you will have to fill in the layCan as well.

![](https://content.gitbook.com/content/x9ICCwvAr5T5HIPaqMYk/blobs/pQLRsAzXLpLOehZJCnIG/Screenshot%202022-08-26%20at%2010.40.44.png)

The nominating process will also change the *booking status* of all of the cargoes on the voyage to 'Clean Fix'.


---

# 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.dataloy.com/release-7.8/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/voyage-functionalities/change-voyage-status.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.
