What is the difference between a Field Alert Report (FAR) and a Biological Product Deviation Report (BPDR), and which one do you file?

1Which report do you file?

The application that approved the product decides, not the kind of problem.¹² Both concern distributed product only.³²

The third row is the one teams miss. Insulins, somatropin, hyaluronidase and other biological products approved under NDAs were deemed to be BLAs on 23 March 2020.¹² FDA says their holders “will be required, once the product is deemed to be licensed under a BLA, to report on events with the potential to affect the safety, purity, or potency of a distributed product by submission of BPDRs to CDER.” A follow-up to a FAR sent before that date is also filed as a BPDR.⁶

For a combination product applicant, 4.102(c) adds FARs for a drug constituent part and BPDRs for a biological one whatever application authorised the product, so a drug-device product authorised as a device still owes FARs.¹⁰ CDER takes BPDRs for the therapeutic biologics it regulates; CBER takes those for vaccines, allergenics, plasma derivatives, in vitro diagnostics, HCT/Ps and gene therapy products.⁵¹³ CDER now takes Form FDA 3486 by email to CDER-BPDR@fda.hhs.gov, although 600.14 still says it accepts no electronic filings.²⁵

2How the two reports differ.

A FAR is due even when the root cause is found and fixed inside the 3 days, and “A recall notification is not a substitute for a required FAR submission.”³ For a BPDR, FDA’s example is blunt: if you distributed product not tested for all specifications, report it “even if you subsequently tested the product and found it to be acceptable.”¹¹

3When does the clock start?

For a FAR, “We consider working days to be any day from Monday through Friday, excluding U.S. Federal holidays.” The clock runs from where the information first appears: “the day a contract lab learns of a sterility failure is day 0”.³

For a BPDR, the 45 days run from when you, your agent or anyone performing a step under your control acquires information reasonably suggesting a reportable event.² “You acquire such information when any employee of your facility, not just those involved in quality assurance or quality control, learns about the event.”¹¹

3.1Example: the clock.

3.2Example: the initial FAR, box by box.

The same event on Form FDA 3331a. FDA asks that an initial FAR give at least the application number, the generic and brand names, the quality problem and a contact, and the rest as far as it is known.³ Follow-up and final FARs are recommended, not required.³

3.3Example: a BPDR on Form 3486.

The second case below, for a licensed antibody: the contract filler held formulated bulk 6 days past its validated hold time before filling two lots, and found this on 5 October 2026, after both lots had shipped.

The code reads from system to detail. Its first pair is IM incoming material, PC process controls, TE testing, LA labelling, PS product specifications or QC quality control and distribution. Question marks such as LA-??-?? are allowed, though a code is strongly encouraged.⁵ FDA updated the list on 1 October 2026 for fiscal year 2027 and made no changes to the non-blood codes.¹⁷

FDA’s CDER BPDR programme lists the most common errors on Form FDA 3486:¹⁶

• Several applications or products on one form.
• The wrong center or office.
• Reporting-firm details that don’t match FDA’s data.
• The wrong problem firm.
• An inappropriate defect code.
• Not referring to the general instructions.

The same slides expect a FAR or BPDR to carry a “complete and accurate assessment of the detailed root cause investigations”, including whether the failure trends across batches and the risk to patients, and a CAPA plan with the measures that would detect a recurrence quickly.¹⁶

4Four cases, decided.

5FAR and BPDR intake checklist.

Run it the day information arrives; each line cites its rule.

1. The application: NDA, ANDA, BLA, a deemed BLA, or none. File one FAR per application; CDER asks for one BPDR per BLA product.³⁵⁶
2. Distribution: has any unit left your control?³¹⁴
3. Day 0: when anyone, a contractor included, first had the information.³¹¹
4. Due date: Day 3 in working days, or day 45 in calendar days.³¹⁵²
5. The trigger in words: the 314.81(b)(1) category or the 600.14(b) event.¹²
6. The fields in the two examples, with the site where the problem occurred, an API or component supplier included.¹⁶³⁵
7. If you decide not to report, the dated determination with its rationale and the factors considered. For a FAR it is made within 3 working days, and it covers a complaint or change judged not significant as well as an invalidated stability OOS or a cleared component lot.³ For a biologic, it is the record that the event could not have affected safety, purity or potency, investigated under 211.192 and 211.198.¹¹
8. Linked duties: recall assessment, adverse event reports, the complaint record.³¹¹

6What inspectors check.

FDA’s field alert compliance programme, CP 7356.021, was last revised in September 2015 and still assigns the work to districts. The district requests a firm’s FAR history from CDER two weeks before an inspection and, for OOS results on marketed product, asks whether FARs were filed. It states:

“Failure of a firm to submit an NDA/ANDA FAR for distributed violative product is reportable as an FDA-483 observation.”¹⁸

A FAR filed only after inspectors found the problem is called out too. Amneal filed one on 26 March 2025, a week after FDA’s inspection of its Gujarat site ended, for ropivacaine infusion bags with particulate contamination. The warning letter said:

“However, these actions were initiated only after FDA identified these problems during the current inspection.”

Amneal Pharmaceuticals, LLC, warning letter 320-25-104, 27 August 2025.¹⁹

For CBER-regulated biologics, investigators “Determine if the manufacturer filed all reportable biological product deviations”, and FDA cites a previously reported deviation only if the investigation or corrective action was inadequate.²⁰ For CDER-regulated biologics, the 2026 prelicense and preapproval programme has the team verify the procedures for complaints, adverse event reports, BPDRs, recalls and returns, review those records, and pass any failure to submit BPDRs to CDER’s Office of Quality Surveillance and Office of Compliance.²¹ CBER’s summary for fiscal year 2024 counts 16,993 deviation reports, 503 of them from licensed non-blood manufacturers.¹³

7Outside the US.

In the EU and UK, a quality defect in a biological medicine follows the same route as any other medicinal product’s. Under EU GMP, defects that may lead to a recall or an abnormal restriction in supply are reported to the authorities concerned.²² EMA expects notice “typically” within one working day of confirming that reporting is required, to the site’s authority and each EEA market, plus EMA for a centrally authorised product, and before market action unless it cannot wait. A technical agreement should say who reports; normally the marketing authorisation holder and the site of final EU batch certification lead.²³

EMA also encourages notice of “confirmed serious GMP issues with the potential to lead to a suspected product defect requiring market action (e.g. media fill failure, serious equipment failure, etc.)” before the investigation ends. FDA’s FAR Q&A treats a media fill failure as a trigger for investigation, with a FAR due within 3 working days if that investigation finds information about a distributed batch that meets 314.81(b)(1).²³³ National authorities may add their own expectations, which apply too.²³ For ATMPs, EudraLex Volume 4 Part IV asks for timely notice of a confirmed quality defect that may lead to a recall or abnormal restriction in supply, and says unplanned deviations handled under its section 11.4 should not be notified.²⁴

In the UK, a manufacturer’s licence holder must inform MHRA “immediately” of a defect that could result in a recall, on the online Defect Reporting Form or by phone when urgent or out of hours. Notifying once a recall “has already commenced will breach the regulations.”²⁵

8How it runs in Seal.

In Seal, a complaint keeps the original report as received, with its time of receipt, and records reportability as the criteria applied, the facts known and missing, and the reviewer’s rationale. A deviation links the batch, its process records and samples, so the question of whether affected product was distributed starts from the record. When a defect leads to market action, a recall derives its scope from lot genealogy and tracks each consignee.

For cell and gene therapy, chain of identity is part of every material record: each scan is checked against the batch, and a mismatch stops the step. Neil, Seal’s AI agent, can prepare the facts known and missing for a reportability review; any reporting decision stays with the authorised reviewers.