On this page
What is an eCTD field-copy certification letter?
For marketing applications under FDA’s eCTD v4 technical guide, it is a copy of the letter notifying the district office of the planned eCTD submission. Identify the drug and application, FDA center and division, and eCTD format. The described process uses FDA network access instead of a separate field copy of the dossier.
Before you begin
Marketing applications within FDA eCTD v4 technical-guide §3.1.8. Confirm the applicable format/version and field-office routing; this is not an IND requirement.
What you will prepare: A factual notification letter and retained evidence of the appropriate handoff.
Understand what the certification represents
The technical guide says that, for marketing applications, the field-copy certification is a copy of a letter notifying the district office of the planned eCTD submission. Because field offices can access the complete submission on FDA’s network, an individual field copy is no longer required in this described process.
Do not write that a physical copy was supplied if no such action occurred. Equally, the absence of a physical dossier does not eliminate the notification described in §3.1.8. The heading’s word “certification” is not a request to certify scientific adequacy or FDA acceptance.
Write the actual notification
The specified content is the drug and application number, FDA center and division, and the statement that the application is in eCTD format. Add the responsible contact and intended submission identity so that the recipient can reconcile the notice. Confirm the appropriate field-office contact through the organization’s regulatory process before transmission; a historical template address may no longer be correct.
Fictional working excerpt: “This notice concerns [confirmed drug], [confirmed NDA number], submitted to [center/division] in eCTD format.” Replace every bracket with an approved factual value. Retain the final letter in 1.3.2 and the operational handoff record. Do not write “FDA has received” while the publishing team is still preparing the sequence.
Change the application type before reusing the letter
Fictional exercise: a team copies the packet into an initial IND because the catalog contains 1.3.2. The cited recommendation expressly addresses marketing applications; the heading alone does not establish an IND obligation. Record that the specific marketing recommendation is not applicable to that scenario and assess any separate FDA instruction actually received.
If the format is not v4, inspect the supported technical specifications for the actual format. Preserve the distinction between content recommendations and submission transport.
Keep the notice, delivery evidence and submission state distinct
Prepare a small notification record before placing the final letter in section 1.3.2. It connects the content of the notice with what actually happened.
| Item | Confirm from | Avoid this unsupported statement |
|---|---|---|
| Application identity | Final application and product record | A previous template’s number identifies this package |
| Center and division | Confirmed receiving organization | The product name alone proves the destination |
| Field-office route | Current contact confirmed through the regulatory process | A historical district-office address is still correct |
| Notice state | Approved letter and actual transmission record | A saved draft was sent |
| Submission state | Publishing and receipt records | FDA received an application that is still being assembled |
Use precise status language internally: drafted, approved for sending, sent, and receipt recorded, where evidence supports the status. These are working labels, not FDA receipt categories. Identify the person responsible for each remaining action and retain the exact version of the notice that was transmitted.
Sequence exercise: the notice was sent, but the application number is corrected before the eCTD package is finalized. Reconcile the notice and package with the regulatory owner, decide how the recipient will receive the correction, and retain the corrected communication. Simply replacing the local letter leaves the external recipient with the earlier information.
The technical guide describes marketing applications and v4. Do not derive an IND requirement from the presence of a catalog heading, or assume the same technical directions apply to every supported format. Cross-check the transaction against the submission cover letter and use the administrative information guide to record the scope decision.
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 field-copy certification mean sending a second physical dossier?
Not in the marketing eCTD process described by section 3.1.8 of the v4 technical guide. It describes notifying the district office and retaining a copy of that letter in the application; field offices can access the submission on FDA’s network.
Does the field-copy heading create an IND notification requirement?
No. The cited technical-guide recommendation expressly addresses marketing applications. The existence of section 1.3.2 in the catalog does not extend that recommendation to an IND. Check the actual submission context and any separate FDA direction before assigning a notification task.
Does a field-copy certification prove that FDA accepted the application?
No. The letter notifies the office of a planned electronic submission; it is not an acceptance decision. Keep the notice, transmission evidence and actual application receipt or agency action distinct. Its inclusion in the dossier does not prove a later event occurred.
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.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.3.2. A heading identifies placement, not mandatory applicability.