How do you calculate a traceability gap score?

Multiply the severity, occurrence, and detection ratings together, the same way an FMEA computes a risk priority number. The default 6, 4, and 3 ratings combine into a normalized score of about 4.55 on this scale for ranking against other gaps.

What is a good traceability gap score?

Lower is better — it means the gap is some combination of low-consequence, rare, and easy to detect. There is no universal threshold; you set an action line and address every gap scoring above it before the ones below.

What do severity, occurrence, and detection mean here?

Severity is how damaging the gap is if it reaches a recall or audit; occurrence is how frequently the gap actually happens; detection is how likely your controls catch it first, where a higher score means harder to detect.

Why multiply instead of add the three scores?

Multiplication makes a gap that is high on all three axes stand out sharply, the way FMEA's risk priority number does. A severe, frequent, undetectable gap should dominate one that is bad on only a single axis.

Traceability gap score vs a full FMEA RPN?

They share the severity times occurrence times detection structure. This calculator is a focused application of that logic to lot-genealogy and serialization gaps rather than a general process FMEA.

How should I act on the score?

Rank all your gaps by score, set an action threshold, and drive down the highest scorers by lowering the most controllable axis — usually detection, by adding a scan checkpoint or a system validation that catches the gap earlier.

Traceability, Serialization & Lot Genealogy calculator

Traceability Gap Score Calculator

The Traceability Gap Score applies FMEA-style risk priority to weaknesses in your lot genealogy and serialization chain, multiplying how bad a gap would be, how often it happens, and how hard it is to catch. Quality engineers and traceability program owners use it to rank gaps — a missing scan checkpoint, an unlinked sub-lot, an ambiguous serial format — so limited resources go to the highest risk first. It matters because not every traceability gap is equal: a rarely triggered, easily caught gap should never outrank one that is severe, frequent, and invisible. The score makes that comparison objective across otherwise apples-to-oranges risks.

What this calculator does

Estimate traceability gap for traceability, serialization and lot genealogy using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when traceability gap in traceability, serialization and lot genealogy needs a defensible ranking against other traceability, serialization and lot genealogy risks for the next review.
It multiplies severity, occurrence, and detection ratings into a single risk priority score for a traceability gap.

Formula used

Traceability gap risk score = traceability gap severity score × traceability gap occurrence score × traceability gap detection score
Use the same scoring scale across comparable traceability gap risks.

Inputs explained

Consequence severity of the traceability gap:
Likelihood the gap occurs:
Ability to detect the gap before impact:

How to use the result

Use it when triaging multiple traceability or serialization weaknesses and you need a defensible ranking of what to fix first.
The score is only meaningful if every gap is rated on the same scale by the same rubric; inconsistent scoring makes the ranking arbitrary.

Common questions

How do you calculate a traceability gap score? Multiply the severity, occurrence, and detection ratings together, the same way an FMEA computes a risk priority number. The default 6, 4, and 3 ratings combine into a normalized score of about 4.55 on this scale for ranking against other gaps.
What is a good traceability gap score? Lower is better — it means the gap is some combination of low-consequence, rare, and easy to detect. There is no universal threshold; you set an action line and address every gap scoring above it before the ones below.
What do severity, occurrence, and detection mean here? Severity is how damaging the gap is if it reaches a recall or audit; occurrence is how frequently the gap actually happens; detection is how likely your controls catch it first, where a higher score means harder to detect.
Why multiply instead of add the three scores? Multiplication makes a gap that is high on all three axes stand out sharply, the way FMEA's risk priority number does. A severe, frequent, undetectable gap should dominate one that is bad on only a single axis.
Traceability gap score vs a full FMEA RPN? They share the severity times occurrence times detection structure. This calculator is a focused application of that logic to lot-genealogy and serialization gaps rather than a general process FMEA.

Last reviewed 2026-05-12.