A field alert report runs on a 3-day clock, not a CAPA's

This blog has already covered the paperwork a manufacturing problem opens inside a drug firm's own quality system — the lab investigation an out-of-specification result opens without presuming a recall, in what an OOS result actually triggers, and the record a deviation carries independent of whether anyone has agreed it mattered, in the gap between recording a deviation and justifying one. A field alert report sits outside that internal trail. It's the separate duty, set at 21 CFR 314.81(b)(1), to tell FDA about certain problems in a batch already in the field within three working days of finding out — a clock that starts whether or not the firm has finished deciding what the problem means.

The clock starts on awareness, not on a conclusion

Section 314.81(b)(1) requires an NDA or ANDA holder to report specified information about distributed drug products to the FDA district office responsible for the facility involved, within three working days of the applicant's receipt of that information. The operative word is receipt, not resolution. A quality investigation can run for weeks before a firm is confident about root cause, and 314.81(b)(1) doesn't wait for that confidence: the clock runs from the day the applicant first learns of a problem through a complaint or its own testing, not the day it confirms or rules the problem out. A firm that waits to report until its investigation closes has already missed the deadline, even if the investigation closes in four days.

Four triggers, and none of them is a judgment call

The regulation names specific triggers rather than leaving the threshold to discretion: any incident that causes a drug product or its labeling to be mistaken for, or applied to, another article; bacteriological contamination; significant chemical, physical, or other deterioration in the distributed product; and a batch's failure to meet any specification established in its approved application. If the fact pattern matches one of those four, the duty exists regardless of how minor the firm judges the practical risk to be, and regardless of whether the batch has already been recalled, retested, or explained. The rule isn't asking whether the problem is serious enough to mention — it's asking whether the problem is one of the four kinds Congress decided FDA needs to hear about on a short clock.

It isn't an adverse-event report, and the two shouldn't travel together

A field alert report is about a defect in the product itself — contamination, mix-up, degradation, a failed spec — not about a patient's reaction to it. Adverse drug experience reports under 21 CFR 314.80 run on their own separate timeline and go through their own reporting path, and FDA's own guidance is explicit that the two shouldn't be submitted together. A firm can satisfy 314.81(b)(1) by phone or other rapid means with prompt written followup, which makes it easy to fold into whatever communication already happens after an OOS or a deviation is opened — but folding the paperwork together isn't the same as folding the obligations together. One is about the batch; the other is about the patient.

A deviation tracker has no field for this duty

A deviation or CAPA record is built to close on root cause and corrective action, and most trackers reflect that: status fields for opened, investigated, and closed, with the clock measured against an internal SOP's own timeline. A field alert report doesn't close that way. It closes on a notification — a date, a district office, a mode of contact, a written followup — that can and often should happen well before the internal investigation is finished. A tracker that only has room for “deviation opened” and “deviation closed” has nowhere to record that the three-day external duty was met, which means the one record most likely to matter in an inspection is the one most trackers never ask for.

Where this meets the file

A field alert tracking template that keeps the three-day notification as its own required field — separate from, and not satisfied by, a deviation or CAPA's own closure date — is previewed in the launch catalog alongside this week's other drug-quality templates. If your firm handles the handoff between an internal investigation and an external notification differently, the shelf takes that correction directly.