Write Module 1 information amendments without duplicating the scientific dossier

What belongs in an FDA Module 1 information amendment?

First classify the transaction by application type and lifecycle. FDA’s eCTD v4.0 technical guide uses 1.11 for information-request responses that do not fit headings in Modules 2–5. Explain the request and response, identify affected evidence and place scientific documents in their proper headings. An IND information amendment is a regulatory transaction, not a rule that all its content belongs in Module 1.

Before you begin

Module 1.11 information-request responses outside Modules 2–5, with IND and marketing-application amendment boundaries explained separately.

What you will prepare: An amendment overview with a clear purpose, evidence map and correct neighboring submission routes.

Classify the transaction before writing the overview

For an IND, 312.31 addresses essential information outside protocol amendments, IND safety reports and annual reports. Identify the nature and purpose, organize the information for review and state whether FDA comment is requested. Do not use an information amendment to postpone a safety-reporting obligation or hide a protocol change.

For an unapproved NDA or ANDA, use the applicable marketing-application amendment process rather than importing the IND cadence. A postapproval change requires its own reporting-category assessment; calling a submission an amendment does not make a prior-approval change permissible.

Use the four administrative headings deliberately

The current v4 Technical Conformance Guide section 3.1.7 describes 1.11 for responses to FDA information requests when the response does not fit a heading in Modules 2–5. Treat that as the placement context for the following map, not permission to place every unsolicited amendment overview in 1.11. Keep the broader transaction explanation in the appropriate cover letter and place scientific documents in their subject headings.

1.11.1: Quality: explain the CMC issue raised, affected product/process and the locations of revised Module 3 evidence. A useful comparison identifies the prior and new state, affected batches or presentations, and where the quality risk assessment is supported. The manufacturing report itself belongs in its scientific location.

1.11.2: Nonclinical: identify the new study or interpretation, the development question it addresses and any effect on clinical exposure or monitoring. Point to the report and updated summaries. State limitations rather than claiming that one completed study clears every clinical risk.

1.11.3: Clinical: explain the new clinical information, the relevant protocol/population and the decision it informs. Distinguish an administrative explanation from the CSR, dataset, protocol amendment or safety report. Each has its own content and submission implications.

1.11.4: Multiple module: use an integrated change map when the transaction spans disciplines. For example, a formulation change can require quality comparability, nonclinical bridging and clinical-exposure explanation. Assign one owner to reconcile the common product identity and dates; do not paste three contradictory cover narratives.

Create a compact change-and-evidence map

An editorial outline is: application and transaction; reason for submission; change table; impact across the dossier; precise questions for FDA; attachment and cross-reference index. In the change table, pair each statement with the previous reference, revised reference, interpretation and responsible reviewer.

Where content already exists in the application, reference the actual sequence/document/version. Where a full report is newly supplied, identify its scientific placement. An absent report is an open item; it is not cured by a summary saying that the results are acceptable.

Worked review: one change spans two departments

Fictional editorial exercise: the CMC team says a new formulation was used only in stability work, but the clinical team identifies it as the material used in a new cohort. Reconcile batch and dosing records before releasing the amendment narrative. If the cohort change affects protocol or safety obligations, assess those routes independently.

Change the scenario to an already approved product: the same scientific evidence may be useful, but the submission classification must be reassessed. A missing lifecycle state prevents the writer from selecting an IND or postapproval procedure.

Make every requested answer traceable to its evidence

For a response to an FDA information request, preserve the request’s numbering and date. Use this internal matrix before assembling files; adapt it to the request rather than treating it as a required agency template.

Response exercise: FDA asks how a formulation change affects exposure. The draft replies that the stability report was updated. That identifies a change but does not answer the exposure question. Reconcile the formulation used in the relevant clinical work, identify any bridging evidence and explain its limitations. Point to the scientific documents in their correct locations and state what remains unresolved. A multi-module response needs one consistent product and batch history across its CMC and clinical explanations.

Do not duplicate a full report in 1.11 merely to make the response look self-contained. Provide the needed explanation and precise reference. Where the response itself belongs under a scientific heading, the technical guide directs that placement rather than defaulting to 1.11. Use the submission cover letter for the broader transaction purpose and document map.

For an IND, §312.31 says information amendments should be submitted as necessary and, to the extent feasible, no more frequently than every 30 days. This is not an instruction to hold urgent information until a monthly date. Protocol amendments, safety reports and annual reports remain separate categories. For an unapproved NDA or ANDA, assess §314.60 or §314.96 respectively; do not transfer the IND cadence to those pathways.

Before release, ask a reviewer unfamiliar with the drafting process to follow one request through the answer, evidence and affected summary. If the reviewer reaches two incompatible product versions, resolve the scientific record rather than rewriting the overview to conceal the conflict.

Frequently asked questions

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Related guides