On this page
What should an ANDA reference-labeling comparison contain?
Preserve the current approved labeling for the correct RLD, the proposed generic labeling and an annotated side-by-side comparison explaining every difference. Include the applicable Medication Guide and other labeling in scope. Support additions, changes and omissions under the actual permitted-difference framework, and inspect their effects on the remaining text. A clean visual comparison does not itself establish legal acceptability.
Before you begin
ANDA labeling comparison under 21 CFR 314.94(a)(8). Do not transfer its sameness framework to a 505(b)(2) NDA or assume every proposed omission is permissible.
What you will prepare: A current reference-label record, proposed labeling and an annotated comparison with an explicit basis for every difference.
Identify the reference product before comparing words
Confirm the reference listed drug identified for the ANDA, including dosage form, strength and the relevant approved labeling version. Save the complete source and its retrieval date, including applicable patient labeling. Distinguish the authoritative approved reference from a historical commercial package or a label belonging to another strength. Record any uncertainty in reference identity before drafting the sameness statement.
Explain every difference, including omissions
Section 314.94(a)(8) calls for the reference labeling, proposed labeling, a statement and an annotated side-by-side comparison. Its permitted differences are conditional. Build a table with reference passage, proposed passage, difference category, legal/regulatory rationale and reviewer. Include deletions, manufacturer changes and formulation-related differences. Patent or exclusivity issues require the appropriate assessment; do not remove a passage merely because it is inconvenient or describe an omission as acceptable without resolving its basis.
Review the effect of each change
Read the remaining text as a whole. Does an omitted use leave an unexplained dose, warning, cross-reference or patient instruction elsewhere? Do the carton, insert and applicable Medication Guide use consistent product identity? Maintain the approved reference text and reference-label copy as the same controlled baseline even if separate electronic artifacts are needed. If the reference label changes during preparation, assess the change and refresh the comparison rather than silently substituting a new file.
Fictional example: a missing dependency
A proposed omission removes a protected-use paragraph but leaves a dosing cross-reference to it. The comparison must show both the omission and the stranded reference. The regulatory and clinical owners decide whether the resulting labeling remains appropriate and legally supported. An unknown exclusivity basis remains unresolved; the author does not label the omission “permitted” to finish the table.
Give every difference an explicit basis and consequence
Freeze the reference identity and version before starting the comparison. The baseline must match the RLD identified for the application, including the relevant product presentation. Keep the preserved source labeling and the text used in the comparison aligned.
| Difference record | What to capture | What must not be assumed |
|---|---|---|
| Location and text | Exact RLD passage and proposed passage, including deletion | That an omitted paragraph is too small to document |
| Difference type | Manufacturer, approved-petition, formulation or another assessed basis | That a category name by itself grants permission |
| Supporting basis | Applicable provision, product facts and responsible review | That a similar competitor label establishes this application's basis |
| Dependent text | Related dosing, warnings, references and patient instructions | That deleting one indication removes every related dependency |
| Disposition | Supported, revised or unresolved, with owner | That blank rationale means no issue exists |
| Version change | Reference version and subsequent updates assessed | That the original comparison stays current after the RLD changes |
Section 314.94(a)(8) includes the RLD labeling, proposed labeling, the sameness statement and the annotated comparison. The same paragraph describes conditional differences, including those associated with an approved suitability petition or different manufacturers and certain protected-use omissions. It does not allow an author to choose any difference that makes the generic label easier to write.
Fictional omission exercise: a proposed indication omission removes the main use paragraph but leaves its dose instruction and a patient question referring to that use. The comparison needs to show the omission and those dependent passages. Have the regulatory and clinical owners assess the legal basis and resulting meaning. Do not silently remove additional safety text simply to eliminate every mention of the omitted use.
Read the resulting label continuously after checking the differences table. A collection of individually explained edits can still produce broken instructions, unexplained headings or incorrect references. Verify consistent product identity across the professional label, applicable Medication Guide, container and carton.
If the RLD labeling changes during preparation, preserve the earlier comparison and assess the new version. Identify which prior conclusions remain valid and which need review. Replacing the attached reference PDF without updating the side-by-side comparison leaves two incompatible baselines in the same package.
Reconcile the RLD identifiers with the ANDA basis statement and the generic/RLD product comparison. Keep the draft-label evidence workflow relevant to its actual pathway: an NDA claim rationale is not automatic permission for an ANDA label difference.
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
Can an ANDA applicant copy a competitor’s label as its reference baseline?
The comparison must use the current approved labeling for the RLD identified for the ANDA. A competitor’s label, historical pack or different presentation does not establish that baseline. Verify the reference identity and preserve the exact source used before evaluating proposed differences.
Must deletions be explained in the ANDA labeling comparison?
Yes. The side-by-side comparison must account for differences, including omissions. Record the deleted passage, applicable basis and effects on dependent text. Do not treat a blank proposed cell as a complete rationale or assume that omission of a protected use permits removal of every related safety statement.
Does a different manufacturer permit any desired labeling difference?
No. Section 314.94(a)(8) describes a conditional framework for differences and their explanation. Identify the specific change, applicable basis and product facts, and obtain the appropriate review. A different company name does not provide a general exemption from the ANDA labeling requirements.
What should happen when the RLD labeling changes before submission?
Assess the new approved version and update the comparison and dependent artifacts as appropriate. Preserve the previous version and record which conclusions changed. Merely attaching the newest reference PDF while keeping an older comparison leaves the reviewer with inconsistent baselines and unsupported sameness statements.
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.94: ANDA labeling ↗Paragraph (a)(8), including reference labeling, comparison and explained differences. Current eCFR reopened September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.14.3. A heading identifies placement, not mandatory applicability.