On this page
How do you document an FDA application name, address or contact change?
Prepare a dated before-and-after record identifying the application, changed value, affected role and effective date. Establish whether the legal entity continues and verify any representative’s authority. Reconcile the notice with forms and submission contacts, and separately assess ownership, licensing, labeling or manufacturing consequences rather than describing every change as administrative.
Before you begin
Administrative changes for an identified FDA human-drug or biologic application. A physical manufacturing-site move requires its own regulatory assessment.
What you will prepare: A dated change notice, reconciled forms and contact metadata, with authority and scope documented.
Sections covered in this guide (2)
Prove whether the same entity continues
Ask the corporate or legal owner for the prior and new legal names, addresses, effective date and whether the entity itself changes. A trade name is not a substitute for legal identity. Record which applications are affected and whether product ownership, establishments or labeling also change.
For a true transfer, use the ownership or sponsor-transfer workflow. For CBER licenses, SOPP 8403 §V.G provides a reissuance process for relevant name/ownership changes. Do not assume an administrative notice changes a license automatically. A new office address and a new manufacturing location are separate facts with potentially different submission consequences.
Write the notice and update each contact role
Editorial notice outline: application and product; type of change; prior value; replacement value; effective date; legal-entity continuity or separately referenced transfer; affected role; scope of authorized representation; attachments supporting authority; contact for questions. Keep sensitive personal details limited to the actual regulatory need.
For a contact or agent change in 1.3.1.2, identify whether the person is the regulatory contact, technical contact or U.S. agent. The v4 technical guide §2.3.3 distinguishes these roles and calls for updates as necessary. Compare the letter with current Form 1571 or 356h, relevant correspondence and publishing metadata. Do not infer a general right to make regulatory commitments merely because someone can transmit files.
Worked check: the address hides a site move
Fictional exercise: a notice describes “address correction,” but the CMC owner confirms that manufacturing moves to another building. Keep the factual administrative correction, and initiate the separate site-change assessment before characterizing the entire event as administrative. If only the office postal address changes, do not create an unsupported manufacturing-change claim.
The final reviewer should be able to reconstruct what changed, when it changed and what remained unchanged from controlled records. Where an agent’s appointment is missing, request it; do not substitute the publishing account owner’s name.
Reconcile the old value, replacement and authority
Use a change register before drafting the notice. This is a preparation aid; it does not prescribe a universal attachment package.
| Item | Record together | Inconsistency to resolve |
|---|---|---|
| Legal identity | Old name, new name and evidence of continuity | Trade name used where the legal entity is needed |
| Address | Old/new addresses and the function of each location | Office move described as if it were a manufacturing change, or the reverse |
| Person and role | Regulatory contact, technical contact or U.S. agent | A transmission account treated as general authority to act |
| Timing | Effective date and transition arrangements | Old contact disabled before the new route is usable |
| Affected records | Application forms, correspondence and metadata | Correct notice paired with stale submission contacts |
Write the first paragraph around the exact change: identified application → affected entity or role → prior value → replacement → effective date. Put the explanation of continuity or separately handled transfer immediately after it. Avoid a broad sentence saying that “all details are unchanged” unless the responsible owners have actually checked the relevant details.
Transition exercise: a technical contact changes, but the regulatory contact remains responsible for FDA questions. Reconcile both fields separately. Test the new technical communication route through the organization’s process and preserve any needed access to prior correspondence. Do not replace both contacts simply because a template uses one shared name.
If continuity is unresolved, return to the administrative change plan. If rights moved, use the ownership and licensing guide. Describe any unresolved authority or site-change question as an open action, with an owner, before the notice is approved.
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
Does changing a company’s legal name always transfer application ownership?
No. A name change may leave the same legal entity in place, while a transfer changes the holder of application rights. Obtain the continuity evidence and apply the appropriate process. For CBER licenses, even a name change can require a licensing action under the relevant staff procedure.
Are the regulatory contact, technical contact and U.S. agent interchangeable?
No. The v4 technical guide identifies separate contact roles for regulatory communication, technical submission issues and U.S. representation. One person may have more than one authorized role, but a shared name or publishing account does not establish that scope. Confirm and update each relevant role.
Can a manufacturing-site move be handled only as an address correction?
Do not classify it from the postal change alone. Establish what activity moves and have the relevant regulatory owner assess the manufacturing change. The administrative notice can state accurate address facts, but it does not establish permission to implement a change to approved manufacturing conditions.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Technical specification
FDA eCTD v4.0 Technical Conformance Guide ↗Version 1.5, June 2026; §§2.3 and 3.1. Exact cover and revision history checked September 22, 2026. Version-specific technical recommendations.
Regulation
21 CFR Part 312: IND responsibilities and status ↗Current part reopened September 22, 2026; relevant provisions identified in each section. Regulatory requirements, not a marketing-application rule.
Regulation
21 CFR Part 314: drug marketing applications ↗Current part reopened September 22, 2026; §§314.50, 314.53, 314.65, 314.72, 314.94, 314.99, 314.108 and 314.150–162 inspected. Not a general BLA rule.
FDA resource
CBER SOPP 8403: issuance, reissuance and voluntary revocation ↗Version 6, effective February 27, 2023; §V.C–G. CBER staff procedure, not an independent applicant regulation. PDF reopened September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.3.1.1. A heading identifies placement, not mandatory applicability.