Process control is the discipline of keeping a process stable, predictable and capable of producing the required result. A control plan translates that discipline into a working document: it identifies what must be controlled, how it will be measured, who is responsible, how often it is checked and what action is required when the process moves outside the expected condition.
Process Control vs Quality Control
Quality control often focuses on checking an output—for example, inspecting received material or verifying a picked order. Process control focuses on the conditions that create the output. The strongest systems use both, but prevention through process control is generally preferable to discovering every problem at the end.
| Process Control | Output / Quality Check |
|---|---|
| Controls how work is performed | Checks what the process produced |
| Can prevent variation or error | Mainly detects an existing issue |
| Examples: parameter limits, approval rules, barcode validation, temperature monitoring | Examples: inspection, reconciliation, final quantity check |
What Is a Control Plan?
ASQ defines a control plan as a written description of the systems used to control part and process quality by addressing key characteristics and requirements. In supply-chain and operational settings, the same logic can be adapted to receiving, warehousing, purchasing, order fulfilment, cold-chain handling and other repeatable processes.
Typical Control Plan Fields
| Field | Purpose |
|---|---|
| Process step | Where the control applies |
| Characteristic / requirement | What must be controlled |
| Specification / target | Required result or acceptance requirement |
| Measurement method | How the characteristic is checked |
| Sample / frequency | How often the check occurs |
| Owner | Who performs or reviews the control |
| Record | Evidence that the control was completed |
| Reaction plan | What happens if the result is unacceptable |
Control Limits vs Specification Limits
This distinction is important. Specification limits are requirements for the product or service—often set by the customer, engineering, regulation or contract. Control limits are statistically calculated from process data and describe the expected range of process variation when the process is stable.
ASQ notes that control-chart limits are determined from historical process data. A process can therefore be statistically stable but still fail customer specifications, or it can produce items within specification while showing an unstable pattern that needs investigation. Control limits should not simply be copied from specification limits.
Statistical Process Control (SPC)
SPC uses data over time to distinguish routine process variation from signals that suggest a special cause. A typical control chart contains a centre line, an upper control limit (UCL) and a lower control limit (LCL). The appropriate chart depends on the type of data being monitored.
An out-of-control signal should trigger investigation rather than an automatic assumption that the product itself is defective. The goal is to understand the cause of unusual process behaviour and restore stability.
Supply Chain Example: Warehouse Receiving Control Plan
| Process Step | Characteristic | Control / Method | Frequency | Reaction |
|---|---|---|---|---|
| Vehicle arrival | Correct supplier / PO | Appointment and PO verification | Every delivery | Hold unloading and escalate mismatch |
| Unloading | Visible condition | Packaging / damage inspection | Every delivery | Photograph, segregate and record exception |
| Quantity check | Received quantity | Count / scan vs PO and delivery note | Every receipt | Record shortage/overage before GRN |
| Product inspection | Specification / quality | Defined sampling or inspection method | Per inspection plan | Quarantine and notify quality/procurement |
| Receipt posting | System quantity | GRN reconciliation | Every receipt | Correct before put-away / invoice match |
Supply Chain Example: Procurement Control Plan
| Step | Requirement | Control | Evidence | Reaction |
|---|---|---|---|---|
| Supplier setup | Approved and verified supplier | Qualification + bank-detail verification | Approved supplier record | Do not release supplier for purchasing |
| PO creation | Correct price / terms | Contract or quotation check | PO and approval record | Correct PO before release |
| Order confirmation | Required delivery date | Supplier acknowledgement | Confirmation | Escalate variance and update plan |
| Invoice | PO / receipt alignment | 2-way or 3-way match | System match record | Block and route exception |
What Makes a Good Reaction Plan?
- Defines what condition triggers action.
- States whether work, stock or shipment must be stopped or quarantined.
- Names the responsible role.
- Requires containment of potentially affected output.
- Defines escalation and communication.
- Requires root-cause/corrective action when appropriate.
- Defines when normal processing may resume.
- Requires evidence of the action taken.
Control Plan, Process Map and FMEA
These tools should reinforce each other. The process map identifies the process steps and handoffs. FMEA identifies what could fail, why, and the current prevention/detection controls. The control plan turns critical controls into routine operational checks with owners, frequency and reaction instructions.
Common Mistakes
- Using the customer’s specification as the statistical control limit.
- Monitoring too many characteristics without identifying what is critical.
- Writing “inspect” without specifying method, sample size or frequency.
- Having no reaction plan for an abnormal result.
- Changing a process without updating the control plan.
- Creating controls that are not supported by records or system evidence.
- Relying only on final inspection instead of prevention.
Useful KPIs
- First-pass yield / right-first-time rate
- Defect or exception rate
- Process cycle time
- Rework rate
- Control-plan compliance
- Out-of-control events
- Corrective-action closure time
- Customer/supplier complaint rate
Interview Question: Control Limit vs Specification Limit
A strong answer is: Specification limits describe what the customer, design or regulation requires. Control limits are calculated from actual process behaviour and show the expected variation of a stable process. They serve different purposes, so I would not automatically set a control-chart UCL and LCL equal to specification limits.
References
Download the Practical Workbook
Use the SCMANA SPC Control Chart Calculator to enter process observations and work through centre-line and control-limit calculations.
Comments 1