Inline Inspection Frequency: Set Checks by Process Risk, Not Habit

Inline Inspection Frequency: Set Checks by Process Risk, Not Habit

An hourly check may be too slow after a tooling change and too frequent for a stable, low-risk process. The calendar alone does not explain what can go wrong, how quickly it can spread, or what an operator must do when a check fails.

Inline inspection frequency is the documented timing and trigger logic for in-process checks that monitor a defined product or process characteristic. It should be tied to risk, process evidence, measurement capability, production flow, and a reaction plan. It is not simply “inspect every hour.”

Frequency follows the control plan. A defensible inline inspection frequency is written into the process controls rather than added after a complaint.

Table of contents

What is inline inspection frequency?

Inline inspection frequency is the defined cadence and event-based triggers for checking a characteristic while production is running. The control may occur at first-off, changeover, a stated interval, after a material or tool event, or at other documented points in the process.

Quality-One describes a control plan as a document that sets process actions such as measurements, inspections, quality checks, or monitoring. It includes method, sample size, sample frequency, controls, and reaction plan.[^1]

Control-plan element Question it answers What it does not answer alone
Frequency When is the next check required? How many units to inspect
Sample size How many units or observations are checked? Which feature is critical
Method How is the feature checked? How often conditions may change
Acceptance criterion What result is acceptable? What to do after a failed check
Reaction plan How does the team contain and investigate? Whether the original interval was appropriate

A inline inspection frequency decision should identify the product feature, process step, risk, and response. Otherwise a check becomes a box on a form.

Why is a fixed interval not enough?

Production conditions can change between two scheduled checks. A good inline inspection frequency includes both interval checks and change-event checks. Tool wear, changeovers, material batches, operator handoffs, machine settings, and process interruptions can create a risk that a clock-only plan does not capture.

Production condition Why it may affect the plan
First-off or restart Setup and adjustment may need confirmation before normal output continues
Tooling or fixture change A physical change can alter the process output
Material or component lot change Incoming variation can affect a controlled feature
Operator or shift handoff A new handoff can require documented verification under the work instruction
Process alarm or interruption The process may no longer represent the prior stable state
Recent nonconformance Temporary added control can contain risk while corrective action is checked
Stable, evidenced process The plan may be reviewed, not automatically reduced, with qualified approval

NIST distinguishes real-time process monitoring from lot acceptance sampling and explains that statistical process control compares current data against historically derived control limits.[^2] A inline inspection frequency plan should therefore include event triggers as well as ordinary timing.

Which inputs should set the frequency?

There is no universal daily, shift, hourly, or per-piece interval. Each inline inspection frequency needs its own documented basis. The team should establish the frequency from the actual process and product evidence.

Input What to review
Product risk Safety, function, fit, customer impact, and consequence of an escape
Special characteristics Features identified by design, customer, risk analysis, or process knowledge
Process evidence Stability, capability where applicable, trend data, and prior nonconformance
Measurement system Whether the method is suitable, repeatable, and practical at the line
Rate of production How much product can be made between checks and how easily it can be contained
Change points Setup, material, tool, program, operator, shift, maintenance, and restart events
Detection downstream Whether later checks can find and isolate the issue before shipment
Customer requirement Written frequency, record, or verification conditions that apply to the part
Reaction capability Ability to stop, label, segregate, trace, and recheck potentially affected output

A inline inspection frequency review should record the rationale. An undocumented “industry standard” interval is not evidence for a particular part or process.

How are frequency, sample size, and acceptance criteria different?

Teams often change all three at once after a defect. An inline inspection frequency review should keep those decisions separate. That can make it impossible to learn which control actually improved detection or process performance.

Decision Example of the question Separate control needed
Frequency Check after each changeover or every defined production interval? Trigger and timing rule
Sample size Inspect one piece, several pieces, or every piece within a defined scope? Sample plan and population definition
Acceptance Is a measurement, attribute, or visual state acceptable? Specification and tolerance
Method Use a gauge, functional test, visual aid, or process parameter record? Validated work instruction and equipment control
Escalation What happens after a failed result? Containment, notification, investigation, and release authority

The Aerospace Engine Supplier Quality FAQ explains that moving away from 100 percent inspection requires evidence appropriate to the situation, such as stable and capable process evidence or other defined process controls. It also notes that process control cannot make an incapable process capable.[^3]

When should inspection become more frequent?

More frequent checks can be a temporary containment measure. The revised inline inspection frequency needs clear scope and ownership. The added frequency should have a scope, owner, records, and exit criteria rather than becoming an unexplained permanent burden.

Trigger Possible controlled response
First-off after a setup or restart Verify the defined characteristics before normal production release
Verified defect or out-of-control signal Contain affected output, investigate, and increase checks for the defined scope
Tool, material, program, or process change Apply the agreed change-control checks and review the first output
New supplier site or new process Use an approved launch or temporary control plan
Measurement disagreement Verify the method, training, equipment status, and reference before changing production settings
Customer complaint linked to a process feature Review the affected history and corrective-action evidence before changing the plan

A inline inspection frequency increase should say when the temporary control ends. “Inspect more often” is not an exit criterion.

What should a reaction plan contain?

A failed check is useful only if the team has a defined response. This is part of every workable inline inspection frequency plan. Quality-One describes reaction plans as actions to prevent production of nonconforming output, including identification, quarantine, disposition, documentation, and notification.[^1]

Reaction-plan field Why it matters
Trigger Identifies the failed measurement, attribute, event, or trend
Immediate action Stops or contains the defined process/output scope
Suspect boundary Defines the last known good check and affected production interval
Identification Keeps suspect material distinct from conforming material
Recheck or test method States how the team verifies containment and disposition
Notification Names the responsible operator, supervisor, quality owner, and customer contact if required
Investigation Connects the issue to root cause and corrective action work
Release authority Prevents informal shipment release of held material
Exit condition Defines evidence needed to return to the normal plan

A inline inspection frequency plan without a reaction plan can find a problem and still let it travel downstream.

When can reduced checking be considered?

Reduced checking requires more than a period of passing results. Review the product risk, customer requirements, process stability, measurement-system evidence, recent changes, corrective-action status, and ability to detect a future issue.

Evidence to review Why it matters
Stable process evidence Passing specification alone does not prove statistical control
Capability evidence where applicable The process must be able to meet the requirement, not only meet it by chance
Measurement-system suitability Bad data can make a process look better or worse than it is
Change history Tool, material, site, program, or process changes can invalidate prior evidence
Defect and complaint history Repeated escapes can show the existing plan misses risk
Written approvals Customer-controlled or special-characteristic plans may require approval

The AESQ FAQ cautions against treating specification limits as control limits because that can create false alarms and unnecessary adjustment to a process that is otherwise controlled.[^3] Reduced inline inspection frequency needs a documented technical basis, not a shortcut based on paperwork volume.

Frequently asked questions

What is inline inspection frequency?

Inline inspection frequency is the documented timing and trigger rule for in-process quality checks during production.

Is hourly inspection always enough?

No. The suitable interval depends on risk, production rate, process evidence, change events, measurement method, and the reaction plan.

Should I inspect after every changeover?

Use the agreed process-control plan. Changeovers, restarts, material changes, and tooling changes are common events to evaluate because they can alter output.

Is 100 percent inspection always safer?

No. It can be costly and still depends on a suitable method and trained execution. Use it under a defined scope when the applicable risk and evidence support it.[^2]

Can a stable process use less frequent inspection?

Possibly, but the decision should be supported by appropriate process, measurement, risk, change-history, and customer-requirement evidence.

What is the difference between sample size and frequency?

Sample size is how many units or observations are checked. Frequency is when those checks occur.

What should happen after a failed inline check?

Follow the reaction plan: contain the defined scope, identify suspect output, verify the method, investigate, document, and release only through the authorized process.

Do specification limits prove process stability?

No. Process stability is assessed with process-control evidence, not only by whether points fall within product specification limits.[^3]

How do I set temporary increased inspections?

Define the trigger, affected process or lot, check method, timing, owner, records, containment boundary, and exit evidence before starting.

Can this guide set my inspection interval?

No. This is general education. Actual intervals need qualified product, process, customer, safety, regulatory, and quality review.

What makes an inspection interval useful?

A useful inline inspection frequency tells the operator when to check, what to check, how to check it, what result is acceptable, and what to do when it fails. The plan should change when the evidence changes.

References

[^1]: Quality-One, “Control Plan Development”

[^2]: NIST/SEMATECH e-Handbook, “What are Process Control Techniques?”

[^3]: Aerospace Engine Supplier Quality, “RM13006 Process Control Methods SMIG Team FAQs”

Scroll to Top