What is the simplest risk scoring model?

Likelihood × impact on a 1–5 scale each, multiplied for a score of 1–25. Use consistent definitions so scores are comparable across risks in the same project.

How many risk levels do I need?

Start with a few response bands your team can act on, such as monitor, mitigate, and escalate. Define the score range, owner, and decision expected at each level before using the bands.

Can a low-scoring risk still need escalation?

Yes. A rare event with severe safety, legal, contractual, or delivery impact can warrant review even when likelihood multiplied by impact produces a low number. Agree on explicit escalation overrides.

Should residual risk be scored separately?

Yes when you have active mitigations. Record inherent score before controls and residual score after, so you can show progress without closing risks prematurely.

Can PMHub store risk scores?

PMHub supports scoring and prioritization on RAID risks so you can sort and filter by severity alongside actions and issues.

Project risk scoring: turn uncertainty into a decision

Use a practical likelihood and impact model to compare project risks. A worked migration example shows how evidence, severe consequences, and review triggers shape the response.