ISO 14001 clause 10.1: make continual improvement evidence-led
ISO 14001:2026 clause 10.1 requires continual improvement of the EMS’s suitability, adequacy and effectiveness to enhance environmental performance. It connects improvement opportunities and necessary action with information from performance evaluation and nonconformity and corrective action. The 2026 numbering matters: continual improvement is addressed here, not in a separate clause 10.3.
What clause 10.1 requires in practice
Clause 10.1 asks the organisation to keep making its EMS more suitable, more adequate and more effective, with the aim of lifting environmental performance. It states two activities that make this real:
- determining opportunities for improvement, with reference to the evaluation activities in clause 9 and to nonconformity and corrective action in 10.2;
- implementing the actions necessary to achieve the intended outcomes of the EMS.
Several points follow from the wording. Improvement is aimed at the system and, through it, at environmental performance, so it is wider than closing audit findings. It is continual, which means recurring effort rather than a single project, but it does not require every indicator to improve every period. And the clause does not prescribe an improvement register, a fixed number of projects or a particular method. In the 2026 numbering, continual improvement sits here, with nothing further after 10.2.
Why continual improvement matters to the business
Operations, regulations and customer expectations keep moving, and a system that stands still slowly becomes less suitable. Continual improvement is how the business keeps its environmental management in step, finding cheaper ways to cut waste, steadier controls and clearer information for decisions. It supports cost control, supplier and customer confidence, and readiness for tighter requirements. It also gives teams a constructive purpose beyond avoiding findings. When improvement is tied to evidence, leaders can show which changes paid off and which did not, and can stop investing in activity that merely looks busy.
How to implement clause 10.1
Aim for a small number of well-chosen improvements with measurable consequences, rather than a long list of recorded actions. Keep the effort proportionate to the organisation, and judge the process by what improved, not by how many suggestions were collected. Share the reasoning with other teams so they can learn from the result as well as the change itself, and revisit past improvements to confirm the gain has lasted.
- Gather opportunities from monitoring, compliance evaluation, audits, management review, corrective-action learning and staff observations.
- Judge each one on expected benefit, obligations, resources, uncertainty and possible side effects, including burden moved to another impact.
- Decide the baseline and the basis for judging success before the change starts, allowing for output and product mix.
- Build the change into the process that controls the work, so it survives staff turnover.
- Check the outcome against the baseline, and report what changed and what the evidence supports.
- Test local solutions for fit before copying them to other sites.
- Use management review to set priorities and release resources.
Use evidence to identify worthwhile improvement
Monitoring, compliance evaluation, audits, management review and corrective-action learning can reveal where the system needs to change. An opportunity may involve better environmental outcomes, more reliable controls or a process that supports those outcomes more effectively. Improvement should have a reason grounded in the organisation’s circumstances.
Do not limit improvement to large capital projects. Clarifying a handover, changing purchasing criteria or improving the reliability of performance information can matter. Equally, rewriting a procedure is not automatically an improvement unless the change makes the system more suitable, adequate or effective.
Select and evaluate the action
Consider the expected benefit, relevant obligations, resources, uncertainty and possible unintended effects. Decide what action is appropriate and integrate it with the process that controls the work. Set a basis for evaluating whether the change produced the intended result.
Continual improvement does not mean that every indicator must improve every reporting period. Conditions and priorities can change. The organisation should demonstrate recurring improvement activity and its contribution to environmental performance, while explaining results accurately. A temporary adverse trend is a reason for understanding and action, not for manipulating the reporting boundary.
Two illustrative improvements
A manufacturer’s monitoring reveals that material losses recur during a particular changeover. Investigation identifies an opportunity to improve the work arrangement. The team evaluates an alternative, applies it under controlled conditions and compares results using a suitable basis. The improvement claim rests on the observed outcome and relevant consequences, not merely completion of a trial.
A software company finds that device-return information arrives too late for reliable end-of-use decisions. It changes the handover between HR, IT and the responsible provider, then checks whether records are complete at the right time. The improvement strengthens the system’s ability to manage environmental outcomes; it does not justify claiming a quantified environmental saving without supporting evidence.
Connect local learning with system change
A useful local solution may be relevant elsewhere, but assess suitability before copying it across sites. Different activities, environmental conditions or obligations can change the result. Share the reasoning and evidence so that other teams can decide whether the approach fits their circumstances.
Management review can help prioritise opportunities and provide resources. Corrective action can reveal systemic weaknesses requiring broader improvement. Keep the connection clear while recognising that not every improvement begins with a nonconformity.
Evidence and common mistakes
Clause 10.1 does not prescribe an improvement register or a fixed number of projects. Evidence can come from implemented changes, evaluation results and records required by connected processes. A practical improvement record may help preserve the problem, decision and result, but its format is optional.
Common weaknesses include counting suggestions as completed improvements, reporting only activity and repeatedly launching new initiatives without evaluating previous ones. Another is treating a favourable business trend as an EMS achievement without establishing a connection. Be precise about what changed and what the evidence supports.
Frequently asked questions
Must improvement always be a new project?
No. Improvements can be integrated into routine processes, provided their purpose and effect are meaningful.
Does every environmental measure have to improve each year?
No universal rule requires that. Evaluate performance and demonstrate continual improvement of the system in its context.
Is improvement limited to corrective action?
No. Corrective action is one source of learning; evaluation can also identify opportunities before a nonconformity occurs.
Select an improvement with a defensible result
Discuss an EMS improvement opportunity with Sterling, including implementation and evaluation evidence. The KPIs, Objectives and Management Review course supports useful result assessment. Effivity ISO & GRC automation software can be scoped to the agreed improvement process. See improvement and the complete directory.