ERP & MRP Planning worked example

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

This worked example runs the schedule risk score numbers for a tougher week than the baseline: due-date impact score of 4 score instead of the typical 8 score. Score schedule risk from due-date impact, constraint likelihood, and visibility or recovery risk.

The inputs for this scenario

  • Due-date impact score: 4 score (the input this scenario stresses; the baseline uses 8)
  • Constraint likelihood score: 7 score (held at the documented default)
  • Visibility and recovery risk score: 6 score (held at the documented default)

Working through the calculation

  • The calculation starts from the formula this tool documents: Schedule risk score = due-date impact × 0.40 + constraint likelihood × 0.35 + visibility/recovery risk × 0.25.
  • Schedule risk score works out to 5.55 score at these inputs, and this is the headline figure for the scenario.
  • Due-date impact score works out to 4 score at these inputs.
  • Constraint likelihood score works out to 7 score at these inputs.
  • Visibility and recovery risk score works out to 6 score at these inputs.

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 22.38% below the baseline at 5.55 score.
  • Use it to prioritize a production schedule, run a daily risk standup, or decide which orders get buffer, expediting, or escalation. A result at this level usually justifies acting on the stressed input before touching anything else, because every other figure in the table is downstream of it.

Results at a glance

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

Run it with your numbers

  • To rerun this with your own numbers, open the live Schedule Risk Score calculator, set due-date impact score to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.