Most organizations I work with treat Clause 4 as the paperwork you finish before the real work begins. They produce a SWOT, list a few stakeholders, write a scope statement, and move on to aspects and objectives. Then, a year later, the certification auditor asks how the issues in 4.1 shaped the risks in 6.1.1, and the room goes quiet.
In my view, Clause 4 is the part of ISO 14001:2015 that decides whether the rest of the system will fit the business or sit on top of it like a coat that belongs to somebody else. This guide walks through each sub-clause, what the standard actually requires, where auditors tend to push, and how to build something you will still use after certification.
What Is "Context of the Organization" in ISO 14001?
Context of the organization is the set of external and internal conditions, plus the expectations of outside parties, that shape what your environmental management system (EMS) needs to accomplish. Clause 4 of ISO 14001:2015 contains four sub-clauses:
- 4.1 Understanding the organization and its context
- 4.2 Understanding the needs and expectations of interested parties
- 4.3 Determining the scope of the environmental management system
- 4.4 Environmental management system
Clause 4 came into ISO 14001 with the 2015 revision, which adopted the Annex SL high-level structure shared by the other ISO management system standards. If you are running ISO 9001 or ISO 45001 alongside ISO 14001, the same four-part opening will look familiar, and that overlap is an advantage when you build an integrated management system.
Think of Clause 4 as the soil. Aspects, compliance obligations, objectives, and operational controls all grow out of it, and if the soil was never examined, you will spend years wondering why things don't take.
Clause 4.1: Understanding the Organization and Its Context
Clause 4.1 requires the organization to determine external and internal issues that are relevant to its purpose and that affect its ability to achieve the intended outcomes of its EMS. Clause 1 of the standard names those intended outcomes: enhancement of environmental performance, fulfillment of compliance obligations, and achievement of environmental objectives.
That wording matters. The standard is not asking for a general business analysis. It is asking which issues could help or hinder those three outcomes.
Environmental conditions are part of the question
Clause 4.1 also says these issues include environmental conditions capable of affecting or being affected by the organization. This is the piece that separates ISO 14001 from the other Annex SL standards, and it is the piece I see skipped most often. A quality manager can write a perfectly reasonable context analysis about customers and competitors and never mention water scarcity, flood exposure, local air quality, or habitat near the site.
Annex A.4.1 gives examples of what this covers: climate, air quality, water quality, land use, existing contamination, natural resource availability, and biodiversity. It also notes that the condition can be something that affects you (a drought threatening your process water) or something you affect (your discharge into a river already stressed by upstream users).
The 2024 climate change amendment
ISO 14001:2015/Amd 1:2024, published in February 2024, added a sentence to clause 4.1 requiring the organization to determine whether climate change is a relevant external or internal issue. The amendment does not require you to conclude that it is relevant. It requires you to ask the question and be able to show how you answered it. A short documented rationale, even for a low-exposure office operation, is cheaper than explaining its absence to an auditor.
External versus internal issues
Annex A.4.1 describes external issues as including cultural, social, political, legal, regulatory, financial, technological, economic, natural, and competitive circumstances, whether international, national, regional, or local. Internal issues include things like organizational culture, governance, capabilities, knowledge, resources, products and services, and contractual relationships.
| Category | Examples relevant to an EMS | Likely link to later clauses |
|---|---|---|
| External: legal and regulatory | New air permit limits, PFAS reporting rules, waste classification changes | 6.1.3 compliance obligations |
| External: environmental conditions | Drought, flood risk, local air quality, protected habitat | 6.1.2 aspects, 8.2 emergency response |
| External: market and financial | Customer sustainability questionnaires, energy price swings | 6.1.1 risks and opportunities, 6.2 objectives |
| Internal: resources and capability | Maintenance backlog, thin environmental staffing, aging equipment | 7.1 resources, 7.2 competence |
| Internal: culture and governance | Leadership engagement, production-over-compliance habits | 5.1 leadership, 5.3 roles |
| Internal: products and processes | Process changes, new product lines, outsourced activities | 6.1.2 life cycle perspective, 8.1 operational control |
Do you need a documented method?
No. Clause 4.1 does not contain a documented information requirement, and Annex A.4.1 is explicit that the standard does not prescribe a formal method. You can use a SWOT, a PESTLE, a workshop with a flip chart, or a structured conversation in management review. The auditor is looking for evidence that the process happened and that it connects to the rest of the system, not for a particular template.
That said, I almost always recommend writing it down. A context register that is dated, owned, and reviewed gives you something to point to when the auditor asks how you know what you know.
Clause 4.2: Needs and Expectations of Interested Parties
Clause 4.2 requires the organization to determine the interested parties that are relevant to the EMS, the relevant needs and expectations of those parties, and which of those needs and expectations become compliance obligations. Interested parties are defined in clause 3.1.6 as a person or organization that can affect, be affected by, or perceive itself to be affected by a decision or activity.
The phrase "perceive itself to be affected" is worth sitting with. A neighbor who has never filed a complaint but who worries about your truck traffic is still an interested party under that definition.
Needs and expectations are not all obligations
The clause draws a line between what interested parties want and what you have to do. Some needs and expectations are mandatory because they are written into law, permits, or contracts. Others are voluntary commitments you choose to adopt, such as a customer code of conduct you agree to, a community agreement, or an industry initiative. The standard calls both categories compliance obligations in clause 3.2.9, but a need or expectation you have not chosen to adopt remains simply an expectation you have considered.
This is the step where I see the most useful conversations happen. A team looks at a list of eight interested parties and realizes that two of them have expectations nobody had ever agreed to either honor or decline.
A practical interested party table
| Interested party | Typical needs and expectations | Becomes a compliance obligation? |
|---|---|---|
| Regulators | Permit conformance, timely reporting, record retention | Yes, legal requirement |
| Customers | Supplier code of conduct, carbon data, restricted substance declarations | Yes, if contractually accepted |
| Employees | Safe handling of chemicals, training, a voice in spill reporting | Partly, through law; otherwise a commitment |
| Neighbors and community | Low odor, noise limits, traffic management, advance notice of incidents | Only if adopted or required by permit |
| Investors and lenders | Disclosure of environmental risk, climate information | Depends on covenants and reporting regimes |
| Suppliers and contractors | Clear requirements, fair expectations, waste take-back terms | Contractual where applicable |
Clause 4.2 also carries the climate sentence from the 2024 amendment, in the form of a note that relevant interested parties can have requirements related to climate change. Customers asking for greenhouse gas data are a common example.
Linking 4.2 to legal requirements
The output of 4.2 feeds directly into clause 6.1.3, where you determine and have access to compliance obligations and decide how they apply to your organization. If you want a working method for the legal side of this, my article on how to identify and track environmental legal requirements under ISO 14001 covers it in detail.
Clause 4.3: Determining the Scope of the EMS
Clause 4.3 requires you to determine the boundaries and applicability of the EMS to establish its scope. When you do that, the standard says you must consider the external and internal issues from 4.1, the compliance obligations from 4.2, your organizational units, functions, and physical boundaries, your activities, products, and services, and your authority and ability to exercise control and influence.
Unlike 4.1 and 4.2, clause 4.3 does require documented information. The scope must be maintained as documented information and must be available to interested parties.
What a good scope statement looks like
A scope statement that holds up in an audit usually names the sites, the activities, and the products or services, and it states any exclusions with a reason. For example: "The EMS applies to the design, machining, finishing, and shipping of aluminum components at the Springfield facility, including on-site wastewater pretreatment and hazardous waste accumulation areas." That sentence tells a reader where the system begins and ends.
The part people get wrong: control and influence
The clause says the organization must have the authority and ability to exercise control and influence over activities within the scope. Notice that the standard does not say you can only include what you fully control. A company that outsources plating but specifies the process and chooses the vendor still has meaningful influence over that environmental aspect.
Clause 4.3 also states that once the scope is defined, all activities, products, and services of the organization within that scope need to be included in the EMS. You cannot define a narrow scope to avoid your worst-performing building. Annex A.4.3 states that the credibility of the EMS depends on the choice of boundaries, and auditors know this. If a scope statement excludes a loading dock that produces most of the site's spills, expect questions.
Scope for multi-site and service organizations
A multi-site organization can certify one site, several sites, or the whole enterprise, and the scope should say which. For service and office-based organizations, the aspects may be smaller (energy, paper, business travel, supplier choices) but the scope logic is the same. If your products or services influence environmental performance during use or end of life, the life cycle perspective required by clause 6.1.2 may bring those into view. I wrote a practical piece on what the life cycle perspective means in practice if you need to see how far that reaches.
Clause 4.4: The Environmental Management System
Clause 4.4 is the shortest of the four. It requires the organization to establish, implement, maintain, and continually improve an EMS, including the processes needed and their interactions, in accordance with the requirements of the standard. It also says that, in doing so, the organization must take into account the knowledge gained from 4.1 and 4.2.
Two points in this clause are easy to read past.
The first is the word "interactions." The standard is asking you to see the EMS as connected processes (for example, how legal tracking feeds objectives, how incidents feed corrective action, how audit results feed management review) and not a stack of separate procedures. A process map or a simple flow of inputs and outputs is a reasonable way to show this, though the standard does not require one.
The second is the phrase "knowledge gained from 4.1 and 4.2." This is a direct instruction to use your context analysis when designing the system. An EMS built for a chemical blender in a water-stressed region should look different from one built for a software company in a leased office floor, and 4.4 is where that difference is supposed to show up.
How Clause 4 Connects to the Rest of the Standard
The strongest evidence of a working Clause 4 is the trail it leaves elsewhere. Clause 6.1.1 says that when planning the EMS, the organization shall consider the issues from 4.1, the requirements from 4.2, and the scope from 4.3 in order to determine risks and opportunities related to its environmental aspects, compliance obligations, and other issues and requirements. Clause 9.3.2 lists changes in external and internal issues and in the needs and expectations of interested parties among the required inputs to management review.
| Clause 4 output | Where it flows | What an auditor may ask |
|---|---|---|
| Issues (4.1) | 6.1.1 risks and opportunities; 9.3.2 management review | "Which risks came from your context analysis?" |
| Interested parties and obligations (4.2) | 6.1.3 compliance obligations; 7.4 communication | "How did you decide which expectations you adopted?" |
| Scope (4.3) | 6.1.2 aspects; 8.1 operational control | "Are all in-scope activities covered in your aspects register?" |
| EMS processes (4.4) | 4.4 itself, plus 9.1 and 10 | "How do your processes interact?" |
If you are building the aspects side now, the guide to an environmental aspects register under clause 6.1.2 is the natural next step.
Common Clause 4 Nonconformities and Weak Spots
From what I see in gap assessments and internal audits, the same problems come up again and again:
- A context analysis with no environmental content. The document reads like a business plan and never mentions environmental conditions.
- A list of interested parties with no needs or expectations. Names without analysis do not satisfy 4.2.
- No decision on which expectations became compliance obligations. The clause asks for that determination, and many registers stop one column early.
- A scope that is vague or silent on exclusions. "The organization's activities" is not a boundary.
- Context done once and never revisited. The standard expects the information to be monitored and reviewed (clause 4.1 requires it), and management review is the natural place to show that.
- No bridge to risks and opportunities. The issues sit in one document and the risk register sits in another, with no visible link.
None of these is hard to fix. They tend to persist because Clause 4 feels abstract, and abstract things get delegated to whoever has the least time.
A Practical Process for Building Clause 4
If you are starting from scratch, this sequence works well in a half-day workshop followed by a few weeks of refinement:
- Gather the right people. Include operations, maintenance, procurement, legal or compliance, and someone who talks to customers. Top management should attend at least part of it, since clause 5.1 expects leadership to ensure the EMS is compatible with the strategic direction and context of the organization.
- List external issues, starting with environmental conditions. Walk the site and the surrounding area before you open a template.
- List internal issues. Be candid about resource gaps and cultural habits.
- Identify interested parties and their needs. Ask what each one has actually said or asked for, not what you assume.
- Decide which expectations are obligations. Record the decision and the reasoning.
- Draft the scope. Test it against your site map and your list of activities, products, and services.
- Link to risks and opportunities. For each significant issue, note where it appears in your 6.1.1 register.
- Schedule the review. Tie it to management review, and add triggers for permit changes, new products, acquisitions, or incidents.
For the broader sequence of clauses 4 through 10, the ISO 14001:2015 implementation checklist and gap analysis shows where this step sits in the larger project.
Keeping Context Alive After Certification
Context changes faster than most people expect. A new regulation lands, a major customer adds a sustainability requirement, a drought hits, a key engineer retires. The simplest habit I know is to put a standing agenda item in management review: what has changed in our issues and in the expectations of interested parties since last time? Clause 9.3.2 already requires that input, so you are not adding a burden, just making it real.
Is your context analysis something people use to make decisions, or something you open the week before the surveillance audit? That question tells you more about the health of your EMS than almost any other.
If you want help building or refreshing your Clause 4 documentation, you can reach me through Certify Consulting or start with the overview of ISO 14001 implementation support.
Last updated: 2026-10-12
Frequently Asked Questions
What does Clause 4 of ISO 14001 require?
Clause 4 of ISO 14001:2015 requires an organization to determine its external and internal issues (4.1), the needs and expectations of relevant interested parties and which become compliance obligations (4.2), the scope of the EMS (4.3), and to establish and maintain the EMS itself (4.4). Only the scope under 4.3 explicitly requires documented information.
Do I need a SWOT analysis to meet clause 4.1?
No. ISO 14001 does not prescribe a method for understanding context, and Annex A.4.1 does not require a formal tool. A SWOT, PESTLE analysis, or facilitated workshop can all work, provided the results include environmental conditions and connect to your risks and opportunities under clause 6.1.1.
What is the difference between interested parties' needs and compliance obligations?
Interested parties' needs and expectations are everything relevant stakeholders want or require. Clause 4.2 asks you to decide which of them become compliance obligations, meaning legal requirements plus other requirements you must or choose to comply with, as defined in clause 3.2.9.
Does ISO 14001 require organizations to address climate change in their context analysis?
Since ISO 14001:2015/Amd 1:2024, clause 4.1 requires the organization to determine whether climate change is a relevant external or internal issue. The amendment does not mandate that it be judged relevant, but you need to show you considered it. Clause 4.2 also notes that interested parties can have climate-related requirements.
Can I exclude part of my operations from the EMS scope?
You can define a scope that covers selected sites, activities, or units, and you should state exclusions and reasons. However, clause 4.3 says all activities, products, and services within the defined scope must be included, and the scope must not be set to avoid compliance obligations or mislead interested parties about the EMS.
Jared Clark
Principal Consultant, Certify Consulting
Jared Clark is the founder of Certify Consulting, helping organizations achieve and maintain compliance with international standards and regulatory requirements.