Specification Limits

The allowable range around the process mean on a control chart that represents the customer's required performance for a product or service. This requirement-based band can be wider or narrower than the statistical control limits.

Key Points

  • Set by the customer, contract, or standard and expressed as LSL (lower specification limit) and USL (upper specification limit).
  • Different from control limits, which are calculated from process variation and show statistical control.
  • May be tighter or looser than control limits; a process can be in control yet still produce outputs outside specs, or vice versa.
  • Used in capability analysis (e.g., Cp, Cpk) to judge whether the process can consistently meet requirements.

Example

A machining process targets a 10.00 mm shaft diameter. The customer specifies 9.95 mm (LSL) to 10.05 mm (USL) as acceptable. The control chart shows the process mean at 10.00 mm with control limits based on natural variation at 9.92 mm and 10.08 mm. Even if the process is stable (within control limits), parts between 10.05 mm and 10.08 mm are out of spec and must be reworked or rejected.

PMP Example Question

Which statement best describes specification limits in quality management?

  1. The statistically computed boundaries (about +/-3 sigma) that indicate expected process variation.
  2. The customer-defined tolerance band that determines which outcomes are acceptable (LSL and USL).
  3. The approved range of the project budget variance allowed by the sponsor.
  4. The set of thresholds used to categorize risks on a probability-impact matrix.

Correct Answer: B — Customer-defined tolerance band (USL and LSL)

Explanation: Specification limits reflect customer or standard requirements, while control limits reflect process behavior based on statistical variation.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Take Control of Project Performance!

HK School of Management and Technology helps you go beyond status reports and gut feelings. In this advanced course, you will learn Earned Value Management (EVM) to measure progress, forecast outcomes, and take corrective action. Learn how WBS quality drives performance, how control accounts work, and how to use EAC, TCPI, and variance analysis. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More