Clause 6.1.2 Environmental Aspects Register: How-To Guide

Clause 6.1.2 is where most ISO 14001 implementations either find their footing or start collecting nonconformities. It's the requirement that turns "we care about the environment" into an actual, auditable list: what the organization does, what environmental aspects those activities create, which of those aspects it has decided are significant, and how it can prove all of that on demand. In my work building environmental management systems for manufacturers, labs, and processors, from a Michigan machine shop to a California specialty chemical plant, the aspects register is usually the first document an auditor asks for. It's also the document most likely to have been built once during initial certification and never touched again. That second part is the real failure mode. Clause 6.1.2 is not a one-time inventory. It carries its own maintenance obligations, and an auditor who finds a register untouched since the initial audit, especially at a site that has since added equipment or changed a process, has found a nonconformity.

This guide walks through what the clause actually requires, a step-by-step method for building a register that holds up under a Stage 2 audit, and what keeps it alive afterward.

What Clause 6.1.2 Actually Requires

ISO 14001:2015 clause 6.1.2, "Environmental aspects," requires an organization to determine, within the defined scope of its environmental management system, the environmental aspects of its activities, products, and services that it can control and those it can influence, along with their associated environmental impacts. That determination has to be made considering a life cycle perspective, not just what happens on-site during normal operations.

The clause then requires two further things. First, when identifying aspects, the organization must account for planned or new developments, and for abnormal conditions and reasonably foreseeable emergency situations, not just steady-state operations. Second, the organization must determine which aspects have, or can have, a significant environmental impact, using criteria it establishes itself. Those are the significant environmental aspects (SEAs), and clause 6.1.2 requires the organization to communicate them across relevant levels and functions.

Clause 6.1.2 closes with a documented information requirement. The organization must maintain records of its environmental aspects and associated impacts, the criteria used to determine significance, and the significant environmental aspects themselves. That documented information requirement is the register. There's no prescribed format in the standard itself, and Annex A of ISO 14001:2015 confirms this explicitly: the aspects register can be a spreadsheet, a database, or a module inside a broader EMS software platform. What matters to an auditor is that the three required elements are present, current, and traceable back to the criteria that produced them.

Environmental Aspect vs. Environmental Impact

This distinction trips up nearly every team building a register for the first time, so it's worth stating plainly: an environmental aspect is an element of an activity, product, or service that interacts with the environment. An environmental impact is the change to the environment that results from that interaction, whether beneficial or adverse.

A diesel generator running on-site is not itself an aspect. The aspect is the combustion emission it produces, or the fuel it consumes, or the noise it generates. The impact is what happens because of that aspect: reduced local air quality, depletion of a finite fuel resource, or a nuisance noise complaint from a neighboring property. Get the aspect right and the impact usually follows logically. Confuse the two and the register ends up listing activities ("welding," "wastewater discharge") instead of the actual aspect-impact pairs an auditor is trained to look for.

Why the Life Cycle Perspective Changes the Exercise

Clause 6.1.2's requirement to consider a life cycle perspective is easy to read past, but it's one of the more consequential changes between the 1996/2004 editions of ISO 14001 and the 2015 edition. It means the register cannot stop at the factory fence. Annex A.6.1.2 lists the life cycle stages an organization should consider: raw material acquisition, design, production, transportation and delivery, use, end-of-life treatment, and final disposal. The organization does not need equal control over every stage. The standard is explicit that the degree of control or influence varies by stage. But it does need to have considered each one and documented why aspects at that stage were or were not carried into the register.

For a manufacturer, this usually means adding aspects tied to supplier-sourced raw materials, packaging that a customer will eventually discard, and the environmental profile of the product once it leaves the gate. I've written more on how this plays out in practice in a companion piece on the life cycle perspective under ISO 14001, which is worth reading alongside this guide before you start populating rows.

Building the Register: A Step-by-Step Method

Step 1: Define Your Boundaries

Start from the scope statement required under clause 4.3. The aspects register has to align with whatever boundary the EMS scope defines, physically, organizationally, and by activity. If the scope excludes a leased warehouse or a subcontracted process, say so explicitly and be ready to defend that exclusion at audit; scope exclusions are a common point of auditor pushback when they look convenient rather than justified.

Step 2: Inventory Activities, Products, and Services

Walk the site, and walk the process flow, not just the org chart. List every activity that consumes a resource, generates an output, or interacts with the environment: production processes, maintenance, utilities, storage, shipping and receiving, grounds keeping, contractor work performed on-site, and office functions. Most teams underestimate how many aspects come from support functions rather than core production.

Step 3: Identify Aspects Under Normal, Abnormal, and Emergency Conditions

For each activity, identify aspects across three operating states, because clause 6.1.2 requires all three to be considered:

Teams that only capture normal-condition aspects are the ones that get flagged during a management system audit, because the emergency-preparedness requirement in clause 8.2 is supposed to trace directly back to aspects identified here.

Step 4: Map Each Aspect to Its Impact

Every aspect gets at least one associated impact. Some aspects have several. A wastewater discharge aspect might carry impacts on both surface water quality and aquatic habitat; document both rather than collapsing them into a single vague line.

Step 5: Set Significance Criteria Before You Score Anything

This is the step teams most often skip or reverse-engineer after the fact, and it's also the specific documented-information item clause 6.1.2 names separately from the aspects list itself. Establish and document the criteria first, then apply them consistently. Typical criteria include:

Most organizations use a simple numeric scale (1–5) for three or four of these criteria, multiply or sum the scores, and set a numeric threshold above which an aspect is flagged significant. The specific scale matters less than consistency: an auditor will pull two or three register entries and check whether the same criteria, applied the same way, produced the significance call recorded.

Step 6: Score, Rank, and Flag Significant Aspects

Apply the criteria uniformly across the full aspect list. Anything tied to an active compliance obligation should generally score as significant regardless of where the numeric threshold falls; regulatory linkage is one of the fastest ways an auditor will test whether your scoring model is honest. Cross-reference the resulting significant aspects list against the legal and other requirements the organization tracks under clause 6.1.3 — if you haven't set up that tracking mechanism yet, the companion guide on identifying and tracking environmental legal requirements covers how the two registers should stay linked.

Here's how that looks with actual numbers. Take a wastewater discharge aspect at a metal finishing site, scored 1–5 against the six criteria from Step 5:

• Severity/magnitude: 4 (a release could reach a downstream intake)
• Probability/likelihood: 3 (occurs during batch changeovers)
• Duration: 3 (effects persist for hours after a release)
• Regulatory status: 5 (subject to an NPDES permit limit)
• Stakeholder concern: 3 (no active complaints but a sensitive watershed)
• Frequency of occurrence: 4 (weekly)

That totals 22 out of a possible 30. Against a documented significance threshold of 18, this aspect is flagged significant — and would have been flagged regardless of where the other five scores landed, because the regulatory-status score alone triggers the override described above.

Step 7: Document It the Way the Clause Actually Asks For

Structure the final register so the three documented-information items required by clause 6.1.2 are each retrievable on their own: the full aspects-and-impacts list, the significance criteria as a standalone documented method, and the resulting significant aspects list. Many organizations combine all three into one spreadsheet with separate tabs; that's acceptable, and often preferable, as long as each element can be produced independently during an audit.

What Goes in Each Register Row

A workable register row, at minimum, includes:

• Activity/process
• Associated aspect
• Associated impact
• Operating condition (normal/abnormal/emergency)
• Life cycle stage
• Control status (controlled or influenced)
• Applicable legal requirement (if any)
• Significance score by criterion
• Total score
• Significance determination
• Existing operational controls
• Date of last review
• Related objective or target (if applicable)

Adding a column for "related objective or target" ties the register directly into clause 6.2 planning, which is exactly the traceability auditors look for when they follow a significant aspect through the rest of the management system.

Common Aspect Categories and Associated Impacts

This table is a starting point, not a substitute for the walk-through in Step 2. Every facility has aspects specific to its own processes that a generic list won't surface.

Keeping the Register Alive: Maintenance Triggers

Clause 6.1.2 doesn't state a fixed review interval, but several events should automatically trigger a register update:

• A new process, product line, or piece of equipment
• A change in raw materials or suppliers
• A new or revised environmental permit condition
• A facility expansion or a leased-space change to the EMS boundary
• An incident or near-miss that reveals an aspect the register missed
• The annual management review required under clause 9.3, which should always include a check on whether the aspects register still reflects reality

If nothing else has changed, the management review cycle is the backstop that prevents the register from going stale.

An auditor reviewing a register untouched since the initial certification audit, especially at a site that has since added equipment or changed a process, will treat that as evidence the organization isn't maintaining the documented information clause 6.1.2 requires, which is itself a nonconformity independent of whatever the register actually contains.

Where the Register Connects to the Rest of the EMS

The aspects register isn't a stand-alone artifact. Significant environmental aspects identified under 6.1.2 feed directly into clause 6.1.4's action planning and clause 6.2's objectives and targets, so a significant aspect with no corresponding objective, target, or operational control is a gap an auditor will find quickly. Clause 8.1 requires operational controls consistent with the life cycle perspective, meaning the register should show a clear line from a significant aspect to a documented control. Clause 9.1.1 requires monitoring and measurement of performance related to significant environmental aspects, so if the register calls something significant, there should be a corresponding monitoring activity somewhere else in the system. If any of those links are missing, the register isn't wrong, it's just disconnected from the system it's supposed to drive.

Common Audit Findings Against Clause 6.1.2

The recurring nonconformities I see fall into a short list:

• Aspects listed without a corresponding impact
• Significance criteria that exist but were clearly not applied consistently across entries
• Abnormal and emergency conditions omitted entirely
• Contractor or supplier activities left out of a register that claims to cover the full EMS scope
• A register that hasn't been updated to reflect a documented process change elsewhere in the management system

Each of these is fixable in an afternoon once it's identified, which is exactly why catching them internally, through the process outlined on our environmental certification help page, costs far less than catching them at Stage 2.

FAQ

What's the difference between an environmental aspect and an environmental impact? An aspect is the element of an activity, product, or service that interacts with the environment, such as a wastewater discharge. An impact is the resulting change to the environment, such as reduced surface water quality. Clause 6.1.2 requires both to be documented as a linked pair, not as separate, disconnected lists.

Does ISO 14001 require a specific format for the aspects register? No. Clause 6.1.2 requires the documented information to exist and be retrievable, but it does not prescribe spreadsheet, database, or software format. Annex A confirms the organization is free to choose the method, provided the aspects, the significance criteria, and the significant aspects list are each identifiable.

How often must the aspects register be reviewed? The standard sets no fixed interval, but a review should occur at every management review under clause 9.3, and immediately after any process change, new equipment installation, permit modification, or incident that could introduce a new aspect.

What counts as a "significant" environmental aspect? Whatever the organization's own documented criteria say counts as significant. There's no universal numeric threshold in the standard. What auditors check is whether the criteria were established before scoring, applied consistently across all entries, and whether any aspect tied to an active legal requirement was scored accordingly.

Do contractor and supplier activities need to be included in the register? Yes, to the extent they fall within the EMS scope and the organization can control or influence them. Clause 6.1.2 explicitly covers aspects the organization can control and those it can only influence, which is the category most on-site contractor work and many supplier-related aspects fall into.

Last updated: 2026-09-14