> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/duration-timeinterval.md).

# Duration (Timeinterval)

Store an elapsed time span such as hours worked or response time.

Use a **Duration** field when the record should store a time span instead of a clock time or a date.

This works well for values such as hours worked, estimated effort, response time, or other elapsed time values.

For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).

Field-specific settings for **Duration** are:

#### Everywhere

* **Default value**:
  * Enter a static value directly in the field
  * <i class="fa-code-simple">:code-simple:</i> **Edit dynamic value** next to the field opens the logic editor where you can add or edit the logic for that setting. After you save the script, Ninox shows the first line of the script instead of the static value field. To switch back to a static value, click <i class="fa-xmark">:xmark:</i> **Remove dynamic value** on the right.

**Display**

* **Duration format**: controls how the duration is displayed
  * a mixed day-and-time value, with optional seconds or milliseconds
  * a total in days, hours, minutes, seconds, or milliseconds
  * a rounded or more precise value, depending on the selected format

{% hint style="info" %}
Use **Duration** for elapsed time. Use **Time** for a clock time. Use **Appointment** when you need a timestamp for start and end.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/duration-timeinterval.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.