On this page
What belongs in CTD 3.2.R regional information?
Include quality information applicable to the specific authority, product and submission context, supported by a current requirement, guidance, request or agreed plan. M4Q’s regional examples are not a universal checklist. Distinguish the reason an item is needed from the electronic heading where it is placed.
Before you begin
FDA-focused use of M4Q(R1) 3.2.R. Individual deliverables require current pathway-, product- and lifecycle-specific authority.
What you will prepare: A documented regional-content decision with a source, trigger, owner and intended destination for each included or unresolved item.
Identify the current reason for each proposed regional item
M4Q presents regional information as material specific to the relevant region. Its examples include U.S. executed batch records, method-validation packages and comparability protocols; these examples do not establish that every FDA application or sequence requires all three. Nor do examples identified for the EU automatically apply to an FDA dossier.
Start with the application pathway, product class, submission purpose and lifecycle stage. Collect applicable current guidance, regulations, agency correspondence or an agreed request that establishes why an item is being considered. Record the exact source passage and its force. If the only support is the existence of the R heading, applicability is undetermined and needs regulatory-owner review.
Prepare the item according to its own purpose
For an executed-record request, identify the actual batch, process version and requested record scope; reconcile with P.3/S.2 and batch analyses. Do not substitute an unexecuted master record while calling it executed. For a method-validation package, reconcile the method version and underlying data with S.4 or P.5 so the regional package does not contradict the main control narrative.
For a proposed comparability protocol, establish the particular change, assessment strategy and applicable regulatory route with the responsible owner. Distinguish a proposal from an agreed protocol and from executed change evidence. This page is a preparation and applicability guide; it intentionally does not supply a universally valid protocol or filing category.
Worked review: an old checklist imports a foreign regional item
Fictional exercise: a global template marks the EU example “process validation scheme” as required in an FDA R section. No current FDA source or request is attached.
Remove the unsupported requiredness assertion from the working map, identify the actual FDA submission context, and have the regulatory owner determine the needed content and placement. Preserve relevant validation evidence in its appropriate technical section while resolving the regional question. Record the decision and authority; do not delete useful evidence merely because the inherited checklist was wrong.
Use the displayed FDA v4 hierarchy for placement and the applicable source for content obligations. The two layers answer different questions. A correct electronic destination cannot cure an unsupported regional applicability claim.
Record the authority behind each regional item
Use this editorial decision record before commissioning a regional document. It prevents a global template from becoming an unsupported local requirement.
| Decision field | Record explicitly | Failure prevented |
|---|---|---|
| Region and authority | Actual destination of the submission | Foreign examples applied without assessment |
| Context | Pathway, product class, purpose and lifecycle stage | An original-application item copied into every sequence |
| Basis | Exact current source, agency request or agreed scope | Requiredness inferred solely from a heading |
| Document status | Proposed, agreed, executed or otherwise defined | A planned protocol presented as completed evidence |
| Technical relationship | Relevant S/P section and source version | Regional material contradicting the main quality account |
Review exercise: the team has an unexecuted master record, but a request concerns an executed batch record. Identify the record needed and the specific batch before assembling the response. A matching document title cannot make the master record evidence of manufacturing that occurred.
If an item is judged not applicable, retain the reason and authority in the preparation record. Do not delete useful technical evidence merely because its proposed regional placement was wrong; route it to the appropriate section after the applicability decision.
Coordinate manufacturing and analytical controls where the regional package relies on those records. Keep the regional decision separate from M4Q(R2) readiness: a proposed future structure is not the basis for a current filing obligation.
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
Are all regional examples in M4Q mandatory for every FDA submission?
No. The examples do not establish universal applicability to every product, pathway or submission sequence. Identify the current source or request supporting an item in the actual context. If that basis is missing, treat applicability as unresolved rather than as a mandatory default.
Can an EU regional checklist be reused unchanged for FDA?
No. Preserve useful technical evidence but reassess each regional item against the FDA submission context and its current basis. A common CTD structure does not make all regional content interchangeable. Record the authority and rationale behind the resulting document and placement decisions.
Is a proposed comparability protocol the same as executed change evidence?
No. A proposal describes a planned assessment approach, while executed evidence documents work performed and its results. An agreed protocol has a distinct status as well. Name the actual status and applicable route instead of implying that the existence of a protocol demonstrates a completed change.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Guidance
ICH M4Q(R1): CTD Quality ↗Step 4, September 12, 2002; Module 3, printed pages 5–18. Organization/content guidance, not a universal list of required studies. Checked September 22, 2026. Guide-specific passages: Module 3 scope and 3.2.R, printed pages 5 and 17–18.
Technical specification
FDA eCTD v4.0 headings and hierarchy ↗Version 2.2, February 2025, printed pages 5–6; electronic placement only. Checked September 22, 2026.
Draft guidance
FDA M4Q(R2) draft status ↗January 2026, Draft Level 1, not for implementation. This preview does not switch dossiers to the proposed structure. Checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 3.2.R. A heading identifies placement, not mandatory applicability.