In short
ISO 9001 describes PDCA in its introduction and applies it both to individual processes and to the quality management system as a whole.
ISO 14001 and ISO 45001 state PDCA as the basis of the system; ISO/IEC 27001 does not name it but shares the same structure, up to clause 10 on improvement.
Correction, corrective action and continual improvement are three different things: only the last two act on causes or on future performance.
The cycle most often breaks between Check and Plan: management review decisions must become objectives and actions with an owner.
The auditor does not look for a PDCA document, but for linked evidence: objectives with a baseline, monitoring, audits, actions and decisions.
Plan, Do, Check, Act: the engine of every ISO standard in four steps, with examples from quality, environment and safety. The PDCA cycle is the pattern through which a management system learns from its own results: you plan, you do, you check, you adjust course and you start again. It sounds simple, and in theory it is. In practice many certified companies know it by heart but only turn it once a year, usually a few weeks before the audit.
In this guide we look at what ISO 9001 actually says about PDCA, why the same pattern also underpins ISO 14001, ISO 45001 and ISO/IEC 27001, and what the difference is between fixing a problem and improving continually. Then we get practical: three complete examples, one for quality, one for the environment and one for occupational health and safety, showing what happens in each phase. We close with the mistakes that stall the cycle and the evidence an auditor expects to see. If you are looking for an introduction to the quality system as a whole, start with our guide to the ISO 9001 quality management system: here we focus on continual improvement and how to make it a habit.
What is the PDCA cycle and what does ISO 9001 say about it?
The PDCA cycle is an iterative four-phase method to plan, carry out, check and improve. ISO 9001 presents it in its introduction (clause 0.3.2 in the 2015 edition) as one of the pillars of the process approach, alongside risk-based thinking. The standard states that the cycle applies to all processes and to the quality management system as a whole. The new edition, ISO 9001:2026, published in September 2026, keeps the process approach section (0.3) in its introduction: if you are planning the transition, check in the new text how the reference to the cycle is worded.
The four phases according to the standard
The ISO 9001 description is concise, and that is exactly what makes it useful. Summarised, it reads like this:
Plan: set the objectives of the system and its processes and the resources needed to deliver results in line with customer requirements and the organisation's policies; identify and address risks and opportunities.
Do: implement what was planned.
Check: monitor and, where applicable, measure processes, products and services against policies, objectives, requirements and planned activities, and report the results.
Act: take actions to improve performance, as necessary.
Two details deserve attention. First, the Plan phase already includes risks and opportunities, so it is not just "making a plan" but deciding where to focus. Second, the Check phase ends with reporting the results. A measured figure that nobody reads does not feed the Act phase, and the cycle stops there.
A small cycle inside a large one
PDCA works on two scales at once. On a small scale it turns within a single process: order handling, machine maintenance, onboarding a new employee. On a large scale it turns across the whole management system, at a pace that usually matches the calendar of internal audits and management review.
The small cycles are the ones that produce visible improvements every month. The large cycle is the one that sets priorities: which processes deserve a new objective, which resources to shift, which risks have changed. A healthy system has both levels running. If only the large one turns, improvement arrives once a year; if only the small ones turn, details get fixed without a shared direction.
Why is PDCA the engine of all ISO management system standards?
PDCA is the common thread because ISO management system standards share the same basic structure. ISO calls it the Harmonized Structure: the same clauses, from context (4) to improvement (10), in the same order and with much identical text. On this framework the cycle almost reads itself.
ISO 14001 (including the new 2026 edition) and ISO 45001 say so explicitly: in their introductions they describe PDCA as the iterative process through which an organisation achieves continual improvement, applicable to the system and to each of its elements. ISO/IEC 27001 does not name PDCA in its text, but it has the same framework, with clause 10 devoted to improvement.
How the clauses of the standard map onto the cycle
ISO 9001 shows in a figure in its introduction how clauses 4 to 10 group in relation to PDCA: context is the starting point, leadership sits at the centre and the other parts are spread across the four phases. The table below follows that logic, which also applies to other standards with the same structure.
Phase | Clauses of the standard | What you find there in practice |
|---|---|---|
Starting point | 4 Context of the organisation | Internal and external issues, interested parties, scope |
At the centre of the cycle | 5 Leadership | Top management commitment, policy, roles and responsibilities |
Plan | 6 Planning | Risks and opportunities, objectives and plans to achieve them, planning of changes |
Do | 7 Support, 8 Operation | Resources, competence, documents, operational processes, suppliers |
Check | 9 Performance evaluation | Monitoring, measurement, internal audit, management review |
Act | 10 Improvement | Nonconformities, corrective actions, continual improvement |
This map is useful for a very practical reason: when a requirement feels abstract, asking which phase of the cycle it belongs to tells you what it is for. Management review, for example, sits in Check but produces decisions that feed the next Plan.
What does "continual improvement" really mean?
Continual improvement means increasing, over time, the system's ability to achieve its intended results. It does not mean improving everything, always, all at once. ISO treats it as one of the seven quality management principles described in ISO 9000, together with customer focus, leadership, engagement of people, process approach, evidence-based decision-making and relationship management.
Correction, corrective action, improvement: three different things
This is the distinction that causes the most confusion in audits. A correction removes the problem in front of you: you rework the defective part, call the customer back, replace the expired extinguisher. A corrective action removes the cause of the problem so that it does not happen again: you find out why the part was defective and change whatever produced it. We cover this in detail in the guide on corrective action and root cause analysis.
Continual improvement goes further: it does not necessarily start from a mistake. It can arise from an indicator that is good but could be better, from an opportunity identified during planning, from an operator's suggestion. The ISO 9001 introduction also notes that, alongside correction and continual improvement, an organisation may need other forms of improvement, such as breakthrough change, innovation and re-organisation.
Continual does not mean constant
Continual improvement moves in steps, not in a straight line. There are periods when a process stabilises and the right objective is to hold the result, and periods when it makes sense to raise the bar. A mature system can tell the two apart and writes it into its objectives. What the standard does not accept is a system that cannot say what has improved compared with the previous cycle, or why.
Quality example: reducing complaints in a machine shop
Take a precision machining shop with around forty employees, certified to ISO 9001. At management review it emerges that complaints about dimensional errors have increased over the last six months and that almost all of them concern one family of turned parts.
Plan: objective, likely cause, plan
The quality manager analyses the complaints and cross-checks the data against shifts and machines. The errors turn out to cluster after tooling changeovers. The objective becomes measurable: halve complaints about dimensional errors on that family of parts within six months. The plan introduces a mandatory first-piece inspection after every changeover, an updated set-up sheet and a short training session for the three operators involved. It also decides who records what, and where.
Do and Check: try on a small scale, then measure
The new check starts on a single machine for one month. Operators record the first-piece result after every set-up. At the end of the month the quality manager compares internal scrap and complaints with the previous period. Scrap falls, but an unexpected finding emerges: the check takes longer than planned because the measuring instrument is shared with another department.
Act: standardise and start again
Management decides to buy a second instrument, extends the check to all machines for that family of parts and updates the procedure. The complaints figure joins the monitored indicators reviewed every month. In the next cycle the objective changes: no longer halving complaints, but keeping them below the new threshold and shifting attention to delivery times. That is exactly the "step" of continual improvement.
Environmental example: less paper waste in a print shop
A print shop certified to ISO 14001 has identified paper waste and ink consumption among its significant environmental aspects. Here PDCA has the same shape but speaks the language of the environment.
In the Plan phase the company sets an environmental objective: reduce the percentage of paper wasted during machine make-ready, measured in kilos per job. It identifies the main cause as colour adjustments made "by eye" on the first sheets. The plan introduces standard colour profiles for the most used substrates and a waste record for every job. In the Do phase the profiles are introduced and the warehouse weighs the waste at the end of each shift.
In the Check phase, after three months, the data show a clear reduction on coated papers and almost no effect on recycled papers. Without measuring by substrate type, the average result would have hidden this difference. In the Act phase the print shop keeps the profiles where they work and opens a new cycle dedicated to recycled papers, involving the supplier. For the typical aspects of the environmental standard you can read more in the guide to the ISO 14001 environmental management system.
Safety example: near misses in the warehouse
A distribution company with a medium-sized warehouse works to ISO 45001. Injuries are rare, and precisely for that reason the injury figure alone says little. Management decides to use a leading indicator: reports of near misses, that is, events that could have caused harm.
Plan: a simple reporting method is set up (a short form, usable from a smartphone too), someone is named to analyse the reports every week and a participation objective is set, not a reduction one. At the start, in fact, an increase in reports is a good sign. Do: shift supervisors present the form in start-of-shift briefings and workers begin to use it.
Check: after two months the reports cluster on a crossing between a forklift aisle and a pedestrian walkway near the loading bays. Act: the company physically separates the routes, updates the risk assessment and communicates the change to everyone, including external drivers. The next cycle measures whether reports for that area go down, and meanwhile looks at new ones. The key point is that workers see reports turning into action: without that feedback, participation fades within a few weeks. If you are considering this standard, you will find the route on the page dedicated to ISO 45001 certification.
How to keep PDCA turning in your management system
PDCA works when each phase has a precise place in the system, an owner and a date. You do not need to invent new tools: the standard already gives them to you, you just need to connect them instead of managing them as separate obligations.
The tools the standard already puts in your hands
For the Plan phase you have the assessment of risks and opportunities and measurable objectives: on how to choose them and turn them into indicators there is a dedicated guide to objectives and KPIs in ISO systems. For the Do phase you have processes, work instructions and records. For the Check phase you have monitoring, internal audit and management review. For the Act phase you have nonconformity management, corrective actions and the decisions of the review.
The link most often lost is the one between Check and Plan. The outputs of management review (decisions on improvement opportunities, changes to the system, resources) should become objectives and actions for the next cycle, with a name next to them. If the review minutes end up in a folder and next year's objectives are a copy of the previous ones, the cycle has broken off halfway.
The right pace: short cycles and an annual cycle
A practical rule: let short cycles run on processes at the pace of their data, monthly or quarterly, and use the annual cycle for top management. An indicator you look at once a year leaves you no time to react. An indicator you look at every week without ever changing anything only creates effort. The right point lies in between, depends on the process and should be written down, not improvised.
This is also where the way you organise the work comes in. At Complaion, the dedicated Lead Auditor who follows your company helps you choose sensible objectives and indicators, while the platform collects the evidence for each phase, manages documents and keeps the schedule of activities: monitoring, corrective actions, internal audits, review. That way the cycle does not depend on one person's memory.
Which mistakes stall the PDCA cycle?
The mistakes that stop the cycle are almost always the same, in companies of every size. Spotting them early saves you audit findings and, above all, months of work that produce no results.
The first is Check without Act. Everything is measured, charts are produced, but nobody decides what to change. The second is Plan on paper only: generic objectives ("improve customer satisfaction") with no baseline, threshold, deadline or owner. Without these elements the Check phase has nothing to compare against.
The third mistake is confusing Act with "redo everything". If the result is good, the right action may be to standardise and consolidate, not to overturn. The fourth is turning the cycle only before the audit: forms are filled in retrospectively and the evidence describes a system that does not exist. The fifth is leaving out the people who do the work. In most cases the best ideas for the Plan phase come from those who operate the process, not from those who write the procedure.
A sixth, subtler mistake affects companies with several standards. Quality, environment and safety run three parallel PDCA cycles, with three reviews and three action lists that never talk to each other. If you manage several certifications, consider unifying the cycle in a single management review: we discuss it in the guide to management review.
What does the auditor look at to see whether the cycle works?
The auditor does not ask to see "the PDCA" as a document. They look for traces of the cycle in the evidence: an objective with a baseline, its monitoring over time, an internal audit that found something, an action that followed, a review that took decisions. It is the consistency of the evidence that shows the system learns.
A good test you can run yourself is to pick a problem that emerged over the last year and follow its path. Where was it recorded? Who analysed the cause? What changed in the process? How did you verify that the change worked? If you can answer all four questions by showing documents and records, your PDCA is turning. If you stop at the second, you already know where to act.
This exercise is also useful in preparation for surveillance audits, when the auditor looks in particular at how the system has changed since the previous visit. Keeping evidence in order during the year, rather than rebuilding it just before the audit, is the simplest way to arrive there with peace of mind.
How Complaion helps you keep PDCA turning all year
PDCA works when each phase leaves a trace and each trace leads to the next phase. This is where Complaion works with you. A dedicated Lead Auditor follows your company, helps you set measurable objectives, conducts the internal audit, the heart of the Check phase, and helps you turn findings and review decisions into concrete actions. The platform collects the evidence, manages documents, keeps the schedule of activities and prepares the audit, so the cycle does not stop between one audit and the next.
Whether you are starting with ISO 9001 or managing several standards together, we propose the route best suited to your company's needs. More than 1,000 clients have already chosen this model. If you want to understand how to apply it to your system, talk to our team and get a tailored quote.
Frequently asked questions about the PDCA cycle and continual improvement
What does PDCA stand for?
PDCA stands for Plan, Do, Check, Act. It is an iterative method for improving processes and management systems. ISO 9001 describes it in its introduction as one of the concepts underlying the process approach. The cycle applies both to a single process and to the whole system.
Is PDCA mandatory for ISO 9001 certification?
The standard does not require you to adopt PDCA as a stand-alone tool, nor to have a document describing it. It does, however, require you to meet requirements that, taken together, make up the cycle: objectives, operations, monitoring, internal audit, review, corrective actions and continual improvement. In practice, if the system works, PDCA is there.
What is the difference between PDCA and continual improvement?
Continual improvement is the goal, PDCA is the method for reaching it. Continual improvement is also one of the seven quality management principles described in ISO 9000. PDCA is the operating pattern through which that principle becomes concrete activities, repeated over time.
Does PDCA also apply to ISO 14001, ISO 45001 and ISO/IEC 27001?
Yes. ISO 14001 and ISO 45001 explicitly mention it in their introductions as the basis of the management system. ISO/IEC 27001 does not name it, but shares the same structure with the other standards, running from context to improvement. That is why a company with several certifications can manage a single integrated cycle.
How often should the PDCA cycle turn?
The standard does not set a single frequency. The cycle for the system as a whole usually follows the pace of internal audits and management review, which the standard requires at planned intervals and which many companies set on an annual basis. Cycles on individual processes can be much shorter, monthly or quarterly, depending on how often useful data come in.
What is the difference between correction and corrective action?
A correction removes the problem that has occurred, for example reworking a defective part. A corrective action removes the cause of the problem, to prevent it from happening again. Continual improvement goes beyond both, because it can also start from results that are already good and that you want to make better.
How do I show the auditor that continual improvement works?
By showing linked evidence: objectives with a baseline, their trends over time, internal audit results, corrective actions closed and verified, management review decisions turned into actions. The auditor looks for continuity across these traces, not a document dedicated to PDCA.
