> 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/cockpit/metrics-and-definitions/throughput/new-work.md).

# New Work%

{% hint style="info" %}
[<mark style="color:purple;">**Understand New Work, Rework, Maintenance through examples**</mark>](/using-hivel/coding/understanding-rework-new-work-and-maintenance.md)
{% endhint %}

**Total lines of code added or modified.**

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

* Low % of New Work indicates the team is trying to change old code even to build new features, which will impact the implementation of high blast radius and poor solid principles.\
  A **low percentage of New Work** means the team is often changing old code, even when building new features. This can lead to more bugs and make the code harder to manage. It may be a sign that the **architecture needs improvement**.\
  It's a signal to review the architecture.
* More New Work, along with slight [<mark style="color:purple;">Rework</mark>](/using-hivel/cockpit/metrics-and-definitions/quality/rework.md) and [<mark style="color:purple;">Maintenance</mark>](/using-hivel/cockpit/metrics-and-definitions/quality/maintenance.md) is always a good sign, as it indicates solid practices are in place, and the team can go ship new features at a faster pace as code is isolated.

#### Industry Benchmarking

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