Criticality index in Monte Carlo schedule analysis

The Critical Path Method computes the longest chain of dependent tasks using one number per task — usually a most-likely or padded estimate. That produces a single critical path and a binary label on every task: critical or not. The problem is that the labels are only true for that exact combination of durations. Change a few estimates within their plausible range and a different chain becomes the longest.

On real R&D programs, where almost every duration is genuinely uncertain, the deterministic critical path is just one sample from a distribution of possible critical paths. Treating it as the critical path concentrates management attention on a chain that may control the outcome far less often than it appears — and ignores chains that quietly drive most of the risk.

A Monte Carlo simulation draws a duration for every task from its probability distribution — commonly a three-point PERT-Beta from optimistic, most-likely, and pessimistic estimates — then runs the forward and backward CPM pass to find the critical path for that single iteration. It repeats this thousands of times, each time with a fresh set of sampled durations.

For each task, the engine counts how many iterations placed it on the critical path and divides by the total number of iterations. That ratio is the criticality index. A task at 100% is on the critical path in every scenario; a task at 0% never controls the finish; the interesting tasks are the ones in between.

The tasks that cause the most trouble are usually not the ones with 100% criticality — those are obvious and already watched. The danger lies in near-critical tasks: those with a high but sub-100% index, say 40% to 80%. They sit just off the deterministic critical path with a thin sliver of float, so a deterministic view marks them as safe even though they take over the critical path in a large share of realistic scenarios.

A task with a 60% criticality index drives your finish date more than half the time, yet a standard Gantt would show it with positive float and no special attention. Watching only the deterministic critical path means you are blind to it until it slips. The criticality index makes these tasks visible and lets you protect them with buffers, resource priority, or a fast-tracking decision before they bite.

Criticality answers "how often is this task on the critical path?" It is a frequency, not a measure of impact. A task can be on the critical path frequently yet contribute little variance because its own duration is tightly bounded.

That is why criticality index is best read alongside a sensitivity measure — often called cruciality or a duration sensitivity index — which correlates each task's duration with the project finish date. A tornado chart ranks tasks by that correlation. Read together, criticality (frequency) and sensitivity (impact) tell you which tasks both control the schedule often and move the finish date hard — the true priority list for risk mitigation.

CritPath AI computes the criticality index as a native output of its Monte Carlo engine. Every simulation run samples task durations from three-point PERT-Beta distributions (with optional duration correlation and discrete risk-event injection) and runs a forward pass across the dependency network. The criticality index reports how often each task finishes at — and so drives — the project end across iterations (a simplified, finish-to-start-focused determination rather than a full per-iteration CPM honoring every dependency type), reported alongside the P50/P80/P90 finish distribution. Optional duration correlation prevents the index from understating risk when related tasks tend to slip together.

The platform pairs criticality with a tornado chart of duration sensitivity, so you see both how often a task is critical and how much it moves the finish date. The AI copilot, grounded in your real dependency graph, surfaces high-criticality near-critical tasks in plain language and explains what protecting them does downstream — rather than leaving you to read a raw probability table.

It is $10 per user per month, with AI usage billed separately by metered usage — full Monte Carlo schedule risk analysis in a modern web app, not a five-figure desktop license.