All insights
Review workspacePostmarket evidence cleanupSource review as of 2026-05-27

How To Organize Overlapping Corrective And Preventive Action, Complaint, Risk, And Postmarket Surveillance Files

When corrective and preventive action (CAPA), complaint, risk, postmarket surveillance (PMS), supplier, service, and change-control files overlap, the problem is usually not that the team has too little documentation. The problem is that nobody can quickly see which records describe the same event pattern, which evidence has already been reviewed, which questions are still open, and what rationale supports the selected action.

The practical answer is not to ask artificial intelligence for a giant summary. The practical answer is to build a product-centered review workspace with source links, duplicate candidates, cross-references, open questions, and a human-approved Decision Record.

For regulatory affairs and quality assurance (RA/QA), quality directors, consultants, small manufacturer CEOs, and operations owners cleaning up scattered product records.

The core problem

Medical device teams often create multiple records around the same product issue: complaint file, service or repair record, CAPA investigation, supplier nonconformance, risk-file review, labeling or usability note, software change request, PMS review point, email thread, and management-review action item.

Each record may be legitimate. The failure is that the records are not organized around the product event and the decision.

Step 1: Build an event map

Start by listing each record as evidence, not as a conclusion. The goal is to answer: are these separate events, duplicate records, or cross-referenced parts of the same product review?

  • Product or product family.
  • Model, version, lot, serial, or software version where available.
  • Event date and record date.
  • Record type: complaint, CAPA, risk, supplier, PMS, service, or change control.
  • Source owner and linked source document.
  • Short event description, alleged failure mode, current action, and status.

Step 2: Cluster duplicate and related records

A cleanup workflow should flag candidate clusters, not close records automatically. Regulatory affairs and quality assurance reviewers decide whether records are actually duplicates, linked, separate, or need escalation.

  • Same product, model, customer, site, distributor, or supplier.
  • Same failure mode, lot, component, software version, or service symptom.
  • Same CAPA or complaint number cited in another file.
  • Same risk-control reference or same source document attached in multiple places.

Step 3: Create a source ledger

Every cleanup packet should preserve source links. A readable summary is not enough if nobody can re-open the underlying record and verify why the summary says what it says.

  • Quality management system (QMS) record ID.
  • Complaint ID, CAPA ID, risk-file section, PMS report, supplier record, service ticket, and change-control ID.
  • Label or instruction for use version.
  • Email or meeting note if allowed by internal policy.
  • External public signal if relevant.

Step 4: Separate facts, review points, and decisions

A clean review workspace separates three layers. Facts describe dates, products, complaints, tests, service notes, supplier reports, labels, software versions, and external source links. Review points identify what the qualified reviewer may need to consider. Decisions capture what the reviewer actually approved.

  • Facts: the source-backed record details.
  • Review points: reportability screen, risk-file impact, supplier follow-up, labeling review, usability review, software change review, PMS trend review, CAPA screen, or management-review input.
  • Decisions: selected action, rejected options, rationale, approver, QMS destination, follow-up owner, and next review trigger.

Step 5: Generate a Decision Record and write back memory

After review, the system should generate a Decision Record that can be attached to the appropriate QMS, PMS, risk, complaint, supplier, or management-review destination.

The same record should also write back into the product knowledge base. That is the closed loop: the next similar issue starts with the prior rationale, source links, rejected options, and reviewer questions instead of repeating the same work.

Workload and cost framing

For a small file cleanup, a careful reviewer may spend 20 to 40 hours. For a messy multi-year product file with complaints, CAPA, risk, supplier, service, PMS, and change-control links, the work can become 80+ hours.

Artificial intelligence can cluster and summarize, but someone still has to verify sources, avoid wrong merges, maintain traceability, and decide what can be closed, reopened, escalated, or attached. That is why the deliverable should be a reviewer workspace and Decision Record, not just a summary.

What TrueMedDevice can prepare

TrueMedDevice can prepare the product-centered review workspace: event map, candidate duplicate clusters, source ledger, open review questions, reviewer options, rationale fields, and attachment-ready Decision Record.

We organize verified evidence and decision memory. The qualified reviewer approves, overrides, rejects, or changes the recommended structure.

Source ledger

U.S. Food and Drug Administration (FDA) Quality Management System Regulation (QMSR)

What it can tell you

FDA states the Quality Management System Regulation became effective February 2, 2026, amends 21 CFR Part 820, and incorporates ISO 13485:2016 by reference.

What it cannot decide

Which internal records your company should close, reopen, escalate, or attach.

FDA Medical Device Reporting (MDR)

What it can tell you

Medical Device Reporting context and FDA's caution that MDR data has limitations and does not determine incidence, prevalence, or causation alone.

What it cannot decide

Whether a specific complaint is reportable or non-reportable.

FDA Postmarket Surveillance Under Section 522

What it can tell you

FDA describes section 522 postmarket surveillance as active, systematic, scientifically valid collection, analysis, and interpretation of data about a marketed device.

What it cannot decide

Whether your product is subject to a specific surveillance order or whether a PMS file is adequate.

FDA Premarket Notification 510(k) overview

What it can tell you

FDA notes device changes may be made under quality-system controls and may be subject to a new 510(k), with justification recorded in change-control records.

What it cannot decide

Whether a specific change requires a new 510(k).

Frequently asked questions

Can artificial intelligence summarize all my CAPA and complaint files?

It can help summarize and cluster files, but summary alone is not enough. A quality review needs traceable source links, duplicate-control discipline, open questions, rationale capture, and reviewer approval.

Why include PMS and risk files?

Complaint, CAPA, service, supplier, risk, and postmarket surveillance records often reference the same product issue from different angles. A reviewer needs to see the cross-reference before deciding what record should carry the rationale.

What changed with QMSR?

FDA states that the Quality Management System Regulation (QMSR) became effective on February 2, 2026 and incorporates ISO 13485:2016 by reference. This page does not interpret QMSR obligations. It describes a practical evidence organization workflow for reviewer use.

What does TrueMedDevice deliver?

A review workspace and Decision Record structure: event map, source ledger, candidate duplicate clusters, related-record links, review points, open questions, selected action, rationale, owner, and attachment-ready output.

Need this organized around one Product ID?

Send the product family and the decision you are preparing for. We can scope a Market-Ready Sales & Support Pack or review packet around one product scene.

Start Product ID scopingSee the service page