Add an external requirement

Last updated August 25, 2026

An external requirement is a rule you did not write and cannot change: ISO 9001 itself, the Machinery Directive, a customer's supplier quality manual. Clause 7.5 expects you to know which ones apply, which edition, and where they are answered in your own documents.

Reading the register needs read_external_requirements. Adding one needs create_external_requirements.

Registering one

The edition matters as much as the title. "EN 60204-1" is not a requirement until you say which edition you are held to - that is what makes a superseded version detectable later.

The register requirement dialog with fields for title, issuing body, version, validity dates and source URL.
Title, issuing body and edition are what identify a requirement. The source URL is where the next person finds the actual text.
  1. Open External Requirements and register a requirement.

  2. Give it the code and title as the issuing body writes them, not an internal nickname.

  3. Record the issuing body and the edition or version.

  4. Set the validity dates and the owner - the person who answers for it here.

  5. Set the next review date. A requirement with no review date is one nobody will revisit.

What the register tells you

The list is the working view: status, when each requirement was last confirmed and how many of your documents answer it. The counters across the top are the ones worth watching.

The external requirements list showing code, issuing body, version, validity, next review, linked document count and status.
Overdue reviews are red, ones falling due are amber, and the linked-documents column is how you tell a live requirement from a filed one.
  • Active is what applies today; obsolete is kept for traceability, not deleted.

  • Pending review means the requirement changed or is being checked - it is not a filing state.

  • A requirement linked to no documents is either new or unanswered.

Next: review a requirement on schedule.

Was this article helpful?