The event-triage moment
Picture the RA/QA lead after support flags a field event. The complaint owner sees one issue, engineering sees a possible design question, supplier quality sees a component question, and leadership wants to know whether customers need a response.
The workspace should not force a premature conclusion. It should turn that event into review points, source links, owner assignments, and a clean boundary.
Product Review Workspace checklist
| Workspace row | What to capture |
|---|---|
| Trigger | Complaint, repair trend, supplier issue, software signal, field event, claim question, customer request, or design change. |
| Source ledger | QMSR, eCFR Part 820, MDR context, MAUDE, recall or early-alert source, internal QMS source, access date, and source limit. |
| Product facts | Device, model, lot, software version, accessory, user workflow, market, customer setting, and distribution context. |
| Record links | Complaint, CAPA screen, risk-file row, PMS record, supplier file, service ticket, labeling, IFU, training, and prior review. |
| Open decisions | Reportability, CAPA, recall, risk, supplier, label, customer, clinical, legal, and leadership questions. |
What good looks like
A useful workspace helps the next reviewer see what is known, what is missing, and who owns the next review. It should reduce guessing, not replace qualified judgment.
The workspace should also create reuse. When the next similar event arrives, the team should be able to see prior source checks, prior questions, and prior decisions instead of rebuilding the review from scratch.
Source ledger
What it can tell you
FDA's public QMSR context for quality-system expectations and inspection transition.
What it cannot decide
Whether one product event has been reviewed, escalated, or documented adequately.
What it can tell you
Current Part 820 source context for quality-system records and finished-device controls.
What it cannot decide
How one event, complaint, CAPA screen, supplier issue, or product review should be handled.
What it can tell you
FDA public reporting context that can frame reportability review questions.
What it cannot decide
Whether one event is reportable or how one company should communicate with FDA.
What it can tell you
Public adverse-event report context for external signal checks.
What it cannot decide
Whether a report applies to a specific device, confirms causation, or changes one company's risk file.
What it can tell you
Public recall and early-alert records that can trigger product-family review questions.
What it cannot decide
Whether one product event needs a field action or customer notice.
Frequently asked questions
Does the workspace decide whether an event should be reported?
No. It organizes reportability review questions, evidence, sources, and owners. Reporting, recall, risk, CAPA, supplier, customer, clinical, legal, and leadership decisions remain with qualified reviewers.
How is this different from a QMS record?
A QMS record stores the formal record. The workspace prepares the cross-record review packet so the reviewer can see public signals, internal evidence, owner questions, and source limits before formal decisions are recorded.
Need an event-triage workspace?
Send one product event and the records it touches. We can scope a source-backed Product Review Workspace checklist for qualified review.
Reader feedback
Useful pages should feed the next topic choices. Leave a signal or a short comment.