Written and maintained by CASRAI Editorial Board
Published
On this page
ICH M4Q is the quality part of the Common Technical Document (CTD), the harmonised format in which pharmaceutical quality information is organised for registration applications; M4Q(R2) is its first major revision, which reorganises Module 2.3 and Module 3 around materials and lifecycle management rather than the older drug substance and drug product headings. As of 17 November 2026 M4Q(R2) is a draft at ICH Step 2: it was endorsed on 14 May 2025, its public consultation has closed, and FDA lists it as draft guidance that is not for implementation. Applications continue to follow the current M4Q(R1) structure until regulators announce otherwise.
What ICH M4Q is and who runs it
The International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) develops the CTD guidelines. The M4 family covers the organisation of the CTD, and M4Q is the quality component: it fixes where chemistry, manufacturing and controls (CMC) information sits in an application. The background concept is covered in the ICH M4 Common Technical Document term, and the electronic wrapper is described under eCTD.
The M4Q(R2) work is led by an ICH Expert Working Group. Its work plan dated 10 July 2026 names Dr Lawrence Yu (FDA) as rapporteur and Dr Hugo Hamel (Health Canada) as regulatory chair, and records that the proposal was endorsed in May 2020 and the Step 2a draft in May 2025. FDA hosts the draft text and runs its own comment docket for it (FDA-2025-D-2275, CDER and CBER).
Scope: what M4Q(R2) covers
The draft states that it establishes the location and structure of quality information for registration applications of all medicinal products for human use. It applies to initial marketing applications and to post-approval submissions, and it supports master files. Sections that do not apply to a product are left out, and the examples in the text are illustrative rather than requirements.
FDA describes the purpose as improving the efficiency of registration and lifecycle management, supporting digitalisation and knowledge management, and providing for emerging technologies. The draft text itself names advanced manufacturing, structured data management, artificial intelligence and machine learning, and bioinformatics among the emerging concepts that more granular sections are meant to accommodate. A stated aim is a single M4Q(R2) dossier that can be used across regions; region-specific information goes in the relevant section only where it is legally unavoidable.
What M4Q(R2) changes: the new structure
Three layers instead of two
Under M4Q(R2) the quality information is organised across three layers that are written to be complementary:
- Module 2.3.3 Core Quality Information (CQI): the core quality content for each material.
- Module 2.3.4 Development Summary and Justification (DSJ): the development story and the justification for the choices made.
- Module 3.2 Body of Data: the repository for detailed descriptions of methods, data and other quality information that supports Module 2.3.
The draft describes Module 2.3 as the basis for regulatory assessment and lifecycle management, and Module 3 as the supporting repository. It also states that Module 2.3 does not supersede regional post-approval change requirements. Module 2.3 additionally carries 2.3.1 General Information, 2.3.2 Overall Development and Overall Control Strategy (including the quality target product profile and a representation of the overall control strategy), 2.3.5 Product Lifecycle Management, and an optional 2.3.6 Product Quality Benefit Risk.
Material-based organisation
The most visible change is in the headings. In M4Q(R2) the sections are organised by material, using two-letter codes such as DS for drug substances and DP for drug products, and each material section is built from the same four elements: Description, Manufacture, Control and Storage. Analytical Procedures (AP) and Facilities (FA) use different headers. Section headers can carry keywords: those in parentheses are mandatory and those in square brackets are optional. The Module 3 body of data in the draft uses headings such as 3.2.DS and 3.2.DP and does not use the 3.2.S and 3.2.P lettering that readers of M4Q(R1) are used to. For a walk through of the current tree, see the CASRAI guide to eCTD Module 3 quality information.
The data table below lists the material codes in the draft, their names, and in which of the three layers each code has a section heading in the draft’s table of contents.
Product lifecycle management in Module 2.3.5
Section 2.3.5 turns lifecycle management into a defined part of the dossier. It has a change summary and justification (2.3.5.1), a Product Lifecycle Management (PLCM) document (2.3.5.2) and a place for post-approval change management protocol (PACMP) content (2.3.5.3). The PLCM document follows ICH Q12 and can include Established Conditions (ECs), reporting categories for changes to ECs, PACMPs and post-approval CMC commitments. The draft is explicit that identifying ECs in the core quality information is not mandatory unless a regional requirement says so, that ECs can be listed in tabular form or by unambiguous reference, and that stating reporting categories is optional, with regional guidelines applying otherwise. Post-approval quality commitments are to be listed in a table and updated over the product lifecycle. A change summary gives the nature of the change, a table comparing present and proposed content with the CTD sections updated, and the justification.
Links to other ICH quality guidelines
The draft ties its development summary to other ICH guidelines rather than restating them. For example, the analytical procedure development section (2.3.4.AP.3) refers to ICH Q14, and the lifecycle section builds on ICH Q12. The table below sets out how these related guidelines relate to the revision.
| Guideline | Connection to M4Q(R2) in the draft | CASRAI page |
|---|---|---|
| ICH Q12 | Source of the PLCM document, Established Conditions and PACMP concepts used in 2.3.5 | — |
| ICH Q14 | Referred to by 2.3.4.AP.3 Analytical Procedure Development | ICH Q14 guide |
| ICH Q2(R2) | Companion guideline on validation of analytical procedures; the draft holds analytical procedures in its AP sections | ICH Q2(R2) guide |
Eligibility and who it applies to
There is no eligibility test: M4Q(R2) is a content and structure standard for applicants, not a programme with entry criteria. When adopted it is intended to apply to the quality section of registration applications for all medicinal products for human use. Whether, how and when it is applied in a given region depends on that regulator’s implementation. For now FDA states that the guidance is a draft, not for implementation, and accepts comments at any time under 21 CFR 10.115(g)(5). FDA has noted that its copy of the draft is left in ICH format and that a final version will be reformatted.
How to prepare while it is a draft
The steps below are preparation, not compliance requirements, because the text can still change.
- Keep submitting in the current structure. Nothing in the draft changes what applicants must file today.
- Map your current content. ICH published a mapping of M4Q(R1) to M4Q(R2) in December 2025 and a mock example in November 2025, according to its work plan; they show where existing 3.2.S and 3.2.P content would land.
- Identify the information that becomes Core Quality Information. Decide which statements are the core content for each material and which belong in the development summary or the body of data.
- Review lifecycle assets. If you maintain Established Conditions, comparability protocols or post-approval commitments, note where 2.3.5 would hold them.
- Follow regional announcements. Comment through the regulator’s docket where one is open, and watch the regional implementation notices after adoption.
Typical timeline phases
ICH guidelines move through numbered steps: a draft is endorsed (Step 2), consulted on by the regions, revised after consultation, then signed off (Step 3) and adopted (Step 4), after which each region implements it. The M4Q(R2) work plan dated 10 July 2026 shows the following phases, with future items described as anticipated in that plan and subject to change.
| Phase | What the work plan records |
|---|---|
| Proposal | New topic endorsed May 2020 |
| Draft endorsement (Step 2a) | Endorsed May 2025 |
| Supporting material | Mock example November 2025; mapping of M4Q(R1) to M4Q(R2) December 2025; Q&A deliverable April 2026 |
| Public consultation | Completed March 2026, with over 2,500 comments |
| Revision after consultation | June 2026: the working group agreed proposed revisions to 2.3.1, 2.3.2, 2.3.3, 2.3.5 and 2.3.6; review and resolution of public comments anticipated November 2026 |
| Sign-off and adoption | Step 3 sign-off and Step 4 adoption anticipated June 2027 |
The same plan lists a face-to-face working group meeting in Prague in December 2026, including a proposal from the Implementation Working Group. Implementation timing is set by each regulator after Step 4.
Common mistakes
- Treating the draft as in force. FDA marks it not for implementation; submissions still follow the current structure.
- Looking for 3.2.S and 3.2.P in the new text. M4Q(R2) uses material codes, so a direct heading-for-heading match to M4Q(R1) does not exist; use the ICH mapping instead.
- Assuming Established Conditions are now compulsory. The draft says identifying them in the core quality information is not mandatory unless a regional requirement says so.
- Treating Module 2.3 as a copy of Module 3. The draft assigns the summary layers and the body of data different jobs, and says Module 2.3 does not supersede regional post-approval change requirements.
- Quoting a final date as fact. Step 4 timing is only anticipated in the work plan.
Sources
- ICH M4Q(R2) Draft, Step 2 text, hosted by FDA (read 17 November 2026)
- FDA guidance page: M4Q(R2) Common Technical Document for the Registration of Pharmaceuticals for Human Use, Quality (read 17 November 2026)
- ICH M4Q(R2) Expert Working Group work plan, 10 July 2026 (read 17 November 2026)
- Docket FDA-2025-D-2275 for the draft guidance, as listed on the FDA guidance page
Data: ICH M4Q(R2) draft: material codes and the CTD layers where each has a section
Compiled from the table of contents of the ICH M4Q(R2) Step 2 draft (hosted by FDA): each material code with its name and whether the draft has a section for it in Module 2.3.3 Core Quality Information, Module 2.3.4 Development Summary and Justification and Module 3.2 Body of Data.
Period covered: 2025/2026.
| Material code and name | In 2.3.3 CQI | In 2.3.4 DSJ | In 3.2 Body of Data |
|---|---|---|---|
| DS Drug Substances | Yes | Yes | Yes |
| SI Substance Intermediates | Yes | No | Yes |
| SM Starting/Source Materials | Yes | Yes | Yes |
| RM Raw Materials | Yes | No | Yes |
| EX Excipients | Yes | No | Yes |
| RS Reference Standards and/or Materials | Yes | Yes | Yes |
| IM Impurities | No | No | Yes |
| DP Drug Products | Yes | Yes | Yes |
| PI Product Intermediates | Yes | No | Yes |
| MD Medical Devices | Yes | Yes | Yes |
| PM Packaged Medicinal Products (multiconstituent products) | Yes | Yes | Yes |
| PH Pharmaceutical Product after transformation | Yes | Yes | Yes |
| AP Analytical Procedures | Yes | Yes | Yes |
| FA Facilities | Yes | No | Yes |
Sources
- ICH M4Q(R2) Draft Step 2 text (hosted by FDA) (accessed 2026-11-17)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







