> 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-6.8/voyage-management-system/step-by-step-guides/voyages/create-voyage.md).

# Create Voyages

1. Open the **Voyages** module in the Core section.
2. Click the create icon<img src="https://798821541-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Liw6C9Fe7rohFtkU25j%2F-M23XjciEP9F3xdDeDrE%2F-M23aB95JDSUt7kYOdWo%2Fcreate-24px.svg?alt=media&amp;token=d69f2239-6a6c-48a4-ba17-ae0bb299c3d0" alt="" data-size="line">in the top right corner and select between "Voyage Charter", "Time Charter Out" or "Voyage From Template".
3. Fill in all required fields listed below in the Create Voyage window.
4. Click **Create**. A default cargo will be created for a Voyage Charter, and a default TC Out will be created for Time Charter Out

**Required fields:**

* Vessel
* Load Port / Delivery Port
* Discharge Port / Redelivery Port

{% hint style="info" %}
By default, new voyages have Voyage Progress set to "Estimate" and Voyage Status set to "T".
{% endhint %}

{% hint style="info" %}
When creating a Voyage Charter, a CoA template can be used for the cargo
{% endhint %}


---

# 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-6.8/voyage-management-system/step-by-step-guides/voyages/create-voyage.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.
