> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/reports/operations-performance-overview/quality-and-defects.md).

# Quality & Defects

#### Quality & Defects

Where quality problems surface - defects, rework, reopens and peer-review failures - and who or what is causing them.

<figure><img src="/files/1ID0mPnDRxhIkFdBFPpp" alt=""><figcaption></figcaption></figure>

&#x20;                                                                *Quality & Defects tab.*

#### **KPI cards**

* **Defects Count -** total defects logged against the team's work in the period.
* **Work Items Reopened -** cases or actions sent back after being resolved, because the resolution wasn't accepted.
* **Work Items Reworked -** items flagged for rework at least once before being resolved.
* **Peer Review Failure Count -** number of times a reviewer found a problem. One item can fail more than once, so this can exceed the number of items reviewed.

#### **Visuals**

* **Defects Trend -** area chart of defects raised over time; drills month → week → day. A rising trend means quality issues are increasing.
* **Defects By Category** - donut breaking the period's defects down by category (e.g. incorrect data entry, missing documentation, process not followed), with the total in the center and each slice's count and share shown around the ring. Use it to see which types of defect dominate so you can target the right fix.
* **Party At Fault -** who was responsible for each defect (platform, agent, customer, third party) - shows where to focus improvement effort.
* **Defects By Queue -** defect counts per queue, split into resolved and unresolved. A large unresolved portion may point to a systemic problem in that queue.


---

# 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.enate.net/enate-help/work-manager/work-manager-2021.1/reports/operations-performance-overview/quality-and-defects.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.