SOP: Regulatory Reporting and Reportability Decisions

This is a ready-to-use SOP for regulatory reporting decisions and filings. A missed or late mandatory report is one of the few quality failures visible to a regulator before you tell them anything, and the clock usually starts on receipt or discovery, before the investigation is finished. Replace every <<FILL: ...>> placeholder with your own specifics and route it through document control. A worked filled specimen follows. Verify each cited regulation against the current source before you rely on it; this is general guidance to adapt, not legal advice.

Document control header

1. Purpose

To ensure that every event which may trigger a mandatory report to FDA is screened at intake, that the reportability decision and its clock are recorded the day the information arrives, that each report is filed within its regulatory clock, and that proof of submission is retained. Scope is US drug and biologics reporting; the same logic carries to combination products and cell and gene therapy products.

2. Scope

Applies to events arising from deviation, complaint, out-of-specification (OOS), and adverse-event intake for <<FILL: products / applications>>. Covers the Field Alert Report (FAR), Biological Product Deviation Report (BPDR), expedited (15-day) adverse-event report, recall notification, drug shortage notification (506C), and the combination-product partner-notification and constituent-part reports. Regional (EU, UK) obligations are handled per <<FILL: SOP-ID for ex-US reporting>>.

3. Responsibilities

4. Definitions

• Day zero: the day the clock starts, which is receipt or discovery of the information, not confirmation or investigation closure.
• Distributed: released for distribution; any quantity having left the firm’s control brings the FAR and BPDR tests into play.
• Serious and unexpected: the two-part test for an expedited safety report (see 5.4).
• Reportability decision: the recorded determination, report or do not report, with rationale, for each candidate report type.

5. Procedure

5.1 Screen every new event on day one (the five questions)

Before the investigation pulls attention away from the clocks, run every new deviation, complaint, or OOS on a distributed product through these five questions and record each answer with its date:

1. FAR? Approved NDA/ANDA drug, distributed, with contamination, a significant change or deterioration, a stability or specification failure, or a mix-up or labeling error? If yes, the FAR clock starts (3 working days from receipt).
2. BPDR? Licensed biologic, distributed, with a deviation from cGMP or an unexpected event that may affect safety, purity, or potency? If yes, the BPDR clock starts (45 calendar days from discovery).
3. Expedited safety? A serious AND unexpected adverse experience with a reasonable possibility of association? If yes, the 15-day clock starts (15 calendar days from first receipt anywhere in the company).
4. Recall? Does the conclusion mean distributed product must be removed or corrected? If yes, convene the recall committee, start a health-hazard evaluation, and notify FDA immediately (in practice within 24 hours for a risk-to-health recall).
5. Drug shortage (506C)? Did it interrupt manufacturing of a covered drug in a way likely to disrupt supply? If yes, run the supply-impact assessment and notify FDA as soon as practicable.

For a combination product, also screen the partner-notification (5-day) and constituent-part reports per 5.7. Record a “not reportable” answer with its rationale; you cannot recover a clock you never noticed had started.

5.2 Field Alert Report (FAR)

Decision owned by the designated Field Alert coordinator (quality unit), with a named backup, recorded the same day. File the initial FAR on Form FDA 3331a to the responsible FDA district office within 3 working days, stating what is known (investigation may be ongoing). File follow-up FAR(s) as findings develop and a final FAR at investigation close. Cross-reference the triggering deviation or OOS. Basis: 21 CFR 314.81(b)(1).

5.3 Biological Product Deviation Report (BPDR)

The reportability assessment against the safety/purity/potency test is a documented step inside deviation closure, not an afterthought, because the 45-day clock runs from discovery. File electronically via eBPDR on Form FDA 3486 to the licensing Center within 45 calendar days of discovery, as a single comprehensive report (update if material new information emerges). Basis: 21 CFR 600.14 (606.171 for blood).

5.4 Expedited (15-day) adverse-event report

Route any intake mentioning patient harm to pharmacovigilance the same day. Assess seriousness (fatal, life-threatening, hospitalization or its prolongation, persistent or significant disability, congenital anomaly, or intervention to prevent permanent impairment) and expectedness (not in current labeling, or more severe or specific than labeled). The expedited test is serious AND unexpected. File the ICSR to FAERS in E2B(R3) format within 15 calendar days of first receipt anywhere in the company. Capture non-expedited events for periodic reporting. Basis: 21 CFR 314.80 (drugs), 600.80 (biologics).

5.5 Recall notification

The recall committee makes the decision, supported by a documented health-hazard evaluation. Notify the FDA district office immediately (21 CFR 7.46 uses “immediately”; treat 24 hours as the working expectation for a risk-to-health recall). The notification covers product and lot(s), reason, health-hazard summary, quantity distributed, distribution pattern, and proposed strategy (depth, effectiveness-check level, public warning if any). Issue consignee communications, conduct effectiveness checks, file status reports, and request termination when product is accounted for. Basis: 21 CFR Part 7.

5.6 Drug shortage notification (506C)

Quality flags any event that interrupts manufacturing of a covered drug. Supply chain documents the supply-impact assessment (including a recorded basis for any “not likely to disrupt supply” decision); regulatory affairs files. Notify at least six months ahead of a planned permanent discontinuance, or as soon as practicable for an unforeseen interruption likely to disrupt supply. Basis: Section 506C of the FD&C Act (21 USC 356c).

5.7 Combination product additional reports

Where the product is a combination product, also apply 21 CFR Part 4, Subpart B: keep the reporting matching your application type and additionally submit the constituent-part reports (device 5-day / malfunction / correction-and-removal; drug FAR and 15-day; biologic BPDR and 15-day). Note the 15-day report becomes a 30-day report where the combination product was authorized under a device application. Where constituent parts are held by different applicants, provide the partner notification within 5 calendar days of receipt (21 CFR 4.103), and keep the 4.103(b) records.

5.8 Log, file, and retain

Record every candidate report in the regulatory reporting log (Records, section 8) with its trigger, day-zero date, clock, due date, filing date, and submission proof. Do not close the triggering deviation, complaint, or OOS until the reportability decision and any resulting filing are recorded.

6. Acceptance criteria

• The five-question screen is completed and dated for every distributed-product event on day one.
• Each reportability decision (report or not, with rationale) is recorded the day the information arrives.
• Each filed report is transmitted within its regulatory clock, with proof retained.
• The reporting log shows nothing open past due.
• Any reportable event from the last two years can be reconstructed from records alone: day zero, decision, clock, filing, and proof.

7. References

21 CFR 314.81(b)(1) (Field Alert Reports); 21 CFR 600.14 and 606.171 (BPDR). 21 CFR 314.80 and 600.80 (postmarketing adverse-experience reporting). 21 CFR Part 7 (recalls); 21 CFR 7.46 (firm-initiated recall notification). Section 506C of the FD&C Act, 21 USC 356c (drug shortage notification). 21 CFR Part 4, Subpart B (postmarketing safety reporting for combination products); 21 CFR 4.103 (5-day partner notification).

Confirm the current text and clause numbers of each reference before issue.

8. Records generated

Reportability decision record (per event); regulatory reporting log (per the paired log template); filed reports and their submission proof; health-hazard evaluations; supply-impact assessments.

9. Revision history

10. Approvals

Filled specimen (excerpt)

Illustrative day-one screen for a confirmed distributed sterility failure on a licensed cell therapy lot.

One sterility result set three clocks running (BPDR, recall notice, and a conditional safety trigger), each independent. Treating it as “just an OOS” would have put the 24-hour recall notice and the 45-day BPDR at risk before anyone realized a clock existed.

Common inspection findings this SOP prevents

• Waiting for the investigation to close before filing, so the FAR lands late.
• Starting the BPDR clock at deviation closure instead of discovery.
• Starting the 15-day clock at safety-database entry instead of first receipt anywhere in the company.
• A recall decision made but FDA notification treated as a follow-up task.
• A manufacturing interruption of a covered drug that no one screens for 506C.
• No proof of submission retained, so timeliness cannot be shown.

How to adapt this SOP

1. Set your document number, owner, and effective date; name the Field Alert coordinator and backup.
2. Put the five-question screen on the front of your deviation, complaint, and OOS intake forms.
3. Point the ex-US and periodic-reporting cross-references to your real procedures.
4. Pair this SOP with the regulatory reporting log and the reportability decision matrix.
5. Confirm every regulation in section 7 against the current published version before issue.