logo
language iconarrow
menu icon

Across the management system standards

Q1 How to read the standard

5 min read · V, IA, EA

All articles

For: V, IA, EA
Source: Forewords, introductions and Annex headings of the PDFs in the folder. The verb forms are set out in the introduction of the respective standard, where the standard defines them.

A requirement is the sentence with "shall" or, in the German version of ISO 45001 and in ISO/IEC 17021-1, the sentence with "muss". A recommendation is "should" or "sollte". A permission is "may" or "dürfen". A possibility is "can" or "können". German "soll" is not a substitute for "shall" in these texts. In the German ISO 45001, "soll" in the introduction and in some places in the Annex stands for the English purpose sentence "is intended to" or for "needs to". That is recorded for the sentence in question in 45001-01 and 45001-17.

Examples are examples. "Such as", "e.g.", "for example" and "can include" do not open a second checklist. A Note explains the sentence it belongs to. It is marked here as guidance. Two limits are stated in the PDFs themselves.

ISO 45001, 0.5, says that notes to a term in clause 3 could contain requirements for the use of a designation. ISO/IEC 42001:2023, Note 2 to 3.26, uses "shall": all identified risks and the controls determined for their treatment shall be reflected in the statement of applicability. That is a requirement inside a Note, explained in 42001-05. "May" in the notes to 3.21 and 3.26 is not an additional obligation alongside that.

An Annex contains requirements only insofar as its heading identifies it as normative, or a sentence within it itself sets a "shall". The editions at hand:

  • ISO 9001:2026. Annex A is informative. A.1 says that the explanations are consistent with the requirements and that they do not supplement them, strike anything out or change them. This edition has no Annex B. The reading key in A.2 is different from the one in ISO 14001. "Consider" means thinking about the subject in order to determine whether it enters the decision. "Take into account" means thinking about it and including it. "Appropriate" and "applicable" are not interchangeable. "Ensure" is responsibility for the result. Activities can be transferred. The key is in 9001-25.
  • ISO 14001:2026. Annex A is informative. A.1 says that the information is not intended to supplement, reduce or change the requirements. The table of contents of this edition has no Annex B. A.3 sets the words differently from ISO 9001, A.2. "Consider" means thinking about the subject; afterwards it can be excluded. "Take into account" means thinking about it, and it cannot be excluded. "Applicable" implies: if it can be done, it shall be done. "Ensure" means that responsibility can be transferred, accountability cannot. The key is in 14001-19.
  • ISO 45001:2018, German version DIN EN ISO 45001:2023-12. Annex A is informative. A.1 says that the explanations are not intended to supplement, reduce or change the requirements. In the German Annex, "muss" appears in several places where the English Annex says "needs to". A.1 remains decisive. A.3 uses "berücksichtigen" for "consider" and "Rechnung tragen" for "take into account". The key is in 45001-17. The national foreword is DIN text. It says that the text was prepared with the aid of the high-level structure given in Annex SL of the ISO/IEC Directives. That is not a requirement of ISO 45001:2018.
  • ISO/IEC 27001:2022. Annex A is normative. The controls are to be used in connection with 6.1.3. A missing row is not, by itself, a nonconformity. Whether a control is necessary is the result of risk treatment. That is set out in 27001-05. The table is not copied out here. This PDF does not contain a reading key of the kind in ISO 9001, A.2.
  • ISO/IEC 42001:2023. Annex A and Annex B are normative. Annex C and Annex D are informative. Table A.1 applies with "shall" insofar as the control is necessary under 6.1.3. The boxes in Annex B formulate the same controls predominantly with "should". The requirement remains the wording in Table A.1. An exception in the box of B.7.6 retains "shall". That is set out in 42001-21.
  • ISO/IEC 17021-1:2015. The auditable requirements are in clauses 5 to 10 and in normative Annex A. Annexes B to E are informative. Clause 4 describes principles. The introduction and 4.1.1 say that principles are not requirements. That is set out in 17021-02. The introduction of this standard defines "müssen", "sollten", "dürfen" and "können".
  • ISO/IEC 27005:2018. Guidance. In clauses 1 to 12 there is no "shall" as a requirement on risk management. "Should" remains a recommendation. Annexes A to F are informative. This edition has no Annex G. That is set out in the explanations of ISO/IEC 27005:2018.
  • ISO/IEC 27006:2015. The introduction sets "shall" for mandatory provisions and "should" for recommendations. Annex A is informative. Annex B is normative. Annex C is informative. Annex D is informative and, in its heading, limited to Annex A of ISO/IEC 27001:2013. D.1 repeats a "shall": the implementation of the controls that the client has determined to be necessary shall be checked. The sentence refers to 9.3.1.2.2 g). It does not create a checklist for Annex A of ISO/IEC 27001:2022. That is set out in 27006-07.

Not in this text: a common word list for all standards, the content of the missing terminology standards, and the tables of the Annexes. ISO/IEC 27002:2022 is not available. The 2017 edition is not read here as implementation guidance.