Product Quality Complaint Intake and Triage Form

This is a ready-to-use product quality complaint intake and triage form. It is the working record a complaint lives on from the moment it arrives until it is closed with a response back to the person who raised it. Replace every <<FILL: ...>> placeholder, set your own document number, version, and effective date, and route the form through your own document control, review, and approval before use. A worked filled specimen follows so you can see how a completed record reads. Verify each cited regulation against the current published source before you rely on it. Using this template does not by itself create compliance; it only structures the work your quality system and procedures still have to do.

A complaint has two clocks that start the instant it is received, and they run independently. One clock is the safety clock: if the complaint describes any harm to a person, the case has to reach pharmacovigilance fast, on the safety system’s own timelines, regardless of what the quality investigation later finds. The other clock is the reportability clock: a quality defect can oblige you to file a Field Alert Report, a Biological Product Deviation Report, or to make a recall decision, each with its own deadline. The single most common way these obligations are missed is a slow or incomplete intake. This form forces the screening questions to the front so neither clock is started late.

Document control header

Section A: Complaint identification

Section B: Reporter and complainant

Section C: Product identification

Section D: Complaint description and category

Record the complaint in the complainant’s own terms first, then the category. Do not record a conclusion about cause here.

Complainant’s account: <<FILL: factual description in their words>>

Section E: Adverse event and pharmacovigilance screen

This screen runs at intake, before triage. If any answer points to harm or possible harm to a person, the case is a potential adverse event and must reach pharmacovigilance on the safety system’s own timeline, independent of this quality investigation. A single intake can be both a quality complaint and an adverse event; treat it as both.

The handler does not assess seriousness or expectedness here. That is pharmacovigilance’s job once the case is handed over. The handler’s only duty is to recognize the possibility and route it without delay.

Section F: Criticality triage

Triage assigns the complaint a criticality that sets the investigation depth and timeline. Use the matrix below; when the safety dimension and the quality dimension disagree, take the higher of the two.

Section G: Reportability screen

A quality complaint can trigger a regulatory clock on its own. Run each screen below. Reportability decisions are made by the responsible function (regulatory affairs and QA), not by the intake handler, but the handler flags candidates so the decision is made in time.

The reportability clock starts when the company has the information, not when the investigation concludes. A pending investigation does not pause the deadline. If a report may be required, file or escalate within the deadline and update afterward.

Section H: Sample availability and handling

If no sample can be obtained, record that and explain how the investigation will proceed without it (reserve sample, batch record review, trend review).

Section I: Investigation assignment

Section J: Closure and response to complainant

A complaint closes only when the investigation is complete, the reportability and pharmacovigilance routes are settled, any CAPA is opened, and a response has gone back to the complainant where one was due.

Triage decision logic

Read this from the top. The first rule that fires sets the path; you still complete every section.

1. If Section E shows any harm or possible harm to a person, route to pharmacovigilance immediately on the safety timeline, and continue the quality complaint in parallel. A safety route never waits on the quality investigation.
2. If the defect could plausibly cause harm even with no injury reported yet (for example suspected contamination, wrong product, mislabeling, suspected counterfeit), rate it Critical and run the reportability screen in Section G the same day.
3. Set criticality by the matrix in Section F. When safety severity and quality severity disagree, take the higher.
4. Run all three reportability questions in Section G regardless of criticality. A Minor cosmetic complaint will usually clear them; a suspected subpotency or contamination will not. Refer any candidate to regulatory affairs and QA before the deadline, not after the investigation.
5. Secure a sample and confirm the reserve sample location before evidence is lost.
6. Assign the investigation at the depth the criticality demands and set the target date from the procedure.
7. Close only when investigation, pharmacovigilance, reportability, CAPA, and the complainant response are all settled.

Worked specimen

The following is a completed example using fictional names. It illustrates a complaint that is both a quality complaint and a potential adverse event, and that also trips the reportability screen.

Document control header

Section A: Complaint identification

Section B: Reporter and complainant

Section C: Product identification

Section D: Complaint description and category

Complainant’s account: Pharmacist found visible floating particles in one vial during preparation. The dose was not administered. Patient reported feeling unwell earlier that day after a dose from a different vial of the same lot.

Section E: Adverse event and pharmacovigilance screen

Section F: Criticality triage

Section G: Reportability screen

Section H: Sample availability and handling

Section I: Investigation assignment

Section J: Closure and response to complainant

In this example the intake handler did three things right within the first hour: spotted the possible adverse event and routed it to pharmacovigilance on the safety clock, rated the complaint Critical because contamination of an injectable can cause harm whether or not anyone was hurt yet, and flagged both the Field Alert Report and the Biological Product Deviation Report so regulatory affairs could start those clocks. The quality investigation, the recall decision, and the final complainant response all run on after intake, but none of the deadlines were started late. That is the point of putting the screens before the investigation.

Common inspection findings this form prevents

• The complaint is logged days after it arrived, so the FAR or BPDR clock is already blown at intake.
• An adverse event sits inside a quality complaint with no evidence it ever reached pharmacovigilance.
• Criticality is assigned with no facts behind it, and a contamination complaint is treated as cosmetic.
• The reportability screen was never run, or was run only after the investigation closed.
• No attempt was made to obtain the sample or to identify the reserve sample, so the defect cannot be examined.
• The complaint is closed while the investigation, the report, or the complainant response is still open.
• Linked complaints on the same lot are not connected, so a trend is missed.

How to adapt this form

1. Set your document number, governing SOP, and effective date in the header.
2. Align the criticality timelines in Section F with your complaint-handling procedure.
3. If your pharmacovigilance handoff uses a defined intake form or mailbox, name it in Section E rather than a free-text route.
4. Localize the reportability screen in Section G to every market you distribute in, keeping the US FAR and BPDR rows and adding the equivalent national defect-reporting and recall routes you are subject to.
5. If complaints, investigations, and CAPA live in separate systems, keep Sections I and J as pointers to those records.
6. Confirm every regulation in the references against the current published version before issue.

Regulations this supports

• 21 CFR 211 Subpart J, written complaint records and review of complaints (US cGMP for finished pharmaceuticals)
• 21 CFR 314.81, Field Alert Report, within 3 working days of the information
• 21 CFR 600.14, Biological Product Deviation Report, within 45 calendar days of acquiring the information
• 21 CFR Part 7, recalls and corrections and removals
• 21 CFR Part 4, current good manufacturing practice for combination products
• EU GMP Chapter 8, complaints, quality defects, and product recalls
• ICH Q10, pharmaceutical quality system, including complaint and feedback handling
• ICH E2D, post-approval safety data management, for the adverse event handling principles
• FDA Data Integrity guidance (2018) and MHRA GxP Data Integrity guidance (2018), for the contemporaneous and attributable recording of intake