
ISO Compliance obligations explained: What every organization needs to know
Every major ISO management system standard has some form of requirement relating to "Compliance Obligations". However, many management systems respond with just a list of legal requirements but compliance obligations are more than that. In this article, we'll explain what the concept means and how you can best address it in your management system.
Let's begin with a simple definition of what compliance obligations are:
Compliance obligations are the legal, regulatory, contractual, and voluntary requirements that an organization must or chooses to comply with.
Legal and regulatory requirements might be thought of as mandatory, while other commitments might be thought of as voluntary (e.g. you choose to comply with). We might categorise them as follows:
Mandatory requirements
These are obligations that your organization must meet. For example:
- Laws and regulations
- Government permits and licences
- Statutory requirements
- Regulatory approvals and conditions
- Court orders or enforceable decrees
Voluntary requirements
These are voluntary in the sense that you don't have to agree to a particular contract, you don't have to offer a warranty beyond the legal requirements, and you don't have to join an industry association. However. once your organization makes these commitments, they become part of its compliance obligations. For example:
- Customer contracts
- Industry codes of practice
- A guarantee or warranty
- Industry association member requirements
- Pledges made to communities or stakeholders
Let's look at some practical examples in the context of the major ISO standards:

The ISO standards generally expect your organization to:
- Identify its compliance obligations
- Assess the risk
- Implement controls
- Evaluate compliance
- Take action to address any nonconformities (and their root causes).
Steps 2-5 can be addressed by existing arrangements within your management system. For step 1, the question is: How best to identify the applicable compliance obligations? The answer we typically suggest is to establish and maintain some form of Compliance Obligations Register.
Qudos3 IMS software clients have just such a Register available as a standard template in their software.
For others, the next Qudos Club newsletter will include a free download of an Excel version.
Relevant standards references
ISO management system standard generally refer to compliance obligations in clause 4.2 Understanding the needs and expectations of interested parties. Here are some other notable references:
- The ISO 9001:2026 Quality standard refers to statutory, regulatory (and other) requirements in clause 8.2.2 Determining requirements for products and services. It mentions Contractual Obligations in a note to clause 8.5.5 Post-delivery activities.
- The ISO 27001:2022 Information Security standard also specifically relates to Compliance Obligations in Annex A Control 5.31.
- The ISO 42001:2023 AI standard refers to Contractual Obligations in clause 4.1 Understanding the organization and its context.
- The ISO 14001:2026 Environmental standard also specifically relates to Compliance Obligations in clause 6.1.3. It also refers to the topic in various other clauses.