Published on 18/12/2025
QOS Quality Control: A Simple Checklist to Clear Red Flags Before Dispatch
Purpose and Scope: What This QC Pass Must Prove in Minutes
A Quality Overall Summary (QOS, Module 2.3) should be short, exact, and consistent with Module 3. The final quality control pass must confirm three outcomes in minutes: (1) every number and name in QOS tables matches the approved or proposed Module 3 content; (2) each claim has a direct pointer to a controlled record (specification row, validation report, stability conclusion); and (3) reviewers can reach that evidence quickly through clear cross-references. The aim is not to rewrite the file. The aim is to verify sameness, traceability, and navigation so the reviewer focuses on science, not on clean-up.
This article provides a simple, regulator-style checklist that authors, publishers, and QA can run before a sequence is built. It covers specification parity, validation traceability, stability wording, control strategy mapping, naming consistency, regional phrasing, navigation aids, and versioning. It also suggests short proof statements and minimal documentation to store as part of an audit trail. Where structure or placement questions arise, use official references such as EMA eSubmission
The checklist is designed for both original applications and post-approval changes. If you are filing a variation or supplement, run the same checks twice: once against the current approved state and once against the proposed state. Mark the QOS as “draft aligned to Seq XXXX” until approval. After approval, replace the draft label with the effective version and archive the parity report with the QOS PDF.
Key Concepts and Definitions Used in This Checklist
Parity. Parity means the text and numbers in the QOS equal those in Module 3. For specifications, it includes attribute names, units, limits, footnotes, and method IDs. For methods, it includes claim language (for example, “stability-indicating”) and report IDs. For stability, it includes the exact shelf-life wording found in 3.2.P.8.3 and any storage statements that appear on labels.
Traceability. Traceability means each claim in the QOS links to a controlled record. This record can be a specification row in your master data, a validation report, a capability study, a stability table, or a change record. In the QOS, traceability appears as a short reference (section and table ID, or report ID). The reviewer should not guess the location. The link must be explicit.
Navigation. Navigation means the reviewer can scan the QOS, click a bookmark or a cross-reference, and arrive at the correct Module 3 table or report. The QC pass checks that bookmarks are present, cross-references are valid, and table IDs are consistent across the document.
Control strategy map. This is the table that links CQAs to controls (materials, process parameters, in-process checks, and release tests). It should be present in the QOS and should match the language used in Module 3. The QC pass looks for missing links or mismatched terms.
Versioning. The QOS must display a version number and the eCTD sequence to which it is aligned (for example, “QOS v06 — aligned to Seq 0018”). When the change is under review, mark the QOS as draft. When approved, mark it as effective with the date.
Checklist Part 1 — Specification Parity and Method Linkage
1. Attribute names and order. Confirm that each attribute name in the QOS specification table matches the name in Module 3.2.S.4 or 3.2.P.5.1. Check spelling, punctuation, case, and order. If Module 3 lists “Subvisible Particles ≥10 µm,” do not convert units or change the phrase. Record a “match” outcome or correct the source table and regenerate.
2. Limits and units. Verify that acceptance criteria are identical to Module 3, including symbols (≤, ≥, NMT) and ranges. Units must match in type and format. If the EU copy uses decimal commas, adjust the punctuation in the regional file but keep the numeric value the same. Note the check result in the QC log.
3. Method IDs. Each spec row in QOS must show a method and an ID that appears in Module 3 (3.2.S.4, 3.2.P.5.1, and 3.2.P.5.3). If the QOS mentions “HPLC assay M-A12,” the same ID must appear in Module 3. If not, correct the master list and regenerate the QOS.
4. Rationale line. If the QOS includes a short rationale column (for example, “qualified impurity; LOQ margin 3×”), confirm that the supporting report and section are referenced (3.2.P.5.6 or equivalent). The text must not introduce new numbers. It must only summarize and point.
5. Release vs stability rows. If the QOS shows both release and stability criteria, confirm that the labels “Release” and “Shelf-life” are used in the same way as in Module 3. Confirm that any alert/action levels are described as such and are present in Module 3 or in a referenced plan.
QC evidence to keep. Export a parity report that compares QOS spec rows to Module 3 tables by ID. Store it with the QOS PDF. Note any corrections and the final “all match” status.
Checklist Part 2 — Validation Traceability and Claim Scope
1. Validation matrix presence. Confirm that the QOS contains a short validation matrix for critical methods. The matrix should list method ID, purpose, key claims (specificity, precision, LOQ, linearity, range, robustness), results in one line, and the validation report ID with the Module 3 location (3.2.X.5.3).
2. Stability-indicating status. If the QOS states that a method is stability-indicating, confirm that a degradation study is cited and that the study is present in the referenced report. Check that stress conditions are described in Module 3 and that specificity results are recorded.
3. Claim scope and conditions. Confirm that method scope matches Module 3 (for example, “assay valid for strengths 5 mg and 10 mg,” or “dissolution method valid for pH 1.2, 4.5, 6.8”). If scope is narrower than implied in QOS, correct the QOS or the source record and regenerate.
4. System suitability. If the QOS mentions system suitability checks, confirm that the exact checks and limits are in Module 3. For performance methods (for example, APSD, IVRT), confirm the presence of suitability or run-acceptance statements in the method file.
5. Report IDs. Every method claim in the QOS should end with a report ID. Check that each ID exists and is the current one. If a report was replaced during lifecycle, ensure the QOS points to the active report.
QC evidence to keep. Produce a short index of method IDs used in QOS with their report IDs and Module 3 locations. Save it with the parity report.
Checklist Part 3 — Stability Synopsis and Shelf-Life Wording
1. Study design alignment. Confirm that the QOS describes long-term, intermediate (if used), and accelerated conditions consistent with Module 3. Confirm time points and container-closure description. Do not add conditions that are not in Module 3.
2. Trend statements. The QOS should use short statements such as “assay decreases by 0.6% at 24 months; no OOS” or “impurity X reaches 0.18% at 36 months.” Confirm that these values appear in 3.2.S.7 or 3.2.P.8 tables and that the wording does not create new claims.
3. Shelf-life conclusion text. The shelf-life statement in the QOS must match 3.2.P.8.3 exactly, including storage conditions. If labels include statements such as “store at 2–8°C; protect from light,” confirm consistency across QOS, Module 3, and labeling.
4. Extrapolation basis. If the QOS mentions extrapolation, confirm that the statistical basis is present in Module 3 and that the confidence interval or model is referenced. Keep language simple and factual.
5. Commitments. If the QOS mentions ongoing or post-approval commitments, confirm there is a pointer to the correct Module 3 or Module 1 location and that the commitment text matches the filed document.
QC evidence to keep. Save a one-page panel with the shelf-life conclusion string, the 3.2.P.8.3 reference, and a tick-box confirming label alignment.
Checklist Part 4 — Control Strategy Map and Lifecycle Signals
1. Map completeness. Confirm that the control strategy map lists the main CQAs (assay, impurities, dissolution or release rate, microbial, particulates, device dose uniformity if relevant). For each CQA, ensure there is at least one material control or CPP, one in-process check if applicable, and one release test, with Module 3 references.
2. Names and terms. The names of CQAs and controls in the QOS must match Module 3. If Module 3 uses “blend uniformity,” do not rename it “content uniformity at blend.” Keep terms stable.
3. Lifecycle references. If your dossier uses a lifecycle document (for example, a PLCM under ICH Q12), confirm that the QOS mentions it in one line and uses the same names for any elements that are designated as established conditions. Do not copy the PLCM text into the QOS.
4. Changes in scope. If the sequence introduces a change (new site, method update, spec change), confirm that the QOS includes a short change index table with section, row ID, old value, new value, reason, Module 3 reference, and the change record ID. This table should cover only changes in the current sequence.
QC evidence to keep. Archive the change index with the QOS. Keep a simple log that shows who checked the map and when.
Checklist Part 5 — Naming, Cross-Document Consistency, and Regional Copies
1. Product identity strings. Confirm that the product name, dosage form, strength, route, and container-closure strings in the QOS match Module 3 and labeling exactly. Do not shorten names or change separators. Small differences cause avoidable questions.
2. Label alignment. Where the QOS mentions storage conditions or presentations, confirm that the wording matches the label or SPL/QRD text. If a term differs by region, keep the numeric values the same and adjust only the phrasing.
3. Regional copies. For EU/UK and Japan, ensure that the QOS numbers are identical to the US copy. Adjust only style elements (for example, decimal commas) and local terms where required. Use EMA eSubmission for placement and PMDA for local naming. Keep a short note of what changed in phrasing.
4. Device terms. For combination products, confirm that device component names match those used in Module 3 device sections and in any regional device documentation. Keep one set of names across all documents.
QC evidence to keep. Save a one-page identity check that lists the key strings and confirms equality across QOS, Module 3, and labeling for the region.
Checklist Part 6 — Navigation Aids, Formatting, and Version Control
1. Table of contents and bookmarks. Ensure the QOS has a simple table of contents with one level of headings and that bookmarks exist for each main section and for each key table (specifications, validation matrix, control strategy map, stability synopsis). Test the links.
2. Cross-references. Check that inline references use exact Module 3 numbering (for example, “see 3.2.P.5.1, Table P5-02”). Avoid vague phrases such as “as shown above.” Each line that states a value should include a clear pointer when helpful.
3. Table IDs and titles. Confirm that table IDs follow a consistent pattern (for example, “QOS-Table-P5-01”) and that titles are short and factual. If a table was updated for the current sequence, add a small note under the title such as “Aligned to Seq 0018.”
4. Page headers and footers. Ensure that the QOS shows product name, dosage form, strength, QOS version, and sequence number on each page. Use continuous page numbers. Keep font and spacing readable.
5. Version banner. On the title page, show “QOS vXX — aligned to Seq XXXX.” If the document is filed for review, mark it as “draft.” After approval, publish the effective copy and remove the draft marker. Archive both the draft and effective copies with the QC reports.
QC evidence to keep. Save a short navigation test log with three sample clicks per section and a screenshot or note of the target location. Keep it with the parity report.
Common Findings and Simple Corrections During QOS QC
Mismatch in limits. A QOS table shows “95.0–105.0%,” while Module 3 shows “95.0–104.5%.” Correction: fix the master specification record and regenerate both Module 3 and QOS tables. Do not patch the QOS text by hand. Re-run parity and store the new report.
Missing method IDs. A QOS row cites “dissolution method” with no ID. Correction: add the method ID to the master list, update Module 3 references, and regenerate QOS. Confirm the validation report ID is present.
Stability wording drift. QOS says “24-month shelf life,” Module 3 says “shelf life 24 months at 25°C/60% RH.” Correction: copy the exact string from 3.2.P.8.3 into the QOS stability section. Re-check label phrases.
Device term inconsistency. QOS uses “metering chamber,” Module 3 uses “dose chamber.” Correction: choose the Module 3 term and update all QOS occurrences. Add the term to a small glossary if helpful.
Old report referenced. QOS cites a validation report that has been superseded. Correction: point the QOS to the current report ID and archive the change in the QC log.
Regional punctuation issues. EU copy shows decimal commas in Module 3 but the QOS uses points. Correction: adjust punctuation in the regional QOS while keeping numeric values identical. Note the change in the regional QC note.
Latest Practice Points and Short SOP Language You Can Reuse
Author from controlled sources. Build QOS tables from master data that also feed Module 3. This removes most parity issues. State this rule in your SOP: “Authors must not type numbers into QOS tables by hand.”
Run QC as a gate. Add a gate in the publishing workflow: no sequence can move to dispatch until the parity report shows “all match,” the navigation test passes, and the version banner is correct. Keep the gate outcome with the QOS PDF.
Use short, repeatable text. Where the QOS needs explanation, keep to one or two sentences and a pointer. Example: “Impurity X limit 0.15% based on qualification and process capability (see 3.2.P.5.6 and 3.2.P.3.5).” Do not add extra narrative.
Prepare for inspection. Keep three items together: the QOS PDF, the parity/logic report, and the change index (if applicable). With these three items, inspectors can verify control without delay.
Use official anchors. For structure and placement, rely on EMA eSubmission. For US expectations on pharmaceutical quality terminology, rely on FDA pharmaceutical quality. For Japan, rely on PMDA. Keep external references limited and neutral.
Outcome. A QOS that passes this checklist presents stable tables, exact wording, and clear links to evidence. Reviewers can confirm key points quickly and move to technical questions. This reduces information requests and keeps timelines predictable.