The CAPA trend-review moment
Picture the VP Quality before management review. Three complaints, two supplier notes, one service pattern, and an older CAPA all point toward the same product-family question, but the records live in different places.
The useful move is not to declare a systemic problem from a count. The useful move is to build a CAPA trending packet that lets qualified reviewers see the source, record family, repeated mechanism candidate, owner, and open decision.
CAPA trending source ledger
| Packet row | What to capture |
|---|---|
| Trigger | Management-review question, complaint cluster, supplier issue, audit observation, service pattern, nonconformity, recall signal, or risk-file concern. |
| Public source context | QMSR, eCFR Part 820, ISO 13485 page, warning-letter search, MDR context, recall or early-alert source, access date, and source limit. |
| Internal record family | Complaint IDs, CAPA IDs, nonconformity records, supplier files, service tickets, risk-file rows, PMS reports, and prior review notes. |
| Pattern hypothesis | Shared failure mechanism, product family, component, user step, supplier, label, software version, or workflow point that needs qualified review. |
| Decision boundary | Open CAPA scope, risk, reportability, recall, supplier, customer, legal, clinical, and leadership decisions. |
What good looks like
A useful CAPA trending packet is not a verdict. It is a review aid that shows where the repeated pattern may be, where evidence is still missing, and which owner needs to review each decision.
The packet should preserve source limits. A public warning letter can frame a question; it cannot decide whether your specific trend, product, CAPA scope, or risk-control file has the right conclusion.
Source ledger
What it can tell you
FDA's current public QMSR context for finished device manufacturers and quality-system inspection transition after February 2, 2026.
What it cannot decide
Whether one manufacturer's CAPA trend package, nonconformity handling, or management-review record is sufficient.
What it can tell you
The current electronic CFR text for Part 820 and its QMSR applicability context.
What it cannot decide
How one CAPA, complaint cluster, supplier issue, or service trend should be handled.
What it can tell you
The official ISO page for the quality management systems standard used in medical-device quality-system contexts.
What it cannot decide
Whether a specific QMS record set, CAPA process, or certification position satisfies a reviewer.
What it can tell you
Public FDA warning-letter search context that can help a team study inspection themes and enforcement language.
What it cannot decide
Whether a cited warning-letter fact pattern applies to one manufacturer or one CAPA trend.
What it can tell you
FDA public context for MDR reporting and medical-device problem reporting pathways.
What it cannot decide
Whether one complaint, malfunction, injury, or trend creates a device-specific reporting action.
What it can tell you
Public recall and early-alert context that can frame product-family review questions.
What it cannot decide
Whether one product family, supplier issue, or CAPA trend needs a company-specific field action.
Frequently asked questions
Does this checklist decide whether a CAPA trend needs escalation?
No. It organizes source context, internal evidence, and open questions. CAPA scope, trend significance, risk, reportability, recall, supplier, customer, legal, and leadership decisions remain with qualified reviewers.
What should be collected before the trend review?
Collect the trigger, source URLs, complaint IDs, CAPA IDs, nonconformity records, supplier records, service records, risk-file rows, PMS notes, prior decisions, owner map, and open questions.
Need a CAPA trend-review packet?
Send the product family, repeated signal, and current review question. We can scope a source-backed CAPA trending checklist for qualified review.
Reader feedback
Useful pages should feed the next topic choices. Leave a signal or a short comment.