ERP & MRP Planning worked example

Schedule Risk Score with due-date impact score of 20 score: a worked example

Push due-date impact score up to 20 score and the picture changes. This example computes every intermediate figure at that operating point. a scheduler needs to rank schedule risk before releasing the plan

The inputs for this scenario

  • Due-date impact score: 20 score (raised for this scenario; the documented default is 8)
  • Constraint likelihood score: 7 score (unchanged)
  • Visibility and recovery risk score: 6 score (unchanged)

Working through the calculation

  • Applying the documented formula (Schedule risk score = due-date impact × 0.40 + constraint likelihood × 0.35 + visibility/recovery risk × 0.25) to the inputs above produces each figure below.
  • At this operating point the engine returns 11.95 score for schedule risk score, the number this scenario is built around.
  • At this operating point the engine returns 20 score for due-date impact score.
  • At this operating point the engine returns 7 score for constraint likelihood score.
  • At this operating point the engine returns 6 score for visibility and recovery risk score.

How this compares with the baseline

  • Against the tool's baseline example, where due-date impact score sits at 8 score and the headline result is 7.15 score, this scenario comes in 67.13% above the baseline at 11.95 score.
  • It computes a weighted 0 to 10 risk score from due-date impact (40%), constraint likelihood (35%), and visibility/recovery risk (25%). The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.

Results at a glance

  • Schedule risk score: 11.95 score (headline result)
  • Due-date impact score: 20 score
  • Constraint likelihood score: 7 score
  • Visibility and recovery risk score: 6 score

Run it with your numbers

  • Every input above is editable in the live Schedule Risk Score calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.