> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/using-hivel/investment/work-item-age.md).

# Work Item Age

**Work Item Age** is a key metric that provides insight into how long it takes for a team to resolve a ticket/item, from its creation to its completion.

{% hint style="info" %}
**Formula:**

Work Item Age = Completion Date - Creation Date
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/BTtAdkv87WVAJBQDcMd8" alt=""><figcaption></figcaption></figure></div>

#### **Example**:

* **Creation Date**: August 1, 2024
* **Completion Date**: August 5, 2024
* **Work Item Age**: 4 days

#### Why Is Work Item Age Important?

Work Item Age is a critical metric for several reasons:

* **Team Efficiency**: A lower Work Item Age indicates that your team is resolving issues quickly, which is a sign of efficiency. A higher Issue Age might suggest bottlenecks or delays in the workflow that need to be addressed.
* **Customer Satisfaction**: For customer-facing teams, reducing Work Item Age is essential. Faster resolution times lead to higher customer satisfaction and a better overall experience.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hivel.ai/using-hivel/investment/work-item-age.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.