The scene
Picture the quality assurance manager in a QMSR readiness review before inspection planning. The team knows it should monitor recalls, adverse-event reports, and warning letters, but the file does not yet show how public signals connect to internal records.
The useful artifact is not a broad PMS summary. It is a monitoring file with source links, internal record references, open questions, owners, and next review triggers.
Monitoring file checklist
- Public-source ledger with FDA recall, MAUDE, warning-letter, and database query details.
- Comparator or product-family relevance note for each signal.
- Internal evidence request: complaint trend, service record, CAPA screen, supplier note, risk-file link, or label review.
- Owner, due date, rationale field, and next review trigger.
- Decision boundary that keeps public signals separate from reportability, compliance, safety, and enforcement conclusions.
Inspection-ready output
| Output | Why it matters |
|---|---|
| Source ledger | Shows what was checked and when. |
| Signal relevance note | Prevents every public event from becoming a product conclusion. |
| Internal evidence map | Links public signals to complaint, CAPA, risk, supplier, labeling, or management-review records. |
| Qualified-review queue | Names what the QA, RA, legal, clinical, or leadership owner still needs to decide. |
Source ledger
What it can tell you
Public FDA recall and early-alert records that can trigger review questions for a product family or comparator.
What it cannot decide
Recall applicability, root cause, reportability, risk acceptability, or quality-system action for a specific manufacturer.
What it can tell you
Public adverse-event report records that may inform signal review and internal evidence requests.
What it cannot decide
Causation, event rate, product defect, complaint disposition, reportability, or safety conclusions for a specific device.
What it can tell you
Public enforcement correspondence that can reveal inspection themes and quality-system review topics.
What it cannot decide
Whether another manufacturer has the same issue or whether one company's file has an enforcement risk.
Frequently asked questions
Does a MAUDE report prove a device caused an event?
No. MAUDE reports are public signals for review. They can be incomplete, duplicated, unverified, or missing exposure context.
What is the first useful output?
An FDA PMS monitoring file with public source ledger, internal evidence map, open review questions, owners, and next trigger.
Need the FDA PMS monitoring file organized?
Send the product family and inspection question. We can scope a source-backed monitoring file for qualified review.
Reader feedback
Useful pages should feed the next topic choices. Leave a signal or a short comment.