> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/troubleshooting/data-quality-issues.md).

# Data Quality Issues

### Overview

Data quality issues reduce trust in reporting and slow delivery work.

Common causes include inconsistent statuses, missing Segment assignments, and inconsistent naming.

### Key Concepts

* **Data integrity**: correctness and completeness of work item fields
* **Consistency**: stable meanings across Projects for statuses and segments
* **Governance**: standards that keep reporting reliable over time

### How It’s Used

Use this page during rollout when importing or standardizing data.

Use it during governance when reporting signals drift.

### Benefits

* More reliable dashboards and pivot tables
* Faster governance meetings with fewer debates about accuracy
* Reduced rework caused by ambiguous statuses and fields

### Setup Steps

{% stepper %}
{% step %}

### Identify the failure pattern

Common patterns include:

* missing Segment values in lists
* inconsistent status meaning across teams
* duplicate items created during imports
* fields left blank that should be required
  {% endstep %}

{% step %}

### Validate segmentation and scope

1. Confirm Segment Types are defined at the Organization level.
2. Confirm Segments exist for the intended reporting breakdown.
3. Apply Segments consistently across requirements and tasks when used for reporting.
   {% endstep %}

{% step %}

### Standardize statuses

1. Define entry and exit criteria for each status.
2. Apply meanings consistently across Projects when possible.

Related: [Status Types and Meanings](/transformations/status-types-and-meanings.md)
{% endstep %}

{% step %}

### Create repair views

Create Save Views that surface records needing cleanup, such as:

* `Segment is empty`
* `Status is Blocked`
* `Owner is empty`
  {% endstep %}
  {% endstepper %}

### Best Practices

* Keep Segment Types stable to protect analytics continuity.
* Keep shared fields minimal and clearly defined.
* Use Save Views for ongoing data hygiene.

### Summary

Data quality improves most from stable governance standards, consistent segmentation, and repeatable cleanup views.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/troubleshooting/data-quality-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.