21 CFR 314.81 reads like a single postmarketing-reports section. In practice it runs two mechanisms that share almost nothing except the regulation number: a Field Alert Report, filed within 3 working days of a quality or distribution incident, and an Annual Report, filed once a year regardless of whether anything went wrong. Teams that treat the FAR as a lightweight version of a supplement, or the Annual Report as a formality, are the ones who miss a deadline on one or the other — or discover during an inspection that neither workflow was ever actually written down.

What triggers a Field Alert Report

Under 314.81(b)(1), an NDA or ANDA holder has to report information showing one of a short list of things: an incident causing a drug product or its labeling to be mistaken for, or applied to, another article; bacteriological contamination; any significant chemical, physical, or other change or deterioration in the distributed product; or the failure of one or more distributed batches to meet the specification in the approved application. The report goes to the FDA district office responsible for the facility involved — not the review division — and the clock is 3 working days from the applicant's receipt of the information, not from when the underlying event happened. Initial notice can go by telephone or another rapid means, with prompt written follow-up; FDA created Form FDA 3331a for electronic FAR submission, and its final guidance on FAR submission (issued July 23, 2021) confirms the requirement reaches every product under an NDA or ANDA, including combination products with a drug constituent part.

  • Initial FAR. Reports the triggering information for the first time, within 3 working days of receipt — even if the investigation is not finished.
  • Follow-up FAR. Adds information as the investigation develops; there is no fixed cadence, but a stalled investigation with no follow-up is itself a finding waiting to happen.
  • Final FAR. Closes the loop with the confirmed root cause and the corrective action taken or planned — the piece FDA actually wants to see the investigation land on.
A Field Alert Report is a notification, not an amendment. It tells FDA something happened; it does not, by itself, change what the application says you're allowed to do. Why a FAR can't substitute for a 314.70 supplement

What the Annual Report actually has to contain

314.81(b)(2) runs on an entirely different clock: within 60 days of the anniversary of the application's US approval date, filed with the FDA division responsible for reviewing it — not the district office the FAR goes to. Where the FAR exists to surface an urgent problem fast, the Annual Report exists to summarize a year of otherwise-unremarkable change: a running account of what shifted in the product and its manufacturing since the last one, whether or not any of it was urgent enough to report on its own.

  • Summary of new information. A brief account of every change made during the period, including changes filed under 314.70(b) CBE supplements and 314.70(c) PAS supplements — the Annual Report cross-references what already went in separately, it doesn't repeat the filing.
  • Distribution data. The quantity distributed of each currently approved strength, by package size, for the reporting period.
  • Labeling changes. Minor labeling changes that did not require their own prior supplement get reported here, under 314.81(b)(2)(i).
  • Stability data. Updated results supporting the approved shelf life or retest period, consistent with the application's stability commitments.
  • Status reports. The state of any open postmarketing study commitments — still in progress, delayed, or complete.
3 working days
The Field Alert Report clock — from the applicant's receipt of the triggering information, not the event itself.
60 days
The Annual Report clock — from the anniversary of the application's US approval date, every year.
Form FDA 3331a
The electronic FAR submission form FDA built to standardize what used to be phone-and-letter reporting.

Where this intersects with change classification

None of this decides how a manufacturing or labeling change gets filed — that's the separate question of how a manufacturing change gets classified and filed under 314.70's CBE-0, CBE-30, and PAS tracks. A FAR can run in parallel with a change filing when the same underlying event triggers both: a batch failure that requires a FAR might also require a supplement if the fix changes an approved specification or process. And when a quality defect reaches the field, the FAR obligation is separate again from how FDA classifies the resulting recall — a FAR can be filed with no recall at all, and a recall can proceed on its own regulatory track once initiated. Treating these as one workflow, rather than three regulations doing three different jobs, is the most common way a team misses a deadline on all of them at once.

A postmarket reporting sequence that holds up
  1. Write down the distinction, not just the deadlines. A one-page SOP that states which events trigger a FAR, which trigger a 314.70 supplement, and which simply wait for the Annual Report — reviewed by someone who owns the decision, not left to whoever notices first.
  2. Own the 3-day clock explicitly. Name who receives quality and distribution incident reports, who decides FAR applicability, and who submits — and rehearse it, because 3 working days does not allow for figuring this out live.
  3. Calendar the Annual Report against the real anniversary date, not the fiscal year or a generic compliance calendar — the 60-day clock starts on the application's actual US approval date.
  4. Cross-reference every 314.70 supplement filed during the period into the Annual Report's summary as you file it, rather than reconstructing a year of changes from memory when the report comes due.

None of this is exotic, but it is easy to under-resource: a FAR workflow nobody has rehearsed, or an Annual Report treated as a low-priority year-end task, both create exposure that has nothing to do with the underlying product and everything to do with process discipline. Our postmarket CMC reporting work builds both mechanisms into the quality system as distinct, owned processes, and our ongoing FDA regulatory support keeps them current as the application and its commitments evolve.

Frequently asked questions

How soon does a Field Alert Report have to be submitted?

Within 3 working days of the applicant receiving information that triggers it — Monday through Friday, excluding federal holidays. Initial notice can go by telephone or another rapid means, with prompt written follow-up, per 21 CFR 314.81(b)(1).

Does a Field Alert Report change my approved application?

No. A FAR is a notification, not an amendment — it does not itself alter the approved NDA or ANDA. A manufacturing or labeling change still has to go through its own CBE-0, CBE-30, or PAS filing under 21 CFR 314.70 to take effect.

What has to be in an NDA or ANDA Annual Report?

A summary of changes made during the year under 314.70(b)/(c) supplements, current distribution data by strength and package size, minor labeling changes, updated stability data, and the status of open postmarketing study commitments — filed within 60 days of the application's US approval anniversary.

Sources & further reading

  1. 21 CFR 314.81 — Other postmarketing reports. ecfr.gov
  2. FDA. Field Alert Report Submission: Questions and Answers — Guidance for Industry (final, July 23, 2021). fda.gov

This article is provided for general informational purposes and reflects the regulatory landscape as of September 2026. It is not legal or regulatory advice. Confirm current FAR and Annual Report requirements with FDA or qualified counsel before acting.