> 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.md).

# Time Charter Contracts

- [Create Time Charter In Contracts](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/create-time-charter-in-contracts.md): A Time Charter Contract records the agreed terms under which a vessel is hired for a defined period. Time Charter In contract must be created in Time Charter Contracts - module.
- [Internal TC Relet Creation](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/internal-tc-relet-creation.md): An Internal TC Relet links a TC Out contract to a corresponding TC In contract within the same organisation.
- [Maintain Time Charter Contracts](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/maintain-time-charter-contracts.md)
- [Duration and Rates](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)
- [TC Duration Details](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/tc-duration-details.md): A TC contract is built around one or more Durations, each representing a defined period with its respective terms during which a vessel can be employed.
- [Index-based Hire Rate](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/index-based-hire-rate.md)
- [Notices](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/maintain-time-charter-contracts/notices.md)
- [Comissions](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/maintain-time-charter-contracts/comissions.md)
- [Payment Terms](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/maintain-time-charter-contracts/payment-terms.md)
- [Speed & Consumption](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/maintain-time-charter-contracts/speed-and-consumption.md)
- [View Voyages](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/maintain-time-charter-contracts/view-voyages.md)
- [Print Statement of Account](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/print-statement-of-account.md): On all Time Charter Contracts it is possible to print the Statement of Accounts if there exists any documents related to the Time Charter Contract


---

# 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.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.