The evidence appears in decisions made outside the risk management file. Complaint evaluations, CAPA investigations, supplier controls, process changes, design changes, acceptance activities, and post-market decisions should show that relevant product and patient risks were considered when those decisions were made.

Inspection friction develops when a manufacturer presents a well-maintained risk file but cannot connect it to current quality events. A serious complaint may reveal a hazardous situation that was never evaluated against existing risk assumptions. A CAPA may correct a recurring failure without considering whether occurrence estimates or risk controls require reassessment.

Investigators can follow those connections across records. If new field information emerges, they may ask where that information entered the risk management process and what changed as a result.

Strong evidence shows that risk information moves through the quality system when circumstances change. The risk file then reflects current operating experience rather than remaining primarily a design-stage artifact.

An effective correction can still leave a significant inspection question unanswered: did the event reveal anything new about the device's risk profile or the effectiveness of existing controls? CAPA records become vulnerable when that question was never evaluated.

Consider a recurring component failure that is successfully corrected through a supplier or manufacturing change. Closing the CAPA based on reduced recurrence may appear reasonable. If the failures exposed a hazardous situation, weakened an existing risk control, or occurred more frequently than assumed, the associated risk analysis may also require review.

FDA investigators can trace the event beyond the CAPA record into complaints, design information, post-market data, and risk documentation. Disconnected conclusions become visible quickly.

A defensible CAPA shows whether the investigation affected existing risk assumptions and documents the basis for that determination. Where no risk file change is warranted, the reasoning should still be evident rather than inferred from the absence of an update.

Repeated non-reportable complaints still require meaningful evaluation because the MDR decision answers only whether a particular event meets reporting requirements. A pattern of events can reveal information about product performance, risk controls, or failure mechanisms even when individual complaints remain below the reporting threshold.

A difficult inspection position develops when every complaint contains a defensible non-reportability decision but nobody has examined the cumulative pattern. Investigators may compare complaint codes, failure descriptions, service records, returned product findings, CAPAs, and risk documentation to determine whether the manufacturer recognized an emerging safety signal.

Consistency also matters. Similar events should not produce materially different MDR decisions without a clear reason.

Strong complaint governance therefore preserves the reasoning behind individual reporting decisions while ensuring recurring events are evaluated collectively. If the pattern changes the understanding of severity, occurrence, detectability, or control effectiveness, that information should reach the appropriate quality and risk processes rather than remain isolated inside complaint records.

Records become difficult to defend when they document what was changed but provide little evidence of why the change was sufficient. FDA may begin with a complaint or CAPA and trace backward into risk management, design changes, verification, validation, and regulatory assessments.

A design change prompted by field experience deserves particular attention because the original problem establishes context for judging the adequacy of the response. If a component, software function, labeling element, or risk control was modified, investigators may ask whether all affected requirements and hazards were identified, whether verification addressed the actual failure mechanism, and whether existing products or configurations were considered.

Weak change records often contain approvals and completed testing but leave these relationships implicit.

A stronger record allows an investigator to follow the sequence from observed problem to risk assessment, design decision, implementation, objective evidence, and post-change evaluation. That continuity demonstrates that the manufacturer controlled the quality issue across the system rather than closing it within one departmental workflow.