> 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/metrics-and-definitions/quality/rework.md).

# Rework

{% 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 %}

### **Rework %**

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

**Rework %** measures the number of changes made to code in the last 30 days.\
If the change is made to a code older than 30 days, it is automatically classified as [<mark style="color:purple;">maintenance</mark>](/metrics-and-definitions/quality/maintenance.md). (30 days is the default setting, you can configure it based on your internal process by going to **Settings -> Configuration**)

* Low rework means the code changes aren't done after the initial work, which indicates that the developers are pushing high-quality code the first time.
* High rework rates are caused by PR feedback, QA feedback, or an engineer trying to improve the code after committing. Too many changes.

#### Industry Benchmarking

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

#### Related article

{% content-ref url="/pages/qu0kVyU7JQHrt0tLerxk" %}
[What to do if my Rework is high?](/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high.md)
{% endcontent-ref %}