> 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.0/voyage-management-system/step-by-step-guides/offhire/maintain-offhire/panel-fields.md).

# Overview

Offhire Drawer Overview tab

The top section of the overview tab contains key information about an offhire.

![](https://content.gitbook.com/content/xZZB7hXaO8vn7fv5p6Tx/blobs/LeK0gG8OgkPa3lrvhMEg/Skjermbilde%202023-08-09%20kl.%2010.20.41.png)

**Main Details and Days** 

The *Main Details* and *Days* sections contain fields used to update an offhire. These fields include those used to [create an offhire](/release-7.0/voyage-management-system/step-by-step-guides/offhire/create-offhire.md#required-fields), as well as the following: 

| **Field**    | Description                                       |
| ------------ | ------------------------------------------------- |
| Planned      | Indicates whether the offhire period was planned  |
| Offhire Days | Length of offhire period                          |
| Percentage   | Percent of offhire period included in calculation |

![Main Details, Days and Result Impact Sections](https://content.gitbook.com/content/xZZB7hXaO8vn7fv5p6Tx/blobs/ingwAGrsopwQod0MCeT3/Skjermbilde%202023-08-09%20kl.%2010.22.52.png)

**Result Impact** 

In this section, there are two checkbox that indicate whether the offhire should be deducted from the charterer, owner or opex. The *Deduct from hire receivable (charterer)* checkbox is only active if the offhire's voyage is a Time Charter. These field will also activate the corresponding bunker consumption table for editing.

**Bunker Consumption Tables**

Two tables show information about bunker consumption for the charterer and the owner/opex. Each table contains 4 rows with information about the quantity and bunker price for each bunker type (FO, LS FO, LS MGO, MGO).

![Bunker Consumption Tables](https://content.gitbook.com/content/xZZB7hXaO8vn7fv5p6Tx/blobs/ab67XoIcBcaeVKIcdeVI/Screenshot%202021-04-13%20at%2009.52.59.png)

{% hint style="info" %}
If the offhire period in on a time-charter-in voyage, the second table will show the owner's bunker consumption. Otherwise it will show the opex's bunker consumption.
{% endhint %}

**Adding/Editing quantity and bunker price**

1. Click on a bunker type row.
2. Change the fields in the Edit Bunker Consumption window.
3. Click **Confirm**.

![Add/Edit Bunker Type Price and Quantity](https://content.gitbook.com/content/xZZB7hXaO8vn7fv5p6Tx/blobs/1BMw7ZSFtOi3uMT7IyK0/Skjermbilde%202023-08-09%20kl.%2010.23.43.png)

**Comment**

At the bottom of the Overview tab, there is a small section for adding a comment to the Offhire. 


---

# 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.0/voyage-management-system/step-by-step-guides/offhire/maintain-offhire/panel-fields.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 `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.