Skip to content
Assyro AI
Assyro AI
Module 1
1.13.4
Guide

Prepare an NDA or ANDA annual report and distinguish BLA requirements

Collect significant new information, reconcile labeling and manufacturing changes, and report distribution with the correct units and application scope.

By Assyro
Published
Article updated FDA · eCTD v4.0 placement
On this page

How do you prepare an NDA or ANDA annual report?

Use the U.S. approval anniversary and §314.81(b)(2) to define the interval and required content. Reconcile significant findings, distribution by the specified product identifiers and dosage units, labeling and manufacturing changes, clinical/nonclinical information and study status. Include the required Form FDA 2252 and distinguish BLA-specific obligations before reusing a template.

Before you begin

NDA/ANDA annual reports under 314.81(b)(2), with explicit BLA boundaries under 601.12; BLA obligations are not a wholesale copy of Part 314.

What you will prepare: A controlled annual package with source-backed changes, distribution and study-status cross-references.

Sections covered in this guide (9)

Establish the approved application and interval

For an NDA/ANDA, retrieve the U.S. approval anniversary, last annual report, approved product scope and interval records. 314.81(b)(2) specifies the report within 60 days of the anniversary and a completed Form FDA 2252. Use the current form and electronic-submission instructions, not historical paper-copy directions embedded in older text.

For a BLA, assess the actual reporting obligations: 601.12(d) addresses annual-report changes, 601.12(f)(3) addresses specified labeling changes, and 601.70 addresses applicable postmarketing-study progress. Do not require every NDA annual-report item for a BLA merely because the catalog presents the same family.

1.13.1–1.13.3 and 1.13.7: summarize evidence and resulting action

Nonclinical (1.13.1): collect new toxicological findings and the relevant unpublished reports or summaries of published reports. Identify the ingredient/product relationship, study scope and significance; do not omit an unfavorable finding because no label change has yet been proposed.

Clinical pharmacology (1.13.2): reconcile new biopharmaceutic, PK and pharmacology information with the relevant published or completed unpublished clinical work. State the population and evidence limitations, and identify whether the finding changes an existing conclusion.

Safety (1.13.3): summarize significant new information that may affect safety, effectiveness or labeling and the actions taken or planned. Coordinate with the periodic and expedited safety-reporting owners; this annual report is not their replacement. Address the regulation's pediatric information where applicable.

Other significant information (1.13.7): explain material developments outside the preceding categories and their disposition. The report should distinguish “reviewed, no new relevant information” from “the owner has not supplied the data.” Include the relevant clinical material according to 314.81(b)(2)(vi), rather than every publication mentioning the drug.

1.13.4: produce a dated labeling-change chronology

Collect the prior and current controlled labeling, implementation records and related submissions. For the NDA/ANDA annual report, provide the current labeling material described by the rule and a chronological summary of implemented changes, or the required no-change statement when supported.

A useful working table includes labeling component, prior version, new version, implementation date, nature of change and regulatory submission/decision reference. Distinguish the date text was drafted, the date FDA acted and the date it was implemented. The annual summary does not make a labeling change eligible for annual reporting if another reporting category applies. Apply the BLA-specific labeling provisions separately.

1.13.5–1.13.6: reconcile changes with their reporting category

For manufacturing changes, obtain the change-control register and the regulatory assessment for each implemented change. Describe changes eligible for the annual-report route, with dates and supporting scientific references. Also summarize relevant new quality findings and their impact. A change's inclusion in this report does not replace a supplement required before or after implementation under the applicable change provisions.

For microbiological changes, identify the actual process/control change or significant finding, product/site/batches affected and the reason it matters. Reconcile this with stability, investigations, deviations and other reports. In a BLA, use the 601.12 framework and its product-quality risk criteria; do not classify a biologic process change by copying a small-molecule example.

1.13.11: report product units, not revenue or shipment totals without context

Reconcile quantity distributed under the approved NDA/ANDA by the required NDC, strength or potency and dosage units, distinguishing domestic and foreign quantities. Obtain the source extract and its definitions: units, packages, bottles or vials are not interchangeable. The regulation does not require pricing information. Address authorized-generic information when applicable.

Have the supply-data owner document how adjustments and source-system conventions affect the reported totals. Investigational supply or product under another application should not silently enter the totals. A pharmaceutical's biological nature alone does not make this NDA/ANDA requirement a universal BLA distribution report; establish any applicable BLA reporting separately.

1.13.14: close the report with a factual open-business log

The NDA/ANDA open-regulatory-business log is optional under 314.81(b)(2)(ix). If included, list unresolved correspondence in either direction, dates and references, the requested next action and the owner. Do not list a received FDA response as unanswered simply because the internal task is still open.

Fictional editorial exercise: a distribution table labels 10,000 bottles as 10,000 tablets, and the labeling summary uses approval dates as implementation dates. Reconcile the source definitions and actual change records. If the units or implementation evidence are absent, those outputs remain unresolved. Changing the application from NDA to BLA requires reassessing the content map, not changing only the cover-page acronym.

Check the units and dates that most easily distort the report

Build a distribution reconciliation before writing the summary. Keep the source extract, unit definitions and transformation logic so the reviewer can reproduce the reported quantity. The working table below is an editorial aid; adapt it to the actual presentation and data system.

Check the units and dates that most easily distort the report
Reconciliation fieldExample or control
Application and productConfirm that the quantity belongs to this approved NDA/ANDA
NDC and strength or potencyRetain the required identifiers rather than merging unlike presentations
Source quantity and unitTen bottles; establish what the source system counts
Dosage-unit conversionFor a hypothetical 30-tablet bottle, ten bottles represent 300 tablets
Domestic and foreign usePreserve the separate quantities and supporting destination definitions
Interval and adjustmentsDocument extract cutoff, exclusions and treatment of source-system adjustments

The example establishes a conversion, not a universal reporting convention for all dosage forms. A vial, tablet and milliliter are different measures. Do not turn a packaging example into a rule that every injectable must be reported as milliliters, or combine strengths into one total that loses the required breakdown. Resolve returns and other adjustments with the data owner rather than silently inventing a net-distribution definition.

For labeling, maintain three distinct dates where applicable: document revision, relevant regulatory submission or action, and implementation. The required chronology concerns implemented changes. A draft revised in February, an agency action in April and implementation in May are not one event. Use the actual implementation record, and identify the correspondence that supports the change without implying that every change required the same route.

Review exercise: the supply table reports ten bottles as ten dosage units, while the labeling narrative dates a change to the day the writer finished the draft. Correct both from source records. If those records are unavailable, retain the gap for resolution; neither a plausible conversion nor a guessed date is suitable evidence.

Keep authorized-generic entry/exit information distinct from ordinary distribution totals, with the required separate treatment of each dosage form or strength. For quality changes, preserve the reporting-category assessment: an annual-report description cannot cure an omitted required supplement. Reconcile study entries with the postmarketing-status guide and confirm the application clock using the annual-report route guide.

Your preparation checklist

0/4 checked

Use this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.

Frequently asked questions

Can sales revenue replace the distribution quantities in an NDA annual report?

No. Section 314.81(b)(2)(ii) calls for the specified NDC, strength or potency, dosage-unit quantities and domestic/foreign breakdown. It expressly does not require financial or pricing data. Sales value cannot establish those quantities, so obtain a source extract with verified product and unit definitions.

Should the labeling chronology use approval dates or implementation dates?

The regulation calls for changes listed in the order they were implemented. Keep agency-action dates and document-version dates as supporting context, but do not substitute them for implementation evidence. If no labeling changes occurred, use the prescribed no-change statement only after the controlled records support it.

Does mentioning a manufacturing change in the annual report replace a required supplement?

No. The annual-report provision distinguishes changes that do not require a supplement under §314.70(b) or (c). Preserve the actual reporting-category assessment and related submissions. Describing a change in the annual package does not retrospectively authorize implementation through an otherwise inappropriate reporting route.

Can the NDA annual-report checklist be reused unchanged for a BLA?

Establish the BLA-specific obligations first. Section 601.12 addresses change reporting and §601.70 addresses applicable postmarketing-study progress; they do not simply import every NDA distribution and content item. Reuse useful collection controls while mapping each requested output to its actual biologic reporting basis.

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.

Regulation

21 CFR 601.12: changes to an approved application ↗

Paragraphs (d) and (f)(3), annual-report changes and labeling; eCFR current through September 18, 2026.

Regulation

21 CFR 601.70: annual progress reports of postmarketing studies ↗

Scope, study status, schedule and written FDA closure; eCFR current through September 18, 2026.

Technical specification

FDA eCTD v4.0 headings and hierarchy ↗

Version 2.2, February 2025; Module 1 printed pages 2–3 and application-specific mapping appendix. Placement does not establish applicability.

Technical specification · placement only

FDA eCTD v4.0 comprehensive hierarchy ↗

Version 2.2, February 2025. Section 1.13.4. A heading identifies placement, not mandatory applicability.

Talk with Assyro about your next document