Schedule riskThrough November 6, 2026

10% of schedules run through the free Schedule Risk Analyzer have at least even odds of finishing by their planned date

Of 804 free and anonymous schedules simulated. At least even odds means the P50 finish, the day half the runs finish by, falls on or before the finish the file states.

How likely is a project schedule to finish on time?

In a Monte Carlo simulation, 10% of 804 schedules run through the free Schedule Risk Analyzer have a P50 finish on or before their planned date. The typical P80 finish, the date four runs in five finish by, lands 13 days after the planned date.

P50 on time, by plan sizeThe share of simulated plans in each size band whose P50 finish falls on or before the planned finish, with its n.
  • 1 to 49 tasks11%
    n = 342
  • 50 to 199 tasks9%
    n = 270
  • 200 to 999 tasks11%
    n = 165
  • 1,000 to 4,999 tasks4%
    n = 27

What this means for your plan

For most plans, the finish date the file states is earlier than the day half the simulated runs finish by. Commit to a P80 date, and treat the gap between the planned finish and the P80 as the contingency to ask for.

Check your own schedule's odds free
  • 10%

    P50 on or before the planned finish

    n = 804

  • 9%

    P80 on or before the planned finish

    n = 804

  • 8 days

    Typical P50 slip past the planned finish

    n = 804

  • 13 days

    Typical P80 slip past the planned finish

    n = 804

  • 7%

    Typical P80 slip, as a share of the planned duration

    n = 796

  • 9 days

    Typical uncertainty band, P10 to P90

    n = 804

  • 4%

    Typical uncertainty band, as a share of the planned duration

    n = 796

Slip is counted in calendar days from the planned finish (the finish the file states, or the finish its links give when it states none) to the simulated date. The uncertainty band runs from P10, the day one run in ten beats, to P90. A share of the planned duration counts from the project start to the planned finish.

Risk by plan size

Grouped by the number of tasks the simulation varied, in bands, never exact sizes.

GroupP50 on timeTypical P80 slipTypical P10 to P90 band
1 to 49 tasks11% n = 3428 d n = 3428 d n = 342
50 to 199 tasks9% n = 27012 d n = 2708 d n = 270
200 to 999 tasks11% n = 16531 d n = 16513 d n = 165
1,000 to 4,999 tasks4% n = 2781 d n = 2724 d n = 27

Risk by near-critical tasks

A near-critical task is on the critical path in at least 20% and under 80% of runs. The more of them, the more paths can take over the finish.

GroupP50 on timeTypical P80 slipTypical P10 to P90 band
No near-critical tasks13% n = 4028 d n = 4027 d n = 402
1 to 4 near-critical tasks10% n = 1849 d n = 18410 d n = 184
5 to 19 near-critical tasks4% n = 14222 d n = 14214 d n = 142
20 or more near-critical tasks3% n = 7633 d n = 7616 d n = 76

Risk by merge points

A merge point is a task waiting on two or more others, where a late input delays it whichever one runs over.

GroupP50 on timeTypical P80 slipTypical P10 to P90 band
No merge points10% n = 2096 d n = 2096 d n = 209
1 to 9 merge points12% n = 14012 d n = 1406 d n = 140
10 to 49 merge points8% n = 16122 d n = 16112 d n = 161
50 or more merge points12% n = 13758 d n = 13718 d n = 137

Quality meets risk: missing links

Plans with tasks that have no links against plans where every task is linked. A task with no links cannot push anything later, so a narrow band on such a plan can be certainty it has not earned.

GroupP50 on timeTypical P80 slipTypical P10 to P90 band
Every task linked10% n = 69515 d n = 69510 d n = 695
Some tasks with no links12% n = 1094 d n = 1094 d n = 109

Execution signals versus drawn plans

Plans whose file records progress, an actual start, an actual finish or a percent complete above zero on any task, against plans with none. Actuals mean someone is statusing the plan. They do not mean the work is ready to start. The files cannot see procurement, permits, site access, engineering deliverables or contractor commitments, so neither row measures execution readiness. Both rows go through the same simulation of the plan's own logic with the same default duration ranges.

GroupP50 on timeTypical P80 slipTypical P10 to P90 band
Being statused (actuals recorded)15% n = 17010 d n = 1708 d n = 170
Drawn only (no actuals recorded)10% n = 35512 d n = 3558 d n = 355

What drives the finish

Of the five tasks whose duration moves each plan's finish the most, pooled across plans, the share in each group by how often the task was critical.

  • Critical in 80% of runs or more53%
    n = 3,911
  • Near-critical (critical in 20% to 79% of runs)19%
    n = 3,911
  • Off the critical path (under 20% of runs)28%
    n = 3,911

How we counted: free and anonymous uploads to the Schedule Health Check, the MPP viewer, Onplana Schedule and the Schedule Risk Analyzer. Paying customers’ plans are never included. We read counts only, never file, task or company names. Any figure from fewer than 20 schedules is left out. Read the Privacy Policy section.

Back to all insights

How does your schedule compare?

Put your own plan through the same simulation in the browser, free, for its P50, P80 and P90 finish. Check it against the DCMA checks with the free Schedule Health Check, or open it on Windows and Mac with Onplana Schedule, a free download.