> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/using-monolith/settings/qa-issue-types.md).

# QA Issue Types

QA Issue Types provide a consistent way to categorize problems identified during Quality Assurance Reviews in Monolith.

Organizations can define Issue Types that reflect the kinds of exceptions, deficiencies, or review findings they want to track.

Examples might include:

* Compliance
* Data Acquisition
* Documentation
* Tool Validation
* Process Deviation
* Reporting
* Policy or SOP Violation
* Other organization-specific quality issues

### View QA Issue Types

The **QA Issue Types** settings page displays the Issue Types currently configured for your organization.

Each Issue Type also shows the number of QA entries currently associated with it.

Use this list to review the classifications available when documenting issues found during a QA Review.

<figure><img src="/files/IMevBP4m58IiApK5WL9x" alt=""><figcaption><p>View QA issue types</p></figcaption></figure>

### Create a QA Issue Type

To create a new QA Issue Type:

1. Select **Create Type**.
2. Enter the name of the new Issue Type.
3. Select **Create Issue Type** to save it.

The new Issue Type becomes available for supported Quality Assurance workflows throughout Monolith.

Choose names that clearly describe the type of problem being documented.

<figure><img src="/files/5zwVSbqq1kMRtnARJE0M" alt=""><figcaption><p>Create a QA Issue Type</p></figcaption></figure>

### Using QA Issue Types

QA Issue Types help standardize how review findings are categorized.

For example, a reviewer may identify an issue related to:

* Evidence handling
* Acquisition methodology
* Missing documentation
* Report content
* Tool validation
* Internal procedure
* Compliance requirements

Using consistent Issue Types makes it easier for teams to distinguish between different kinds of QA findings rather than relying only on free-text descriptions.

### QA Issue Types and QA Reviews

QA Issue Types are used as part of the Case-level Quality Assurance workflow.

During a QA Review, reviewers can document issues identified while checking work against the appropriate QA Checklist.

This allows the review record to preserve both:

* The checklist or review process being performed
* The type of issue identified during that review

See [**QA Checklist Items**](/monolith/using-monolith/settings/qa-checklist-items.md) for information about creating reusable Quality Assurance review checklists.

### Delete a QA Issue Type

QA Issue Types can be deleted when they are no longer needed.

Before deleting an Issue Type, review whether it is still being used by existing QA records and whether the classification should remain available for future reviews.

<figure><img src="/files/Vhf2uACkut0ZiHpjec5n" alt=""><figcaption><p>Delete QA Issue type</p></figcaption></figure>

### Recommended Practices

* Create Issue Types that represent meaningful categories of QA findings.
* Keep names clear and consistent across the organization.
* Avoid creating duplicate or overlapping Issue Types.
* Use categories broad enough to remain useful across multiple review workflows.
* Review Issue Types periodically as quality procedures and organizational requirements change.
* Coordinate QA Issue Types with your QA Checklists so reviewers have consistent ways to classify findings.

### Related Documentation

* [**QA Checklist Items**](/monolith/using-monolith/settings/qa-checklist-items.md)
* [**Cases**](/monolith/using-monolith/case-management/cases.md)
* [**Tasks**](/monolith/using-monolith/dashboard/tasks.md)