This guide helps you organize those supplemental records for a US-market medical-device manufacturer. It does not replace your complaint procedure, the incorporated ISO requirements or a device-specific reporting assessment. Check your role, operations and applicable exemptions against Part 820's scope before applying the worksheet.
What belongs in medical device complaint records?
Start with the complaint and the decisions it prompted. Section 820.35(a) requires records of review, evaluation and investigation for complaints involving possible failure of a device, labeling or packaging to meet its specifications. The section supplements ISO 13485 rather than reproducing the whole complaint-handling process.
Keep the original allegation accessible alongside your assessment. As a practical organizing choice, give the record an identifier and link any investigation, product assessment, correspondence and reporting evaluation to it. These linking fields help a reviewer reconstruct the work; the regulation does not prescribe this worksheet or its layout.
Do not turn missing details into a completed negative finding. If you have not confirmed the affected device identifier or obtained the original report, record the gap and your next action rather than guessing.
Which seven supplemental fields does the rule specify?
The seven-field list applies to complaints reportable to the Food and Drug Administration (FDA) under Part 803, complaints you determine must be investigated, and complaints you actually investigate regardless of those requirements. Preserve that scope when turning 820.35(a)(1) to (7) into a form.
| Required information for those complaints | Practical record check |
|---|---|
| Name of the device | Can the reviewer distinguish the affected product? |
| Date the complaint was received | Is the receipt date clear, rather than only the later record-creation date? |
| Any unique device identifier (UDI) or universal product code (UPC), and other device identification | Does the record capture the available identifiers without substituting an internal ticket number? |
| Complainant's name, address and phone number | Are the required contact details recorded and any missing information visible? |
| Nature and details of the complaint | Can the reviewer understand the allegation from the record? |
| Any correction or corrective action taken | Are actions traceable to what you actually did? |
| Any reply to the complainant | Can the reviewer retrieve the reply rather than only a closed status? |
These seven entries are not the entire ISO complaint record or the full FDA adverse-event report. They also do not mean that other complaints can be discarded. Keep your broader procedure and applicable obligations in view.
Can you rely on an earlier investigation?
You can rely on a prior investigation for a similar complaint under 820.35(a), but you must retain justification for not performing another investigation. A repeated symptom is a starting point for that assessment, not evidence that the earlier investigation covers the new event.
As a practical review method, identify the prior investigation, compare the device and relevant circumstances, and explain why its findings apply. If you discover a different packaging configuration, new harm information or an unresolved cause, make that difference visible to the person deciding what investigation is needed.
Keep this decision separate from Medical Device Reporting, the US adverse-event reporting framework in Part 803. Section 803.50(b)(3) makes manufacturers responsible for investigating each event and evaluating its cause within that reporting framework. A duplicate-complaint justification does not, by itself, discharge those separate responsibilities.
How should you connect the reporting decision?
Give the reporting assessment its own rationale and evidence. Section 803.17 requires written procedures for timely identification, communication and evaluation, a standardized reporting review, and relevant documentation. Section 803.18(b)(1)(i) includes deliberations about whether a device-related death, serious injury or malfunction was or was not reportable.
Do not make product return or completed root-cause analysis the starting point for reporting review. Section 803.50(a) sets the ordinary manufacturer reporting deadline at no later than 30 calendar days after the day you receive or otherwise become aware of information from any source that reasonably suggests a specified reportable event. Its criteria include certain malfunctions even without an actual death or serious injury.
A separate five-work-day rule applies in the circumstances specified in 803.53, including reportable events necessitating remedial action to prevent an unreasonable risk of substantial public-health harm, or an FDA written request. Do not treat the ordinary deadline as universal or equate every internally urgent complaint with that five-day trigger.
For missing information, 803.50(b) requires reasonably known information, investigation and explanation of incomplete information and the steps taken to obtain it. Your record should make those attempts retrievable without presenting an incomplete assessment as closure.
What could a linked record look like?
Use the following illustrative trace after adapting it to your procedure. All identifiers and circumstances are invented. It shows pending work, not a reportability determination, an accepted regulatory response or a complete complaint file. The seven required fields above still need their own entries where applicable.
| Recommended trace field | Illustrative entry |
|---|---|
| Complaint and source | C-042 links the original distributor email alleging an open package seal |
| Device and evidence gap | Product named in email; affected lot and photographs requested, not yet confirmed |
| Receipt and awareness evidence | Original email timestamp retained; reporting owner asked to evaluate information and applicable awareness rules |
| Prior investigation | INV-018 concerns a previous seal complaint; packaging configuration comparison remains open |
| Investigation decision | No decision to omit a new investigation recorded while that comparison is unresolved |
| Reporting assessment | RA-042 assigned to reporting lead; allegation, potential consequences and missing facts linked; no negative determination inferred |
| Action and correspondence | Request for lot details and photographs linked; any product action recorded separately with its actual scope |
| Next action | Named owner to obtain the requested information and route new facts to the investigation and reporting reviews |
The useful feature is the connection between decisions. Closing the customer reply does not automatically complete the investigation, reporting assessment or any product action. Let each status reflect its own evidence.
Can another person reconstruct the decision?
Choose one completed record and ask a colleague to locate the original allegation, applicable supplemental fields, investigation or documented justification, reporting rationale and correspondence. This retrieval exercise is a practical check, not a prescribed regulatory test. Record what they could not find and repair the missing links before relying on a summary dashboard.
For reportable events, include the submitted reports and FDA electronic acknowledgments required by 803.18(b)(1)(ii) and (iii). That section permits references to other information instead of duplicate copies. Make sure those references remain usable to the people who need them.
Sources and further reading
- 21 CFR 820.35, Control of records sets out supplemental complaint-record content and the similar-complaint investigation provision.
- 21 CFR 803.17 and its linked Part 803 navigation helps you locate reporting procedures, event records and manufacturer reporting provisions.
- 21 CFR 803.50 and 803.53 distinguish ordinary manufacturer reports from specified five-day reports. Check the full applicable framework, including any approved reporting alternatives, for your device and role.
The eCFR describes its text as authoritative but unofficial. These current section pages were checked on 12 November 2026. This guide explains selected supplemental and reporting provisions, not every incorporated ISO requirement.
Fit the record into your quality system
Your eQMS selection should account for how people retrieve evidence and understand unfinished work. The related supplier-qualification guide provides another example of connecting a quality decision to its supporting evidence, although supplier approval and complaint handling are different processes.
