How often should capability be rechecked at stable operations?

There is no universal interval that fits every process. In stable operations, capability is usually rechecked on a defined risk-based cadence, not left open-ended and not repeated so often that it adds cost without improving control.

As a practical starting point, many organizations use a periodic review such as monthly, quarterly, or semiannually depending on process criticality, production volume, historical stability, and how quickly the process can drift. Higher-risk or high-volume characteristics are typically reviewed more often. Low-volume work, high-mix environments, and processes with limited data may need event-based reassessment instead of a simple calendar rule.

What should drive the frequency

• Characteristic criticality: Safety, fit, function, or key characteristics generally justify more frequent checks.

• Process stability history: A process with recurring special causes, adjustment activity, or marginal capability should be reviewed more often than one with a long, well-controlled history.

• Production rate and data availability: High-volume lines can support shorter review cycles. Low-rate aerospace-style production may need lot-based or campaign-based reviews because enough comparable data may not accumulate quickly.

• Measurement-system performance: If the measurement system is weak or has drift risk, capability conclusions are less reliable and rechecks may need to be more frequent.

• Change exposure: Tool replacement, maintenance, software changes, fixture changes, alternate materials, supplier shifts, operator turnover, and routing changes are all valid triggers for early reassessment.

When to recheck immediately

Do not wait for the scheduled interval if any of the following occurs:

• Out-of-control signals or sustained trend shifts

• Nonconformances, escapes, elevated rework, or inspection fallout

• Equipment repair, rebuild, relocation, or major preventive maintenance

• New tooling, fixture changes, program edits, or parameter changes

• Material lot changes or supplier changes that affect variation

• Updated methods, revised drawings, or specification changes

• MSA concerns, recalibration issues, or gage replacement

Common policy pattern

A workable policy is to define both a routine review interval and event-based triggers. For example, an organization may review capability quarterly for critical characteristics, semiannually for stable noncritical ones, and require immediate reassessment after defined changes. That approach is usually more defensible than a blanket annual rule.

The main tradeoff is simple: checking too infrequently can miss drift and weaken evidence for ongoing process control, while checking too often can consume engineering and quality effort without improving decisions. The right answer depends on how much risk the process carries and whether the underlying data is actually comparable over time.

In brownfield environments, this also depends on system integration quality. If data comes from mixed MES, QMS, SPC, and manual inspection records, the effective review cadence may be limited by data completeness, revision alignment, and confidence in traceability. A capability review built on inconsistent part revisions, mixed routings, or unvalidated data pipelines can create false confidence. In regulated operations, that means the review process itself should be controlled, traceable, and subject to change management.

So the short answer is: recheck capability at a documented risk-based interval during stable operations, and recheck sooner whenever data, equipment, methods, materials, or control signals indicate the original capability evidence may no longer represent the current process.