> 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.13/voyage-management-system/step-by-step-guides/voyages/create-voyage/create-voyage-charterer.md). # Create Voyage Charterer ### Steps: 1. Open the **Voyages** module from the menu on the left. 2. On the top right corner, click the icon. 3. Select **Create Voyage Charterer**. 4. In this modal, you can have *two* options: a. you can **fill in** the required fields and **add** any additional information about the new voyage b. you can choose the **Use CoA Template Cargo** button, which will link to the same modal as described here: [Create Cargo From CoA Template](/release-6.13/voyage-management-system/step-by-step-guides/cargoes/create-cargoes/create-cargoes-from-templates.md). 5. After you have filled in or chosen a CoA Template for the cargo information, you can click **Create**. #### **Required fields:** * Vessel * Load Port * Discharge Port ### The modal:

Create Voyage Charterer modal

### Features: * After choosing a vessel, you will now be able to choose a Ballast Port. * The modal is now *draggable*, making it easier to see the information "behind" the modal. Hover over the title or the top of the modal to activate it. --- # 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-6.13/voyage-management-system/step-by-step-guides/voyages/create-voyage/create-voyage-charterer.md?ask=&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.