How do you calculate a traceability audit readiness risk score?

Multiply severity by occurrence by detection on a common scale. Here 6 x 4 x 3 gives a scaled risk score of about 4.55, which is then used to rank this gap against others.

What is a good traceability audit readiness score?

Lower is better. There is no universal threshold, but teams commonly set an action line — for example, anything above the top third of your scored items gets a corrective action before the audit.

Why use FMEA scoring for traceability instead of a checklist?

A checklist tells you what is missing; RPN tells you what to fix first. Weighting by severity, occurrence and detection lets you spend prep time on the genealogy gap most likely to become an actual finding.

Severity vs detection — which matters more for audits?

For audit readiness, low detection is often the silent killer: a severe gap you always catch internally rarely becomes a finding, but a moderate gap you never detect surfaces exactly when the auditor pulls a random lot.

How often should we re-score traceability readiness?

Re-score after any process change, new SKU, MES upgrade, or traceability escape, and always in the run-up to a scheduled audit. Keep the scoring scale identical between reviews so trends are comparable.

Can this score replace a mock audit?

No. It prioritizes where to look, but a mock audit that actually pulls lots and walks the genealogy backward validates whether the fixes worked.

Traceability, Serialization & Lot Genealogy calculator

Traceability Audit Readiness Calculator

Traceability audit readiness scoring is an FMEA-style risk priority number applied to your lot-genealogy and serialization system: how badly a gap would hurt in an audit, how often such gaps occur, and how likely you are to catch them first. Quality managers and regulatory affairs teams in regulated manufacturing use it to rank which traceability weaknesses to fix before an FDA, notified-body, or customer audit lands. A high score flags a link in the chain — a manual lot record, an un-scanned rework loop, an orphaned serial — that could produce a finding. It turns a vague sense of 'we might not be ready' into a ranked, defensible action list.

What this calculator does

Estimate traceability audit readiness 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 audit readiness 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 scores into a single risk priority number for a specific traceability weakness.

Formula used

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

Inputs explained

Impact severity if traceability fails an audit:
Likelihood of a traceability gap occurring:
Ability to detect gaps before the auditor does:

How to use the result

Use it during audit prep, after a near-miss traceability escape, or when triaging which genealogy gaps to close first with limited resources.
RPN treats the three factors as equally weighted multiplicatively, so a very high severity can be masked by low occurrence — always review high-severity items regardless of total score.

Common questions

How do you calculate a traceability audit readiness risk score? Multiply severity by occurrence by detection on a common scale. Here 6 x 4 x 3 gives a scaled risk score of about 4.55, which is then used to rank this gap against others.
What is a good traceability audit readiness score? Lower is better. There is no universal threshold, but teams commonly set an action line — for example, anything above the top third of your scored items gets a corrective action before the audit.
Why use FMEA scoring for traceability instead of a checklist? A checklist tells you what is missing; RPN tells you what to fix first. Weighting by severity, occurrence and detection lets you spend prep time on the genealogy gap most likely to become an actual finding.
Severity vs detection — which matters more for audits? For audit readiness, low detection is often the silent killer: a severe gap you always catch internally rarely becomes a finding, but a moderate gap you never detect surfaces exactly when the auditor pulls a random lot.
How often should we re-score traceability readiness? Re-score after any process change, new SKU, MES upgrade, or traceability escape, and always in the run-up to a scheduled audit. Keep the scoring scale identical between reviews so trends are comparable.

Last reviewed 2026-05-12.