What it is about
Compliance obligations are everything an organisation has to comply with in environmental protection or has committed itself to complying with. They include laws and regulations, permits with their conditions and local bylaws, but also contracts with customers, agreements with authorities, industry standards and voluntary commitments. Once adopted, an obligation is binding, whether it comes from the legislator or from the organisation’s own decision.
Clause 6.1.3 asks for three things: to determine the obligations that relate to your own environmental aspects, to have access to them and to know what they mean in concrete terms for your operations. That is how a duty in the law becomes a task in everyday work, such as an inspection interval for a plant, proof of waste disposal or a report to the authority. The usual tool for this is the legal register.
A register is never finished. Laws are amended, permits renewed, customers send new terms of supply. Keeping it up to date requires reliable sources, a fixed review cycle and a responsible person. It needs to be distinguished from the evaluation of compliance in clause 9.1.2: 6.1.3 asks which obligations apply, 9.1.2 asks whether they are fulfilled.
Compliance obligations are closely linked to the environmental aspects and to the interested parties. Expectations the organisation adopts become obligations, and an obligation is often what makes an environmental aspect significant in the first place.
What the auditor checks
“How do you know which laws apply to you?”
Whether there is a reliable source: a legal update service, a trade association, the authority, a questionnaire with a traceable derivation. “Our environmental officer knows that” is not a procedure that survives a holiday cover.
“What does this regulation mean in concrete terms for your operations?”
The translation into everyday work. A register that only lists the titles of laws does not say which inspection, which record or which deadline follows from them. The auditor picks out an entry and asks to be shown how it is implemented.
“Which of your customers’ requirements concern environmental protection?”
The requirements most often overlooked are those of customers. Requirements on packaging, banned substances, CO2 data or evidence are in terms of supply and quality assurance agreements, but not in the register. That is why the auditor asks specifically about the contracts of the most important customers and compares them with the register.
“How do you find out about a change in the law, and what happened with the last one?”
Source, review cycle and responsible persons. A concrete example with a date is convincing: change noticed, evaluated, process or instruction adapted.
“Show me your permit and the conditions in it.”
Whether the conditions attached to permits are recorded individually. That is precisely where monitoring duties, reports and limit values are found that do not appear in the law itself in that form.
“Which obligations have you entered into voluntarily?”
Whether commitments from sustainability reports, industry agreements or memberships are recorded. Entered into voluntarily does not mean non-binding: what has been adopted is treated in the audit like any other obligation.
Which evidence convinces
A legal register with source, version, link to the environmental aspect, concrete obligation and responsible persons
It shows what applies, why and who takes care of it. The standard requires compliance obligations to be maintained as documented information; a register is the usual way to do that, whether as a spreadsheet or in software.
The reason why a source applies
A characteristic of the operation explains the entry, for example a store for hazardous substances or a plant requiring a permit. That way someone else can also follow why one obligation is in the register and another is not.
Permits, contracts and agreements
They are the actual source of many obligations and show that more than just laws were considered.
Evidence of updating
Date of the last review, the next date and, for a change in the law, the evaluation together with the follow-up action. This shows the auditor that the register is maintained and does not merely exist.
The link to the evaluation of compliance
For each obligation, the result of the last check under 9.1.2 with date and evidence. Register and evaluation together close the chain from knowing to fulfilling.
Typical nonconformities
The register is out of date
Versions from years ago, repealed laws still listed, new ones missing, no recognisable last review. If there is no procedure for updating at all, the system is not working at this point, and it is a major nonconformity. If only individual changes are missing, it is usually a minor nonconformity.
Obligation known but not implemented
The inspection interval for the oil separator is in the register, but the inspection itself has been overdue for months. If a legal obligation remains unfulfilled without the system having noticed it, the system is not working at this point, and a major nonconformity is likely.
Customer requirements are missing
Environmental requirements from contracts and terms of supply sit with the sales team, while the register only lists laws. This is the most common blind spot in this clause, because customer requirements are rarely perceived as compliance obligations.
Titles instead of obligations
The register names “waste legislation” or the Water Resources Act, but not what follows from them for the operation. Without a concrete obligation, nothing can be implemented and compliance cannot be evaluated.
Permit conditions not recorded
The permit sits in the managing director’s files, and its conditions with monitoring duties and reporting deadlines do not appear in the register.
Register and evaluation of compliance mixed up
A column saying “fulfilled: yes” without a date, evidence or person does not replace the evaluation of compliance under 9.1.2. Conversely, what is often missing is the cycle at which the register itself is reviewed for new obligations.
Differences by standard
ISO 14001ISO 14001
Compliance obligations are an ISO 14001 term. Determining them is covered in clause 6.1.3, planning the related actions in 6.1.5 (6.1.4 in the 2015 edition) and evaluating compliance in 9.1.2. The 2026 edition gives more weight to the link between environmental aspects, compliance obligations, actions and measurable performance. In an integrated system, the other standards have related requirements: ISO 9001 requires statutory and regulatory requirements for products to be known, and ISO/IEC 27001 has a control in Annex A on legal, statutory, regulatory and contractual requirements. A shared register with a column for the standard concerned is therefore often the simplest route.
How IMScollect covers it
The legal register in IMScollect starts with a questionnaire on 29 characteristics of your operation, such as whether you store hazardous substances or run a plant requiring a permit. Which legal source follows from this is decided by fixed rules and not by a language model, and every row carries its reason with it. The question “Why is this in your register?” then has an answer that can be checked: because you answered this question with yes. The catalogue behind it covers German federal and EU law with a verified version; you add state law, local bylaws and the rules of the statutory accident insurers yourself.
You create your own obligations by hand, as a law, regulation, standard, contract or other, which includes your customers’ environmental requirements. Every obligation has a responsible person and a next review date. When a new version of a legal source is released, a task is created for every obligation affected. You check compliance directly on the obligation, with result, remark and evidence; for “partially compliant” or “non-compliant”, an action with an owner and a deadline is required. The AI advisor Conni suggests an evaluation of compliance; only what you approve is adopted.
Frequently asked questions
What counts as a compliance obligation?▾
Everything the organisation has to comply with in environmental protection or has adopted voluntarily: laws and regulations, permits and their conditions, bylaws, customer contracts and terms of supply, agreements with authorities, industry standards and its own voluntary commitments.
Does the legal register have to contain the texts of the laws?▾
No. What matters is the reference, the applicable version and the concrete obligation for your operation. The wording is read at the official source anyway; a register full of complete texts tends to be harder to audit.
How often does the legal register have to be updated?▾
The standard does not set a fixed interval. A cycle that suits the density of obligations is usual, often quarterly or every six months, plus every trigger: a new plant, a new substance, a new customer or a change in the law that has become known.
What is the difference between clauses 6.1.3 and 9.1.2?▾
Clause 6.1.3 asks which obligations apply and what they mean. Clause 9.1.2 asks whether they are being complied with and requires an evaluation with a defined frequency and a documented result. The register is the basis, the evaluation of compliance is the evidence.
