Control Limits vs. Specification Limits: What’s the Difference?

Control limits and specification limits look alike on paper — lines a measurement is supposed to stay inside — and confusing them is among the most common mistakes in quality work. Control limits are the voice of the process: calculated from the process’s own data, they describe what it actually does. Specification limits are the voice of the customer: set by engineering, contract, or regulation, they describe what will be accepted. One is a fact about the process; the other is a demand placed upon it. Nothing guarantees the two agree.

How it’s used

The two kinds of limits answer different questions. Control limits, drawn on a control chart, answer: is the process stable — behaving as it has been behaving? Specification limits answer: is this particular unit acceptable? Keeping the questions separate yields four possible worlds. A process can be stable and capable — predictable and comfortably inside spec. Stable but incapable — predictably producing scrap at a steady rate. Unstable but currently in spec — passing inspection on luck. Or unstable and incapable — the usual crisis. Each demands a different response, which is why capability analysis always starts by establishing stability first.

A worked example

A machine shop turns shafts to a diameter specification with a tight tolerance. The control chart shows textbook stability: no signals, calm ranges, a settled center. But when the team compares the process’s natural spread to the specification width, the spread is wider. The process is in control and reliably producing a steady percentage out of tolerance — stable and incapable. No amount of watching the chart will fix that, and neither will urging the operators on. The choices are structural: reduce variation at its sources, buy capability with better equipment, or renegotiate the specification. The chart’s role was to prove the problem is the system, not an off day.

• Never draw specification limits on an X-bar chart — subgroup averages vary far less than the individual units the customer receives, so the picture flatters.
• In specification does not mean in control, and in control does not mean in specification. Check both, separately.
• Never set control limits at the specification values by decree; limits are calculated from data or they are meaningless.
• Establish stability before computing capability — capability numbers from an unstable process predict nothing.
• When a stable process cannot meet spec, the options are system change or spec renegotiation. Exhortation is not on the list.

Control limits report what the process is doing; specification limits report what the customer needs. Management begins where the two disagree.

This distinction sits at the heart of Green Belt training, where control charting meets capability analysis. Our Green Belt program ($299, about 35 hours) makes the separation second nature — and the 100-question proctored exam is written to catch anyone who blurs it.