> 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/master-data/various-costs-and-revenues/various-items-rules/various-rule-onhire-days.md).

# Various Rule: Onhire Days

The on-hire days rule calculates the total various amount similar to the Voyage - Per Day rule, but instead of using total voyage days, the days excluding total downtime intervals are utilized: 

$$
Amount = (Total Voyage Days - Total Offhire Days) \times Rate
$$

For example, consider a voyage with port calls A and B that takes 10 days in total. Assume the following downtime intervals are recorded:

* Port Call A: 1 day
* Port Call B: 2 days

Total offhire time is 1 + 2 = 3 days, so the onhire days used by the rule are 10 − 3 = 7 days.

***

{% hint style="warning" %}

### Important notes about the Onhire rule

* The various amount for each item is **updated** dynamically as the **voyage** or **downtime days change**.
* This rule is currently **only** available for **Voyage** various
  {% endhint %}


---

# 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/master-data/various-costs-and-revenues/various-items-rules/various-rule-onhire-days.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.