Labs Support
EN SV
ISO 14001 cl. 6.1.3 - ISO 45001 cl. 6.1.3 - ISO 9001 cl. 4.2 - ISO 27001 cl. 4.2

Do you know which compliance obligations apply to you?

Compliance obligations affect ownership, risks, ways of working, and decisions. AmpliFlow gathers laws, regulations, authority directives, permit conditions, and contractual requirements so you know what applies, who owns it, and what needs follow-up.

Book a demo What counts as a compliance obligation?

Companies managing compliance obligations with AmpliFlow

The challenge

Most organisations lack a working register

Identifying and managing compliance obligations is a requirement in all four ISO standards. But the value appears when requirements guide ownership, risks, and everyday decisions.

No central register

Legal requirements live in spreadsheets, emails, binders, and in key people's heads. Nobody has the complete picture.

Unclear what actually applies

You know requirements exist. But you haven't done a systematic applicability assessment. That makes it hard to know what should guide the work.

Nobody owns it formally

Everyone knows roughly who monitors what - until that person leaves. Responsibility for compliance obligations needs to be formally assigned and documented.

The register is never current

Laws change, new regulations arrive, permits renew. Without an active process, the register falls behind quickly.

What the standards require

Four standards, one core requirement

All four ISO standards require identifying and managing compliance obligations. One register covers them all.

Bild
ISO 14001:2015 Clause 6.1.3

Compliance obligations

Determine and have access to compliance obligations related to environmental aspects. Determine how they apply and take them into account in the management system.

ISO 45001:2018 Clause 6.1.3

Legal requirements and other requirements

Determine and have access to up-to-date legal requirements and other requirements applicable to the organization's hazards and OH&S risks.

ISO 9001:2015 Clause 4.2

Interested party requirements

Determine relevant requirements of interested parties, including applicable statutory and regulatory requirements for products and services.

ISO 27001:2022 Clause 4.2

Interested party requirements

Determine requirements of interested parties relevant to information security, including legal, regulatory, and contractual obligations.

The solution

The register that makes requirements useful

AmpliFlow gives you a central register for all compliance obligations with structure for identification, applicability assessment, ownership, and follow-up.

1

Central register for all compliance obligations

Gather laws, regulations, permit conditions, and contractual requirements in one place. Categorize by subject area: environment, health and safety, information security, quality.

2

Applicability assessment for each requirement

Document whether it applies, how you are affected, and how you comply. That makes requirements easier to use in ISO work and ongoing follow-up.

3

Responsible person with traceability

Each compliance obligation gets an owner. Clear accountability: the right person monitors the right area, with name and date recorded.

4

Live register with status management

Mark requirements as new, amended, applied, or repealed. Import existing registers via bulk import. Export for audits.

Book a demo
Everyday work

When a requirement changes, you should know what it affects

With AmpliFlow, you see whether the requirement applies, who owns it, how you meet it, and which actions need follow-up.

That turns the register into decision support, not just a list you open when someone asks for it.

Next step

Make requirements useful in daily work

The register is the starting point. Once you know what applies, requirements can connect to risks, environmental work, and customer commitments.

01 Risk Management When a requirement creates uncertainty, assess the risk, choose the action, and follow up ownership. Open tool 02 Environmental Aspects Connect environmental requirements to the activities that affect emissions, waste, and resource use. Open tool 03 Customer Requirements Keep legal obligations, contract requirements, and customer-specific requirements connected without losing the full picture. Open tool
FAQ

Questions about the compliance obligations register

What is the difference between legal requirements and compliance obligations?
Compliance obligations is the broader term ISO 14001 (clause 6.1.3) uses. It includes laws and regulations but also authority directives, permit conditions, contractual requirements from customers, and voluntary commitments your organisation has made. The register in AmpliFlow covers all of these, not just legislation.
Which subject area should I choose?
AmpliFlow has eight predefined subject areas: Environment, Health and Safety, Information Security, Quality, Energy, Finances, Product Safety, and Other. They map directly to the ISO standards you are certified against. A requirement can belong to multiple subject areas.
How do we meet ISO 14001 requirement 6.1.3?
Clause 6.1.3 requires you to determine which compliance obligations apply, how they apply, and to take them into account in the management system. The register in AmpliFlow gives you the structure: identification, applicability assessment, responsible person, and status, so requirements can be followed up in the work.
Can we import an existing legislation register?
Yes, via bulk import. Export the register for audit reports or backup too. All fields are supported in the import: subject area, status, applicability, responsible person, how we meet the requirement.
Does AmpliFlow monitor legal changes automatically?
AmpliFlow gives you a structured register for documenting and following up compliance obligations. For automatic monitoring of legal changes, we recommend combining it with an external monitoring service that sends notifications when laws change.
Does this apply to all ISO standards we are certified against?
Yes. ISO 14001 (6.1.3), ISO 45001 (6.1.3), ISO 9001 (4.2), and ISO 27001 (4.2) all require identifying and managing compliance obligations. One register covers all standards, categorized by subject area.