On this page
How do you organize an FDA labeling submission?
Start with the application pathway, requested action and actual labeling baseline. Inventory each proposed, final, reference, patient or investigational artifact with its version, owner and purpose. Reconcile text, annotations, artwork and structured renditions before publishing. A Module 1 heading organizes the files; it does not establish which labels apply, their approval status or the correct regulatory route.
Before you begin
FDA Module 1 labeling for human drugs and biological products. Application pathway, prescription/nonprescription status and submission purpose determine the applicable content rules. A heading is not a requirement to submit every labeling type.
What you will prepare: A labeling inventory with a documented baseline, owners, proposed changes and the correct review task for each artifact.
Identify whose label and which state
Begin with the application number, authority, product, strength, dosage form and route. Record whether you are proposing language, implementing an agreed version, comparing a listed drug, or preparing investigational supply. These are different preparation decisions. Do not call a sponsor-approved working file FDA-approved. If the application pathway is unknown, inventory the files but leave the pathway-specific content and submission route unresolved.
Build the package map
| Artifact | Starting evidence | Review output |
|---|---|---|
| Draft text | Proposed claims, underlying reports, agency comments | Clean text and a traceable annotation set |
| Final text | Authoritative agreed/approved baseline and change instructions | Reconciled release copy, with any deviation escalated |
| Carton or container | Actual package dimensions and product identity | Readable artwork for each presentation |
| Listed-drug reference | Correct reference product and current approved label | Preserved reference plus explained comparison |
| Investigational material | Protocol, supply plan and known risks | Study-appropriate label or investigator brochure |
This is an editorial control table, not a prescribed FDA form. Give each file a version, language, effective or proposed date, owner and relationship to its predecessor. Keep source content, review annotations and submission rendition identifiable.
Keep companion workflows separate
SPL is a structured representation, not a substitute for deciding what the label should say. Have the publishing owner verify applicable technical specifications and compare the rendered structured content with the approved writing baseline. Product labeling accompanying a promotional 2253 submission has a separate role at 1.14.6; promotional claims and annotated support belong in the promotional workflow. A foreign label is evidence of that jurisdiction’s text, not automatic authority for a US claim.
Fictional review exercise
A team receives a file named “final-label-v7” and artwork using a different storage statement. First locate the actual agency correspondence and agreed text; the filename cannot settle status. Compare the storage statement with the controlled CMC evidence and labeling decision. Hold the conflicting artifact for its owner to resolve. If the task changes from an original NDA to an ANDA, add the identified reference-listed-drug baseline and an explained differences review rather than reusing the NDA rationale unchanged.
Use one package map to coordinate different writing tasks
Build the package map before dividing work between medical writing, regulatory, clinical, quality, design and publishing. Without a shared baseline, each team can produce an internally consistent file that conflicts with the others.
| Package decision | Record | Release question |
|---|---|---|
| Pathway and purpose | Actual application, product and requested action | Are these proposed claims, final implementation, an ANDA comparison or investigational material? |
| Authoritative baseline | Decision correspondence and the exact associated text | What establishes this version's status? |
| Artifact inventory | Document type, presentation, language, version and owner | Which files are required for this actual task, and which are not applicable? |
| Change dependencies | Affected passages across professional, patient and packaging material | Has the same change been assessed everywhere it matters? |
| Unresolved items | Question, source needed, owner and disposition | Is a missing input being mistaken for a negative or not-applicable conclusion? |
| Publishing handoff | Approved working source, renditions and reconciliation result | Did conversion preserve the intended content? |
Keep three dates separate: the source document's date, the submission date and the date of the actual agency decision. An internal review date is a fourth event. A file delivered later can still contain older language; chronological order alone does not establish the governing baseline.
Fictional package review: the professional label contains a proposed handling instruction, the patient document uses the prior wording, and the carton team has already treated the new instruction as approved. First establish the instruction's actual status and scientific basis. Record the proposed change in the dependent-document map, obtain the appropriate decisions and reconcile each affected artifact. Updating every file to the newest wording without that status check would spread the same unsupported assumption.
Use task-specific handoffs. The draft-labeling guide controls evidence annotations and clean text. The history guide preserves how the proposal arose. The carton/container guide assesses physical presentation. The final-package guide reconciles the release renditions. An ANDA reference comparison has its own sameness and explained-difference requirements.
Do not make the package map a new source of regulatory decisions. Its status entries should point to the decision records. If the responsible owner changes a conclusion, update both the affected files and the record explaining why. Keep review copies distinguishable from material actually submitted or implemented.
Your preparation checklist
0/2 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Does every labeling submission need every Module 1.14 document type?
No. The applicable artifacts depend on the application pathway, product and submission purpose. Establish those inputs and record why each item applies or does not apply. A catalog heading is an organizational location, not evidence that every product needs every patient-labeling, reference or investigational document.
Does a file named final establish that FDA approved its content?
No. Verify the actual agency correspondence and the exact text or attachment it concerns. Keep internal approval, submitted proposal and agency decision as separate states. A filename or later modification timestamp cannot establish which wording FDA accepted for the actual product and action.
Does valid SPL establish that the labeling package is correct?
Technical validation does not establish that the content matches the intended regulatory baseline. Compare the rendered structured content with the controlled text, including symbols, tables and dependent instructions. The publishing check and the substantive labeling review answer different questions, and both need a documented result.
Can investigational labeling or promotional support replace the professional label?
These artifacts have different purposes and governing contexts. Investigational labeling concerns study supply; promotional support concerns claims and materials in the promotional workflow. Identify the current product-label artifact required for the particular submission and keep those companion records separately identified rather than substituting one for another.
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.50: NDA content and labeling ↗Paragraphs (c)(2)(i), (e)(2) and (l). Current eCFR reopened October 6, 2026, displaying currency through October 2, 2026. Annotated proposed text and labeling copies are separate provisions.
Regulation
21 CFR 314.94: ANDA labeling ↗Paragraph (a)(8), including reference labeling, comparison and explained differences. Current eCFR reopened September 22, 2026.
Regulation
21 CFR 312.6: Investigational drug labeling ↗Paragraphs (a)–(c), including limited stockpile exception procedure. Current text checked September 22, 2026.
Guidance
FDA: Submissions of Promotional Labeling and Advertising ↗April 2022 final, Revision 1; IV.A–J, VI.E–H and VII. PDF production/PRA update April 2023 does not change the cover revision. Its legacy backbone syntax is not an eCTD v4 implementation guide. Checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.14. A heading identifies placement, not mandatory applicability.