On this page
What belongs in an FDA eCTD v4.0 labeling history?
Section 3.1.4 of the June 2026 technical guide describes one PDF summarizing the current proposed changes and reasons, the last approved labeling date, intervening changes with their originating submissions and rationale, and pending supplements that may affect review. Build that record from actual submissions and decisions, keeping proposed, approved and implemented states distinct.
Before you begin
Labeling history preparation using section 3.1.4 of the June 2026 FDA eCTD v4.0 Technical Conformance Guide. Verify the applicable electronic version and product instructions; the editorial table below is not an FDA form.
What you will prepare: A chronological, evidence-linked change record that distinguishes proposals, decisions and implementation.
Include the complete labeling-history record
For the v4.0 workflow, section 3.1.4 recommends one PDF containing the current proposed changes and reasons, the most recent labeling approval date, every intervening change linked to its originating submission and rationale, and pending supplements relevant to this review. Reconcile the submission tracker against the history before export. An original application without prior approved labeling must identify that context, not invent an approval date. If a pending supplement changes the same passage, make the dependency visible rather than showing only the latest proposal.
Reconstruct the record from authoritative artifacts
Gather prior submissions, agency correspondence, approved or agreed text and the current proposal. Record document dates separately from submission dates and effective implementation dates. A filename or internal approval timestamp cannot establish FDA acceptance. When a version is missing, mark the interval as unresolved and ask the regulatory owner for the actual record.
Write a history that explains decisions
| Event | Evidence | Change and rationale | Status | Current consequence |
|---|---|---|---|---|
| Agency comment | Dated letter and item | Requested change to a defined passage | Received | Response needed |
| Sponsor response | Submitted file and sequence | Revised text and supporting source | Proposed | Awaiting disposition |
| Agreed baseline | Actual decision record | Accepted version or instruction | Verified state | Baseline for next comparison |
Use actual statuses rather than assuming every later submission supersedes every earlier one. Link each change to the affected section and carry unresolved items into the current issues list.
Fictional example: an unaccepted proposal
Version 4 adds a population statement, but the only agency letter concerns version 3. The history should say version 4 was proposed and identify the pending question. It must not say the expansion was approved. If the current package removes that proposal, explain the withdrawal of the proposed wording and verify that no dependent leaflet still contains it.
Track the consequence of each change, not only its date
A chronological list is useful only if the reviewer can see how earlier events affect the current proposal. Give each change a stable identifier and connect it to a passage, source event and current disposition.
| History entry | Record | Current-review question |
|---|---|---|
| Last approved baseline | Actual approval date and exact labeling version | Is the comparison starting from the correct text? |
| Intervening submission | Submission identifier/date and originating change | Where was this proposal first described? |
| Change and reason | Affected passage, before/after wording and rationale | What changed and why? |
| Agency disposition | Correspondence and the specific item addressed | Was this change accepted, rejected, modified or still unresolved? |
| Pending supplement | Identifier and overlapping passage or dependency | Could its outcome change the current review? |
| Current proposal | Retained, revised or withdrawn changes | Does the history agree with the clean and annotated files? |
Fictional overlap exercise: one pending supplement proposes a population change and another proposes a related instruction. The current label assumes both have been approved, but only one decision exists. Show the two submissions separately, preserve each actual status and identify the overlapping text. Ask the regulatory owner to resolve how the current proposal should represent the dependency. Do not make a later sequence number stand in for an agency decision.
For an original application without previously approved labeling, state that context. Leave no ambiguous blank that could mean either “not applicable” or “missing approval record,” and do not invent a date merely to populate the table. Where a historical attachment is missing, name it and preserve the unresolved consequence until the source is recovered.
The history is not the same as a word-processing revision log. Internal edits can explain drafting activity but do not establish what was submitted or accepted. Likewise, the history does not replace the annotated support for the current proposal. Keep the draft-label evidence record and the agency decision trail linked.
Before exporting the single history PDF described by the v4.0 technical guide, reconcile it with the submission tracker and the actual label comparison. Check that every current material change appears, that withdrawn proposals no longer survive in dependent artifacts, and that pending supplements have not disappeared from the account. Verify the technical version for the actual submission rather than treating v4.0 instructions as universal backbone syntax.
Use the final-package review to record the later release and implementation decisions. Those events should remain distinct from both the sponsor proposal and FDA's labeling decision.
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
Is a tracked-changes document enough to serve as the labeling history?
It can help show textual differences, but the v4.0 technical guide also describes reasons, the last approved date, originating submissions for intervening changes and pending supplements affecting review. Assemble that decision context in the history rather than assuming a redline contains it all.
Must pending supplements be included when they may affect the current labeling review?
Yes, the June 2026 v4.0 technical guide includes them in the recommended history content. Identify the supplement and its relevant dependency. Do not present the proposed outcome as approved or omit the pending change simply because it belongs to a different submission sequence.
What date should an original application use when no labeling has been approved?
Do not invent an approval date. State that there is no prior approved labeling for this application and identify the actual proposed baseline. Keep that situation distinct from an existing application whose approval record is missing and needs to be recovered.
Does the latest submission automatically supersede every earlier labeling decision?
A later submission establishes what was proposed at that time, not automatically what FDA accepted. Trace the actual decision and affected passages, including unresolved overlapping supplements. The history should explain the current consequence of each event rather than assigning approved status solely by chronological order.
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.
Technical specification
FDA eCTD v4.0 Technical Conformance Guide ↗Version 1.5, June 2026; section 3.1.4 labeling history. Cover, revision table and operative passage checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.14.1.5. A heading identifies placement, not mandatory applicability.