---
title: "Browse and maintain requirements"
description: "Find standard requirements and create organisation-owned obligations."
url: https://helpcenter.complytrain.net/en/articles/145-browse-and-maintain-requirements
collection: "Requirements"
updated: 2026-09-22
language: en
---

# Browse and maintain requirements

Find standard requirements and create organisation-owned obligations.

Find standard requirements and create organisation-owned obligations.

For the relationship between a standard's published controls, requirement records and your organisation's operating controls, see [standards, requirements and controls](https://help.complytrain.net/en/controls/standards-requirements-controls/).

## Find the requirement

Product location: `/reqms/requirements`

Open **Requirements**, then **Requirement Explorer**. Filter by standard or source, scope, criticality and coverage. The default scope is in-scope requirements; clear or change filters when investigating a missing entry.

Enable a standard in QMS to see its requirements. Customer, vendor, internal and other sources allow organisation-owned requirements without selecting a standard.

## Create or clone

Product location: `/reqms/requirements`

Select **New requirement**, choose its source and enter its code and text. Add a clause reference, category, criticality, description, examples and verification guidance as appropriate. Record scope status and a justification for exclusions.

The source is fixed after creation. A clause reference is a display label; navigation uses the requirement code. Codes must be unique within the applicable scope.

System requirements are read-only. **Clone** creates an editable organisation-owned copy; it does not alter the original requirement. Review the new copy's identity before mapping documents to it.

## Retire deliberately

Product location: `/reqms/requirements`

**Deactivate** removes a requirement from scope, coverage and gap statistics while retaining its document mappings. Reactivation can restore those associations. Do not use deactivation merely to make a coverage measure look complete; record the actual reason the obligation no longer applies.
