← Decisions and trade-offs Dependency-network model

Schedule sensitivity sandbox

Project Risk Gradient

Toy scenario

See where one additional day of protective buffer creates the largest reduction in a risk index—and whether that buffer moves the commitment date.

This is a transparent learning model, not a calibrated risk forecast. It uses a simple CPM network, an exponential risk response, and finite differences to make the “next best buffer day” visible.

Risk response

Risk index and marginal reduction as the selected task receives buffer.

index points / day

Risk-reduction ranking

Higher values indicate more risk-index reduction from the next available buffer day. Tasks at the 10-day limit are excluded.

Explanation for project managers

A risk gradient answers a practical question: where would the next day of contingency buy the most reduction in this model’s risk index?

  • The ranking shows the marginal reduction from adding one day to each task.
  • A “no finish-date impact” badge means the extra day currently fits inside another path’s float.
  • Critical-path buffers usually move the commitment date, so compare index reduction with schedule cost.
  • Use the sliders to test a small allocation, then reset and compare alternatives.
Advanced explanation for risk and scheduling specialists

The model holds baseline CPM weights constant, adds protective buffer to each task’s baseline total float, and approximates a partial derivative with a one-day forward difference.

Task risk index = 100 × exp(−(baseline slack + buffer) × coefficient / 2)

For a task with zero float and no buffer, the first day lowers its index by 18.13 points at coefficient 0.4, or 32.97 points at coefficient 0.8. These supplied coefficients, baseline float and task weights determine the ranking; they are not fitted probabilities.

Displayed gradient = Project index(b) − Project index(b + 1 day)

The mathematical derivative is negative; the interface reports its positive magnitude as index reduction. Commitment impact is calculated separately by rerunning the dependency network with buffer added to task duration. The index uses fixed baseline slack and weights; it does not infer new protection from recalculated float. Within this example’s 0–10-day slider limits, the same branch remains critical: Documentation and Training together can use at most 20 of their 22 days of baseline float.

The chart includes a hypothetical next-day reduction at 10 days to show the response curve; allocating an 11th day is outside the controls. Recommendations and rankings include only allocations still available within the limit.

Adjust protective buffers

Select a task for the chart, then allocate 0–10 days. Dates below are the recalculated commitment schedule.