6.1.2 Environmental aspects: what your organization actually does to the environment

This is the technical heart of clause 6 and the part of ISO 14001 that most clearly distinguishes it from ISO 9001. An environmental aspect is an element of an organization's activities, products or services that interacts or can interact with the environment. An environmental impact is the change to the environment, whether adverse or beneficial, wholly or partially resulting from that aspect.

Clause 6.1.2 requires the organization to determine the environmental aspects of its activities, products and services that it can control and those it can influence, and their associated environmental impacts, within the defined scope of the EMS. Critically, this determination must take into account:

• Change: including planned or new developments, and new or modified activities, products and services.
• Abnormal conditions: startups, shutdowns, and reasonably foreseeable emergency situations — not only steady-state, business-as-usual operation.
• A life cycle perspective: the standard explicitly requires consideration of a life cycle perspective, though it does not require a full life cycle assessment.

Once aspects are identified, the organization must determine those that have or can have a significant environmental impact, using established criteria, and communicate this information across relevant levels and functions of the organization. The standard requires this information to be maintained as documented information: the environmental aspects and associated environmental impacts; the criteria used to determine significant aspects; and the significant environmental aspects themselves.

The life cycle perspective: broader than your fence line

One of the most frequently misunderstood requirements in clause 6.1.2 is the life cycle perspective. This does not mean the organization must conduct a formal, quantitative life cycle assessment for every product — that level of rigor is neither required nor practical for most industrial operations. What the standard does require is that the organization think beyond the boundary of its own site when identifying aspects, considering stages such as:

• Raw material acquisition: the environmental footprint embedded in the materials and components you purchase.
• Design and development: decisions made at the design stage that determine downstream environmental performance — material selection, energy efficiency, recyclability.
• Production: the aspects generated directly within your controlled processes — the traditional focus of most environmental programs.
• Transportation and delivery: the environmental burden of moving materials in and products out.
• Use and end-of-life treatment: what happens to the product after it leaves your control, including its eventual disposal, reuse or recycling.

In practice, applying a life cycle perspective for most manufacturers means adding a few extra questions to the aspects identification exercise, such as whether a component supplier uses a particularly energy-intensive process, or whether the packaging chosen for a product is recyclable in the markets where it is sold. It is a perspective to apply when identifying aspects, not a separate deliverable to produce.

6.1.3 Compliance obligations: knowing what you must (and choose to) comply with

Clause 6.1.3 requires the organization to determine and have access to the compliance obligations related to its environmental aspects, and to determine how these obligations apply to the organization. Compliance obligations, as defined by the standard, include both:

• Legal requirements the organization must comply with: national, regional and local environmental legislation and regulations, permits, licenses and consents, and requirements from regulatory authorities.
• Other requirements the organization chooses to comply with: agreements with public authorities or customers, non-regulatory guidelines, voluntary principles or codes of practice, requirements of trade associations, and commitments to community groups or NGOs.

These compliance obligations must be taken into account when establishing, implementing, maintaining and continually improving the EMS, and the organization must maintain documented information on its compliance obligations. This register becomes the direct input for the compliance evaluation required later under clause 9.1.2 — the two clauses work as a pair: 6.1.3 defines what you must track, and 9.1.2 requires you to periodically evaluate whether you are actually meeting it.

6.1.4 Planning action: turning findings into a plan

Clause 6.1.4 brings the previous three subclauses together. The organization must plan to take actions to address its significant environmental aspects, compliance obligations, and the risks and opportunities identified in 6.1.1, and to integrate and implement these actions into its EMS processes, or other business processes, evaluating the effectiveness of these actions.

When planning these actions, the organization must consider its technological options and its financial, operational and business requirements. This is a deliberate acknowledgement by the standard that environmental improvement has to be realistic — a small manufacturer is not expected to adopt the same abatement technology as a multinational with a dedicated capital budget, but it is expected to have a genuine, resourced plan proportionate to its significant aspects.

6.2 Environmental objectives: from significance to measurable targets

Clause 6.2 is split into two subclauses that separate what objectives must look like from how you plan to achieve them.

6.2.1 Environmental objectives requires the organization to establish environmental objectives at relevant functions and levels, taking into account the organization's significant environmental aspects and associated compliance obligations, and considering its risks and opportunities. The objectives must be:

• Consistent with the environmental policy.
• Measurable (if practicable).
• Monitored.
• Communicated to relevant interested parties.
• Updated as appropriate.

The organization must maintain documented information on these environmental objectives. A common shortfall auditors flag is an objective that is aspirational but not actually measurable — "reduce our environmental footprint" is a policy statement, not an objective; "reduce process water consumption per unit produced by 8% against the 2025 baseline by December 2027" is an objective that clause 6.2.1 is looking for.

6.2.2 Planning actions to achieve environmental objectives requires the organization to determine, for each objective: what will be done; what resources will be required; who will be responsible; when it will be completed; and how the results will be evaluated, including the indicators used to monitor progress toward measurable objectives. This is effectively an action-plan requirement layered on top of the objective itself, and it must also address how these actions can be integrated into the organization's business processes rather than run as isolated environmental projects.

Common audit findings in clause 6

Across certification and surveillance audits in manufacturing, the recurring weaknesses in clause 6 tend to fall into a small number of patterns:

• 6.1.2 — Aspects register not updated after change: a new machine, a new chemical, or a discontinued process line that never made it into the aspects register.
• 6.1.2 — Abnormal conditions overlooked: the register covers routine operation but says nothing about startup, shutdown or foreseeable emergency scenarios such as a spill or a containment failure.
• 6.1.3 — Incomplete compliance obligations register: permits and regulations are tracked, but voluntary commitments the organization has chosen to comply with (a customer code of conduct, an industry charter) are missing.
• 6.2.1 — Objectives that are not measurable: vague statements of intent presented as objectives, with no baseline, target value or deadline.
• 6.2.2 — Action plans without assigned resources: an objective exists on paper, but no budget, responsible person or timeline was ever defined, so nothing actually happens before the next management review.

Frequently asked questions about ISO 14001 clause 6

Do I need a formal life cycle assessment to comply with clause 6.1.2?

No. ISO 14001 requires the organization to consider a life cycle perspective when identifying environmental aspects, but it does not require a formal, quantitative life cycle assessment (LCA) as defined in ISO 14040/14044. In practice, this means thinking through the stages before and after your own operations — raw material sourcing, use, and end-of-life — when identifying aspects, rather than commissioning a full LCA study. Organizations with mature environmental programs sometimes choose to run an LCA for specific high-impact products, but it is a choice, not a clause 6 requirement.

What is the difference between an environmental aspect and an environmental impact?

An aspect is the element of your activity, product or service that interacts with the environment — for example, the discharge of process wastewater. The impact is the resulting change to the environment, adverse or beneficial — for example, the increase in chemical oxygen demand in the receiving watercourse. Clause 6.1.2 requires you to identify both the aspect and its associated impact, because the significance of an aspect is judged largely on the severity of its impact.

How do I decide which environmental aspects are significant?

ISO 14001 does not prescribe a specific methodology — it requires the organization to establish its own criteria for determining significance and to apply them consistently. Commonly used criteria include the severity and scale of the potential impact, the frequency or probability of occurrence, the sensitivity of the receiving environment, legal or regulatory sensitivity, the concerns of interested parties, and the organization's ability to control or influence the aspect. Whatever criteria you choose, they must be documented and applied consistently across the aspects register, since auditors will test the logic behind why one aspect was scored significant and another was not.

Are compliance obligations only legal requirements?

No. Clause 6.1.3 defines compliance obligations as both legal requirements the organization must comply with and other requirements it chooses to comply with. The second category includes things like customer contract clauses on environmental performance, membership requirements of an industry association, voluntary sustainability charters, and public commitments made to community groups. If your organization has voluntarily signed up to a requirement, it becomes a compliance obligation under the standard and must be tracked and evaluated just like a legal one.

Do all environmental objectives need to be quantitatively measurable?

Clause 6.2.1 requires objectives to be measurable "if practicable." This wording acknowledges that a small number of objectives may be genuinely difficult to quantify, but in the vast majority of cases — energy consumption, water use, waste generation, emissions, spill incidents — a numerical target with a baseline and a deadline is achievable and is what auditors expect to see. Objectives framed only in qualitative terms, without any way to verify progress, are one of the most common nonconformities raised against this subclause.

What happens to an environmental aspect linked to a process that has been discontinued?

The aspects register must be kept current, which means it should be updated whenever activities, products or services change — including when a process is discontinued or a piece of equipment is decommissioned. The associated aspect should be removed or marked as no longer applicable, with a record of when and why the change was made. Leaving obsolete aspects in the register without review is treated the same way as failing to add new ones: both indicate the register is not being actively maintained as clause 6.1.2 requires.

Expert ISO 14001 · Updated 2026-07-31 · ISO 14001 step-by-step series: Article 2 — Clause 5 · Article 4 — Clause 7