Matrix: Complaint Reportability Decision and Regulatory Clocks

This is a ready-to-use decision matrix for the reportability step of complaint handling: given what a complaint says, which reporting obligations come into play, on what clock, and what has to be written down about the decision. Replace every <<FILL: ...>> placeholder, set your own document numbers, and route it through your normal document control before use.

Read this first. This document is educational. Reporting obligations depend on what your product is, which applications or licences it is marketed under, which markets it was distributed into, and the commitments you have made to your health authorities. No matrix can determine your obligations for you. Every branch below has to be confirmed against the current text of the regulation and agreed with your own regulatory affairs and pharmacovigilance functions before you rely on it. Where a decision is genuinely borderline and a deadline is close, escalate and report rather than deliberate: a report you later close out as not required is recoverable, a missed deadline is not.

This matrix is written for drug products, licensed biological products, and cell and gene therapy products, with a combination product branch for the case where a device constituent part is implicated. It is not a device vigilance procedure. If your primary product is a device, use a device-specific procedure and treat the Part 803 rows here only as a pointer.

Document control header

1. How to use this matrix

1. Run it on every complaint, including ones you expect to clear every branch. The record of a negative assessment is what shows the assessment happened.
2. Run it on the facts as received, at the point of receipt, not on the facts as later confirmed. The clocks run from awareness.
3. Run every branch, not just the first one that fires. One complaint can trigger a safety report, a defect report, and a field action at the same time, on three different clocks, owned by three different functions.
4. Record the rationale for each branch using the block in section 8, including for branches assessed as not applicable.
5. Re-run the matrix when the investigation concludes. The conclusion can move a branch from not applicable to applicable, or the reverse. Both assessments are retained.

2. Day zero: when the clock starts

Almost every missed deadline in complaint handling is a day-zero error rather than a decision error. The rules below are the ones that cause the trouble.

Record the date of awareness, the person who became aware, and how, on the face of the complaint file. Where the date of awareness and the date logged differ, record both and explain the gap.

3. The clocks at a glance

Confirm each against the current published source before you rely on it.

4. Branch A: post-marketing adverse experience reporting

Trigger for the branch: the complaint describes, or reasonably suggests, an untoward medical occurrence in a person who received the product. Route it to pharmacovigilance the same working day. The complaint function screens; pharmacovigilance decides seriousness, expectedness, and causality, and owns the report.

4.1 Seriousness criteria

The screening criteria used at complaint intake are those established in ICH E2A, Clinical Safety Data Management: Definitions and Standards for Expedited Reporting, and reflected in the US regulations at 21 CFR 314.80(a) and 21 CFR 600.80(a). Described in general terms rather than reproduced from the copyrighted guideline, an event is treated as serious when the outcome is death, when the event was life-threatening, when it caused hospital admission or lengthened an existing admission, when it left the person with a lasting or significant disability or incapacity, when it produced a congenital abnormality or birth defect, or when it is another medically important event that needed intervention to stop one of the preceding outcomes from happening.

Two points that complaint handlers get wrong:

• Serious is not the same as severe. A severe headache that resolves is not serious. A brief hospital admission for observation is.
• The complaint handler does not make this call. The screen records the facts; the medically qualified assessor in pharmacovigilance decides. The screening question exists to make sure the case reaches that assessor on time, not to pre-empt them.

Case exchange with health authorities and partners uses the individual case safety report format specified in ICH E2B(R3), the ICH guideline covering the data elements and message specification for the electronic transmission of individual case safety reports. Post-approval case handling definitions sit in ICH E2D(R1), Post-Approval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports. Obtain these guidelines from the official ICH source; do not reproduce their text inside your procedures.

See pharmacovigilance and safety data integrity for the mechanics on the safety side.

5. Branch B: Field Alert Report, 21 CFR 314.81(b)(1)

Applies to: applicants holding an approved application for a drug product under 21 CFR Part 314. It is a drug application obligation. A licensed biological product marketed under a BLA is not covered by this branch on its own account; confirm the position for your specific product with regulatory affairs, and see Branch E where a combination product is involved.

Clock: within 3 working days of receipt of the information. The regulation identifies two categories.

21 CFR 314.81(b)(1)(i): “Information concerning any incident that causes the drug product or its labeling to be mistaken for, or applied to, another article.”

21 CFR 314.81(b)(1)(ii): “Information concerning any bacteriological contamination, or any significant chemical, physical, or other change or deterioration in the distributed drug product, or any failure of one or more distributed batches of the drug product to meet the specification established for it in the application.”

Practical notes:

• The three working days are short. Treat a Field Alert Report as a candidate at intake and refer it to regulatory affairs the same day the complaint arrives, not after triage has finished.
• The trigger is information, not proof. Waiting for laboratory confirmation before filing is a common way to miss this clock.
• A Field Alert Report can be followed up and can be closed out. Filing and later resolving it is a normal outcome.

6. Branch C: Biological Product Deviation Report, 21 CFR 600.14

Applies to: the manufacturer who holds the biological product licence and who had control over the product when the deviation occurred. The regulation carries exceptions, including for certain in vitro diagnostic products and for blood and blood component manufacturers, who report under their own provision. Confirm the applicability to your product and your role in the supply chain with regulatory affairs.

Clock: as soon as possible, and not to exceed 45 calendar days from the date you, your agent, or another person performing a manufacturing, holding, or distribution step under your control acquires information reasonably suggesting that a reportable event has occurred.

Scope: an event that either departs from current good manufacturing practice, applicable regulations, applicable standards, or established specifications, or is an unexpected or unforeseeable event, and that may affect the safety, purity, or potency of a distributed licensed biological product.

Practical notes:

• Forty-five calendar days sounds generous and is not. The clock runs from information reasonably suggesting a reportable event, which is normally the complaint receipt date, not the investigation conclusion date. Investigations on biologics routinely run longer than 45 days, so plan to report inside the clock on what you know and follow up afterwards.
• The Field Alert Report and the Biological Product Deviation Report are separate obligations with different clocks and different scopes. Assess both wherever both could apply, and record both conclusions.

7. Branches D, E, and F

Branch D: EU and other markets

Add one row per market. The most common gap in a reportability matrix is a market that was added to the distribution footprint but never added to the matrix. Reconcile this table against the distribution records at every periodic review.

Branch E: combination products

Where the product is a combination product, the drug or biologic obligations above continue to apply, and constituent-part obligations may apply on top. 21 CFR Part 4 Subpart B sets out post-marketing safety reporting for combination products: which reports a combination product applicant must submit for its product and its constituent parts, what information must be shared with other constituent-part applicants, how and where reports are submitted, and the recordkeeping requirements.

Keep this branch in proportion. For most drug and biologic complaint systems it fires rarely, and treating every complaint as a potential device report buries the branches that fire often. But when it does fire, the 5 work day clock is the shortest one on this page. See combination products and cGMP under Part 4.

Branch F: recall and field action

Recall decisions and authority notification run under 21 CFR Part 7 in the US and the equivalent national route in each other market. Confirm the current notification expectation for each market with regulatory affairs. Execution runs under the recall and field action plan. See also recall management and field actions.

8. Rationale documentation block

Complete one of these per complaint. The value is in the negative rows: a branch marked “not applicable” with a reason shows the assessment was performed, and a branch left blank shows nothing at all.

Write the rationale in facts, not conclusions. “Not reportable, cosmetic” is not a rationale. “Scuff to the outer carton only; blister, tablet, and all label content intact and legible; no specification in question; product remains within its release specification” is a rationale, and it is one a reviewer can test two years later.

9. Worked examples: one complaint, different branches

The same reported experience routes very differently depending on the product, the application type, and where the lot went. In every variant below, the reported facts are identical: a hospital pharmacist reports visible haze in a reconstituted parenteral product and a patient who received an earlier unit of the same lot developed fever and chills within the hour. The date of awareness is 6 July 2026 in all variants.

Variant 1: licensed biological product under a BLA, distributed in the US only

Variant 2: small molecule injectable under an approved NDA, distributed in the US only

The difference between Variants 1 and 2 is not the complaint. It is the application type. The same haze that gives a biologic 45 days gives a drug product 3 working days, and a company that assumes its biologic reflexes apply across its portfolio will miss that deadline on its first small molecule complaint.

Variant 3: licensed biological product under a BLA, lot distributed in the US and Germany

Variant 4: the same biologic presented in an on-body injector, US only, where the pharmacist also reports that the injector stalled mid-delivery

Variant 5: the same complaint, but the vial was never dispensed and no patient received any unit of the lot

Variant 5 is the one that catches people. The absence of an adverse event closes exactly one branch and leaves every other branch open. Complaint systems that route on “was anyone hurt” as the single gate miss the defect reports entirely.

10. References

21 CFR 211.198, Complaint files, including the requirement to determine whether a complaint represents a serious and unexpected adverse drug experience requiring a report to FDA. 21 CFR 314.80, Postmarketing reporting of adverse drug experiences, 15 calendar day Alert reports and 15 calendar day follow-up reports. 21 CFR 600.80, Postmarketing reporting of adverse experiences for licensed biological products. 21 CFR 310.305, Records and reports concerning adverse drug experiences on marketed prescription drugs for human use without approved new drug applications. 21 CFR 314.81(b)(1), NDA Field Alert Report, within 3 working days. 21 CFR 600.14, Reporting of biological product deviations by licensed manufacturers, not to exceed 45 calendar days. 21 CFR Part 4 Subpart B, Postmarketing safety reporting for combination products, sections 4.100 to 4.105. 21 CFR 803.50 and 21 CFR 803.53, manufacturer reporting, 30 calendar days and 5 work days respectively, where device reporting applies. 21 CFR Part 7, Enforcement policy, for recalls. EU GMP Chapter 8, Complaints, Quality Defects and Product Recalls. EU GVP modules, in particular Module VI, Collection, management and submission of reports of suspected adverse reactions to medicinal products, for the 15 calendar day serious and 90 calendar day non-serious EudraVigilance timelines, and for the scope difference between them: the serious obligation covers cases occurring in the EU and in third countries, the non-serious obligation covers cases occurring in the EU. ICH E2A, Clinical Safety Data Management: Definitions and Standards for Expedited Reporting, for the seriousness criteria. ICH E2B(R3), for the individual case safety report data elements and message specification used in electronic case exchange. ICH E2D(R1), Post-Approval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports. ICH Q9(R1), Quality Risk Management, and ICH Q10, Pharmaceutical Quality System.

Confirm the current version and text of every reference before issue. ICH guidelines are copyrighted; obtain them from the official ICH source and describe them in your own words in your procedures rather than reproducing their text.

11. Filled specimen

Rationale documentation block, completed for Variant 4 above.

The specimen is worth reading for the two “No” rows rather than the “Yes” rows. Branch B is negative, but it names the regulation, states the product’s application type, and records that regulatory affairs confirmed the position on a specific date. Branch D is negative, but it says which distribution record was checked. Those two rows cost about four minutes to write and they are the difference between a defensible file and a file where an inspector cannot tell whether anyone ever considered a Field Alert Report at all.

Common inspection findings this matrix prevents

• Reportability is not documented at all, so a reviewer cannot tell whether the decision was made, by whom, or on what basis.
• A “not reportable” conclusion carries a category code but no facts and no named decision maker.
• Reportability was assessed only once, at closure, so a 3 working day Field Alert Report clock had already run out by the time anyone looked.
• The company waited for laboratory confirmation before assessing reportability, treating the investigation as a precondition for a decision the regulation ties to receipt of information.
• Only the branch that fired was recorded, so there is no evidence the other obligations were considered.
• Day zero was recorded as the date the complaint reached quality assurance rather than the date any employee first became aware.
• A biologic reflex was applied to a drug product, or the reverse, so the wrong clock was counted.
• A lot was distributed into a market that is not represented in the matrix, so a national obligation was never considered.
• A combination product complaint implicating the device constituent was handled entirely under the drug procedure, with no assessment of the constituent-part obligations.
• The absence of an adverse event was treated as closing the whole assessment, so the defect reporting branches were never run.
• Reportability was not reassessed when the investigation changed the facts.

How to adapt this matrix

1. Set the document number, owner, and reviewers in the header, and list every market you distribute in.
2. Have regulatory affairs and pharmacovigilance jointly own this document. A reportability matrix maintained by quality assurance alone drifts out of date the moment a regulation or an authorisation changes.
3. Add one row per market to Branch D, with the local defect reporting route, the local safety reporting obligation, and the clock for each. Reconcile that list against actual distribution records at every periodic review, not against the product’s intended market footprint.
4. Map your own product portfolio against Branches B and C explicitly, product by product, application type by application type. Most reportability errors trace to a wrong assumption about which regulation a given product sits under.
5. If you do not market combination products, mark Branch E as not applicable in your issued version rather than deleting it, and note the trigger that would bring it back into scope.
6. Wire the rationale block in section 8 into your complaint record or electronic system as mandatory fields, including the “not applicable” rationale fields. A field that can be left blank will be left blank.
7. Set a review trigger on this document for any change to the regulations, any new market, any new product type, and any change in your role in the supply chain, in addition to the periodic review date.
8. Confirm every clock in section 3 against the current published regulation before issue, and record the date of that confirmation in the revision history.