How do you calculate a project ranking score?

Multiply the three ratings: severity x occurrence x detection. The output here is presented on a normalized 1-10 band, so 6 x 4 x 3 maps to a ranking risk score of about 4.55 rather than the raw product of 72.

What is a good project ranking score?

Lower is better, it means low impact, low likelihood, and easy early detection. There is no fixed threshold; rank your portfolio and act on the top tier. Scores in the upper third of your range usually warrant mitigation before approval.

Why multiply instead of add the three factors?

Multiplication makes a project dangerous only when no factor protects you. A high-severity risk that is rare and easy to catch scores low, which correctly de-prioritizes it relative to a moderate risk that is frequent and hard to detect.

What is the detection score?

Detection rates how hard it is to catch the problem before it does damage, a low score means controls reliably flag it early, a high score means it surfaces only after harm. In the example detection is 3, meaning reasonably detectable.

Severity vs occurrence, which matters more?

Neither dominates by design; they carry equal weight in the product. A severity-9, occurrence-1 risk and a severity-3, occurrence-3 risk land at the same raw value, so you weigh them by the third factor, detection.

Can I use this outside FMEA?

Yes. Any project trade-off where you can rate consequence, likelihood, and visibility on a consistent scale works, capex prioritization, supplier risk, or launch readiness all fit the same severity-occurrence-detection structure.

Manufacturing Project Portfolio & Capex calculator

Project Ranking Score Calculator

Project Ranking Score adapts the classic FMEA risk priority number to capital and improvement portfolios, giving each candidate project a single comparable risk figure from severity, occurrence, and detection ratings. Portfolio managers and PMO leads use it to rank competing projects on an apples-to-apples scale instead of arguing from gut feel. Because the three factors multiply, a project that scores moderately on all three can outrank one that is catastrophic but rare and obvious, which is exactly how you want scarce capital and attention allocated.

What this calculator does

Estimate project ranking for manufacturing project portfolio and capex using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when project ranking in manufacturing project portfolio and capex needs a defensible ranking against other manufacturing project portfolio and capex risks for the next review.
It computes a multiplicative risk priority score for a project from severity, occurrence, and detection ratings on a shared scale.

Formula used

Project ranking risk score = project ranking severity score × project ranking occurrence score × project ranking detection score
Use the same scoring scale across comparable project ranking risks.

Inputs explained

Project impact severity (1-10):
Likelihood the risk occurs (1-10):
Difficulty of detecting it early (1-10):

How to use the result

Use it when ranking a backlog of projects or risks against each other and you need a defensible, repeatable ordering rather than subjective debate.
The score is only comparable when every project is rated on the identical scale and rubric; inconsistent rating anchors make the ranking meaningless.

Common questions

How do you calculate a project ranking score? Multiply the three ratings: severity x occurrence x detection. The output here is presented on a normalized 1-10 band, so 6 x 4 x 3 maps to a ranking risk score of about 4.55 rather than the raw product of 72.
What is a good project ranking score? Lower is better, it means low impact, low likelihood, and easy early detection. There is no fixed threshold; rank your portfolio and act on the top tier. Scores in the upper third of your range usually warrant mitigation before approval.
Why multiply instead of add the three factors? Multiplication makes a project dangerous only when no factor protects you. A high-severity risk that is rare and easy to catch scores low, which correctly de-prioritizes it relative to a moderate risk that is frequent and hard to detect.
What is the detection score? Detection rates how hard it is to catch the problem before it does damage, a low score means controls reliably flag it early, a high score means it surfaces only after harm. In the example detection is 3, meaning reasonably detectable.
Severity vs occurrence, which matters more? Neither dominates by design; they carry equal weight in the product. A severity-9, occurrence-1 risk and a severity-3, occurrence-3 risk land at the same raw value, so you weigh them by the third factor, detection.

Last reviewed 2026-07-13.