How do you calculate a launch readiness score?

Combine severity, occurrence, and detection ratings on a common scale. With severity 6, occurrence 4, and detection 3, this model returns a launch readiness risk score of 4.55.

What is a good launch readiness score?

Lower is better. There's no universal threshold, but launches typically gate on relative ranking — any score well above the cohort median should have a closed action before go-live.

How is this different from a standard FMEA RPN?

It uses the same severity-occurrence-detection inputs as an RPN but normalizes them into a launch-readiness scale so risks across a launch can be compared on one yardstick.

Why does a high detection rating matter?

Detection captures whether you'd catch the failure before it ships. A high-severity risk you can't detect is far more dangerous than one your controls reliably catch.

Severity vs occurrence vs detection — which matters most?

Severity caps the danger because a catastrophic failure is unacceptable however rare; occurrence and detection then determine how urgently you must add controls.

How should the team set the rating scales?

Define each scale with written anchors before scoring so a 6 means the same thing to everyone; reusing one consistent scale across comparable risks is what makes the scores rankable.

NPI, DFM/DFA & Engineering Change calculator

Launch Readiness Score Calculator

Launch Readiness Score applies FMEA-style risk thinking to a product launch by combining how severe a launch failure would be, how likely it is to occur, and how well you'd detect it before it reaches customers. NPI leads and quality engineers use it to rank open launch risks on a common scale so the launch gate decision is evidence-based rather than a gut call. It matters because launching with an undetected high-severity risk is how field failures, recalls, and warranty spikes begin. Scoring each risk the same way makes the highest-priority items obvious during gate reviews.

What this calculator does

Estimate launch readiness for npi, dfm/dfa and engineering change using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when launch readiness in npi, dfm/dfa and engineering change needs a defensible ranking against other npi, dfm/dfa and engineering change risks for the next review.
It produces a single launch readiness risk score from severity, occurrence, and detection ratings so risks can be ranked and gated.

Formula used

Launch readiness risk score = launch readiness severity score × launch readiness occurrence score × launch readiness detection score
Use the same scoring scale across comparable launch readiness risks.

Inputs explained

Launch defect severity rating:
Launch defect occurrence rating:
Launch defect detection rating:

How to use the result

Use it at launch gate reviews and during pre-launch risk assessments to prioritize which issues must close before go-live.
The score is only as good as the rating scale; if severity, occurrence, and detection aren't defined consistently across the team, scores aren't comparable.

Common questions

How do you calculate a launch readiness score? Combine severity, occurrence, and detection ratings on a common scale. With severity 6, occurrence 4, and detection 3, this model returns a launch readiness risk score of 4.55.
What is a good launch readiness score? Lower is better. There's no universal threshold, but launches typically gate on relative ranking — any score well above the cohort median should have a closed action before go-live.
How is this different from a standard FMEA RPN? It uses the same severity-occurrence-detection inputs as an RPN but normalizes them into a launch-readiness scale so risks across a launch can be compared on one yardstick.
Why does a high detection rating matter? Detection captures whether you'd catch the failure before it ships. A high-severity risk you can't detect is far more dangerous than one your controls reliably catch.
Severity vs occurrence vs detection — which matters most? Severity caps the danger because a catastrophic failure is unacceptable however rare; occurrence and detection then determine how urgently you must add controls.

Last reviewed 2026-05-12.