> 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-5.44/voyage-management-system/step-by-step-guides/voyages.md).
# Voyages
## Voyage drawer
To open the voyage drawer, go to the **Core**
**Voyages** module.
### Summary
The top of the voyage drawer "Overview" tab has four summary cards for TCE, total days, hire costs and bunker costs.
Click **See More** to open detailed charts for the numbers in the summary.
#### Result
The "result" chart is a waterfall chart for costs and revenue on the voyage. Hover the mouse over the bars to see further details behind the calculation.
#### Days
The "days" chart has a timeline chart for the port calls on the voyage and a table of the total days on voyage.
The port calls timeline shows the days at sea and days in port. It also shows the names of the ports above the bars. Hover the mouse over each bar to see more information.
---
# 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-5.44/voyage-management-system/step-by-step-guides/voyages.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 `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.