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.
- 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 free10%
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.
| Group | P50 on time | Typical P80 slip | Typical P10 to P90 band |
|---|---|---|---|
| 1 to 49 tasks | 11% n = 342 | 8 d n = 342 | 8 d n = 342 |
| 50 to 199 tasks | 9% n = 270 | 12 d n = 270 | 8 d n = 270 |
| 200 to 999 tasks | 11% n = 165 | 31 d n = 165 | 13 d n = 165 |
| 1,000 to 4,999 tasks | 4% n = 27 | 81 d n = 27 | 24 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.
| Group | P50 on time | Typical P80 slip | Typical P10 to P90 band |
|---|---|---|---|
| No near-critical tasks | 13% n = 402 | 8 d n = 402 | 7 d n = 402 |
| 1 to 4 near-critical tasks | 10% n = 184 | 9 d n = 184 | 10 d n = 184 |
| 5 to 19 near-critical tasks | 4% n = 142 | 22 d n = 142 | 14 d n = 142 |
| 20 or more near-critical tasks | 3% n = 76 | 33 d n = 76 | 16 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.
| Group | P50 on time | Typical P80 slip | Typical P10 to P90 band |
|---|---|---|---|
| No merge points | 10% n = 209 | 6 d n = 209 | 6 d n = 209 |
| 1 to 9 merge points | 12% n = 140 | 12 d n = 140 | 6 d n = 140 |
| 10 to 49 merge points | 8% n = 161 | 22 d n = 161 | 12 d n = 161 |
| 50 or more merge points | 12% n = 137 | 58 d n = 137 | 18 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.
| Group | P50 on time | Typical P80 slip | Typical P10 to P90 band |
|---|---|---|---|
| Every task linked | 10% n = 695 | 15 d n = 695 | 10 d n = 695 |
| Some tasks with no links | 12% n = 109 | 4 d n = 109 | 4 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.
| Group | P50 on time | Typical P80 slip | Typical P10 to P90 band |
|---|---|---|---|
| Being statused (actuals recorded) | 15% n = 170 | 10 d n = 170 | 8 d n = 170 |
| Drawn only (no actuals recorded) | 10% n = 355 | 12 d n = 355 | 8 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.
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.