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

# Various Rule: Per Day

The Per Day rule uses the entered rate and the calculated number of days to estimate the various amount.

$$
Amount = Days \times Rate
$$

Days are calculated differently depending on the entity the various item is created for.

* For **voyage**, the voyage duration is used: the difference between the voyage start date and the last port call’s departure date, and the estimated days are stored in the various item’s quantity
* For **cargo**, the voyage duration is also used
* For **downtime**, the offhire duration is used
* For **port call**, the duration between the arrival and departure dates is used.

***

{% hint style="warning" %}

### Important notes about the Per Day rule

* The various amount for each item is **updated** dynamically as the **voyage, downtime** or **port call** days change.
  {% 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-per-day.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.