> 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.6/voyage-management-system/step-by-step-guides/time-charter-contracts/maintain-time-charter-contracts/duration-and-rates/create-duration-and-rates.md). # Create Duration and Rates When creating a **Duration** you can enter **Duration** information in the fields and at the bottom you can see the current **Rates** on the **Duration.** Create requirements: At least one **Rate** added**.**

Create Duration Modal

If you want to add **Rates** to the **Duration** you can click the ![](https://content.gitbook.com/content/abKRDklBEhQhQ2rpVkHk/blobs/WvfsjSrxNs3Edb5ie0eQ/image.png)-icon in the upper right of the **Rates** Section to create a **Rate** on the **Duration.** This will open up a new **Create Rate** modal. Create requirements: **Tc Rate Duration**

Create Rate modal

After creating a Duration or a Rate you can click on the row in their respective lists to open their edit modals.

Edit Duration Modal with Delete button

Edit Rate Modal with Delete button

--- # 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.6/voyage-management-system/step-by-step-guides/time-charter-contracts/maintain-time-charter-contracts/duration-and-rates/create-duration-and-rates.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.