Skip to content

Free template

Updated

PDCA template

A PDCA template is a one-page form for running one plan-do-check-act cycle: you plan a change from the problem and its cause, try it on a small scale, check the result against the goal, and act by standardizing what worked or adjusting and starting another cycle. This one puts the plan on the left (problem, goal, analysis and an action plan with owners and dates) and do, check and act on the right, with a results table that compares baseline, goal and result. The Excel version has the same cycle on one sheet, with a results table that works out the change, the share of the gap to the goal closed and whether the goal was met, a filled-in example, and a cycle log of one row per cycle.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

The PDCA templateA Plan box on the left with problem, goal, analysis and an action table, and Do, Check with a results table, and Act boxes on the right.
Plan: problem, goal, analysis, actionsDoCheck: baseline, goal, resultAct: standardize or adjustCycle numberCycle log

When to use it

When to use a PDCA template

  • For a small improvement you can test quickly, such as a new layout, a changed setting or a revised check.
  • When you want to test an idea on one line or shift before rolling it out everywhere.
  • To coach a team through structured problem solving without the full weight of an A3 or an 8D.
  • When a problem needs several tries: number each cycle and keep the sheets together.

How to fill it in

  1. 1

    Fill in the header

    Title, owner, team, start date and the cycle number, starting at 1.

  2. 2

    Describe the problem

    What is wrong, where, since when and how big, as a fact rather than a cause or a solution.

  3. 3

    Set the goal

    A measurable target with a date: from what to what, by when.

  4. 4

    Analyze the cause

    The current condition and the root cause, using data, a sketch of the process, the 5 Whys or a fishbone diagram.

  5. 5

    Plan the change and the measure

    What you will try, who does it and by when, and how you will measure the result. Record the baseline now.

  6. 6

    Do it on a small scale

    Run the change as planned on one line, shift or machine first. Note anything that went differently and collect the data.

  7. 7

    Check against the goal

    Fill in baseline, goal and result for each measure, and ask whether the change caused the result.

  8. 8

    Act

    If it worked, update the standard, train people and share it with similar areas. If not, write what you will change and start the next cycle.

The four stages

What happens at each PDCA stage

What each stage is for, what it produces and who usually does it. Check is the stage where the result is compared with the goal; act is where the change becomes the standard or the next cycle is planned.

  • Plan

    What happens
    Describe the problem with facts, set a measurable goal, find the root cause, choose the change to try and decide how the result will be measured. Record the baseline.
    Output
    Problem statement, goal with a date, root cause, action plan with owners and dates, the measure and its baseline.
    Who
    The owner and the people who do the work; the supervisor agrees the plan.
  • Do

    What happens
    Try the change as planned, on a small scale first: one line, shift or machine. Note what went differently and collect the data.
    Output
    The change in place in the trial area, notes on what happened, the data.
    Who
    The team in the trial area, led by the owner.
  • Check

    What happens
    Compare the result with the goal and the baseline, and ask whether the change caused it or something else did.
    Output
    Baseline, goal and result for each measure, and what was learned.
    Who
    The owner and the team, reviewed with the supervisor or manager.
  • Act

    What happens
    If it worked, update the standard, train every shift and share it with similar areas. If not, decide what to change and start the next cycle.
    Output
    An updated standard and training records, or the plan for the next cycle.
    Who
    The owner, the supervisor and whoever owns the standard.

A filled-in example

Illustrative, not a benchmark

A PDCA cycle on a label printer that keeps jamming on a packing line. The Excel version has the same example filled in.

The example's one cycle, stage by stage

  1. 1PlanAbout 6 jams a shift; goal 3 or fewer. 37 of 48 came after a roll change.
  2. 2DoA threading diagram at the printer, tried on day shift for two weeks.
  3. 3Check2.5 jams a shift on the trial shift; other shifts stayed near 6.
  4. 4ActMade standard, shown to every shift, copied to other lines.
Next cycle on the other lines
The trial shift closed 117% of the gap: (2.5 − 6) ÷ (3 − 6). So the change became the standard.
  • Plan: jams stop the line about 6 times a shift. Goal: 3 a shift or fewer on the trial shift within four weeks. Analysis: 37 of 48 jams logged in two weeks came within ten minutes of a label roll change, and operators threaded the roll three different ways. Action: a threading diagram at the printer and a short demonstration for each operator.
  • Do: tried on the day shift for two weeks; operators asked for the diagram to be moved to the printer door, which was done on day two.
  • Check: jams on the trial shift averaged 2.5 a shift against the goal of 3, which closes 117% of the gap ((2.5 − 6) ÷ (3 − 6)), while the other shifts stayed near 6.
  • Act: the diagram became part of the printer's standard, every shift was shown it, and it went up at the printers on the other lines.

One cycle on one page: the problem, the evidence, what was tried and whether it worked, ready to copy to other lines.

Common mistakes

  • Skipping the plan

    Going straight to a fix means you cannot tell whether it worked or why. Write the problem, the goal and the cause first.

  • No measure in the plan

    Decide how you will check the result before you start, and record the baseline.

  • Rolling out before checking

    Test on a small scale first. A change that fails everywhere at once is harder to undo.

  • Stopping at check

    If it worked, standardize it and train people; if not, adjust and go round again. Without the act step, gains fade.

  • Treating one cycle as the end

    PDCA is a cycle. Many problems need several turns, each learning from the last.

In LeanSuite

Use this as a Lean Studio board

The same method is one of the 30 ready-made board templates in Lean Studio, LeanSuite's whiteboard: PDCA Cycle, continuous improvement cycle for iterating on a change through Plan, Do, Check, Act.

  • Start from the PDCA Cycle template: four quadrants around a circle, one per step.
  • Put the plan on stickies in the first quadrant, then move through Do, Check and Act as the cycle runs.
  • Use a Line Graph or Single Data widget in Check to show the result against the target.

Worked example · sample data

The sample cycle is a changeover trial on press 2. Plan: cut the changeover from 42 to 30 minutes by moving die pre-heating off-line. Do: a pre-heat stand was built and used on 12 changeovers in week 36. Check: the average came down to 31 minutes, close to target, but two runs went over 35 minutes because the single stand was in use on another press. Act: the team ordered a second stand and updated the changeover standard to include the off-line pre-heat. The one-minute miss against target was not treated as failure; the check told the team exactly which condition broke the result, and that became the next plan.

Four quadrants for a changeover reduction trial, from the plan to pre-heat dies off-line through to the updated standard. Sample data.

Open this board in LeanSuite

PDCA Cycle is one of the 30 ready-made boards in Lean Studio, LeanSuite's whiteboard. Try LeanSuite in your browser, or run it on your own lines for 90 days.

What Lean Studio is

How to run a PDCA Cycle session

  1. 1Plan: state the problem with a number, set the target and the date, and decide exactly what will change and how you will measure it.
  2. 2Do: run the change on a small scale first, one line or one week, and record what happened, including what went wrong.
  3. 3Check: compare the measured result with the target, not with a feeling. Put the numbers on the board.
  4. 4Act: if the target was met, write the change into the standard and train it. If not, keep what worked, adjust the plan and start the next cycle.
  5. 5Keep the cycles short. A PDCA that takes six months is a project; a PDCA that takes two weeks is how a team learns.

Common mistakes

  • Skipping Check. Most teams plan and do; few measure the result against the target before declaring success.
  • A plan without a number, so Check has nothing to compare against.
  • Changing five things at once in Do, then not knowing which one worked.
  • Treating Act as 'done'. Act means updating the standard and training it, or starting the next cycle.
  • Running the first cycle on the whole plant instead of one line.

Where it goes next in LeanSuite

  • PDCA is one of the ready-made methodologies for a Kaizen project, with phases, due dates per phase and savings tracked against plant targets. Kaizen & Projects
  • The result in Check can be a KPI with a target and RAG ranges, so the trend after the change is visible on the dashboard. KPI Dashboards

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

LeanSuite's continuous improvement software has built-in PDCA, A3 and DMAIC templates, suggests a method for the type of loss you are tackling, from a simple PDCA cycle to a full DMAIC project, and tracks projected and actual savings for each project.

See it in a 45-minute demo

FAQ

PDCA template: common questions

  1. Plan, do, check, act: plan a change, try it, check the result against what you expected, and act by standardizing it or by adjusting and going round again. It is also called the Deming or Shewhart cycle.

  2. PDSA replaces check with study, to stress learning from the results rather than only checking them. The steps are otherwise the same, and this template works for either.

  3. PDCA is the cycle; an A3 is one way of writing it down, with more room for background and root cause analysis. This PDCA template is lighter and suits smaller improvements. Use an A3 when the problem needs a fuller analysis or agreement from several people.

  4. Both are structured improvement cycles. DMAIC (define, measure, analyze, improve, control) comes from Six Sigma and is usually used for larger, data-heavy projects. PDCA is simpler and suits quick, small-scale tests.

  5. Long enough to see whether the change works, and no longer. Some tests on the floor take days; others need weeks of data. Set the check date when you write the plan.

More free templates

All templates
Browse all 199 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.