Skip-Lot Thresholds in Quality Inspector

Skip to main content

Skip-Lot Thresholds in Quality Inspector

You are here:

Quality Inspector supports multiple ways to determine when to advance to a reduced-inspection level in a skip-lot scheme:

Threshold Type What it Counts Best Used When
Create Threshold Number of tests created (or skipped). You care about inspection frequency / workflow pacing.
Pass Threshold Number of tests that successfully pass. You care about only advancing once quality is demonstrated.
Fail Threshold Number of failed tests allowed (usually 1). You need to immediately reset to full inspection.

Most regulatory skip-lot procedures require failures to reset the sequence, so Fail Threshold is usually set to 1.

Create Threshold (Count Created/Skipped Tests)

Skip-lot step advances once a specified number of tests have been created or skipped regardless of test outcome.

Use when:

  • You want to follow a schedule like “inspect every X lots”.
  • You want to move forward even if tests take time to finish.
  • You are not required to wait for confirmed passing results before reducing inspection.
  • The main goal is to reduce workload, not enforce strict quality proof before skipping.

Example

“Inspect the first 10 lots, skip the next 5, and inspect 1 every so often.”

Configuration Pattern:

  • Create Threshold: 10 → 5 → 1
  • Pass Threshold: leave empty (optional)

Industry Scenario Example:

  • Supplier consistently performs well.
  • No regulatory requirement to confirm pass before reducing inspection.
  • A pragmatic skip-lot program to reduce QA load.

Pass Threshold (Count Passed Tests)

Skip-lot step advances only after [X] lots have passed inspection.

Use when:

  • You must prove acceptable quality before reducing inspection.
  • Lot results must be complete before advancing.

Regulatory, customer, or audit requirements demand confirmed passes

Example

“The first 10 lots must pass before reducing inspection frequency.”

Configuration Pattern:

  • Pass Threshold: 10
  • Create Threshold: optional (may be lower or equal)
  • Fail Threshold: usually 1

Industry Scenario Example:

  • USDA / CFR-style regulated processes.
  • Pharmaceutical, medical device, or aerospace manufacturing.
  • Where a failed lot must block advancement.

Use Create Threshold and Pass Threshold together

You may configure Create Threshold and Pass Threshold at once.
Typical pattern:

Scenario Behavior
Both set System advances when either condition is satisfied (whichever comes first).
Pass only Must wait for passes — strict compliance.
Create only Strict cadence — fastest movement to skip-lot.

Considerations

  • Many sites block lots (or restrict grades) so a failed lot cannot ship or be consumed. If so, waiting for passes may not be necessary; the process ensures containment anyway.
  • Choose thresholds based on:
    • Regulatory requirements
    • Risk tolerance
    • Inspection cycle time
    • Operational efficiency goals
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Need help?
Tags:

Leave A Comment

Table of Contents
Go to Top