Out-of-Trend (OOT) Results: Detection, Statistical Triggers, and Investigation

An out-of-trend (OOT) result is a value that sits inside specification but does not match the historical pattern you expected. The batch still passes. The number still releases. And yet something has shifted: a stability assay falling faster than its peers, an impurity creeping up two batches in a row, a content-uniformity mean drifting toward an edge. OOT is the early-warning system that sits underneath the pass or fail line. Handled well, it catches a failing trend months before it becomes an out-of-specification (OOS) result. Handled badly, it becomes a stack of unexplained results that an inspector reads as a quality system that cannot tell signal from noise.

This article covers what OOT is, why it is regulated, the statistical methods used to flag it, and the step-by-step investigation. The emphasis is on stability data, because that is where OOT does most of its work and where inspectors look first.

OOT versus OOS: the distinction that matters

OOS and OOT are different events with different triggers and different consequences. Confusing them is one of the most common findings in this area.

• An OOS result breaches a registered or compendial acceptance criterion. Assay below 95.0 percent when the limit is 95.0-105.0 percent. A single impurity above its specification. OOS handling is governed by the FDA guidance Investigating Out-of-Specification (OOS) Test Results for Pharmaceutical Production (2006) and is built around confirming or invalidating a single failing number.
• An OOT result is within specification but breaches a statistical or historical expectation. The value is acceptable against the registered limit but abnormal against the data set it belongs to. There is no single binding regulation titled “OOT.” The expectation comes from the broader trending and quality-system requirements in 21 CFR 211.180(e), ICH Q10, and ICH Q1E.

A useful mental model: OOS asks “is this batch acceptable?” OOT asks “is this batch behaving like it should, and is the process or product still under control?” An OOT result that you ignore is often the second-to-last data point before an OOS.

There is a third category worth naming so you do not mislabel it: an atypical or anomalous result, which is a value that looks wrong for an assignable laboratory or sampling reason (a transcription slip, a failed system suitability, an obvious sample-prep error). Atypical results are handled under laboratory investigation procedures and may overlap with OOT, but the trigger is different. OOT is specifically about deviation from a statistical trend, not about a suspected error.

The triage decision, as a flow

When a result lands, the first job is to route it to the right process before you do anything else. The routing is a small number of yes/no questions, and getting it wrong (treating an OOT as an OOS, or waving away a real trend as noise) is itself a common finding.

A result can be more than one thing in sequence: an atypical result that is confirmed real can still be OOT, and an OOT result whose confirmation reveals an assignable error moves to the atypical path. Route by the first YES, then re-evaluate after each confirmation step.

Why OOT is required: the regulatory basis

There is no CFR section that uses the words “out of trend,” so people sometimes claim OOT is optional. It is not. The obligation is assembled from several requirements.

21 CFR 211.180(e) requires that records be reviewed at least annually to evaluate the quality standards of each drug product and to determine the need for changes. The regulation specifically calls for review of records to find trends:

…written records required by this part shall be maintained so that data therein can be used for evaluating, at least annually, the quality standards of each drug product to determine the need for changes in specifications, manufacturing, or control procedures.

You cannot evaluate trends or determine the need for changes without a defined way to detect when data departs from the trend. That detection mechanism is OOT.

21 CFR 211.165(d) and 211.160(b) require that test methods and laboratory controls be scientifically sound and that data establish that the product conforms. A statistically defensible trending program is part of “scientifically sound.”

ICH Q1E, Evaluation of Stability Data (2003), is the closest thing to a dedicated OOT reference. It describes statistical evaluation of stability data, regression analysis to establish shelf life, poolability testing across batches, and the expectation that you understand the slope and variability of degradation. When a stability point does not fit the established regression, ICH Q1E is the framework that tells you that the fit, and therefore the result, deserves scrutiny.

ICH Q1A(R2), Stability Testing of New Drug Substances and Products (2003), sets the storage conditions, time points, and bracketing/matrixing design that produce the data OOT acts on.

ICH Q10, Pharmaceutical Quality System (2008), requires a system that monitors process and product performance and feeds it into continual improvement and management review. OOT detection and escalation is one of the monitoring outputs that Q10 expects.

ICH Q9, Quality Risk Management (2005, revised R1 2023), governs how you classify the risk of an OOT result and how deep your investigation goes.

A well-known piece of practical guidance is the MHRA-associated industry paper often cited in the field, the PhRMA CMC Statistics and Stability Expert Teams publication on OOT results (Torbeck and others, published in Pharmaceutical Technology, 2003-2005). It is not a regulation, but it is where the three common stability OOT methods (regression control chart, by-time-point, and slope-control) were formalized, and inspectors and auditors recognize them.

The risk rationale is straightforward. Specifications are set with margin. A result can drift halfway across that margin while still passing every batch. If you only watch the spec limit, you discover the problem when a batch finally fails, by which time you may have months of product in the field. OOT converts that lagging failure signal into a leading drift signal.

Where OOT applies

OOT is not only a stability concept, though stability is the heartland. The major application areas:

1. Stability studies. Assay decline, impurity growth, dissolution drift, water content, pH. This is the primary use and the rest of this article weights it heavily.
2. Batch-to-batch trending of release data. Assay, impurities, content uniformity, particle size, bioburden, endotoxin across commercial batches. See annual-product-review-pqr.
3. Continued process verification (CPV). Control charts on critical process parameters and critical quality attributes. See continued-process-verification-cpv and statistics-in-quality-cpk-control-charts.
4. Environmental and utility monitoring. Trending of viable and non-viable counts, water conductivity and TOC, where a within-alert-level upward trend is itself a signal. See environmental-monitoring-program and water-system-validation-usp-1231.
5. Analytical performance. Drift in system suitability, reference-standard response, or control-sample results over time.

The statistical triggers: how you flag OOT

OOT detection needs an objective rule. “It looks high” is not defensible. The methods below are the standard toolkit. For stability, the three regression-based methods are the recognized approaches; for batch trending, control charts and run rules dominate.

Method 1: by-time-point limits (the simplest)

You build an expected range for each individual time point from historical batches, then compare the new result against that range.

• Pool the results at, for example, the 6-month time point from all prior validated/representative batches.
• Compute the mean and standard deviation.
• Set OOT limits, commonly the mean plus or minus 3 standard deviations, or a tolerance interval that covers a stated proportion of the population with a stated confidence (a 95/99 tolerance interval is common).
• A new 6-month result outside the limit is flagged OOT.

Strength: easy to compute and explain. Weakness: it treats each time point independently and ignores the shape of the curve, so it can miss a result that is consistent with a previously bad batch but inconsistent with a healthy degradation slope. It also needs enough historical batches (a practical minimum is often stated as 6-8 batches before limits are meaningful, fewer than that and you carry wide uncertainty).

Method 2: regression control chart (slope and intercept based)

This is the workhorse for stability. You fit a regression line (usually linear) to historical stability data for the attribute, then build a prediction interval around the expected value at each time point.

• Fit the degradation model from representative batches (assay versus time, impurity versus time).
• Construct a prediction interval at each time point. The prediction interval is wider than a confidence interval because it accounts for the variability of a single future observation, not just the uncertainty in the mean.
• A new result falling outside the prediction interval at its time point is OOT.

Strength: it respects the expected shape of the curve and the natural widening of uncertainty over time. Weakness: it assumes your model form is correct (linear, or a justified transformation) and that residuals behave.

Method 3: slope-control (by-batch trend)

Here the unit of analysis is the slope of an individual batch, not a single point.

• Estimate each batch’s degradation slope by regression.
• Build a control limit on slope from historical batches (mean slope plus or minus 3 standard deviations of slope).
• A batch degrading materially faster than the historical population, even while every individual point is in spec, is flagged.

This is the method that catches the dangerous case: a batch that is passing now but degrading on a trajectory that will breach spec before expiry. It is the most direct link between OOT and predicted shelf-life risk.

Method 4: control charts and run rules (batch-to-batch and CPV)

For release-data and process trending, Shewhart control charts with Western Electric / Nelson run rules are standard:

• One point beyond 3 sigma.
• Two of three consecutive points beyond 2 sigma on the same side.
• Four of five consecutive points beyond 1 sigma on the same side.
• Eight (or seven, depending on the rule set) consecutive points on the same side of the centerline.
• Six consecutive points trending in the same direction.

Any run-rule violation is an OOT signal even when no single point is out of specification. See statistics-in-quality-cpk-control-charts for chart construction and capability indices.

A worked numeric example (regression control chart)

Suppose assay (percent of label claim) for a tablet at 25C/60%RH, historical batches give a fitted line:

Predicted assay = 100.4 minus (0.18 percent per month) times months.

Historical residual standard deviation around the line is 0.45 percent. For a single future observation, the prediction interval half-width at 12 months works out to roughly plus or minus 1.0 percent (the exact value depends on the design and the t-multiplier; here we use approximately 2.2 times the prediction standard error).

At 12 months the predicted value is 100.4 minus (0.18 times 12) = 98.2 percent. The prediction interval is about 97.2 to 99.2 percent.

The specification might be 95.0-105.0 percent. Batches C and D pass spec comfortably, yet both are OOT. Batch C matters most: a result below the expected curve hints at faster-than-modeled degradation and is the one to investigate hard against shelf-life risk. Batch D, above the curve, is usually lower risk for product safety but still needs a cause (often an assay or reference-standard issue, sometimes a real formulation difference).

Notice that an unusually high assay is still OOT and still investigated. People sometimes wave away “good news” results; do not. A high result can be the first sign of an analytical drift or a calculation error that will read low next time.

A worked numeric example (slope-control)

The regression chart above flags a single point. Slope-control flags a whole batch that is on a bad trajectory even when every point it has produced so far is comfortably inside both the spec and the by-time-point limits. That is the case a point-by-point method misses.

Say the historical batches for the same tablet assay give a mean degradation slope of -0.18 percent per month with a standard deviation across batches of 0.03 percent per month. A 3-sigma slope control limit is therefore -0.18 +/- 0.09, i.e. a batch is flagged if it degrades faster than about -0.27 percent per month or slower than about -0.09 percent per month.

Batch G is the dangerous one. At 6 and 12 months its individual assays may still be 98-99 percent and pass every by-time-point check, but its slope predicts a spec breach before the 24-month expiry. Slope-control catches it now, while there is still time to investigate cause and reassess shelf life, rather than at the release point where the batch finally fails. This is the most direct statistical link between an OOT signal and predicted shelf-life risk, and it is why a program that relies only on by-time-point limits is incomplete.

Choosing a limit method: a comparison

The four methods are not interchangeable, and picking the wrong one is a real source of both missed trends and false alarms. Match the method to the question.

A mature stability trending program usually runs at least two of these together: a regression prediction interval on each point plus a slope-control limit on each batch, so that both a single anomalous point and a bad trajectory are caught. Confidence intervals (uncertainty in the mean) are deliberately absent from this table: for judging a single new result you want a prediction interval, which is wider because it also carries the variability of one future observation. Using a confidence interval here is a common statistical error that produces far too many false OOT flags.

Setting the limits: a few rules of practice

• Decide the limit before you generate the result. Limits set after seeing a number are not credible.
• State the method in an SOP and the specific limit basis (3 sigma, tolerance interval, prediction interval) in the stability protocol or trending SOP.
• Distinguish alert and action style OOT limits if useful: a tighter alert level that prompts heightened review and a wider action level that mandates a formal investigation. This mirrors environmental-monitoring practice.
• Re-baseline limits periodically (for example at each annual product review) but document the change so an inspector can see history and rationale. See annual-product-review-pqr.
• Watch your false-positive rate. A 3-sigma rule applied across many attributes and time points generates expected false flags by chance. That is fine and expected; the point of the investigation is to separate noise from signal, not to pretend every flag is a defect.

OOT for biologics and advanced therapies: the small-n problem

The methods above were formalized on small molecule stability data, where a program may have dozens of batches and low assay variability. Biologics, cell and gene therapy, and other advanced modalities break both assumptions, and the trending program has to adapt rather than pretend it can compute a clean 3-sigma limit from thin data.

Two structural differences drive the change:

• Few batches. A viral vector or an autologous cell product may have only a handful of GMP lots at the point where you need trending, and each lot can be a single patient’s material. You cannot build a stable mean and standard deviation from three or four points, and a 3-sigma limit computed from them is not a control limit, it is an artifact. See the note under common mistakes on presenting limits from too few batches.
• High and heterogeneous assay variability. Potency by cell-based bioassay, vector genome titer by ddPCR, and identity by sequencing are inherently more variable than a small molecule HPLC assay. A wide method variance widens the prediction interval, so a genuine product trend can hide inside the analytical noise unless the method variability is characterized and separated from batch-to-batch variability.

Practical adaptations that hold up in an inspection:

• Widen the evidence base, not just the limit. Use development, engineering, and clinical lots (with a documented rationale for their representativeness) to inform expected ranges while commercial data accumulates, and state clearly which data supports the limit.
• Separate analytical from process variability. Where possible, use assay controls and reference-standard trending to quantify method variability, so the OOT limit reflects real product drift rather than assay scatter. A shift in the assay control is an analytical signal, not a product trend.
• Lean on slope and multi-condition coherence over single points. With noisy assays, one point outside a band is weak evidence; a consistent slope across time points, or a coherent story across storage conditions, is much stronger. Weight the batch-level and cross-condition view accordingly.
• Treat every point as high-value. With few lots, a single confirmed OOT is a larger fraction of your total knowledge about the product. The investigation depth for a confirmed biologic OOT is usually higher than for a mature small molecule, and it ties directly to comparability and to potential shelf-life or specification changes. See comparability and potency assays and data integrity in gene therapy.
• Be explicit that limits are provisional and will tighten. Document that early limits are wide by necessity and are re-baselined as data accumulates, with the audit trail of each change. An inspector accepts a wide, honestly-derived early limit; they do not accept a limit that was quietly widened after a result fell outside it.

The underlying principle does not change: detect within-spec drift early, investigate proportionately, and connect the conclusion to shelf life and to the product’s control strategy. The statistics just have to be honest about how little data supports them.

Acceptance criteria: what good looks like

You know your OOT program is in good shape when:

• The OOT limits and the detection method are defined in a controlled SOP and applied prospectively, not reverse-engineered after a result.
• Every stability protocol references the trending/OOT evaluation approach.
• OOT results are detected in a timely way (each time point is evaluated when generated, not only at the annual review), and there is a defined trigger and timeline for opening an investigation.
• Each OOT investigation reaches a documented conclusion: confirmed real trend, analytical/sampling cause, or statistical noise, with the rationale.
• OOT outcomes feed shelf-life decisions, specification reviews, and management review. They do not die in a spreadsheet.
• The trend evaluation looks at the whole study, not the isolated point: a single flagged result is read in the context of the batch’s other time points and sister batches.

The OOT investigation: step by step

Below is a defensible sequence. Adjust depth by risk per ICH Q9. Not every OOT result needs a full multi-week investigation, and a program that treats every statistical blip as a major deviation will collapse under its own weight. The art is proportionate response.

Step 1: detect and document the flag

The moment a result trips the OOT rule, record it. Capture the attribute, the value, the time point, the limit it breached, the method used, and the date. Open the appropriate quality record. Many sites use a tiered approach: a quick technical assessment first, escalating to a formal deviation only if the assessment cannot close it. See deviation-management and quality-event-classification-triage.

Step 2: confirm the data, not just the result

Before chasing a manufacturing cause, confirm the number is real.

• Re-check the calculation, the data entry, the integration (for chromatographic methods), and the transcription from instrument to LIMS. A surprising share of OOT flags are arithmetic or transcription artifacts. See chromatography-data-system-integrity.
• Verify system suitability and instrument calibration were within limits at the time of test. See calibration-and-metrology-program.
• Confirm the reference standard lot, its assigned value, and its expiry. A new reference-standard lot with a slightly different assigned potency is a classic cause of an apparent step change across an entire stability program.
• Confirm sample handling: was the stability sample pulled, stored, and pulled from the correct chamber and condition? A misfiled or mis-conditioned sample produces a genuine but meaningless OOT.

If you find a clear assignable data error, document it, correct it under data-integrity-sound change control, recompute, and reassess against the OOT limit. Do not simply delete the original. See good-documentation-practices and data-integrity-foundations.

Step 3: assess the result in context

Pull the surrounding data and ask whether this is one point or a pattern.

• Plot the full curve for this batch. Is the OOT point an isolated spike, or is the whole batch trending off?
• Compare with sister batches at the same time point and on the same condition.
• Compare across conditions: a real degradation signal usually shows a coherent story across 25C, 30C, and 40C accelerated data, with the higher stress conditions moving more.
• Check whether the same analyst, instrument, column lot, or reagent lot is common to other flagged results.
• For impurities, is it a known specified impurity behaving predictably, or an unexpected peak?

This step is where you decide the likely nature of the event: laboratory cause, sampling cause, real product/process trend, or statistical noise.

Step 4: laboratory investigation (if indicated)

If the data confirmation in Step 2 did not resolve it and a lab cause is plausible, run a structured lab investigation aligned with the principles of the FDA OOS guidance Phase I: interview the analyst, review the method, examine standards and reagents, and where scientifically justified perform a retest or re-assay under a pre-approved protocol. Re-testing an OOT result is allowed but must be governed: define the retest plan and the decision rule before you run it, never test into compliance. The same anti-”testing-into-compliance” discipline that governs OOS applies here. See oos-investigation-process.

Step 5: root cause analysis

If the result is confirmed and not a lab artifact, determine why. Use structured tools, not guesswork: fishbone (Ishikawa), 5-Whys, fault tree as appropriate. See root-cause-analysis-techniques. Typical real causes for stability OOT:

• A formulation, excipient, or supplier change that altered the degradation rate.
• A container-closure change affecting moisture or oxygen ingress. See container-closure-integrity-testing.
• A process change that shifted initial impurity levels or moisture, so the batch starts higher and reaches the line faster.
• A genuine inherent batch-to-batch variability that the historical model under-represented (the model needs widening, not the batch needs blaming).
• An analytical method drift: column aging, mobile-phase change, standard degradation.

Step 6: impact and risk assessment

Now answer the questions a reviewer and an inspector will ask:

• Shelf life: does the observed trend, if extrapolated, threaten the assigned expiry? Re-run the regression including the new point and check the worst-case batch against spec at expiry per ICH Q1E.
• Other batches: are batches on the market or in the same campaign affected? Is a field action conceivable? See recall-management-field-actions.
• Specifications: do the data suggest the registered spec or the internal alert limits need revision?
• Patient risk: for an impurity trend, is there a toxicological or nitrosamine concern? See nitrosamines-impurities-q3-m7.

Document the risk decision and who made it.

Step 7: CAPA and disposition

If a real cause is found, define corrective and preventive actions: tighten an in-process control, change a supplier qualification, revise the method, update the stability model, add monitoring. Verify effectiveness later, do not assume it. See what-is-a-capa and capa-effectiveness-verification. Record the disposition of the affected batch(es): in most OOT cases the batch remains released because it is within spec, but the rationale and any conditions (for example continued enhanced monitoring or a shortened expiry) are documented.

Step 8: escalate, close, and trend the trend

Close the record with a clear conclusion. Feed confirmed OOT findings into the annual product review and management review so they inform continual improvement. See management-review-q10. And track whether OOT events themselves are increasing, which is a meta-signal about process control or about loose limits.

Roles and responsibilities

A point of separation: the analyst who generated the result should not be the sole person who decides it was “just noise.” QA owns the disposition. That independence is what makes the conclusion credible.

Common mistakes and inspection-finding patterns

These are the patterns auditors and inspectors repeatedly cite. None require naming a company.

• No OOT program at all. The firm watches only the spec limit and has no defined method to detect within-spec drift. Finding: failure to evaluate trends adequately under 211.180(e).
• OOT limits set after the fact. Limits widened, or the method changed, only once a result fell outside, with no contemporaneous justification. Reads as data manipulation.
• OOT flags raised but never investigated. A trending report shows flagged points that were acknowledged and then closed with no rationale, or with a boilerplate “within specification, no action.”
• Treating OOT as automatically equal to OOS, or vice versa. Either over-escalating every statistical blip into a full OOS-style invalidation, or under-reacting to a real degradation trend because “it still passed.”
• Ignoring the slope. Evaluating only individual points against by-time-point limits and missing a batch that is degrading on a trajectory toward failure.
• Reference-standard step changes mistaken for product trends (and the reverse). Failing to check standard lot history when an entire program shifts at one time point.
• Testing into compliance. Retesting an OOT result without a pre-approved plan, then reporting only the result that fits the trend. This is a data-integrity finding, not just a procedural one. See data-integrity-foundations.
• Not enough batches to support the statistics. Setting 3-sigma limits from two or three batches and presenting them as established control limits.
• OOT data not connected to shelf life. A confirmed downward assay trend with no documented reassessment of expiry under ICH Q1E.
• No periodic re-baselining, or re-baselining with no audit trail. Limits silently changed in a spreadsheet with no version control. See infrastructure-qualification-and-spreadsheet-validation for spreadsheet control expectations.
• Manual, uncontrolled spreadsheets doing the trending, with broken formulas and no validation, so the limits themselves are wrong.

Interview-ready: questions and strong answers

Q: What is the difference between OOS and OOT? A: OOS breaches a registered or compendial specification limit; the batch may be unacceptable. OOT is within specification but breaches a statistical or historical expectation; the batch usually still releases, but the result is an early warning that the product or process may be drifting. OOS handling follows the FDA 2006 OOS guidance. OOT obligation comes from 21 CFR 211.180(e), ICH Q10, and for stability ICH Q1E. The key insight is that an OOT result is often the data point before an OOS.

Q: Walk me through how you would set OOT limits for a stability assay. A: I would use representative historical batches, fit the degradation regression (assay versus time, typically linear or a justified transform), and build a prediction interval at each time point because a single future observation has more variability than the mean. I would define this method and the limit basis in an SOP and the stability protocol before any new result is generated, set the limits prospectively, and re-baseline at the annual product review with a documented audit trail. I would also consider a slope-control limit to catch a batch degrading faster than the population.

Q: A 12-month stability assay comes in at 97.0 percent, spec is 95.0 to 105.0, predicted was 98.2 with an interval of 97.2 to 99.2. What do you do? A: It passes spec but is OOT, below the prediction interval. First I confirm the data: calculation, integration, transcription, system suitability, calibration, and the reference-standard lot, because a standard lot change is a common cause. If the data is sound, I assess context: the full curve for this batch, sister batches, accelerated conditions, and common analyst/instrument/reagent. If it is a real trend I do root cause analysis, re-run the regression including this point, and check the worst-case batch against spec at expiry per ICH Q1E to see whether shelf life is at risk. I document the conclusion and disposition and feed it into the PQR.

Q: Is a high OOT result, above the expected line, a problem? A: Yes, it still gets investigated. A high assay is often an analytical or calculation artifact, or a reference-standard issue, and it can mask a real low result coming next. The investigation depth may be lower if patient risk is low, but you do not dismiss it just because it looks like good news.

Q: Can you retest an OOT result? A: Yes, but only under a pre-approved retest plan with a defined decision rule, the same discipline as OOS. You never keep testing until you get a result that fits the trend. Retesting without a plan, and reporting selectively, is a data-integrity finding.

Q: Which regulations and guidances support OOT? A: 21 CFR 211.180(e) for the requirement to review records and detect trends, 211.165(d) and 211.160(b) for scientifically sound controls, ICH Q1E (2003) for statistical evaluation of stability data and shelf life, ICH Q1A(R2) (2003) for the study design, ICH Q10 (2008) for monitoring and continual improvement, and ICH Q9 (2005, R1 2023) for risk-based investigation depth. The PhRMA OOT industry papers from the early 2000s are the recognized source of the three stability OOT methods.

Q: How do you avoid drowning in false OOT flags? A: Accept that a 3-sigma rule across many attributes and time points will produce expected false positives by chance, and design the investigation to be proportionate: a quick technical assessment for low-risk noise, escalating to a formal investigation only when the data and risk warrant it. Use context (sister batches, the full curve, multiple conditions) to separate signal from noise, and re-baseline limits so they reflect real process variability rather than an unrealistically tight early estimate.

Practical tips

• Evaluate each stability time point against OOT limits when it is generated, not only at the annual review. The whole value of OOT is the early warning, which you lose if you batch the analysis to once a year.
• Keep a single controlled, validated tool for the trending. If it lives in a spreadsheet, that spreadsheet is a GMP record and needs version control and validation. See infrastructure-qualification-and-spreadsheet-validation.
• Always check the reference-standard lot history first when an entire program steps at one time point. It is the highest-yield check.
• Write the OOT decision rule and retest plan before you see the result. Contemporaneous, prospective limits are what make the whole program defensible.
• Tie every confirmed OOT conclusion to a shelf-life check and to the PQR. An OOT investigation that does not touch expiry or feed continual improvement is incomplete.
• Distinguish alert-level and action-level OOT so your response is graded, the same logic environmental monitoring uses.
• Trend your OOT events themselves. A rising count of OOT flags is a signal about either tightening process control or limits that are too tight.

Related articles

• oos-investigation-process
• stability-programs-ich
• statistics-in-quality-cpk-control-charts
• continued-process-verification-cpv
• annual-product-review-pqr
• root-cause-analysis-techniques
• deviation-management
• what-is-a-capa
• quality-risk-management
• nitrosamines-impurities-q3-m7