| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | ISO 14001:2026 clause | Requirement — original excerpt | Explanation, examples and evidence | Documentary evidence required? | Yes | No | Not applicable | Client evidence / gap / justification | |||||||||||||||||||
2 | 4.1 | The organization shall determine external and internal issues that are relevant to its purpose and that affect its ability to achieve the intended outcomes of its environmental management system. | Identify internal and external issues affecting EMS outcomes, such as site location, resource availability, technology and customer expectations. No standalone context document is prescribed. Supporting evidence: managers explain relevant issues and demonstrate how operational decisions address them; a context review can help. | No | — | ||||||||||||||||||||||
3 | 4.1 | These issues shall include environmental conditions being affected by the organization or capable of affecting the organization, such as pollution levels, availability of natural resources, climate change, biodiversity or ecosystem health (see A.4.1). | Consider environmental conditions affected by the organisation and those affecting it: pollution, resources, climate, biodiversity and ecosystem health. No separate report for each topic is required. Supporting evidence: a reasoned understanding of local and life-cycle conditions reflected in operational choices; not every example automatically requires a separate objective. | No | — | ||||||||||||||||||||||
4 | 4.2 a–c | which of these needs and expectations become its compliance obligations (see 6.1.3) and will be addressed through the environmental management system. | Identify relevant parties, needs/expectations and which become compliance obligations. Mandatory legal requirements cannot be opted out of; accepted voluntary commitments also count. A stakeholder matrix itself is not mandatory. Supporting evidence: responsible staff explain affected parties and requirements; resulting compliance obligations must be documented under 6.1.3. | No | — | ||||||||||||||||||||||
5 | 4.3 a–e | The organization shall determine the boundaries and applicability of the environmental management system to establish its scope. | Define scope considering context, obligations, functions/sites, activities/products/services and authority to control or influence their life cycle. A documented scope is required. Example: an approved statement clearly describing organisational and physical boundaries, including relevant relationships with a parent organisation. | Yes | — | ||||||||||||||||||||||
6 | 4.3 | Once the scope is defined, all activities, products and services of the organization within that scope shall be included in the environmental management system. | Include all activities, products and services within the defined scope. The documented scope is required by 4.3; check it against site operations, including auxiliary areas. Do not use boundaries to evade significant aspects or compliance obligations. A separate document for each included activity is unnecessary. | Yes | — | ||||||||||||||||||||||
7 | 4.3 | The scope shall be available as documented information and shall be available to interested parties. | Keep the documented EMS scope available to interested parties. An approved scope statement, website page or provision on request can work. A certificate alone does not replace an accurate description of the management system boundaries. | Yes | — | ||||||||||||||||||||||
8 | 4.4 | The organization shall consider the knowledge gained in 4.1 and 4.2 when establishing and maintaining the environmental management system. | Establish, implement, maintain and improve the EMS and interacting processes to achieve intended outcomes, including better environmental performance. Use context and stakeholder knowledge. No separate EMS manual or process map is mandated. Supporting evidence: purchasing, operations and design actually apply environmental controls and coordinate responsibilities. | No | — | ||||||||||||||||||||||
9 | 5.1 a–c | taking accountability for the effectiveness of the environmental management system; | Management remains accountable, aligns policy/objectives with context and strategy, and integrates the EMS into business processes. No separate leadership declaration is required. Supporting evidence: management participation, environmental criteria in investment/purchasing decisions and action on recurring problems. | No | — | ||||||||||||||||||||||
10 | 5.1 d–i | ensuring that the environmental management system achieves its intended outcomes; | Management provides resources, communicates the importance of the EMS, supports people and relevant managers, ensures results and promotes improvement. No standalone leadership report is required. Supporting evidence: funded controls, completed management actions and practical support to staff; appointing an environmental specialist alone is insufficient. | No | — | ||||||||||||||||||||||
11 | 5.2 a–c | includes a commitment to the protection of the environment, including prevention of pollution and other specific commitment(s) relevant to the context of the organization; | The environmental policy fits purpose/context, scale and impacts, provides a basis for objectives and commits to environmental protection, pollution prevention and relevant specific commitments. A documented policy is required. Examples of context-specific commitments include water conservation or protecting local ecosystems. | Yes | — | ||||||||||||||||||||||
12 | 5.2 d–e | includes a commitment to continual improvement of the environmental management system to enhance environmental performance. | The documented policy must include meeting compliance obligations and continual EMS improvement to enhance environmental performance. Check that both commitments appear in the actual text and guide organisational action. A generic environmental slogan is not sufficient. | Yes | — | ||||||||||||||||||||||
13 | 5.2 | be available as documented information; | Keep the policy documented, communicated internally and available to interested parties. Required document: the current policy. Staff interviews and operational decisions demonstrate understanding and application; a separate sign-off sheet is not specifically required. | Yes | — | ||||||||||||||||||||||
14 | 5.3 | Top management shall ensure that the responsibilities and authorities for relevant roles are assigned and communicated within the organization. | Assign and communicate responsibilities, including EMS conformity and reporting EMS/environmental performance to top management. No particular appointment order or role matrix is prescribed. Supporting evidence: staff know who decides and reports, responsibilities are consistently understood and cover absences. | No | — | ||||||||||||||||||||||
15 | 6.1.1 | The organization shall establish, implement and maintain (a) process(es) needed to meet the requirements in 6.1.2 to 6.1.5. | Establish processes for aspects, obligations, risks/opportunities and action planning. Under 6.1.1 these processes must be documented to the extent necessary for confidence in planned execution. A combined method with supporting registers can suffice; separate procedures for every subclause are unnecessary. | Yes | — | ||||||||||||||||||||||
16 | 6.1.2 | Within the defined scope of the environmental management system, the organization shall determine the environmental aspects of its activities, products and services that it can control and those that it can influence, and their associated environmental impacts, considering a life cycle perspective. | Identify controllable/influenceable aspects and impacts across relevant life-cycle stages. Document aspects and associated impacts as required by 6.1.2. Example: water use/resource depletion or packaging/end-of-life waste. A full quantitative life-cycle assessment is not mandated; a documented aspect-impact evaluation may suffice. | Yes | — | ||||||||||||||||||||||
17 | 6.1.2 a–c | normal and abnormal conditions; | Include normal/abnormal conditions, changes and new developments, modified activities/products/services and potential emergencies in aspect identification. Required documentation: aspects and impacts reflecting these conditions. Examples include filter operation, maintenance, start-up and failure in an aspect register. | Yes | — | ||||||||||||||||||||||
18 | 6.1.2 | The organization shall determine potential emergency situations (see 8.2), including those that can have an environmental impact. | Determine potential emergencies, including environmental effects, such as spills, firewater or treatment failure. Document associated aspects/impacts under 6.1.2 and necessary planning/response processes under 6.1.1/8.2. A scenario list linked to the aspect register and emergency arrangements is a practical form; no past incident is needed for applicability. | Yes | — | ||||||||||||||||||||||
19 | 6.1.2 | The organization shall determine those aspects that have or can have a significant environmental impact (i.e. significant environmental aspects) by using established criteria. | Use established criteria to determine significant environmental aspects. Document the criteria and resulting significant aspects. Examples: severity, scale and frequency of impacts. Check that assessment is reproducible and environmental significance is not arbitrarily downgraded through unrelated criteria. | Yes | — | ||||||||||||||||||||||
20 | 6.1.2 | The organization shall communicate its significant environmental aspects among the various levels and functions of the organization, as appropriate. | Communicate significant aspects to relevant levels/functions. No separate aspect-briefing form is specifically prescribed by this sentence. Supporting evidence: purchasing and operators correctly explain relevant aspects and controls. Appropriate communication evidence is nevertheless required under 7.4.1 and can be existing instructions or briefing records. | No | — | ||||||||||||||||||||||
21 | 6.1.2 | The following shall be available as documented information: — environmental aspects and associated environmental impacts; — criteria used to determine its significant environmental aspects; — significant environmental aspects. | Keep all three explicitly required elements documented: aspects/impacts, significance criteria and significant aspects. A single register with the evaluation method can cover them. Check that the information is current and includes relevant activities and conditions, not merely a list of waste types. | Yes | — | ||||||||||||||||||||||
22 | 6.1.3 a–c | determine how these compliance obligations apply to the organization; | Identify and access obligations related to aspects, determine their applicability and incorporate them into the EMS. Compliance obligations must be documented. Example: a register linking permit conditions, legal requirements and accepted commitments to the relevant site/process and responsible function. | Yes | — | ||||||||||||||||||||||
23 | 6.1.3 | The compliance obligations shall be available as documented information. | Keep documented compliance obligations available. A list of law titles alone is insufficient if actual applicable duties are unclear. Example: current register of specific requirements with sources, permit conditions and accepted contractual/voluntary obligations. Required legal documents depend on activity and jurisdiction. | Yes | — | ||||||||||||||||||||||
24 | 6.1.4 a–c | The risks and opportunities that need to be addressed shall be available as documented information. | Document risks/opportunities needing action, considering context, parties, scope, aspects and obligations. Examples: drought threatens water supply; closed-loop water use offers improvement. Link them to intended EMS outcomes, prevention/reduction of undesirable effects and continual improvement. A risk/opportunity register or integrated planning record can suffice. | Yes | — | ||||||||||||||||||||||
25 | 6.1.5 a | The organization shall plan: a) to take actions to address its: 1) significant environmental aspects determined in 6.1.2; 2) compliance obligations determined in 6.1.3; 3) risks and opportunities determined in 6.1.4; | Plan action for significant aspects, compliance obligations and risks/opportunities. Under 6.1.1 document the planning process to the extent necessary for reliable execution. Examples: integrated actions for bunding, permit controls and water resilience. An annual objectives list alone may not cover all three groups. | Yes | — | ||||||||||||||||||||||
26 | 6.1.5 b | evaluate the effectiveness of these actions (see 9.1). | Plan implementation within EMS or other business processes and effectiveness evaluation, considering technology, financial, operational and business requirements. Necessary process documentation falls under 6.1.1; evaluation results are retained under 9.1.1. Example: an investment/action plan linked to actual resource-loss or emission reductions. | Yes | — | ||||||||||||||||||||||
27 | 6.2.1 | The organization shall establish environmental objectives at relevant functions and levels, taking into account the organization's significant environmental aspects and related compliance obligations, and considering its risks and opportunities. | Set documented objectives for relevant functions/levels, taking significant aspects and related obligations into account and considering risks/opportunities. Example: reduce water use per unit by 8% without compromising treatment quality. The objectives themselves must be documented; a separate objective for every significant aspect is not required. | Yes | — | ||||||||||||||||||||||
28 | 6.2.1 a–f | measurable (if practicable); | Objectives must align with policy, be measurable where practicable, monitored, communicated, updated and documented. Use assessable outcomes for qualitative objectives. Required information: the objectives, for example an approved list or business-plan section; progress data can show monitoring. | Yes | — | ||||||||||||||||||||||
29 | 6.2.2 a–e | how the results will be evaluated, including indicators for monitoring progress toward achievement of its measurable environmental objectives (see 9.1.1). | Determine actions, resources, responsibilities, completion dates and evaluation, including progress indicators; consider integration into business processes. A separate objective-achievement plan is not expressly required by 6.2.2. Supporting evidence: owners know actions/timing and demonstrate resources and progress. Objectives and monitoring results have separate documentation requirements. | No | — | ||||||||||||||||||||||
30 | 6.3 | The changes shall be managed to ensure that the organization can achieve the intended outcomes of its environmental management system. | Plan and manage changes that affect or can affect the EMS. Examples: new materials, lines, sites or contractors. No dedicated change form is prescribed by 6.3. Supporting evidence: aspects/obligations and controls are updated before implementation and staff are prepared. Existing required EMS documents must remain current. | No | — | ||||||||||||||||||||||
31 | 7.1 | The organization shall determine and provide the resources needed for the establishment, implementation, maintenance and continual improvement of the environmental management system. | Provide resources needed for the EMS, such as skilled people, monitoring funds, functioning treatment equipment and spill response supplies. No standalone resource plan is mandatory. Supporting evidence: actual availability and adequacy of people/equipment when needed; budgets or contracts may corroborate this. | No | — | ||||||||||||||||||||||
32 | 7.2 a–c | determine training needs associated with its environmental aspects and its environmental management system; | Define competence affecting environmental performance and obligations, verify education/training/experience and identify training needs, including controlled contractors. Competence evidence is expressly required by 7.2. Examples: qualifications, verified experience and practical assessments; a separate training-needs matrix is optional. | Yes | — | ||||||||||||||||||||||
33 | 7.2 d | where applicable, take actions to acquire the necessary competence, and evaluate the effectiveness of the actions taken. | Address competence gaps and evaluate action effectiveness. Documentary competence evidence is required by 7.2. Examples: practical verification after waste-handling training, assessment results or task authorisation. Course attendance alone does not show effective learning. | Yes | — | ||||||||||||||||||||||
34 | 7.2 | Appropriate documented information shall be available as evidence of competence. | Keep appropriate competence evidence available. Examples: qualifications, relevant training, verified experience, practical assessments or authorisations. Choose evidence appropriate to environmental responsibilities, including aspect evaluation, compliance evaluation, auditing and emergency response where relevant. | Yes | — | ||||||||||||||||||||||
35 | 7.3 a–d | the significant environmental aspects and related actual or potential environmental impacts associated with their work; | People understand policy, job-related significant aspects/impacts, their contribution and consequences of failing EMS requirements or obligations. No mandatory awareness sign-off is specified. Supporting evidence: workers correctly explain waste controls, spill response and their role, and act consistently with that understanding. | No | — | ||||||||||||||||||||||
36 | 7.4.1 a–d | The organization shall establish, implement and maintain the process(es) needed for internal and external communications relevant to the environmental management system including: a) on what it will communicate; b) when to communicate; c) with whom to communicate; d) how to communicate. | Define communication topics, timing, recipients and methods, considering obligations. No separate communications matrix is mandated, but appropriate evidence of actual communications is required elsewhere in 7.4.1. Examples: submitted reports, correspondence, notifications or briefing records showing the process works. | Yes | — | ||||||||||||||||||||||
37 | 7.4.1 | ensure that environmental information communicated is consistent with information generated within the environmental management system and is reliable. | Ensure communicated environmental information is reliable and consistent with EMS data. No separate reliability certificate is prescribed. Supporting evidence: published figures reconcile with underlying monitoring/accounting data and responsible staff can explain the method. Actual communications and monitoring results have their own record requirements. | No | — | ||||||||||||||||||||||
38 | 7.4.1 | The organization shall respond to relevant communications on its environmental management system. | Respond to relevant EMS communications and keep appropriate evidence under 7.4.1. Examples: an odour complaint response, regulatory correspondence or sent notifications. If no incoming messages occurred, check the channel and response arrangements rather than inventing replies. | Yes | — | ||||||||||||||||||||||
39 | 7.4.2 a–b | ensure that its communication process(es) enable(s) persons doing work under the organization's control to contribute to continual improvement. | Communicate relevant information and changes internally and enable controlled personnel to contribute to improvement. Keep appropriate communication evidence under 7.4.1. Examples: shift briefings, communicated changes, logged improvement suggestions and responses. Interviews help establish that communication is effective. | Yes | — | ||||||||||||||||||||||
40 | 7.4.3 | The organization shall externally communicate information relevant to the environmental management system, as established by the organization's communication process(es) and as required by its compliance obligations. | Communicate externally as defined by the process and compliance obligations. Keep appropriate evidence under 7.4.1, such as submitted reports, stakeholder responses or contractor requirements. Retain confirmation of submission where relevant; the standard does not prescribe one universal reporting form. | Yes | — | ||||||||||||||||||||||
41 | 7.5.1 a–b | documented information determined by the organization as being necessary for the effectiveness of the environmental management system. | Include standard-required information and any additional information needed for EMS effectiveness. Required documents/records arise from applicable clauses and the organisation's needs. Existing business systems may be used; a standalone EMS manual is not required. | Yes | — | ||||||||||||||||||||||
42 | 7.5.2 a–c | review and approval for suitability and adequacy. | Ensure suitable identification/description, format/media and review/approval of new or updated documents. No separate approval protocol is prescribed. Supporting evidence: current identifiers, authorised revisions and a demonstrable approval workflow in the existing system. | No | — | ||||||||||||||||||||||
43 | 7.5.3 | it is adequately protected (e.g. from loss of confidentiality, improper use, or loss of integrity). | Ensure document availability, suitability and protection; control access, storage/legibility, changes, retention and disposal. No separate document-control procedure is mandatory. Supporting evidence: current instructions can be retrieved, access restrictions work and retained records remain readable; backup recovery can demonstrate protection. | No | — | ||||||||||||||||||||||
44 | 7.5.3 | Documented information of external origin determined by the organization to be necessary for the planning and operation of the environmental management system shall be identified as appropriate, and controlled. | Identify and control external information needed for the EMS, such as permits, equipment manuals and applicable standards. No separate external-document register is prescribed. Supporting evidence: staff use current authorised sources and can access relevant information; the underlying permits and other required information must still be available. | No | — | ||||||||||||||||||||||
45 | 8.1 | establishing operating criteria for the process(es); | Establish operating criteria and control processes to meet EMS requirements and Clause 6 actions. Under 8.1 document processes to the extent necessary for planned execution. Examples: tank filling limits, filter settings, storage rules and waste-handling instructions reflecting actual controls. | Yes | — | ||||||||||||||||||||||
46 | 8.1 | The organization shall control planned changes and review the consequences of unintended changes, taking action to mitigate any adverse effects, as necessary. | Control planned changes and assess/mitigate consequences of unintended changes. Document the operating process to the extent necessary under 8.1; no universal change-record form is prescribed. Examples: a temporary-control instruction or approved revised settings for reagent substitution, supported by impact evaluation where needed. | Yes | — | ||||||||||||||||||||||
47 | 8.1 | The type and extent of control or influence to be applied shall be defined within the environmental management system. | Define and apply control/influence over external processes, products and services relevant to EMS outcomes. Document necessary operational arrangements under 8.1. Examples: environmental contract conditions, contractor instructions and supplier checks proportionate to waste transport, chemicals or site works. | Yes | — | ||||||||||||||||||||||
48 | 8.1 a | establish controls, as appropriate, to ensure that its environmental requirement(s) is (are) addressed in the design and development process for the product or service, considering each life cycle stage; | Address relevant environmental requirements in product/service design across life-cycle stages. Document necessary controls under 8.1, for example design specifications or review criteria covering materials, energy use, repairability and disposal. The extent depends on appropriate control/influence and the nature of design activity. N/A applies only to this conditional design-control activity where there is no relevant design activity or ability to control/influence it. Justify the decision; 8.1 as a whole remains applicable. | Yes | |||||||||||||||||||||||
49 | 8.1 b–c | communicate its relevant environmental requirement(s) to external providers, including contractors; | Determine appropriate environmental purchasing requirements and communicate relevant requirements to providers/contractors. Required information is the necessary operational documentation under 8.1 and appropriate communication evidence under 7.4.1. Examples: purchase conditions, packaging requirements, waste rules and contractor briefings. | Yes | — | ||||||||||||||||||||||
50 | 8.1 d | consider the need to provide information about potential significant environmental impacts associated with the transportation or delivery, use, end-of-life treatment and final disposal of its products and services. | Consider whether information is needed about significant impacts during delivery, use and end of life. Under 8.1 document the process to the extent necessary; actual information is needed only where the consideration identifies a need. Examples: handling/disposal instructions. A separate written negative decision is not automatically required. | Yes | — | ||||||||||||||||||||||
51 | 8.1 | The process(es) for 8.1 shall be available as documented information to the extent necessary to have confidence that they are carried out as planned. | Document operational control processes to the extent needed for confidence in planned execution. Examples: treatment instructions, storage rules, contractor controls and inspection checklists. The documentation should express actual operating criteria, not only general environmental intentions. | Yes | — | ||||||||||||||||||||||
52 | 8.2 | The organization shall establish, implement and maintain the process(es) needed to prepare for and respond to the potential emergency situations determined in 6.1.2. | Prepare for and respond to the emergencies identified in 6.1.2. Document response processes to the extent necessary under 8.2. Examples: a spill plan, roles, contacts, isolation points and required equipment. Verify that supplies are available and personnel understand the arrangements. | Yes | — | ||||||||||||||||||||||
53 | 8.2 a–c | respond to actual emergency situations; | Plan prevention/mitigation and respond proportionately to actual emergencies. Document necessary response processes under 8.2; incident records may also be required by obligations or 10.2 when a nonconformity occurs. If no emergencies occurred, verify preparedness and do not create fictitious event records. | Yes | — | ||||||||||||||||||||||
54 | 8.2 d | periodically test the planned response action(s), where practicable; | Periodically test planned responses where practicable, for example a simulated spill, notification test or tabletop exercise. Document the testing process as necessary under 8.2; an exercise report is a useful form of supporting evidence, not a universally prescribed template. Use findings to improve arrangements. N/A applies only to a specific test that is not practicable. Explain why and consider a safe alternative. This does not exclude 8.2 as a whole. | Yes | |||||||||||||||||||||||
55 | 8.2 e | periodically review and revise the process(es) and planned response action(s), in particular after the occurrence of emergency situations or tests; | Review and revise response processes periodically, especially after emergencies/tests. Keep necessary documented response arrangements current under 8.2. Examples: revised contacts, equipment lists or drainage-isolation instructions addressing identified weaknesses. A separate review protocol is not prescribed for every revision. | Yes | — | ||||||||||||||||||||||
56 | 8.2 f | provide relevant information and training related to emergency preparedness and response, as appropriate, to relevant interested parties, including persons working under its control. | Provide appropriate emergency information and training to relevant parties, including controlled personnel. Necessary process documentation is required under 8.2 and competence evidence under 7.2. Examples: instructions, briefing materials and practical assessment of responders. Include contractors/security or external responders where relevant. | Yes | — | ||||||||||||||||||||||
57 | 8.2 | The process(es) for 8.2 shall be available as documented information to the extent necessary to have confidence that they are carried out as planned. | Keep emergency preparedness/response processes documented to the extent necessary for planned execution. Examples: current emergency plan, site layout, contacts, action sequence and assigned roles. The information must be usable when an emergency occurs, not merely stored in an inaccessible folder. | Yes | — | ||||||||||||||||||||||
58 | 9.1.1 a–e | The organization shall evaluate its environmental performance and the effectiveness of the environmental management system. | Define what/how/when to monitor, measure and analyse, performance criteria/indicators and evaluation timing. Evaluate environmental and EMS performance. 9.1.1 expressly requires evidence of results, such as resource/waste data, discharge results, objective progress and evaluation conclusions. | Yes | — | ||||||||||||||||||||||
59 | 9.1.1 | The organization shall ensure that calibrated or verified monitoring and measurement equipment is used and maintained, as appropriate. | Use and maintain calibrated/verified equipment as appropriate. This sentence does not separately require a particular calibration certificate. Supporting evidence: identifiable valid status, reference checks and maintenance, including external laboratory arrangements. Certificates may support this or be required by compliance obligations; monitoring results must be retained separately under 9.1.1. N/A applies only where relevant monitoring/measuring equipment is neither used nor needed. Outsourcing measurements does not remove the need for reliable results. | No | |||||||||||||||||||||||
60 | 9.1.1 | The organization shall communicate relevant environmental performance information both internally and externally, as identified in its communication process(es) and as required by its compliance obligations. | Communicate relevant environmental performance information internally/externally according to processes and obligations. Appropriate communication evidence is required under 7.4.1. Examples: management reports, notifications of exceedances and submitted external reports linked to underlying performance data. | Yes | — | ||||||||||||||||||||||
61 | 9.1.1 | Appropriate documented information shall be available as evidence of the monitoring, measurement, analysis and evaluation results. | Retain monitoring, measurement, analysis and evaluation results. Examples: laboratory reports, resource/waste accounts, intensity calculations and trend conclusions. Raw figures alone may not demonstrate the required evaluation; results should have identifiable periods and sources. | Yes | — | ||||||||||||||||||||||
62 | 9.1.2 | The organization shall establish, implement and maintain the process(es) needed to evaluate if it is meeting its compliance obligations. | Establish compliance evaluation processes and determine frequency. 9.1.2 requires documented evaluation results, not a particular procedure template. Example: a requirement-by-requirement assessment linked to permits, records and submitted reports. A legal register or absence of fines alone does not demonstrate compliance evaluation. | Yes | — | ||||||||||||||||||||||
63 | 9.1.2 b–c | evaluate compliance and take action if needed; | Evaluate compliance, take needed action and maintain knowledge of current status. Required evidence: evaluation results under 9.1.2, showing the obligation checked, evidence, conclusion and any action needed. Example: assessment of permit conditions against measurement and reporting records. | Yes | — | ||||||||||||||||||||||
64 | 9.1.2 | Appropriate documented information shall be available as evidence of the compliance evaluation result(s). | Retain compliance-evaluation results. A useful form is obligation, evidence checked, result, gap/action and date. This is distinct from a general EMS audit, although the activities may be combined if both purposes are met. A blank checklist is not a completed evaluation. | Yes | — | ||||||||||||||||||||||
65 | 9.2.1 a–b | The organization shall conduct internal audits at planned intervals to provide information on whether the environmental management system: a) conforms to: 1) the organization’s own requirements for its environmental management system; 2) the requirements of this document; b) is effectively implemented and maintained. | Audit at planned intervals against internal and standard requirements and effective implementation/maintenance. Programme and audit evidence are required by 9.2.2. Examples: completed reports based on operations, interviews and sampled records, rather than document-presence checks alone. | Yes | — | ||||||||||||||||||||||
66 | 9.2.2 | The organization shall establish, implement and maintain (an) internal audit programme(s), including the frequency, methods, responsibilities, planning requirements and reporting of its internal audits. | Document an audit programme covering frequency, methods, responsibilities, planning and reporting, considering environmental importance, changes and previous results. 9.2.2 explicitly requires the programme itself, implementation evidence and results. A schedule with risk-based coverage and linked reports is a practical format. | Yes | — | ||||||||||||||||||||||
67 | 9.2.2 a–c | select auditors and conduct audits to ensure objectivity and the impartiality of the audit process; | Define objectives, criteria and scope for each audit; ensure auditor objectivity/impartiality and report to relevant management. Keep implementation and audit-result evidence under 9.2.2. Examples: audit plan, suitable auditor assignment, report and evidence that management received the findings. | Yes | — | ||||||||||||||||||||||
68 | 9.2.2 | The following documented information shall be available: — the audit programme(s); — evidence of the implementation of the audit programme(s); — evidence of the audit results. | Keep all three documented elements: audit programme, evidence of its implementation and audit results. Examples: current programme, completed reports and findings. A planned calendar alone does not establish implementation or results. | Yes | — | ||||||||||||||||||||||
69 | 9.3.1 | Top management shall review the organization's environmental management system, at planned intervals, to ensure its continuing suitability, adequacy and effectiveness. | Top management reviews the EMS at planned intervals for suitability, adequacy and effectiveness. Document results under 9.3.3. Examples: management minutes or coordinated regular reviews with conclusions; it need not be a separate standalone meeting if all required topics/results are covered. | Yes | — | ||||||||||||||||||||||
70 | 9.3.2 a–b | the status of actions from previous management reviews; | Review previous actions and changes in context, interested-party requirements/obligations, significant aspects and risks/opportunities. Review results must be documented under 9.3.3. A consolidated review record can show these inputs were considered; separate reports for every topic are not prescribed. | Yes | — | ||||||||||||||||||||||
71 | 9.3.2 c–g | opportunities for continual improvement. | Review objective achievement; trends in nonconformities/actions, monitoring, compliance and audits; resources; stakeholder communications/complaints; and improvement opportunities. Document the review results under 9.3.3. An integrated review pack with trends, explanations and decisions can meet the need. | Yes | — | ||||||||||||||||||||||
72 | 9.3.3 a–c | conclusions on the continuing suitability, adequacy and effectiveness of the environmental management system; | Record conclusions on EMS suitability, adequacy and effectiveness, decisions on improvement opportunities and needed changes, including resources. Required evidence: management review results, such as approved minutes or electronic decisions. A presentation containing only input data is insufficient. | Yes | — | ||||||||||||||||||||||
73 | 9.3.3 d–f | actions, if needed, when environmental objectives have not been achieved; | Review results include actions where objectives were missed, opportunities for business-process integration where needed and implications for strategy. Document these results under 9.3.3. If further action is unnecessary, the basis should be understandable; do not invent actions merely to fill a template. | Yes | — | ||||||||||||||||||||||
74 | 9.3.3 | Documented information shall be available as evidence of the results of management reviews. | Retain evidence of management review results. Examples: minutes containing conclusions and decisions or approved electronic actions. Owners and deadlines help implementation but no fixed minutes template is specified. Input presentations without resulting conclusions/decisions do not cover the full requirement. | Yes | — | ||||||||||||||||||||||
75 | 10.1 | The organization shall continually improve the suitability, adequacy and effectiveness of the environmental management system to enhance environmental performance by determining opportunities for improvement (see Clause 9 and 10.2) and implementing necessary actions to achieve the intended outcomes of its environmental management system. | Determine and implement improvement opportunities from performance evaluation and nonconformities to improve the EMS and environmental performance. No separate improvement register is required. Supporting evidence: reduced resource losses, prevented spills or more effective controls. Improvement need not occur everywhere simultaneously; related monitoring/review records have their own requirements. | No | — | ||||||||||||||||||||||
76 | 10.2 a | deal with the consequences, including mitigating adverse environmental impacts; | React to nonconformities through control/correction and handling consequences, including environmental impacts. Required records under 10.2 cover the actual issue and subsequent actions. Examples: leak containment, clean-up and follow-up case records. Without an actual event, verify response readiness rather than manufacturing records. | Yes | — | ||||||||||||||||||||||
77 | 10.2 b–c | determining the cause(s) of the nonconformity; | Assess the need to eliminate causes by reviewing the issue, its causes and similar actual/potential cases; implement needed action. Required evidence under 10.2 includes the issue, actions and corrective-action results. Example: investigate tank overfill and check other tanks for the same cause. | Yes | — | ||||||||||||||||||||||
78 | 10.2 d–e | review the effectiveness of any corrective action taken; | Review action effectiveness and change the EMS where needed, proportionate to significance and environmental impacts. Required evidence includes corrective-action results. Examples: repeat checks of protective controls and no recurrence over an appropriate period, supported by changed procedures where necessary. | Yes | — | ||||||||||||||||||||||
79 | 10.2 | Documented information shall be available as evidence of: — the nature of the nonconformities and any subsequent actions taken; — the results of any corrective action. | Keep records of actual nonconformities, subsequent actions and corrective-action results. Examples: a case record showing the event, cause, measures and effectiveness review. Do not create records for events that did not occur; note the absence of cases and check process readiness as appropriate. | Yes | — | ||||||||||||||||||||||
80 | |||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||
100 |