> 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/chartering/time-charter-contracts/maintain-time-charter-contracts/duration-and-rates.md).

# Duration and Rates

In the **Durations and Rates** tab you will see two main section&#x73;**;**

* &#x20;**Durations**, which includes create-button and a list of the durations of the Time Charter Contract (TC)
* &#x20;**Duration and Rates** which includes a list of the **Rates** along with the connected **Duration** of the TC

<figure><img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/U8hqb4HFfSeJSlCtjlW3/Screenshot%202026-03-30%20at%2013.13.07.png" alt=""><figcaption><p>New Durations and Rates layout introduced in v8.25</p></figcaption></figure>

From version v8.25, both of these lists are turned into a grid, which means you can now use [all of these functionalities](/release-8.31/voyage-management-system/step-by-step-guides/data-grids.md).&#x20;


---

# 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/chartering/time-charter-contracts/maintain-time-charter-contracts/duration-and-rates.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.
