AQL 2.5 vs AQL 4.0: The Logic of Choosing Risk Tolerance

The Silence in the Conference Room That Day, Understood Only After Switching from AQL 2.5 to 4.0

To be honest, after fifteen years in the factory, what I hate most are meetings. Not meetings themselves, but those "everyone's putting on a show, but the problem isn't actually solved" kind of meetings. I remember one time, our production line had just gotten a new client. During the pre-production meeting, the PM proudly announced that they had negotiated with the client, convincing them to relax the AQL from 2.5 to 4.0. The look on the PM's face, a mix of "I've saved the company money and reduced shipping pressure," I still remember clearly. The result? On the first shipment, the client rejected four containers! In that meeting, from team leader to factory manager, everyone sat in silence in the conference room, no one dared to speak, and it stayed that way for a full three seconds.

Where Did the Problem Lie? What's the Difference Between AQL 2.5 and 4.0?

AQL, Acceptable Quality Level, simply put, is the "acceptable quality level" agreed upon with your client. It doesn't mean how much defect rate your product can have; rather, it specifies how many defective items, when sampled, should trigger the rejection of that batch of goods.

So the key point is: AQL 2.5 means that if you inspect 200 products, if there are more than 10 defective items, this batch of goods should be rejected. But if it's AQL 4.0, inspecting 200 products means the batch should only be rejected if there are more than 14 defective items.

It sounds like 4.0 is much "looser" than 2.5, doesn't it? The PM thought so too at the time. Essentially, the larger the AQL number, the higher your tolerance for defective products.

How to Actually Do It? It Depends on Your "Risk Tolerance"

So, should you choose AQL 2.5 or 4.0? There's truly no standard answer; it reflects the consensus between you and your client regarding "quality risk."

In other words, when we select an AQL value, we are essentially asking ourselves a few questions:

1. How critical is your product? Imagine if you're manufacturing aerospace parts, where a loose screw could lead to an air disaster. Would you dare use AQL 4.0? Of course not! In such a case, AQL 1.0 or even more stringent levels might still be considered insufficient. However, if you're making disposable cutlery, and a fork breaks, the client might just complain; then AQL 4.0 or even 6.5 might be acceptable.
2. What is your process capability? If your process capability is poor, with a Cpk of only 0.67 and a daily production line defect rate as high as 20000 DPMO, would you dare sign AQL 2.5 with a client? Isn't that asking for trouble? Conversely, if your process capability is excellent, with Cpk consistently above 1.67 and a defect rate below 3.4 DPMO, then offering the client AQL 2.5, or even 1.5, not only demonstrates your quality confidence but can also help secure more orders.
3. What are the client's pain points? Some clients are particularly concerned about "yield" figures, some about "delivery time," while others are most afraid of "customer complaints." Understanding the client's pain points allows you to make informed trade-offs when selecting an AQL.

In our previous case, the PM simply didn't understand that the client's relaxation of AQL to 4.0 wasn't because their quality requirements had genuinely lowered. Instead, our product was considered a "non-critical component" within their system. But the problem is, when the defect rate of these "non-critical components" reaches a certain level, causing their production line to halt, then the return of goods is entirely justified.

The Most Common Pitfall: Treating AQL as a "Target"

The most common mistake I see engineers make is treating AQL 2.5 or 4.0 as if "our goal is to only have this many defective products." This fundamentally misunderstands the point! AQL is a "judgment criterion"; it is not your process target.

Simply put, your process defect rate should always be lower than the AQL you agreed upon with the client. If your process defect rate is consistently hovering at the edge of the AQL, then every shipment you make is a nail-biter.

It's like driving; if the speed limit is 100 km/h, would you really drive at 99 km/h all the time? Of course not! You'd drive at 80, 90, leaving some margin just in case. The same logic applies to AQL.

One Thing You Can Do Today

Go back and review your current AQL settings, ensuring they match your process capability and client requirements.