This is a ready-to-use register for capturing OOS events in a structured, queryable form so recurring problems by method, analyst, instrument, or product surface before they become a pattern an inspector finds first. A single OOS is a laboratory or manufacturing event; the same method, the same instrument, or the same analyst behind several OOS events in a short window is a quality system signal, and you can only see the second if the data is structured, discrete fields, not prose summaries. Keep one register per site or per laboratory. Replace every <<FILL: ...>> placeholder, maintain it in a queryable system rather than a narrative log, and route the review record through your normal QA oversight. Verify each cited regulation against the current source before you rely on it.
Why structure matters
An OOS investigation record answers “what happened with this result.” This register answers a different question: “does this keep happening, and to what.” A laboratory that closes every individual OOS competently can still have a failing instrument, an undertrained analyst, or a marginal method generating a disproportionate share of them, and that will not show up anywhere unless the closed investigations are coded into fields and counted. This register is the layer between the individual OOS investigation record and the quality metrics program: narrower and more diagnostic than an aggregate OOS rate, because it is broken out by the specific method, analyst, instrument, and product that generated each event.
Part 1: OOS register (one row per event)
| Field | Format | Required | Notes |
|---|---|---|---|
| OOS ID | Text | Yes | Links to the full investigation record |
| Date opened | Date | Yes | For time-based trending |
| Material / product | Text or code | Yes | For per-product rates |
| Test / method (ID, version) | Code | Yes | For per-method rates |
| Instrument ID | Code | Yes, where applicable | For per-instrument rates |
| Analyst | Initials or ID | Yes | For per-analyst rates; never used punitively without a documented process cause first |
| Phase 1 conclusion | Assignable cause / No cause | Yes | Drives the lab-error fraction |
| Assignable-cause category | Controlled list | Conditional | e.g. integration, preparation, standard/reagent, equipment/SST, calculation, other |
| Phase 2 root-cause category | Controlled list | Conditional | e.g. process parameter, raw material, equipment, N/A if closed at Phase 1 |
| Disposition | Release / Reject / Further characterize | Yes | |
| CAPA reference | Text | Conditional | Where raised |
| Closure date | Date | Yes, to close | For time-to-close |
| Timeline met | Yes / No | Yes | Per the governing OOS SOP target |
Register table
| OOS ID | Date | Material | Method | Instrument | Analyst | Phase 1 | Cause category | Phase 2 category | Disposition | CAPA | Closed | On time |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Part 2: Trending metrics
Compute on a defined cadence (commonly monthly, with a rolling quarterly and annual view for the periodic review and the product’s annual review). Use the right denominator so a high-throughput method or a busy analyst is not unfairly flagged.
| Metric | Definition | Threshold / action |
|---|---|---|
| Overall OOS rate | Confirmed OOS per <<FILL: 1,000 tests>> | <<FILL: e.g. above 12-month baseline = review>> |
| OOS rate by method | OOS per <<FILL: 100 runs>>, per method ID | <<FILL: e.g. > 2x the site mean for that method type = method robustness review>> |
| OOS rate by instrument | OOS (especially SST/equipment-category assignable causes) per <<FILL: 100 runs>>, per instrument ID | <<FILL: e.g. >= N assignable-cause events in a quarter = maintenance/requalification trigger>> |
| OOS rate by analyst | OOS per <<FILL: 100 runs performed>>, per analyst | <<FILL: e.g. >= N events with the same cause category = training signal, not a disciplinary trigger by itself>> |
| OOS rate by product / material | Confirmed OOS per <<FILL: 100 batches or lots tested>>, per product | <<FILL: rising trend = feed to Phase 2 pattern review and the product's annual review>> |
| Lab-error fraction | Events closed at Phase 1 (assignable cause) / total events | <<FILL: rising fraction = lab practice or training signal; falling fraction with rising Phase 2 closures = potential product/process signal>> |
| Repeat-cause rate | Events sharing the same cause category, same method or instrument, within the period / total events | <<FILL: >= N repeats = systemic, not isolated>> |
| On-time closure rate | Events closed within the SOP-committed timeline / total closed | <<FILL: target %>> |
Part 3: Review record
| Field | Entry |
|---|---|
| Review period | <<FILL>> |
| Total OOS events in period | <<FILL>> |
| Metrics reviewed against thresholds | <<FILL>> |
| Outliers identified (method / instrument / analyst / product) | <<FILL>> |
| Decisions (requalification, retraining, method review, CAPA, escalate to management review) | <<FILL>> |
| Prior-period actions: status | <<FILL: closed / open, overdue called out>> |
| Reviewer (name, date) | <<FILL>> |
| QA approval (name, date) | <<FILL>> |
Acceptance criteria
- OOS data is captured in discrete, queryable fields (method, instrument, analyst, product, cause category), not free text.
- Metrics are computed on the defined cadence with the correct denominator, so a busy method or analyst is not flagged on raw count alone.
- Any metric crossing its threshold is named in the review record with a decision and an owner; a review that always concludes “no action” is not a real review.
- Repeat-cause concentration by instrument, method, or analyst is explicitly checked, not left to be noticed by chance.
- The register feeds, and is reconciled against, the site’s quality metrics program rather than existing as a parallel, disconnected count.
Retention
Retain the register and each period’s review record per the records retention schedule, for not less than <<FILL: retention period>>.
References
21 CFR 211.192 (investigation of discrepancies and failures) and 211.180(e) (review of records to evaluate quality standards, including trend detection). FDA Guidance for Industry, Investigating Out-of-Specification (OOS) Test Results for Pharmaceutical Production (originally October 2006, Level 2 revision May 2022). ICH Q10, Pharmaceutical Quality System (performance monitoring, management review, and continual improvement). ICH Q9, Quality Risk Management (risk-based prioritization of signals arising from trends). EU GMP Chapter 1 (Pharmaceutical Quality System) and the Product Quality Review.
Confirm the current version of each reference before issue.
Filled specimen
The following shows one quarter’s register excerpt and review for an example QC laboratory, so you can see the level of detail an inspector expects. The company, instrument, and numbers are illustrative; replace them with your own.
Reporting period: 01 May 2026 to 31 July 2026. Scope: finished-product HPLC assay testing, Site B QC laboratory.
Register (excerpt)
| OOS ID | Date | Material | Method | Instrument | Analyst | Phase 1 | Cause category | Disposition | CAPA | On time |
|---|---|---|---|---|---|---|---|---|---|---|
| OOS-2026-0118 | 12 May | Product X, lot AB1211 | AM-201 v6 | HPLC-07 | J. Doe | Assignable cause | Integration | Release (corrected) | CAPA-2026-0061 | Yes |
| OOS-2026-0134 | 29 May | Product X, lot AB1219 | AM-201 v6 | HPLC-07 | J. Doe | Assignable cause | Integration | Release (corrected) | CAPA-2026-0061 | Yes |
| OOS-2026-0151 | 14 Jun | Product Y, lot CD3302 | AM-114 v3 | HPLC-07 | S. Nair | Assignable cause | SST failure | Release (corrected) | CAPA-2026-0074 | Yes |
| OOS-2026-0142 | 02 Jun | Product X, lot AB1234 | AM-201 v6 | HPLC-07 | J. Doe | Assignable cause | Integration | Release (corrected) | CAPA-2026-0078 | Yes |
| OOS-2026-0167 | 09 Jul | Product Z, lot EF4410 | AM-201 v6 | HPLC-11 | M. Alvarez | No cause | N/A | Reject | CAPA-2026-0091 | Yes |
Trending metrics and decision
| Metric | Value | Decision |
|---|---|---|
| OOS rate, HPLC-07 | 4 of 5 site events in the quarter, all on one instrument | Instrument-level pattern regardless of cause category mix |
| Repeat-cause rate, integration | 3 of 4 HPLC-07 events, all coded “integration,” all involving J. Doe | Analyst and instrument both implicated; not a coincidence at this concentration |
| Lab-error fraction | 4 of 5 events (80 percent) closed at Phase 1 | High fraction; investigate whether the laboratory practice itself, not the product, is generating events |
Decision: the repeat integration-cause events on HPLC-07, concentrated with one analyst, triggered a targeted review rather than three separate closed CAPAs treated as unrelated. The review found the CDS default integration parameters on HPLC-07 had drifted from the method’s validated settings after a software update, and J. Doe had not been retrained on manual integration justification since the update. Corrective action: reset and lock the default integration parameters on HPLC-07 against the validated method, verify the same setting on every instrument the update touched, and retrain all analysts using that CDS on manual integration justification, not just the one analyst whose name appeared most often.
This is what the register is for: three individually closed, individually correct OOS investigations, each with a valid documented laboratory cause, still added up to one unaddressed system problem until they were counted against the same instrument and cause category together.
Common inspection findings this register prevents
- Individually well-documented OOS investigations that never get compared to each other, so a repeat instrument or analyst pattern goes unnoticed.
- An OOS rate tracked only in aggregate, hiding that the events are concentrated in one method, one instrument, or one analyst.
- CAPAs closed as isolated laboratory-error fixes when the same root cause recurred across multiple events.
- A high lab-error (Phase 1 closure) fraction with no review of whether the laboratory practice, not the product, is the actual signal.
- A trending review that runs every period but never changes a decision, signalling the review is procedural rather than real.
How to adapt this register
- Set your controlled cause-category lists in Part 1 so the fields stay queryable and match the categories your OOS SOP already defines.
- Calibrate the thresholds in Part 2 to your testing volume; a low-volume specialty method needs a different trigger than a high-throughput release assay.
- Reconcile the overall OOS rate and lab-error fraction with the same figures reported in your quality metrics program so the two never diverge.
- Feed confirmed outliers into instrument requalification, analyst training, or method review as the finding warrants, and track the resulting action to closure in the next period’s review.