Elite Project Controls System — 9 intelligence modules infographic
Enterprise Upgrade

Elite Project Controls System

The Complete Project Controls Intelligence Platform

9 intelligence modules, 170+ AI project controls prompts, executive dashboards, risk analytics, forecasting and recovery planning — all in one professional framework.

Better insight · Better decisions · Better results

Risk

RAID Log Severity Score

Compute a weighted severity score across Risks, Assumptions, Issues and Dependencies for executive reporting.

Calculator
Severity = 3·Risks + 1·Assumptions + 4·Issues + 2·Dependencies
Enter values to compute.

Interpretation Guide

  • 0 – 19Manageable.
  • 20 – 49Elevated.
  • ≥ 50Critical.

Example

5 risks + 4 assumptions + 3 issues + 6 deps → 3·5 + 4 + 12 + 12 = 43 (elevated).

Real-world use cases

  • Weekly RAID reviews
  • Programme governance

Common mistakes

  • Counting closed RAID items in the score

Professional tips

  • Trend the score weekly to spot escalation
FAQ

Frequently asked questions

Why are issues weighted highest?

Issues are realized problems impacting the project today, so they need the most weight.

What this tool does

Compute a weighted severity score across Risks, Assumptions, Issues and Dependencies for executive reporting.

It applies the standard formula Severity = 3·Risks + 1·Assumptions + 4·Issues + 2·Dependencies so planners, schedulers and PMOs get a defensible number they can put in front of a steering committee.

Looking for the underlying terminology? Open the PM Glossary or the PM Cheat Sheet for quick references on EVM, scheduling and risk terms.

When to use it

  • Weekly RAID reviews
  • Programme governance

Typical owners: project managers, planning engineers, project controls leads and PMO analysts running weekly or monthly performance reviews on EPC, infrastructure, IT and construction projects.

How to interpret the result

Treat the number as a signal, not a verdict. Read it together with the trend over the last 3–6 reporting periods, the critical-path status, and the risk register before you change the plan.

  • Compare against the baseline, not against another project.
  • Investigate the drivers behind the value before reporting it up.
  • Pair it with at least one complementary KPI (cost, schedule, risk or quality).

Worked example

5 risks + 4 assumptions + 3 issues + 6 deps → 3·5 + 4 + 12 + 12 = 43 (elevated).

In a real project review, document the inputs, the resulting value, the interpretation, and the corrective action you committed to. That audit trail is what turns a calculator output into a controls decision.

Learn more on PMMilestone

Related tools

Continue exploring

Enterprise Upgrade

Upgrade to Enterprise-Level Project Intelligence

Discover the Elite Project Controls System — a professional intelligence framework for modern project controls, forecasting, executive reporting, AI PM workflows and risk management.

  • Executive-grade KPI frameworks
  • AI-powered project workflows
  • Forecasting & risk intelligence
  • PMO-ready reporting templates
Buy me a coffee