Study guide
Control Plans
ASQ Certified Six Sigma Green Belt CSSGB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
CSSGB Exam Facts & Logistics How to Study for an Open-Book ASQ Exam
2 Six Sigma Foundations
Value of Six Sigma & Quality Leaders Organizational Goals & Six Sigma Projects Organizational Drivers, KPIs & Scorecards
3 Lean Principles in the Organization
Lean Concepts Value Stream Mapping & Waste
4 Design for Six Sigma
DFSS Road Maps: DMADV & IDOV FMEA Basics & Risk Priority Number Design FMEA vs Process FMEA
5 Define: Project Identification
Project Selection & DMAIC Fit Process Elements & Boundaries Benchmarking Types SIPOC & Process Inputs/Outputs
6 Stakeholders & Voice of the Customer
Owners & Stakeholders Customer Identification Customer Data Collection CTQ, QFD & Kano
7 Project Management Core
Agile & Top-Down Project Methods Project Charter & Problem Statements Project Scope Tools Primary & Consequential Metrics
8 Planning, Risk & Closure
WBS, Gantt, CPM, PERT & Tollgates Project Documentation Project Risk Analysis & Management Project Closure & Lessons Learned
9 Management Tools & Business Results
Eight Management & Planning Tools DPU, RTY, CoPQ, DPMO & Sigma Level Organizational Communication
10 Team Dynamics & Performance
Team Stages & Negative Dynamics Six Sigma Roles & RACI Brainstorming, NGT & Multivoting Team Communication
11 Measure: Process & Probability
Process Maps & Documentation Basic Probability Concepts Central Limit Theorem
12 Distributions & Data Collection
Statistical Distributions Data Types & Measurement Scales Sampling & Data Collection Plans Descriptive Statistics
13 Graphical Methods & MSA
Graphical Methods Measurement System Analysis & Gage R&R Bias, Linearity, Stability & P/T
14 Process & Performance Capability
Process Performance vs Specifications Process Capability Studies Cp, Cpk, Pp, Ppk & Cpm Short-Term vs Long-Term Capability & Sigma Shift
15 Analyze: Exploratory Data Analysis
Multi-Vari Studies Correlation & Linear Regression
16 Hypothesis Testing
Hypothesis Testing Basics Tests for Means, Variances & Proportions
17 Gap & Root Cause Analysis
Gap Analysis Root Cause Analysis Tools
18 Design of Experiments
DoE Basic Terms Main Effects & Interaction Plots
19 Implementation Planning & Lean Tools
Implementation Planning & Pilots Waste Elimination Tools Cycle-Time Reduction & SMED Kaizen & Kaizen Blitz
20 Statistical Process Control
SPC Basics: Common vs Special Cause Rational Subgrouping Control Chart Selection & Construction
21 Sustaining Improvements & Lean Control
Control Plans Document Control, Training & Audits Plan-Do-Check-Act (PDCA) TPM & Visual Factory
Control Plans
Key Takeaways Explain This Topic AI
A control plan documents how a process is monitored and kept on target after improvements so gains do not fade when the project team leaves.
Core control-plan elements include process steps, characteristics, specifications, measurement methods, sample size/frequency, control method, reaction plan, and owners.
Link each critical characteristic to a clear control method (SPC chart, checklist, poka-yoke, visual standard) and a written reaction plan for out-of-control or out-of-spec conditions.
Update the control plan when the process, specs, measurement system, or risk profile changes; treat it as a living document under document control.
Green Belts apply control plans in DMAIC Control to translate pilot success into sustained process performance owned by operations.
Last updated: July 2026
Control Plans (CSSGB BoK VI.B.1 — Apply)
Quick Answer: A control plan is a living document that states how a process is monitored and controlled after improvements. It lists process steps, product/process characteristics, specifications, measurement methods, sample size and frequency, control methods, reaction plans, and owners. Green Belts apply control plans in DMAIC Control so gains survive handover to operations.
The Control phase fails when the team celebrates a pilot and walks away. Without a structured control system, operators revert to old habits, settings drift, and defect rates climb back toward baseline. VI.B.1 is at the Apply level: you must build and use a control plan, not merely define the term.
Purpose of a Control Plan
A control plan documents the system used to keep a process on target and within requirements. It answers:
What must stay controlled (characteristics and process steps)?
How do we know it is controlled (measurement method, sample size, frequency)?
What method keeps it controlled (SPC, poka-yoke, checklist, visual standard)?
Who acts when something goes wrong, and what do they do (reaction plan)?
Control plans bridge project work and day-to-day management. They are common in automotive and regulated industries (often aligned with AIAG-style process control documentation) and equally valuable in healthcare, services, and transactional processes when CTQs can drift.
When Green Belts Build the Control Plan
Typical timing:
Late Improve / early Control — draft after the pilot proves the solution works.
Control phase — finalize measurement methods, charts, reaction plans, and owners.
Project closure — hand the controlled process to the process owner with training and document control in place.
Ongoing — revise when process, equipment, specs, risk, or customer requirements change.
The control plan is not a one-page certificate of completion. It is the operating contract for sustaining the improved process.
Core Elements of a Control Plan
Exam questions often test whether you can name and apply the standard fields. A practical control-plan row or block includes:
- Element What it captures Why it matters
- Process step / operation Where in the flow control applies Ties control to the real process map
- Product / process characteristic CTQ or critical process parameter Focuses effort on what drives quality
- Specification / tolerance Target, LSL/USL, or attribute criteria Defines “good” vs “needs reaction”
- Measurement technique Gage, test method, checklist criteria Ensures consistent detection of problems
- Sample size & frequency How much, how often Balances risk and cost of monitoring
- Control method SPC chart type, poka-yoke, SOP, audit States the preventive or detective control
- Reaction plan Immediate containment and escalation Prevents shipping defects or long downtime
- Owner / responsibility Who measures, who reacts, who escalates Removes ambiguity on the floor
Some formats also list machine/device, classification (critical/major/minor), and related FMEA references. For CSSGB, prioritize characteristics, measurement, control method, reaction plan, and ownership.
Product vs Process Characteristics
Product characteristics are features of the output (dimension, purity, on-time completion, error-free form). Process characteristics are settings or conditions that drive the output (temperature, cycle time, torque, hold time, queue age).
Strong control plans often monitor leading process parameters in addition to lagging product results. Waiting only for final inspection finds problems late. Controlling the parameter that creates the defect catches drift earlier and supports prevention.
Control Methods Green Belts Choose
Match method to risk and data type:
Statistical Process Control (SPC): variable or attribute charts when data are available and special-cause signals matter.
Poka-yoke (error-proofing): physical or system design that makes the error impossible or immediately obvious.
Standard work / checklists: sequenced steps for consistent execution of critical tasks.
Visual standards: photos, shadow boards, limit samples that make abnormal conditions obvious.
Layered process audits or layered checks: short, frequent verification that standards are followed.
First-piece / setup verification: confirm setup before a full run ships risk downstream.
The control plan names the method; related documents (chart worksheets, SOPs, work instructions) hold the how-to detail.
Reaction Plans
A reaction plan states what happens when a control limit is breached, a checklist fails, a poka-yoke trips, or a product is out of specification. Effective reaction plans include:
Containment — stop the process, quarantine suspect product, protect the customer.
Immediate correction — restore the process to a known good state if the fix is defined.
Escalation — notify the process owner, quality, or engineering when criteria require it.
Documentation — record the signal, action, and disposition for learning and audits.
Root-cause follow-up — when special causes recur, trigger investigation beyond the band-aid.
Vague reaction language such as “notify supervisor” without stop/quarantine rules is a common exam and real-world weakness.
Sampling and Frequency Decisions
Sampling and frequency should reflect risk (severity of failure), process stability, and cost of measurement. High-severity CTQs may need 100% inspection or continuous monitoring until stability and capability are proven. Stable, capable processes with strong poka-yoke may use reduced sampling. Frequency should catch drift soon enough to prevent large nonconforming lots—not only once per month for a high-volume critical characteristic.
Building and Implementing the Plan (Apply Steps)
Identify critical characteristics from CTQs, FMEA high RPNs, and capability risks.
Confirm measurement systems are adequate (MSA where relevant) so control data are trustworthy.
Select control methods appropriate to data type and failure mode.
Write reaction plans with containment, correction, and escalation.
Assign owners for monitoring and for reaction authority.
Train operators and supervisors on standards, charts, and reaction steps.
Pilot the control system alongside the improved process; adjust frequency and methods.
Place the plan under document control and schedule periodic review.
Transfer ownership to the process owner at project close with metrics still visible.
Control Plan vs Related Documents
Control plan — what is controlled, how, how often, and what to do when out of control.
Work instruction / SOP — detailed steps to perform the job correctly.
FMEA — risk analysis that helps prioritize which characteristics need strong control.
Process map / flowchart — visual of steps; the control plan attaches controls to those steps.
Project charter / storyboard — project history; the control plan is the sustained operating system.
Do not confuse a control plan with a project plan. A Gantt chart schedules project work; a control plan sustains process performance after the project ends.
Exam Focus
Expect scenario questions: which fields belong on a control plan, what belongs in a reaction plan, whether a lagging-only inspection strategy is enough, and when to update the plan after a process change. Apply-level success means choosing a coherent monitoring and reaction system for a described CTQ—not memorizing a logo or form number alone.
Key takeaway: The control plan turns improved performance into a managed process with clear characteristics, measurement, control methods, reaction plans, and owners so DMAIC gains last.