> 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="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2F26TpaG3A28JGzusr7JGE%2Fimage.png?alt=media&amp;token=0fcdc105-d627-4405-afd7-c6abe29f1cc2" 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.