On this page
How do you prepare an FDA field alert report without delaying the reporting clock?
Assess the distributed-product event promptly, preserve the initial discovery date including relevant contractor discovery, and identify the approved NDA or ANDA and affected batches. Submit the required initial FAR within three working days using known facts and clearly identified uncertainties. Complete the investigation separately, retain delivery evidence and provide recommended follow-up information as significant findings become available.
Before you begin
Approved NDA/ANDA products under 314.81(b)(1); not a substitute for biologic product deviation or adverse-event reporting.
What you will prepare: An initial FAR or follow-up with verified product/event identity and an accountable submission handoff.
Assess the event immediately and preserve receipt time
Identify the approved application, distributed product, implicated batch/label, initial discovery date and applicant handoff. The regulation specifies reporting within three working days for the listed events, including certain labeling mix-ups, contamination, significant deterioration or change, and failure of distributed batches to meet application specifications. FDA’s July 2021 guidance, III.3.a, explains that the day a contract lab learns of a sterility failure is day 0. Do not restart the clock at a later applicant handoff. The guidance counts Monday through Friday excluding U.S. Federal holidays; do not replace working days with an unqualified calendar-day rule.
Have quality/regulatory personnel assess reportability as soon as the information arrives. A full root-cause investigation may not be complete within the reporting window. Do not delay an otherwise reportable initial FAR while waiting for final laboratory or recall conclusions.
Write the initial report around established facts
Use the current Form 3331a and instructions from FDA. Reconcile applicant/application, product name, strength, dosage form, manufacturing site, lot/batch, expiry, distribution and event chronology. Explain what was observed, the basis for the report, known affected scope, immediate actions and the investigation status. Clearly label unknowns and preliminary interpretations.
Retain source records for dates and identifiers. A product complaint description and a laboratory finding can refer to different lots; reconcile them rather than merging them into one event. Assign an owner for follow-up and changes in the assessed scope.
Submit through the FAR route and maintain the follow-up record
Follow FDA's current FAR delivery instructions and verify the submission handoff. The 1.12.16 heading does not mean an ordinary eCTD copy alone replaces the FAR reporting channel. Store the receipt, report version and references to follow-up reports in the controlled application record.
Update the report as the investigation establishes cause, affected batches, corrective action and final disposition. Assess recall, adverse-event and other reporting duties separately. A BLA quality problem requires assessment of the applicable biologic deviation/reporting framework; do not apply the NDA/ANDA FAR template indiscriminately.
Worked review: investigation uncertainty is not permission to wait
Fictional editorial exercise: a distributed batch has an out-of-specification finding. The laboratory is investigating possible analytical error, and the draft FAR is held until the next weekly quality meeting.
Escalate the reporting decision now, preserve when the information was received and prepare the known facts with the investigation marked open. If the batch was never distributed, reassess the FAR scope rather than automatically applying the distributed-product conclusion; other quality obligations still need their own assessment.
Keep the reporting clock separate from investigation completion
Build the initial report from a short event record that quality, regulatory and the submitting owner can reconcile. The point is to communicate a potentially important product problem promptly, with enough context for FDA to understand what is known.
| Record | What to capture | Common failure to prevent |
|---|---|---|
| Initial discovery | Date, source and exact information first identified | Replacing contractor discovery with a later internal meeting date |
| Product/application | NDA/ANDA, product, strength, presentation and distributed status | Treating an undistributed batch as proof that no distributed lots are affected |
| Affected scope | Known lots, relevant distribution and sites, with unresolved scope labeled | Combining different lots or assuming the first identified lot is the only one |
| Reportability | Relevant 314.81(b)(1) category and quality assessment | Waiting for confirmed harm, a recall decision or a completed root cause |
| Immediate actions | Actions actually taken, responsible owners and dates | Describing planned quarantine or corrective action as already completed |
| Submission | Initial report version, delivery route and receipt | Assuming an eCTD copy alone completed the FAR handoff |
| Investigation updates | New findings, scope changes, corrected facts and final disposition | Losing the connection to the original discovery and report |
Fictional clock exercise: a contract laboratory learns of a sterility failure on Friday. Under the July 2021 guidance's III.3.a example, Friday is day 0. In a week with no intervening U.S. Federal holiday, Monday, Tuesday and Wednesday are working days 1, 2 and 3, and submission is due by close of business Wednesday. An applicant handoff on Tuesday does not make Tuesday day 0. If Monday is a U.S. Federal holiday, count Tuesday through Thursday instead. Record the actual dates and verify the holiday calendar for the real event.
An open investigation and a scientifically invalidated finding are different states. Guidance III.1.h explains that a stability OOS result for a distributed product that is scientifically invalidated within three working days does not require a FAR. Suspecting laboratory error is not scientific invalidation. If the result is not invalidated within that period, submit the required FAR on time. By contrast, identifying and correcting a genuine reportable problem within the window does not eliminate reporting under III.1.j.
Assess the actual product and event. Not every complaint is reportable, but complaint assessment cannot simply wait until the next routine meeting. A manufacturing issue discovered in an undistributed batch may reveal a problem in already distributed batches. Products marketed under an approved NDA/ANDA can be subject to FAR reporting even when distributed outside the United States. Keep that circumstance distinct from a product marketed solely under a foreign approval, while checking whether shared materials or processes implicate a U.S.-approved product.
The July 2021 guidance recommends follow-up and final FARs; it does not describe them as universally required reports under the initial FAR provision. Recommended follow-ups communicate significant findings, additional affected lots or sites, and corrections to earlier information. A final report connects the investigation conclusion with corrective actions and closure. Repeated complaints concerning the same problem, application and batch during the ongoing investigation do not each need their own follow-up under the guidance's III.6.c scenario; preserve the cumulative complaint record.
A recall notification does not replace a required FAR. Likewise, the NDA/ANDA annual report is not a later substitute for timely reporting. This guide addresses the NDA/ANDA workflow; combination-product and biologic reporting paths require their own applicability assessment.
Your preparation checklist
0/3 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Does the three-working-day FAR clock begin only when regulatory affairs receives the event?
No. FDA’s guidance uses the day a contract laboratory learns of a sterility failure as day 0 and applies the timing regardless of where reportable information is identified. Preserve the original discovery and subsequent handoffs. A later internal escalation must not restart the reporting window.
Can a FAR wait while a laboratory investigates a possible error?
An investigation alone does not justify waiting beyond the reporting window. The guidance distinguishes a stability OOS result scientifically invalidated within three working days from an unresolved result. Document the actual scientific invalidation if established; otherwise submit the required initial report with the investigation status clearly stated.
Does correcting a reportable problem within three working days remove the FAR requirement?
No. FDA’s guidance says a reportable event still requires the FAR even if the investigation identifies the root cause or corrective action occurs within that period. Describe the confirmed cause and completed or ongoing actions in the report rather than treating rapid correction as an exemption.
Are follow-up and final FARs always mandatory?
The July 2021 guidance identifies follow-up and final FARs as recommended, while the qualifying initial report is required under the regulation. Follow-ups should convey significant new findings or corrections, and final reports should explain the investigation outcome and actions. Other applicable reporting or quality obligations need separate assessment.
Does a recall notice or annual report replace an initial FAR?
No. A recall notice does not replace a FAR when the underlying information meets the reportability criteria. Nor can an annual report defer that time-sensitive obligation. Track each applicable report and its delivery evidence separately, while keeping product identity, event facts and corrective-action status consistent.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Regulation
21 CFR 314.81: other postmarketing reports ↗Paragraphs (a), (b)(1) and (b)(2); eCFR current through September 18, 2026.
Guidance
Field Alert Report Submission: Questions and Answers ↗July 2021 final guidance; applicability, timing, initial/follow-up reports and investigation questions.
FDA resource
FDA Field Alert Reports ↗Live FDA resource and Form 3331a links, checked September 22, 2026. Regulation uses three working days.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.12.16. A heading identifies placement, not mandatory applicability.

