21 CFR 514.80: Animal Drug Records and Reports
Who records, who forwards, and which reporting clock applies to experience with approved US animal drugs.

On this page · 9 sections
- 1What 21 CFR 514.80 Means
- 2Applicant and Nonapplicant Responsibilities
- 3Field Alerts and 15-Day Alerts
- 4Follow-Up and Clock Control
- 5Periodic Drug Experience Reports
- 6Records, Retention, and Causation
- 7Fictional Intake-to-Handoff Timeline
- 8Reporting Versus Manufacturing and Release
- 9US Scope and Product Boundaries
How does 21 CFR 514.80 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What 21 CFR 514.80 Means
21 CFR 514.80 is the US regulation governing records and reports concerning experience with approved new animal drugs. It connects information about safety, effectiveness, and product or manufacturing defects to the holder of an approved new animal drug application (NADA) or abbreviated new animal drug application (ANADA), and ultimately to FDA. Its requirements include indexed records, expedited reports, periodic drug experience reports, and retention.
The central distinction is between keeping information and submitting a particular report. Applicants and nonapplicants have recordkeeping responsibilities, but their reporting destinations differ. Applicants report to FDA; nonapplicants provide information to the appropriate applicant, which then reports to FDA as required. Domestic and foreign information are both covered, even though this definition addresses only US law.
Under 21 CFR 514.3, an adverse drug experience is not limited to an injury proven to be caused by the drug. It includes adverse events associated with use, whether or not considered drug-related, lack of expected effectiveness, and adverse events in humans exposed during manufacture, testing, handling, or use. Events involving extralabel use of an approved new animal drug are also included.
02Applicant and Nonapplicant Responsibilities
An applicant owns, or holds on behalf of the owner, the approval for an NADA or ANADA. A nonapplicant is a different person whose name appears on the product label and who engages in manufacturing, packing, distribution, or labeling. Both parts of the nonapplicant definition matter: the activity and the name on the label.
| Role | Records and Reporting Responsibility | Practical Handoff |
|---|---|---|
| Applicant | Maintains the required files and submits required experience reports to FDA for each approved NADA or ANADA. | Assign a regulatory owner for classification, submission, follow-up, and reconciliation. |
| Nonapplicant | Maintains required files and forwards adverse drug experience reports to the applicant within 3 working days of first receiving the information. | Preserve the original receipt date and obtain evidence that the applicant received the transfer. |
| Contract manufacturer not named on the label | Manufacturing activity alone does not establish nonapplicant status under § 514.3. | Confirm the legal role and define escalation responsibilities in the operating agreement; do not assume the nonapplicant label applies. |
For nonapplicant adverse drug experience reports, § 514.80(b)(3) requires records of the receipt date, the applicant's name and address, and a copy of the report with its submission date to the applicant. Electing also to report directly to FDA does not replace the stated forwarding duty; direct FDA reporting follows the provision's electronic-format requirements and exceptions.
In practice, give the applicant access to the original narrative and attachments, not merely a rewritten summary. Keep uncertainty visible: an unconfirmed lot, an incomplete outcome, or a disputed relationship to the drug should remain identifiable as such. A handoff should transfer the information and its history, not create a new apparent first-receipt date.
03Field Alerts and 15-Day Alerts
The two expedited FDA reporting routes address different questions. A three-day field alert concerns a product or manufacturing defect that may result in serious adverse drug events. A 15-day alert concerns each serious, unexpected adverse drug event, regardless of the information source. Neither route should be reduced to a generic complaint deadline.
| Route | Trigger | Clock | Destination |
|---|---|---|---|
| Three-Day NADA/ANADA Field Alert — § 514.80(b)(1) | A product or manufacturing defect that may result in serious adverse drug events. | Within 3 working days of first becoming aware that a defect may exist. | Appropriate FDA District Office or local FDA resident post; nonapplicant information goes through the applicant. |
| 15-Day NADA/ANADA Alert — § 514.80(b)(2)(i) | Each serious, unexpected adverse drug event, regardless of source. | Within 15 working days of first receiving the information. | FDA, through the applicant. |
| Nonapplicant Forwarding — § 514.80(b)(3) | Reports of adverse drug experiences received by a nonapplicant. | Within 3 working days of first receiving the information. | The applicant; this is distinct from the FDA field-alert route. |
Section 514.3 defines a product defect by reference to a distributed product: deviation from approved-application standards, or significant change or deterioration in the distributed drug product. A manufacturing defect is a product defect caused or aggravated by manufacturing or a related process. The field-alert trigger therefore does not require a confirmed injury or a completed root-cause investigation: the wording concerns a defect that may exist and may result in serious adverse drug events.
For the 15-day route, serious and unexpected are separate assessments. Serious includes fatal or life-threatening events, events requiring professional intervention, abortion, stillbirth, infertility, congenital anomaly, prolonged or permanent disability, and disfigurement. Unexpected means not listed in current labeling and also includes related events that differ from labeled events in greater severity or specificity.
Field-alert information may initially be provided by telephone or other telecommunication means, with prompt written follow-up using Form FDA 1932. The mailing cover must be plainly marked “3-Day NADA/ANADA Field Alert Report.” Initial 15-day alerts are submitted electronically, unless a waiver is obtained or FDA requests an alternate format.
04Follow-Up and Clock Control
Under § 514.80(b)(2)(ii), the applicant must promptly investigate every adverse drug event that is the subject of a 15-day alert. Significant new information starts a follow-up obligation: submit the follow-up within 15 working days of receiving that information. The follow-up must state the initial report date and provide the additional information. Electronic submission applies, subject to the specified waiver or FDA-requested alternate-format exceptions.
There is also a no-information follow-up requirement. If additional information is sought but not obtained within 3 months of the initial report, a follow-up is required describing the steps taken and why the additional information was not obtained. This is not a replacement for a significant-new-information follow-up, nor is it expressed as a 90-day period.
- Maintain separate timestamps for first receipt, first awareness of a possible defect, transfer to the applicant, and receipt of significant new information.
- Assign an owner to each active report and follow-up task, with a backup for absences.
- Document information requests and unsuccessful attempts so that a no-information follow-up can explain what happened.
- Reassess new information rather than leaving the initial seriousness, expectedness, or defect assessment unexamined.
05Periodic Drug Experience Reports
Section 514.80(b)(4) establishes the ordinary periodic schedule: every 6 months for the first 2 years following NADA or ANADA approval, then yearly. Six-month reports are due within 30 days after the reporting period ends; yearly reports are due within 90 days of the approval anniversary. Reports cover the full period, identify previously submitted information, and are accompanied by completed Form FDA 2301. Annual timing or frequency may change through an FDA-approved petition, and FDA may require different or more frequent reporting.
At a summary level, the content framework covers:
- Distribution data, including domestic and export quantities and product presentations, under the applicable distribution-data provisions.
- Current applicant and distributor labeling, with a dated summary of changes or a statement that there were none.
- Specified nonclinical studies and clinical information not previously reported, including descriptions of completed applicant-conducted or applicant-sponsored trials within the provision's timeframe.
- Product or manufacturing defects and adverse drug experiences not previously reported through the expedited routes.
- Literature adverse drug experience reports and pertinent references, plus previously unreported experiences from postapproval studies.
- A separate narrative summary of increased frequency of serious adverse drug events, expected or unexpected, when such an increase is identified.
Periodic reporting is not permission to replace all individual cases with a narrative total. Paragraphs (b)(4)(iv)(A) and (C) require individual electronic reporting for the specified defects and adverse drug experiences, subject to the stated exceptions. The increased-frequency assessment must occur at least as often as periodic reporting; its narrative addresses comparison periods, methods, relevant report references, and interpretation.
As a working practice, reconcile the periodic package against intake records, expedited submissions, literature records, and the distribution dataset. This helps distinguish “previously reported,” “reportable in this period,” and “still awaiting information” without treating the periodic report as a substitute for an earlier deadline.
06Records, Retention, and Causation
The records obligation is broader than a folder of submitted forms. Section 514.80(a)(1) requires indexed and complete files containing full records of pertinent safety or effectiveness information. For applicants, it addresses information not previously submitted as part of the NADA or ANADA; for nonapplicants, it addresses information received or otherwise obtained. Both include domestic and foreign sources.
| Record Set | Retention Rule | Avoid This Substitution |
|---|---|---|
| Records and reports required by § 514.80 | Applicants and nonapplicants retain them for 5 years after the date of submission under § 514.80(e). | Do not substitute intake date, investigation closure, or batch expiry for the stated submission-based anchor. |
| Drug product complaint records under § 211.198(b) | Generally, at least 1 year after product expiration or 1 year after complaint receipt, whichever is longer. | Do not assume the five-year reporting rule is the only retention rule affecting the complaint file. |
| Batch-associated production, control, or distribution records under § 211.180(a) | Generally, at least 1 year after the batch expiration date. | Do not calculate all manufacturing-record retention from the adverse-event submission date. |
The two Part 211 provisions have specific three-year, distribution-based rules for qualifying OTC products without expiration dating. In practice, map each linked record set to its applicable retention requirements and preserve shared evidence through the longest applicable period rather than assigning one blanket destruction date.
Under § 514.80(f), applicants and nonapplicants must allow authorized FDA officers or employees, upon request and at reasonable times, access to copy and verify the required records and reports. A practical index should therefore connect the original intake, assessment, correspondence, submissions, follow-up, and related investigation without losing their individual dates.
07Fictional Intake-to-Handoff Timeline
FICTIONAL EXAMPLE: A label-named distributor receives a complaint about Fictional Product P, an assumed approved ANADA product, on Monday, September 14, 2026. The account describes a separated bottle seal and visible deterioration in distributed lot FIC-2609, plus an animal event requiring professional intervention. These product, lot, and case details are invented.
For this example only, Saturdays and Sundays are non-working days, there are no holidays or other closures during the illustrated counting period, and the receipt or awareness date is Day 0. Subsequent weekdays are counted. Actual deadline counting requires regulatory confirmation.
- Preserve IntakeDistributor records the original account and receipt timestamp.
- Transfer and AssessApplicant receives the account; regulatory and quality reviewers assess the event and possible defect separately.
- Assign Reporting WorkApplicant assigns field-alert and 15-day alert owners without waiting for a completed investigation.
- Track Follow-UpNew information and unsuccessful information requests remain linked to the initial report.
- Reconcile RecordsSubmission evidence, case status, and quality-investigation references are connected for later review.
| Fictional Date | Action | Handoff Evidence |
|---|---|---|
| Monday, September 14 | Distributor forwards the account that day. Applicant reviewers identify a possible defect that may result in serious adverse events and assess the animal event as serious and unexpected against current labeling. | Original receipt and same-day transfer timestamps; separate defect and event assessments. |
| Tuesday, September 15 | Applicant sends a written field alert to the appropriate FDA office using Form FDA 1932. | Report copy and transmission evidence linked to the defect record. |
| Wednesday, September 16 | Applicant submits the initial 15-day alert electronically. | Initial submission date and case reference retained for follow-up. |
| Friday, September 18 | Applicant receives significant new veterinary outcome information. | New-information receipt timestamp and reviewer assessment. |
| Monday, September 21 | Applicant submits a follow-up identifying the September 16 initial report and providing the new information. | Follow-up linked to the initial submission; September 19–20 were assumed non-working days. |
Under these assumptions, the three-working-day date from September 14 is September 17, and the 15-working-day date is October 5. Both initial reports were submitted earlier. The September 21 follow-up is on the first working day after the significant new information arrived. Investigation can continue, but neither submission resolves causation or determines the disposition of any remaining stock.
08Reporting Versus Manufacturing and Release
Animal drugs are drugs: Parts 210 and 211 are part of the applicable drug CGMP framework, not an unrelated human-drug requirement. Section 210.2 describes the applicable CGMP regulations as supplementing one another unless otherwise specified. Section 514.80(a)(5) expressly places its records and reports in addition to those required under Parts 211, 225, and 226.
The operational connection is especially clear in § 211.198. Written complaint procedures must provide for quality-control-unit review of possible specification failures and a determination about investigation. They must also provide for review of whether a complaint represents a serious and unexpected adverse drug experience reportable under the cited reporting provisions, including § 514.80.
- Regulatory decision: assess reportability, destination, deadline, submission content, and follow-up.
- Quality decision: assess the product concern, investigation, affected stock, and disposition or release through the applicable quality process.
- Shared evidence: connect the complaint to relevant lot records, distribution information, investigations, and any proposed corrective action without merging the decisions.
Keep these as human decisions: regulatory personnel decide the reporting route, and the quality unit decides disposition and release through its quality process. A completed report is not a release criterion, and an open investigation should not be used as a reason to postpone an otherwise triggered reporting task.
For this site's lot-packet guide, see Veterinary Pharma Manufacturing Readiness. Keep proposed manufacturing changes on a separate assessment path; the NADA/ANADA Readiness Guide addresses change routes rather than treating an experience report as a change submission.
09US Scope and Product Boundaries
This definition addresses US requirements as of October 20, 2026, for experience with approved NADA and ANADA products. It is not a route guide for conditional approvals, indexed products, or compounded preparations; those categories should not be collapsed into the approved-NADA/ANADA workflow described here. Extralabel use of an approved new animal drug is included in the adverse drug experience definition, but prescribing and compounding rules are outside this page's scope.
Section 514.80(a)(4) also applies the section to approved Type A medicated articles. It specifically applies paragraphs (b)(1), (b)(2), (b)(4)(iv), and (b)(4)(v) to approved Type A medicated articles incorporated in animal feeds. Section 514.80(a)(6) excludes designated medical gases, whose certification and animal-use experience records and reports are addressed under Part 230.
For scope navigation, medicated feed/Part 225, Type A medicated articles/Part 226, and USDA-licensed veterinary biologics/9 CFR Part 113—including the separate topic of serials in licensed establishments—are manufacturing boundaries, not protocols explained here. Use product-specific review rather than extending this glossary's drug-reporting workflow to every animal-health product.
Frequently asked questions
Q.What does 21 CFR 514.80 require?+
It requires specified records and reports concerning experience with approved new animal drugs. Applicants maintain required information and report to FDA; nonapplicants maintain required information and provide it to the applicant. The section includes field alerts, 15-day alerts and follow-up, periodic reports, and five-year retention after submission.
Q.How is a three-day field alert different from a 15-day alert?+
A field alert concerns a product or manufacturing defect that may result in serious adverse drug events and is due within 3 working days of first awareness that a defect may exist. A 15-day alert concerns each serious, unexpected adverse drug event and is due within 15 working days of first receiving the information.
Q.Does every complaint require a 15-day alert?+
No. The initial 15-day route requires a serious, unexpected adverse drug event. Other information may engage the field-alert route, periodic reporting, or recordkeeping requirements. A nonapplicant's three-working-day forwarding duty for adverse drug experience reports is not limited to events meeting the 15-day criteria.
Q.Is every contract manufacturer a nonapplicant?+
No. Under § 514.3, a nonapplicant must be someone other than the applicant whose name appears on the label and who engages in manufacturing, packing, distribution, or labeling. Confirm that definition against the actual arrangement, then document the information-transfer process.
Q.How should working days be counted?+
Confirm the counting convention, non-working days, and due dates with your regulatory team. Preserve receipt and awareness dates separately from internal transfer dates. The assumptions in the fictional example are illustrative and should not be adopted as a legal definition.
Q.Is follow-up required if no additional information is obtained?+
Yes, in the stated circumstance: if additional information is sought but not obtained within 3 months of the initial 15-day alert, a follow-up must explain the steps taken and why it was not obtained. Significant new information has its own follow-up deadline of 15 working days after receipt.
Q.How long must 514.80 records be retained?+
Applicants and nonapplicants must retain the required records and reports for 5 years after the date of submission. This is not a five-year clock from complaint receipt or batch expiration. Related complaint and manufacturing records can have separate applicable retention requirements.
Q.Does submitting an adverse drug experience report admit causation?+
Not necessarily. Section 514.80(i) states that submission, and FDA's release of the information, does not necessarily reflect a conclusion that it constitutes an admission that the drug caused or contributed to the event. A person need not admit, and may deny, such an admission.
Primary sources
Further reading
- Veterinary Pharma Manufacturing ReadinessBuild the lot packet that supports a separate human quality and release decision.
- NADA/ANADA Readiness and Change RoutesKeep manufacturing-change assessments distinct from experience reporting.
- 21 CFR 211Understand the drug CGMP context for complaint and manufacturing records.
Want to see how 21 CFR 514.80 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
