Control Limits

On a control chart, the upper and lower boundaries placed three standard deviations above and below the process mean (centerline) for a normally distributed measure. They show the range of variation expected from common causes and are not the same as specification limits.

Key Points

  • Set at plus or minus three standard deviations around the centerline of the control chart.
  • Indicate the expected common-cause variation of a stable, normally distributed process.
  • Points beyond these limits signal potential special causes and a process out of control.
  • Different from specification limits, which reflect requirements or tolerances, not process behavior.

Example

A project team tracks weekly defect counts. The average is 12 defects with a standard deviation of 2. The control limits are set at 12 minus 6 (LCL = 6) and 12 plus 6 (UCL = 18). A week with 19 defects falls outside the UCL, prompting investigation into a special cause such as a recent code change.

PMP Example Question

Which statement best describes control limits on a control chart?

  1. They are the customer-defined tolerance boundaries for acceptable results.
  2. They are fixed limits at two standard deviations from the mean for any process.
  3. They are statistically derived bounds, typically at plus or minus three standard deviations from the mean, indicating expected process variation.
  4. They are thresholds set by the project manager to meet schedule objectives.

Correct Answer: C — Statistically derived bounds at about plus or minus three sigma around the mean

Explanation: Control limits are based on process data and show the expected common-cause variation. They are not customer tolerances (specification limits) or arbitrary manager-set thresholds.

ICS/OT Incident Response Drills and Exercises

An incident response plan is only a theory until the people who must use it have run it under pressure. This course helps OT engineers, operations leaders, IT responders, and security teams turn a plan on paper into a tested capability.

Define safe states and manual fallback before an incident forces the decision. Build escalation paths, tabletop exercises, and scenarios that expose the gaps a document review cannot find.

Then turn the results into evidence: an after-action report, owned improvements, recovery checks, and a drill cadence that keeps the program alive after the exercise ends.

24 lessons, 2.4 hours. US$47 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Drills and Exercises course preview

Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management and Technology, not on Udemy.

See What Is Included