This is a ready-to-use traceability matrix confirming that every claim made in the Quality Overall Summary’s process validation content, 2.3.S.2.5 and 2.3.P.3.5, is fully and accurately supported by Module 3, and that Module 3 contains nothing load-bearing that the QOS silently omits. Run it before a filing goes to final QA and regulatory sign-off. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows.
Document control header
| Field | Entry |
|---|---|
| Document title | QOS-to-Module-3 Traceability Matrix for <<FILL: product, submission type and number>> |
| Document number | <<FILL>> |
| Version | <<FILL>> |
| Review date | <<FILL>> |
| Reviewer(s) | <<FILL>> |
1. Purpose
This matrix maps every validation claim stated in the Quality Overall Summary’s 2.3.S.2.5 and 2.3.P.3.5 to the specific Module 3 content that supports it, so a reviewer moving between the two never finds a QOS statement Module 3 cannot back up, and so nothing genuinely load-bearing in Module 3 is missing from the summary a reviewer reads first.
2. Scope
Applies to <<FILL: submission type, e.g. original BLA, supplement>> for <<FILL: product>>, covering the drug substance and drug product process validation content in both the Quality Overall Summary and Module 3.
3. Method
Read the QOS’s S.2.5 and P.3.5 content sentence by sentence. For each distinct claim, batch count, conclusion, statistical basis, deviation disclosure, or Stage 3 commitment, locate its exact supporting content in Module 3 and record the cross-reference. Then read Module 3’s own S.2.5 and P.3.5 content and confirm every genuinely load-bearing point, anything that would change the conclusion if it were missing, is at least gestured at in the QOS; a QOS that omits a real deviation or a materially qualified conclusion is a disclosure gap, not an acceptable compression.
4. Traceability matrix
| # | QOS claim (2.3.S.2.5 / 2.3.P.3.5) | Module 3 support (3.2.S.2.5 / 3.2.P.3.5 section and location) | Fully supported? | Notes |
|---|---|---|---|---|
| 1 | <<FILL: e.g. validation approach and batch count statement>> | <<FILL>> | <<FILL: Yes/No>> | <<FILL>> |
| 2 | <<FILL: e.g. PPQ conclusion sentence>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 3 | <<FILL: e.g. reference to Stage 3 CPV commitment>> | <<FILL>> | <<FILL>> | <<FILL>> |
| 4 | <<FILL: e.g. reference to a comparability or flexibility-guidance basis>> | <<FILL>> | <<FILL>> | <<FILL>> |
Add one row per distinct claim; a QOS paragraph of two or three sentences typically yields three to five rows.
5. Reverse check: Module 3 content not reflected in the QOS
| # | Module 3 content | Is it load-bearing for the conclusion? | Reflected in QOS? | Action |
|---|---|---|---|---|
<<FILL>> | <<FILL: e.g. a disclosed PPQ deviation and its resolution>> | <<FILL: Yes/No>> | <<FILL: Yes/No>> | <<FILL: add a QOS sentence / no action, non-load-bearing detail appropriately left to Module 3>> |
A “No” in the load-bearing column with a “No” in the reflected column is the expected, correct state; a “Yes” and “No” pairing on the same row is the finding this section exists to catch.
6. Disposition
| Field | Entry |
|---|---|
| Total QOS claims checked | <<FILL>> |
| Claims not fully supported by Module 3 (blocks sign-off until resolved) | <<FILL>> |
| Load-bearing Module 3 content missing from the QOS (blocks sign-off until resolved) | <<FILL>> |
| Recommendation | Approve QOS and Module 3 content as consistent / Hold pending resolution of item(s) <<FILL>> |
7. References
See the paired article, writing CMC validation summaries for regulatory filings, for the reasoning behind the QOS-versus-Module-3 discipline this matrix checks. ICH M4Q, Common Technical Document, Quality (informal Quality Overall Summary length guidance: roughly 40 pages of text excluding tables and figures, extending to roughly 80 pages for biotech products or products made by more complex processes).
8. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL>> | <<FILL>> | Initial issue. |
9. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Reviewer (Regulatory writer) | <<FILL>> | ||
| Approver (Regulatory Affairs Lead) | <<FILL>> |
Filled specimen
Extract for an example cell therapy BLA’s S.2.5 content. Company and product are illustrative.
| # | QOS claim | Module 3 support | Fully supported? | Notes |
|---|---|---|---|---|
| 1 | ”Process validation followed traditional process validation across two commercial-scale batches, reflecting the total batches manufactured at commercial scale to date.” | 3.2.S.2.5, paragraph 1, states the same approach and batch count; batch matrix table in 3.2.S.2.5 lists both batches by ID | Yes | Wording matches; no independent claim introduced |
| 2 | ”See 3.2.S.2.5 for the batch-count rationale and PPQ results.” | 3.2.S.2.5, paragraphs 2 through 4, and the master PPQ summary table | Yes | Pointer is accurate and specific enough for a reviewer to navigate directly |
Reverse check finding: Module 3’s 3.2.S.2.5 discloses a minor in-PPQ deviation (a processing hold-time excursion, resolved with no CQA impact) in its narrative. The QOS made no mention of it at all, not even a general statement that a deviation occurred and was resolved. Determination: this deviation is load-bearing enough to warrant at least a one-clause acknowledgment at the QOS level, since a QOS that reads as a flawless two-batch campaign when Module 3 discloses a real deviation creates exactly the inconsistency this matrix exists to catch. Action: added the clause “one minor processing deviation occurred and was resolved with no impact on product quality; see 3.2.S.2.5” to the QOS paragraph.
Common findings this matrix prevents
- A QOS conclusion stated more strongly, or with fewer caveats, than the Module 3 data it summarizes actually supports.
- A real deviation or qualification disclosed honestly in Module 3 but invisible in the QOS, so a reviewer who reads the QOS alone forms a more favorable impression than the full record supports.
- A QOS cross-reference that points to the wrong Module 3 section or an outdated version, discovered only when a reviewer tries to follow it.
- A QOS drafted before a late Module 3 revision, never reconciled back to the final text.
How to adapt this matrix
- Run this matrix after Module 3’s validation content is finalized, not before, since reconciling the QOS against a still-changing Module 3 wastes the exercise.
- Populate section 4 by reading the QOS literally sentence by sentence; do not summarize the QOS from memory of what it is supposed to say.
- Take the reverse check in section 5 seriously; the more common failure is an omission from the QOS, not an overstatement in it.
- Re-run this matrix if either the QOS or Module 3 content changes after this review, even a small wording change, since a cross-reference or claim can silently break.