Attribute inspection records a pass/fail judgment, conforming or not, counted as whole numbers. Variable inspection records a measured value on a continuous scale, such as a diameter or a weight. Attribute data is cheap and fast but needs large samples; variable data costs more to collect but carries far more information, enabling process capability and tighter control with smaller samples.

The choice between them decides how you sample, which control chart you use, how big your samples must be, and how early you can see a process drifting. It is one of the most consequential decisions in a quality plan, and plants make it every day without naming it. This piece lays out the difference and the trade-offs, so you pick the data type on purpose rather than by habit.

What is the difference between attribute and variable data?

Attribute data answers a yes/no question about each unit: does the part fit the gauge, pass the visual check, function or not? The result is a count, the number of defective parts, the number of scratches, always a whole number. Variable data answers "how much?": the shaft measured 6.37 mm, the fill weighed 502 grams. The result is a value on a continuous scale, carrying not just whether the part conformed but by how much and in which direction.

That extra information is the whole story. A go/no-go gauge tells you a hole passed; it cannot tell you the hole was drifting toward the upper limit and will fail next week. A bore gauge reading tells you both. Attribute inspection sees a cliff edge; variable inspection sees the slope leading up to it.

Attribute pass/fail versus variable measured valueTwo ways to look at the same partsATTRIBUTE: pass / failPASSFAILVARIABLE: measured valueLSLUSLdriftingAttribute sees the cliff; variable sees the slope leading to it.
Same parts, two data types. The variable view shows a part creeping toward the upper limit that attribute inspection would still call "pass."

How does each type drive sampling plans?

Attribute sampling underlies the familiar acceptance plans. Because each unit is just pass or fail, you count defectives in a sample and compare against an acceptance number, the logic behind AQL sampling and standards like ANSI/ASQ Z1.4. Variable sampling, governed by the sister standard Z1.9, uses the measured values, and their spread, to make the accept/reject decision, which is why it can reach the same confidence with a smaller sample.

The sample-size gap is real and often surprising. Because a measured value carries more information than a pass/fail flag, variable plans typically need far fewer pieces than attribute plans to reach the same discrimination between good and bad lots. The catch is that variable plans generally cover one characteristic at a time, while an attribute inspection can judge many characteristics of a part at once with a single pass/fail verdict. That trade, fewer samples versus fewer characteristics per check, is the practical calculus.

Which control charts go with each?

Control charts split cleanly along the same line, and picking the wrong family is a common mistake. Attribute data uses charts that plot counts or proportions; variable data uses charts that plot the measured values and their spread.

Which control chart matches which data typePick the chart from the data typeDATA TYPEATTRIBUTE (counts)VARIABLE (measured)p / np% / # defectivec / u# defectsX̄-R / X̄-SsubgroupsI-MRsingle valuesDefective = whole nonconforming unit; defect = each flaw. That distinction picks p/np vs c/u.
The chart family follows the data type. Within attributes, the choice hinges on whether you count defective units or individual defects.

Within attributes, the split is defectives versus defects. A p-chart or np-chart tracks the proportion or number of defective units (each unit is good or bad); a c-chart or u-chart tracks the count of defects, where one unit can carry several. Within variables, X̄-R and X̄-S charts plot subgroup averages and spread, while an individuals and moving-range (I-MR) chart handles cases where you measure one piece at a time. Getting this right is foundational to statistical process control; the deeper mechanics live in the guide to control charts.

Why do variable charts catch problems faster?

Because they react to the measured value, not just the pass/fail outcome. A variable chart can flag a process that is trending toward a limit, or one whose spread is widening, long before any part actually fails. An attribute chart, by contrast, only moves once parts start failing, which means the process is already producing scrap by the time the signal appears. Variable data lets you steer; attribute data mostly lets you count the wreck.

This early-warning power is also why variable data unlocks process capability indices like Cp and Cpk. Capability is a statement about how the measured distribution sits inside the spec limits, so it needs measured values; you cannot compute a meaningful Cpk from pass/fail counts alone. If a customer wants capability evidence on a key characteristic, as automotive and aerospace customers routinely do, you are committed to variable data on that feature.

When should you use attribute inspection anyway?

Plenty of the time, because it is faster, cheaper, and sometimes the only option. Use attribute inspection when the characteristic is genuinely go/no-go (a hole is present or not, a label is legible or not), when a measurement would be prohibitively slow or expensive, when you are screening many characteristics at once, or when the check is a visual or functional judgment that has no natural number. Attribute checks also need less operator training and cheaper gauges, and they scale to high-speed lines where measuring every dimension is impossible.

  1. Ask whether the characteristic has a natural measured value. A dimension, weight, or torque does; presence, legibility, or function may not.
  2. Weigh the cost of measurement against its value. Variable data is worth the gauge and time when the characteristic is critical or when you need capability evidence.
  3. Prefer variable data for critical characteristics. Anything you must prove capable, or steer before it fails, wants a measured value and a variables chart.
  4. Use attribute data for screening and go/no-go features. Fast, cheap, many-characteristics-at-once inspection where a pass/fail verdict is enough.
  5. Mind the sample size trade. Variable plans need fewer pieces per characteristic; attribute plans judge more characteristics per piece but need larger samples for the same confidence.

Can you turn attribute data into variable data?

Sometimes, and it is often worth the effort. A characteristic checked with a go/no-go gauge can usually be measured instead with a variable gauge, converting a pass/fail flag into a number. The payoff is everything variable data unlocks: capability, early warning, smaller samples. The reverse move, collapsing a measured value into pass/fail, throws information away and is only sensible when the measurement is too slow to sustain. A common upgrade path is to start a new part on attribute inspection for speed, then move the critical characteristics to variable inspection once the process stabilizes and the customer asks for capability. The point is that the data type is a choice you can revisit, not a fixed property of the part.

How does data type change what you can do downstream?

The data type you collect at inspection ripples through everything after it. Variable data feeds capability studies, first article inspection results, and the tighter control that regulated customers expect; attribute data feeds defect tracking Pareto analysis of failure modes, and yield reporting. Both flow into your nonconformance and cost of quality records, but they tell different stories: variable data explains why a process is drifting, attribute data counts what it cost. A comparison of the two at a glance:

Attribute inspectionVariable inspection
ResultPass/fail, count (whole numbers)Measured value (continuous scale)
Typical toolGo/no-go gauge, visual checkCaliper, micrometer, CMM, scale
Control chartsp, np, c, uX̄-R, X̄-S, I-MR
Sample sizeLarger for same confidenceSmaller per characteristic
Enables Cpk?NoYes
Cost to collectLow; fast; less trainingHigher; calibrated gauges; trained operators
Early warningOnly after parts failDetects drift before failure

What does the measurement side require?

Variable data is only as good as the gauge behind it, which raises the stakes on measurement quality. A variable measurement carries information about how close a part sits to its limit, but if the gauge itself is imprecise or biased, that information is fiction. This is why variable inspection leans hard on measurement systems analysis and gage R&R: a measurement system that eats a big share of the tolerance cannot be trusted to say whether a part is drifting or the gauge is. Attribute checks have their own version, attribute agreement analysis, testing whether inspectors agree with each other and with a known standard. The data-type facts worth pinning down:

Choosing between attribute and variable inspection is really a choice about how much you want to know and what you will pay to know it. On a plant floor the honest answer is usually "both, in the right places": attribute checks for speed and coverage, variable checks on the characteristics that matter most. Keeping all that inspection data, and the gauges and standards behind it, connected and searchable is the quiet challenge, and the problem Harmony's paperwork digitization and AI search was built to solve on the systems you already run, standardized to the way your quality system expects the data.