Study guide
9.8 Control Plan Development and Process Owner Handoff
ASQ Certified Six Sigma Black Belt CSSBB
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CSSBB Exam Strategy
1.1 CSSBB Exam Format, Scoring, and Testing Windows 1.2 Eligibility, Project Affidavits, Application, and Recertification 1.3 Open-Book Strategy, Reference Materials, and a 16-Week Study Plan
2 Chapter 2: Organization-Wide Planning and Deployment
2.1 Fundamentals of Six Sigma and Lean Methodologies 2.2 Selecting the Right Methodology: DMAIC, DFSS, and Lean 2.3 Business Systems, Processes, and Stakeholder Relationships 2.4 Strategic Planning and Deployment of Six Sigma Initiatives 2.5 Six Sigma Roles and Responsibilities 2.6 Organizational Barriers and Common Causes of Six Sigma Failure 2.7 Change Management: Stakeholder Analysis, Readiness, and Communication
3 Chapter 3: Organizational Process Management and Measures
3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders 3.2 Benchmarking Types and Performance Goal Setting 3.3 Performance Measures: Balanced Scorecard, KPIs, KBIs, OKRs, and Line of Sight 3.4 Leading and Lagging Indicators and Performance Dashboards 3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis 3.6 Cost of Poor Quality and Hard versus Soft Savings
4 Chapter 4: Team Management
4.1 Team Types and Constraints 4.2 Team Roles, Responsibilities, and Member Selection 4.3 Team Success Factors and Ground Rules 4.4 Motivational Techniques and Overcoming Demotivators 4.5 Stages of Team Development and Conflict Resolution 4.6 Team Communication Plans 4.7 Team Leadership Models: Direct, Coach, Support, and Delegate 4.8 Group Behaviors, Conflict Resolution, and Meeting Management 4.9 Facilitation Techniques and Team Decision-Making Methods 4.10 Team Training: Needs Assessment, Delivery, and Evaluation
5 Chapter 5: Define Phase
5.1 Customer Identification and Segmentation 5.2 Customer Data Collection: Methods, Validity, and Reliability 5.3 Customer Requirements: CTX, CTQ Trees, and Operational Definitions 5.4 The Kano Model and Quality Function Deployment 5.5 SIPOC and Process Mapping 5.6 Business Case Justification 5.7 The Project Charter and the Problem Statement 5.8 Project Scope and Boundaries 5.9 SMART Goals and Project Performance Measurements 5.10 Project Charter Reviews and Toll-Gate Governance 5.11 Project Management Tools: Gantt Charts, Toll-Gate Reviews, WBS, and RACI 5.12 Analytical Tools Used Throughout the DMAIC Cycle
6 Chapter 6: Measure Phase
6.1 Process Flow Metrics and the Hidden Factory 6.2 Process Analysis Tools and Value Stream Mapping 6.3 Types of Data and Measurement Scales 6.4 Sampling Concepts, Methods, and Sample Size for Estimation 6.5 Data Collection Plans and Common Pitfalls 6.6 Gage R&R for Variable Measurement Systems 6.7 Attribute Agreement Analysis and Audit MSA 6.8 Measurement Systems Across the Organization, and Metrology 6.9 Population Parameters, Sample Statistics, and Valid Statistical Conclusions 6.10 Descriptive Statistics: Central Tendency, Dispersion, and Shape 6.11 Graphical Methods for Exploratory Data Analysis 6.12 Probability Concepts, Common Distributions, and the Central Limit Theorem 6.13 Additional Distributions: Hypergeometric, Exponential, Lognormal, Weibull, and Bivariate 6.14 Process Capability and Performance Indices 6.15 Capability Studies, Attributes Capability, Yield Metrics, and Long-Term Capability
7 Chapter 7: Analyze Phase
7.1 The Correlation Coefficient, Its Confidence Interval, and Causation 7.2 Linear Regression and Residual Analysis 7.3 Multivariate Tools: Factor Analysis, Discriminant Analysis, and MANOVA 7.4 Hypothesis Testing Terminology, Errors, and Single-Sample Tests 7.5 Statistical Versus Practical Significance 7.6 Sample Size for Hypothesis Tests 7.7 Point Estimates, Confidence, Prediction, and Tolerance Intervals 7.8 Tests for Means, Variances, and Proportions 7.9 Analysis of Variance 7.10 Chi-Square Goodness-of-Fit and Tests of Independence 7.11 Types of Risk and Failure Mode and Effects Analysis 7.12 Gap Analysis and Root Cause Analysis 7.13 Waste Analysis: The Seven Classic Wastes and Resource Under-Utilization
8 Chapter 8: Improve Phase
8.1 Design of Experiments: Objectives, Terminology, and Effects 8.2 DOE Design Principles: Randomization, Blocking, Replication, and Resolution 8.3 Planning and Evaluating Designed Experiments 8.4 One-Factor Experiments: Completely Randomized, Randomized Block, and Latin Square Designs 8.5 Full Factorial Experiments and Design Selection 8.6 Two-Level Fractional Factorial Experiments and Confounding 8.7 Response Surface Methodology and Optimization 8.8 Waste Elimination: Pull Systems, Kanban, 5S, and Poka-Yoke 8.9 Cycle-Time Reduction: Continuous Flow, SMED, and Heijunka 8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE 8.11 Implementation Planning, Piloting, and Solution Selection
9 Chapter 9: Control Phase
9.1 SPC Objectives, Variable Selection, and Rational Subgrouping 9.2 Control Charts for Variables Data 9.3 Control Charts for Attributes Data 9.4 Short-Run SPC and Moving Average Charts 9.5 Control Chart Analysis: Common Cause, Special Cause, and Run Rules 9.6 Total Productive Maintenance and Visual Controls 9.7 Measurement System Reanalysis 9.8 Control Plan Development and Process Owner Handoff 9.9 Lessons Learned, Documentation, and Training for Sustainment 9.10 Ongoing Evaluation of the Improved Process
10 Chapter 10: Design for Six Sigma (DFSS)
10.1 DFSS Frameworks: DMADV, DMADOV, and Design Transfer 10.2 Design for X (DFX) 10.3 Robust Design, Parameter Design, and Verification 10.4 Tolerance Design and Statistical Tolerancing
9.8 Control Plan Development and Process Owner Handoff
Key Takeaways Explain This Topic AI
The Body of Knowledge defines the control plan's three jobs as maintaining improved performance, enabling continuous improvement, and transferring responsibility from the project team to the process owner.
Control plan requirements became a standalone AIAG manual (CP-1, 1st edition) in March 2024, which added a fourth Safe Launch phase alongside prototype, pre-launch, and production, plus reaction-plan owner and change-level columns.
Control plans are the third link in the core-tools chain: every significant failure mode in the PFMEA must map to a control-plan row, and every row should trace back to a failure mode.
Control methods rank by robustness -- design elimination, preventing poka-yoke, automated detection, SPC with a reaction plan, sampling, 100% inspection, and procedure or training last; 'retrain the operators' is the weakest control and a standard exam distractor.
Handover is evidenced, not announced: published standard work, verified training, capability sustained over roughly 30 days (Cpk >= 1.33 existing, >= 1.67 critical), controls executed by operators, and a signed agreement, followed by finance-validated audits at 30, 60, 90, and 365 days.
Last updated: August 2026
Improving a process creates value only if the improvement survives the team's departure. The Body of Knowledge states the task precisely (VIII.C.2): develop a control plan that maintains the improved performance, enables continuous improvement, and transfers responsibility from the project team to the process owner . All three clauses are examinable, and the third is the one projects fail.
What a control plan is, and the current standard
A control plan is a living document describing the systems and controls used to manage the process inputs ( X X X 's) and outputs ( Y Y Y 's) that determine the customer CTQs. It is a specification for how the process will be run and monitored, not a record of how it was improved.
The automotive sector supplies the reference format. Control plan requirements previously lived inside the AIAG APQP and Control Plan manual; since March 2024 the control plan is a standalone AIAG manual (CP-1, 1st edition) , which added a fourth phase and extra data fields. The four phases:
- Phase Applies to Control intensity
- Prototype Dimensional, material, and performance evaluation on early builds Highest; near-total measurement
- Pre-launch Pilot and trial production before full release Elevated inspection frequency, extra containment
Safe launch Early production immediately after launch (added in CP-1) Temporary additional checks until stability is demonstrated
Production Ongoing commercial operation Steady-state sampling, SPC, and reaction plans
Six Sigma teams outside automotive use the same structure, usually with pre-launch controls during the pilot and production controls at handover.
The core-tools chain
A control plan is never authored from a blank page. It is the third document in a chain, and each row of it should be traceable backwards:
Process flow diagram → PFMEA → control plan
The process flow names every step. The PFMEA (section 7.11) names the failure modes at each step and scores their risk. The control plan specifies the control for each significant failure mode the PFMEA identified. The audit test is a two-way one: every high-RPN or special-characteristic failure mode in the PFMEA must have a corresponding control-plan row, and every control-plan row should trace to a failure mode. A control with no failure mode behind it is usually inherited inspection nobody has questioned in years; a failure mode with no control is an uncontrolled risk that the improved process will eventually surface.
Anatomy of a control plan row
- Column Purpose Example
- Process step / operation Step number and name from the process map Op 40: CNC shaft turning
- Machine, jig, tooling Equipment and fixture identity CNC lathe #4 (asset EQ-402)
- Product characteristic The output ( Y Y Y ) being protected Shaft outer diameter
- Process characteristic The input ( X X X ) that drives it Spindle speed, feed rate, coolant temperature
- Special characteristic Safety or critical classification, if any SC (significant characteristic)
- Specification / tolerance Nominal and limits 25.000 ± 0.025 25.000 \pm 0.025 25.000 ± 0.025 mm
- Evaluation method Gauge or inspection procedure, with its MSA status Digital micrometer GM-12, GRR 8.4%
- Sample size and frequency Rational subgroup and interval n = 5 n = 5 n = 5 every 2 hours
- Control method How the characteristic is actually controlled X ˉ \bar{X} X ˉ and R R R chart
- Reaction plan What to do when the control signals OCAP-04
- Owner Named role accountable for the reaction (added in CP-1) Cell team leader
- Change level / revision Version control for the row Rev C, 2026-07-14
- Choosing the control method: the robustness hierarchy
Selecting the control method is the judgment the exam tests. The options are not equivalent, and they rank in a fixed order of robustness:
- Rank Control Why it ranks here
- 1 Eliminate the failure mode by design No failure mode, no control needed, no ongoing cost
- 2 Poka-yoke that prevents or shuts down Error becomes physically impossible; independent of attention
- 3 Automated detection with alarm or lock-out Catches the error immediately, but relies on a response
- 4 SPC chart with a reaction plan Detects drift before nonconformance, but requires discipline
- 5 Sampling inspection Detects after the fact; misses what falls between samples
- 6 100% human inspection Roughly 80% effective at best, fatiguing, expensive
- 7 Procedure and training alone Depends entirely on memory and attention; weakest of all
Two rules follow. Always select the highest feasible level , and treat any control plan whose rows are mostly at ranks 6 and 7 as a sustainment failure already in progress. And note the exam trap: "retrain the operators" is the most frequently proposed and least robust control there is. Training is a prerequisite for every level, never a control by itself.
Error-proofing levels
Within rank 2 and 3, poka-yoke (Shigeo Shingo) appears in three forms: prevention devices that make the error physically impossible, such as asymmetric connectors that cannot be inserted reversed; shutdown devices that stop the machine on detection, such as light curtains; and warning devices that signal with a beacon or buzzer and require acknowledgment. The lean tooling behind these is developed in section 8.8; here the question is only which of them earns a row in the plan.
Reaction plans and the OCAP
The reaction-plan column is where control plans are thinnest. "Notify supervisor" is not a reaction plan. A usable out-of-control action plan (OCAP) is a short decision tree answering six questions:
Trigger -- exactly which signal starts it (a point beyond a control limit, seven-point run, gauge alarm)?
Containment -- what stops immediately, and what is quarantined?
Suspect material -- which units are suspect, back to which last known-good check, and who dispositions them?
Diagnosis -- the ordered checks to perform, and by whom.
Escalation -- who is called if the first checks do not resolve it, and within what time.
Record -- where the event, cause, and action are logged so the data feeds continuous improvement.
Point 3 is the one that saves the recall: without a defined lookback, nobody knows which product is affected. Point 6 is how the plan satisfies the BoK's "enables continuous improvement" clause -- the log of control-plan reactions is the input to the next improvement cycle.
Transactional and service processes
The columns translate directly; only the vocabulary changes.
- Manufacturing Transactional equivalent
- Operation and machine Process step and system or queue
- Product characteristic Output attribute: accuracy, completeness, cycle time
- Process characteristic Input attribute: field completeness, queue depth, staffing
- Gauge and MSA Audit checklist with attribute agreement analysis
- Sample size and frequency Daily audit of n n n transactions
- Control chart p p p chart on error rate, individuals chart on cycle time
- Poka-yoke Mandatory fields, validation rules, workflow lock-outs
- Equipment, measurement, and maintenance entries
Three sustainment mechanisms belong in the plan as rows rather than as separate initiatives. Maintenance tasks that protect a controlled characteristic -- the autonomous and planned maintenance routines of TPM (section 9.6) -- are written in with their own frequency and owner, because equipment deterioration reintroduces variation invisibly. Where equipment availability itself drives the CTQ, an OEE target (section 8.10) is entered as a monitored measure. And every gauge named in the evaluation column carries a calibration interval and an MSA re-analysis trigger (section 9.7), since a measurement system adequate for the old process may be inadequate for the improved one.
Revision and document control
A control plan is living, which means it has revision triggers rather than a review calendar alone: an engineering or specification change, a new failure mode discovered in production, a capability shift, a gauge or measurement-system change, equipment relocation or replacement, and any customer complaint traced to an uncontrolled characteristic. Each revision is versioned, re-approved, and re-issued to the floor; an obsolete copy at the workstation is a finding in any audit.
Handover to the process owner
Transfer of responsibility is a gate, not an email. The process owner should receive a defined package: the approved control plan and OCAPs, updated SOPs and work instructions, training records for every affected operator and shift, evidence of sustained capability, the monitoring plan with named leading and lagging indicators, and the benefit-tracking basis agreed with finance.
Readiness is demonstrated, not asserted:
Standard work published -- SOPs, work instructions, and visual management updated to the new method.
Training completed -- all shifts trained and competency verified, not merely briefed.
Capability sustained -- typically C p k ≥ 1.33 C_{pk} \ge 1.33 C p k ≥ 1.33 for an existing characteristic and ≥ 1.67 \ge 1.67 ≥ 1.67 for a new or critical one, demonstrated over a monitoring period of about 30 days rather than a single study.
Controls executing -- charts being plotted and reactions logged by the operators, not the project team.
Formal sign-off -- a handover agreement signed by Black Belt, process owner, sponsor, and where applicable the Master Black Belt.
After sign-off the team audits rather than operates: finance-validated savings checks at 30, 60, 90, and 365 days against the charter baseline, hard and soft benefits reported separately, then documentation archived and lessons circulated (section 9.9). A project closed without the sign-off and the first audit is closed on paper only.