A control plan procedure is a documented, step-by-step method for creating, maintaining, and updating a control plan, which is a living document that specifies the actions needed to keep a process stable and its outputs within specification. This procedure ensures that every critical product characteristic and process parameter has a defined monitoring method, reaction plan, and responsible owner.
Background and Purpose
Control plans originated in the automotive industry, particularly through the Advanced Product Quality Planning (APQP) framework, but they are now used in manufacturing, healthcare, and service industries. The core purpose is to translate customer requirements into actionable process controls. A control plan is not a one-time document; it evolves with the process, reflecting changes in equipment, materials, measurements, and personnel. The procedure for managing it is what keeps it relevant and effective.
Without a formal procedure, control plans often become shelf documents—written once during launch and never updated. A robust procedure ensures that the plan is reviewed at defined intervals, updated when process changes occur, and used daily by operators and quality staff.
Key Elements of a Control Plan
Before writing the procedure, you need to understand the structure of a typical control plan. Most plans include the following sections, which the procedure will reference:
- Process step: The specific operation or step being controlled.
- Machine/equipment: The specific asset used.
- Characteristic: The product or process characteristic being monitored (e.g., torque, temperature, diameter).
- Specification: The upper and lower limits or target value.
- Measurement technique: The gauge, sensor, or test method used.
- Sample size and frequency: How many units are checked and how often.
- Control method: The type of control (e.g., X-bar R chart, go/no-go gauge, automated alarm).
- Reaction plan: The defined actions to take when the control indicates a problem.
Step-by-Step Procedure
Here is a generic control plan procedure that can be adapted to any organization. It assumes you have already identified the critical characteristics through a Process Failure Mode and Effects Analysis (PFMEA).
- Define the scope and team. Identify the process or product family to be covered. Assemble a cross-functional team including engineering, quality, operations, and maintenance.
- Review inputs. Gather the PFMEA, design FMEA, process flow diagram, customer requirements, and historical quality data.
- Draft the control plan. Using the template (see below), fill in each column for every process step that affects the critical characteristics.
- Assign responsibilities. For each control method and reaction plan, name a specific person or role (e.g., line operator, quality technician).
- Validate the plan. Have the team walk through the process and confirm that the measurement methods are available, the sample sizes are practical, and the reaction plans are feasible.
- Train and deploy. Train operators and inspectors on their roles. Post the control plan at the work station or make it accessible digitally.
- Review and update. Set a regular review cadence (e.g., quarterly) and define triggers for ad-hoc updates: new equipment, new tooling, engineering change, customer complaint, or a failed capability study.
- Document changes. Maintain a revision history. Each update should be approved by the same cross-functional team.
How to Choose Control Methods
The control method you select should match the risk level of the characteristic. High-risk characteristics (e.g., safety-related torque) require more robust controls than low-risk ones (e.g., cosmetic finish). Common control methods, in increasing order of robustness, include:
- Operator self-check (visual or manual measurement)
- Checklist or attribute inspection (go/no-go)
- Variable data collection with control charts (e.g., X-bar R)
- Automated gauging with real-time feedback
- Error-proofing (poka-yoke) devices that stop the process if a condition is not met
When choosing, consider the cost of the control versus the cost of failure. A simple checklist may suffice for a low-risk characteristic, but a safety-critical one may justify an automated system.
Common Problems and Misconceptions
One common mistake is treating the control plan as a static document. Another is writing reaction plans that are vague, such as “notify supervisor” without specifying what the supervisor should do. A good reaction plan includes immediate containment (e.g., quarantine suspect product), root cause analysis steps, and verification of effectiveness.
Another misconception is that a control plan is the same as a work instruction. A work instruction tells the operator how to perform a task; a control plan tells them what to check, how often, and what to do if the check fails. They complement each other but serve different purposes.
Costs and Benefits
Implementing a control plan procedure has upfront costs: time for training, documentation, and potentially new measurement equipment. However, the benefits typically outweigh these costs. A well-maintained control plan reduces scrap, rework, and warranty claims. It also provides a clear audit trail for customers and certification bodies. For example, in automotive supply, customers often require a control plan as part of PPAP (Production Part Approval Process).
The cost of not having a procedure is often higher: missed customer requirements, process instability, and firefighting quality issues.
Template
Control Plan Template
| Process Step | Machine/Equipment | Product/Process Characteristic | Specification | Measurement Technique | Sample Size | Frequency | Control Method | Reaction Plan | Responsible |
|---|---|---|---|---|---|---|---|---|---|
Sample (fictional): For a bottle filling line, Process Step: Fill; Machine: Filler-3; Characteristic: Fill volume; Spec: 500 ml ± 5 ml; Measurement: Weigh scale; Sample: 5 bottles; Frequency: Every 30 minutes; Control Method: X-bar R chart; Reaction Plan: Stop line, quarantine last 30 min, notify shift lead; Responsible: Operator.
Frequently Asked Questions
How often should a control plan be updated?
At a minimum, review it quarterly or whenever a significant change occurs, such as new equipment, a new supplier, a revised specification, or after a customer complaint. Some industries require annual re-approval.
Who should write the control plan?
A cross-functional team, not just one person. Typically, a quality engineer leads the effort, but operators, maintenance, and process engineers must contribute because they know the real process.
What is the difference between a control plan and an inspection plan?
An inspection plan focuses solely on product inspection attributes and frequencies. A control plan is broader; it includes process parameters, control methods, and reaction plans. It also links to the PFMEA.
Can a control plan be used for non-manufacturing processes?
Yes. Service processes like order entry, patient intake, or software deployment can benefit from a control plan. Identify the critical output characteristics and the process steps that affect them, then apply the same logic.
What should I do if my process is not stable?
First, use the control plan to document the current state. Then, use problem-solving tools like DMAIC or 8D to identify and eliminate special causes. Update the control plan to include new controls that prevent recurrence.
If your situation involves regulatory compliance or contractual obligations, consult a qualified professional to ensure your control plan procedure meets industry-specific requirements.