Regulatory Submission Strategy & Planning
A submission is the point where every other function is asked to produce evidence at the same time. The plan is what decides whether that arrives as an integrated argument or as a pile of documents written to a deadline. The structure is settled — ICH M4 defines the Common Technical Document, ICH M8 defines the electronic specification — so the difficulty is never the format. It is dependency, ownership and readiness.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 22 LINKSA submission is an argument assembled from work done years earlier, so the planning question is not how to write it but what evidence the argument will need — decided while that evidence can still be generated.
06 · QUALITY MATURITY — REGULATORY SUBMISSION STRATEGY & PLANNING, REACTIVE TO ADAPTIVE
The submission is compiled at the end from whatever exists. Gaps are discovered during assembly, when nothing can be done about them.
A plan and a timeline exist, but they describe document production rather than the evidence the argument rests on.
The target label drives the plan: each claim is traced to the study or data that will support it, and gaps are visible while they are still fixable.
Content is generated in submission-ready form as work completes, and lifecycle maintenance is planned alongside the initial filing rather than after it.
The dossier is a maintained asset rather than an event: variations, market extensions and post-approval change reuse a structure that was built to be reused.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 5
Derived from the 5 standards SPEQ maps to this subject, across 3 regulatory bodies: FDA, ICH, EC.
RECORDS & OBJECTIVE EVIDENCE
- The target product profile or intended label, and the claims it commits to
- A traceability map from each claim to the evidence intended to support it
- The submission plan with content ownership and readiness status
- Document control arrangements ensuring the filed version is identifiable
- The lifecycle maintenance plan for variations and market extensions
COMMON INSPECTION FINDINGS
- Evidence gaps discovered at compilation, when the studies that would close them are finished
- Claims in the label with no traceable supporting evidence in the dossier
- Uncontrolled versions, so which document was actually filed cannot be established
- Regional differences handled by ad hoc rework rather than by a planned structure
- No maintenance plan, so the first variation restarts the assembly effort
The CTD is a format agreement, and that is its value
ICH M4 organises a marketing application into five modules: Module 1 regional administrative information, Module 2 the summaries, Module 3 quality, Module 4 nonclinical study reports, Module 5 clinical study reports. Only Module 1 is regional; Modules 2 to 5 are common across the ICH regions. M4 says where information goes; M4Q, M4S and M4E say what the quality, safety and efficacy content should contain.
That separation is what makes a cross-region submission plan possible at all. It does not make the dossier portable — regional Module 1 differs, and national requirements attach — but it means a single content plan can serve multiple filings, which is the whole basis of a global regulatory strategy.
Module 2 is where the organisation becomes visible
Module 2 is written from Modules 3 to 5. The Quality Overall Summary describes what Module 3 contains; the Clinical Overview argues benefit-risk from what Module 5 shows. It is therefore an integration activity, not a summary-writing task, and it is where inconsistency between functions becomes visible to a reviewer — a specification in the Quality Overall Summary that does not match Module 3, a benefit-risk argument that the clinical data does not quite support.
Teams schedule Module 2 as though it were the last thing written and the easiest. It is the last thing written and the hardest, because it is the only place the whole dossier has to agree with itself. Scheduling it as an integration gate, with someone other than the authors assessing whether the content supports the claim, is the single highest-return change to most submission plans.
Plan by dependency, measure by readiness
The recurring planning failure is a content plan that lists documents and dates but not the dependencies between them. A study report that slips silently blocks the summary that must describe it, the specification justification that cites it, and the benefit-risk argument that rests on it — so a single amber item is actually four, and the critical path is discovered late.
The second failure is measuring readiness by document count. A module at ninety per cent of its documents can be nowhere near ready if the missing ten per cent is the pivotal study report. Readiness criteria should be stated per module in terms of whether the content supports the claim being made, and assessed by someone other than the author — because authors assess their own drafts generously and consistently.
Publishing is not an administrative step
ICH M8 specifies the electronic submission: how documents are packaged, identified, versioned and replaced across sequences. Version 4.0 is built on HL7 Version 3 Regulated Product Submission Release 2, and its implementation package — implementation guide and controlled vocabularies, versioned separately since May 2024 — carries the validation criteria a submission must pass.
Adoption is staged and regional. FDA began accepting eCTD v4.0 voluntarily in September 2024 with mandatory use projected later, and EU implementation guidance has followed its own timeline, so organisations should plan for a period of running both formats rather than a clean cutover. The practical discipline is to rehearse technical validation against the target authority before the real dispatch — publishing is treated as the administrative step at the end and then becomes the actual bottleneck.
SPEQ interpretation — the lifecycle outlives the filing
Submission planning is usually organised around a filing date, and then the machinery is stood down. But the eCTD lifecycle operations — how a document is replaced, appended or deleted across sequences — are what determine, years later, whether anyone can show what was actually filed and what was actually approved. An archive that captures what was sent but not what came back leaves current registration status to be inferred rather than read.
So the useful test of a submission plan is not whether it hit the date. It is whether, three years and forty sequences later, the organisation can answer what the approved position is for a given market without reconstructing it. That is a records-architecture question posed at planning time, and almost nobody poses it then.
FREQUENTLY ASKED
What are the five CTD modules?
Module 1 is regional administrative information and is not common across regions. Module 2 holds the summaries — the Quality Overall Summary, Nonclinical Overview and Summaries, and Clinical Overview and Summary. Module 3 is quality, Module 4 nonclinical study reports, Module 5 clinical study reports. ICH M4 defines the organisation; M4Q, M4S and M4E define what the content should contain.
What is the difference between CTD and eCTD?
The CTD (ICH M4) is the structure — which content goes in which module. The eCTD (ICH M8) is the electronic specification for transmitting that structure: the message standard, controlled vocabularies, lifecycle operations and validation criteria that make the submission machine-processable. One is what you write, the other is how it is packaged and sent.
Is eCTD v4.0 mandatory yet?
Not universally. FDA began accepting eCTD v4.0 on a voluntary basis in September 2024, with mandatory use projected for later, and other regions are following their own implementation timelines. The planning consequence is a transition period in which both formats are in use, so a submission strategy should assume both rather than a single cutover date.
How should submission readiness be measured?
By whether the content supports the claim being made, assessed per module by someone other than the author — not by document count. A module at ninety per cent of its documents is not ninety per cent ready if the missing piece is the pivotal study report everything else cites.