What do complaint files need under the QMSR?
By Savi C., Co-Founder · Published Nov 16, 2026
Three layers of requirements
The old complaint files section of Part 820 is gone, but complaint handling did not get lighter. The first layer is ISO 13485 clause 8.2.2, which requires documented procedures for timely complaint handling covering at least receiving and recording information, evaluating whether feedback is a complaint, investigating complaints, determining the need to report to regulatory authorities, handling complaint-related product, and determining the need for corrections or corrective actions. If a complaint is not investigated, the justification must be documented, and complaint handling records must be kept.
The second layer is 21 CFR 820.35(a), which requires records of the review, evaluation and investigation of any complaint involving the possible failure of a device, labeling or packaging to meet its specifications, and lists the information those records must contain. Where a similar complaint has already been investigated, a new investigation is not necessary, but the justification for not performing one must be recorded.
The third layer is Part 803. Section 820.10(b)(3) ties ISO 13485 clause 8.2.3, reporting to regulatory authorities, to the Part 803 reporting criteria, so every complaint needs an MDR decision.
What 820.35(a) requires in the complaint record
For complaints reportable under Part 803, complaints the manufacturer determines must be investigated, and complaints it investigated regardless:
Item
820.35(a)(1)
Requirement
The name of the device
Item
820.35(a)(2)
Requirement
The date the complaint was received
Item
820.35(a)(3)
Requirement
Any UDI or UPC, and any other device identification
Item
820.35(a)(4)
Requirement
The name, address and phone number of the complainant
Item
820.35(a)(5)
Requirement
The nature and details of the complaint
Item
820.35(a)(6)
Requirement
Any correction or corrective action taken
Item
820.35(a)(7)
Requirement
Any reply to the complainant
Complaint file review checklist
Intake and evaluation
- Date the complaint was received recorded, as 820.35(a)(2) requires
- Decision recorded on whether the feedback is a complaint, with the reason
- All seven 820.35(a) items present for every reportable or investigated complaint
- Device identification includes the UDI or UPC where one was available
MDR decision
- A documented reportability decision against the Part 803 criteria: death, serious injury, or a malfunction likely to cause or contribute to one if it recurred
- Where reportable, the report submitted within 30 calendar days of becoming aware under 803.50, or 5 work days where 803.53 applies
- The MDR event file holds the deliberations and decision, copies of reports and FDA acknowledgments, as 803.18 requires
Investigation and closure
- Investigation performed, or a written justification for not performing one, including reference to an earlier investigation of a similar complaint
- Returned product handled and its evaluation recorded
- Need for correction or corrective action assessed, and any action recorded and linked
- Any reply to the complainant recorded
Retention and access
Complaint records follow ISO 13485 clause 4.2.5 for retention. MDR event files have their own rule: under 803.18 a manufacturer must keep them for 2 years from the date of the event or the expected life of the device, whichever is greater, and must let FDA access, copy and verify them. Keeping the complaint record and the MDR event file cross-referenced avoids the common inspection finding where an MDR decision exists but cannot be traced to the complaint that triggered it.
How Litewave fits
Complaint files are records reviewed against a fixed list of required content. Litewave reads paper or electronic records, checks every entry against your specifications and procedures, and shows QA only the exceptions, each linked to the page it came from, such as a missing UDI or an investigated complaint with no recorded MDR decision. Litewave proposes, qualified people approve, and the reportability decision stays with your team. Our published results come from pharmaceutical manufacturing, and device figures will be published only when a device customer has agreed to them.
Questions we get asked
Does every complaint have to be investigated?
No. ISO 13485 clause 8.2.2 allows a complaint not to be investigated if the justification is documented, and 820.35(a) allows relying on an earlier investigation of a similar complaint with a recorded justification. Every complaint still needs an MDR reportability decision.
Do the 820.35(a) items apply to every complaint?
They apply to complaints that must be reported under Part 803, complaints the manufacturer determines must be investigated, and complaints it investigated regardless. In practice many manufacturers capture them for every complaint at intake, because the category is often not known until later.
Is the MDR event file the same as the complaint file?
Not necessarily. 803.18 requires MDR event files that hold the reportability deliberations, reports submitted and FDA acknowledgments. They can reference the complaint record rather than duplicate it, but they must be clearly identified and accessible.
Sources
- 21 CFR 820.35, Control of records (eCFR)
- 21 CFR 820.10, Requirements for a quality management system (eCFR)
- 21 CFR 803.17, Written MDR procedures (eCFR)
- 21 CFR 803.18, MDR files (eCFR)
- 21 CFR 803.50, Manufacturer reporting requirements (eCFR)
- 21 CFR 803.52, Individual adverse event report contents (eCFR)
- 21 CFR 803.53, Five-day reports (eCFR)
- ISO 13485:2016, Medical devices, Quality management systems
