Matrix: Quality Metric Regulatory Traceability

This is a ready-to-use traceability matrix. Build one row per metric in your mandatory set, not per regulation, so an inspector (or your own gap review) can start from any tile on the dashboard and get a straight answer to “why do you track this, and where does the number come from.” Replace every <<FILL: ...>> placeholder with your own metrics and sources. A worked filled specimen follows the template. This content is general educational reference, not legal or regulatory advice; confirm every citation against the current published source before you rely on it.

Document control header

1. Purpose

A quality metrics program is rarely built from one regulation. It is assembled from several sources read together, which is exactly why a metric-by-metric traceability view earns its place alongside the metric definition sheets: the definition sheet fixes how one metric is calculated, this matrix fixes why the program bothers tracking it at all, and the two together are what a reviewer pulls when they ask the program to justify itself end to end.

2. Scope

This matrix covers every metric in the mandatory set reported through management review, whatever tier it sits at (site, area, or executive rollup). It does not replace the quality metric definition sheet, which governs the calculation of one metric at a time, or the general regulatory requirement to governing procedure cross-reference, which maps the wider QMS, not the metric set specifically.

3. The matrix

4. How to build and maintain it

1. Start from the mandatory metric set, not from a list of regulations. For each metric already on the dashboard, work backward to the regulation, guidance, or internal risk rationale that justifies tracking it.
2. State what the metric demonstrates in plain language, one phrase, not a restatement of the regulation. This is the line a metric owner uses when an inspector asks “why do you track this one.”
3. Where the basis is a non-binding source, such as the FDA quality metrics initiative’s proposed definitions, say so plainly in the cell rather than implying a formal submission obligation that was never finalized as a binding rule.
4. Do not leave a metric with no basis at all. A metric nobody can justify is a candidate for the retirement discussion in the main article, not a permanent blank row.
5. Update the matrix the moment a metric is added, redefined, or retired, and whenever a regulation or guidance it relies on changes. Review it alongside the metric definition sheets at the same cadence, since the two documents answer different halves of the same question.

5. Acceptance criteria

• Every metric in the mandatory set has a named regulatory or guidance basis, or an explicit internal risk rationale where no regulation directly applies.
• No cell implies a binding submission obligation that is not actually in force.
• Every metric maps to exactly one named source system and one current metric definition sheet reference.
• The matrix has been updated within the current cycle for every metric added, changed, or retired since the last review.

6. References

ICH Q10, Pharmaceutical Quality System (process performance and product quality monitoring; management review). 21 CFR 211.180(e) (annual records review), 211.192 (investigations), 211.198 (complaint files), 211.100 and 211.110 (procedures and in-process controls). EU GMP Chapter 1 (Pharmaceutical Quality System) and the Product Quality Review provisions. FDA quality metrics initiative draft guidances (Submission of Quality Metrics Data, 2015 and revised 2016), for the Lot Acceptance Rate, Product Quality Complaint Rate, and Invalidated OOS Rate definitions. The mandatory submission scheme in those drafts was never finalized as a binding rule.

Confirm the current version and clause numbers of each reference before issue.

7. Revision history

Filled specimen

The following shows four rows completed for an example oral solid dose site, so you can see the level of detail expected. The company, systems, and document numbers are illustrative; replace them with your own.

A gap check against this specimen would flag, for example, a dashboard tile for “complaint rate” with no corresponding row at all, which is exactly the kind of orphan metric this matrix is built to surface before an inspector finds it first.

Common inspection findings this matrix prevents

• A metric owner who cannot say, in one sentence, why a tracked metric is tracked, beyond “it has always been on the dashboard.”
• A claim that a metric is “FDA-required” when its actual basis is a non-binding draft guidance definition the firm chose to adopt.
• A dashboard tile with no traceable link back to either a regulation, a guidance, or a documented internal risk rationale.
• A metric added mid-year with no record of why, discovered only when the trend shows an unexplained step change.

How to adapt this matrix

1. Set the owner and update-trigger fields in the header; like any traceability artifact, this one only stays useful if someone owns keeping it current.
2. Build the metric list from your actual mandatory set as defined in your quality metrics program SOP, not from this specimen’s examples.
3. Where a metric’s basis is purely an internal risk decision rather than a named regulation, write that plainly rather than stretching a citation to fit.
4. Review this matrix and the metric definition sheets on the same cycle, since a changed metric usually touches both.