What it means
Probability–impact scoring combines an estimate of likelihood with the magnitude of effect on objectives to support relative risk prioritization.
Why it matters
The method is simple and useful, but a single score can conceal very different consequences, time horizons, and uncertainty.
Practical focus
- Define probability and impact levels with objective-specific examples and ranges.
- Preserve the underlying ratings and rationale rather than reporting only a combined score.
- Consider non-linear consequences, multiple objectives, and threshold effects when interpreting the result.
- Retain the approved definitions, assumptions, decisions, ownership, exceptions, measures, and change history that demonstrate how Probability–Impact Scoring operates in real project work.
- Exercise this failure scenario: A rare safety or compliance event receives a moderate combined score and is deprioritized despite consequences that exceed organizational tolerance.
Common mistakes
- Using Probability–Impact Scoring as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a template, meeting, tool screen, or status report as proof that Probability–Impact Scoring works consistently in normal delivery.
- Optimizing a single activity while ignoring dependencies, incentives, risk transfer, and the end-to-end outcome.
- Testing only the expected path and never rehearsing this failure condition: A rare safety or compliance event receives a moderate combined score and is deprioritized despite consequences that exceed organizational tolerance.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: