Get P50, P80 and P90 finish dates from a schedule file
The Schedule Risk Analyzer is a free tool that answers one question about a schedule file: how likely is the finish date? It runs a Monte Carlo simulation of the plan and returns three dates you can commit to, with no Onplana account.
Run an analysis
Section titled “Run an analysis”-
Open onplana.com/tools/schedule-risk and upload a Microsoft Project
.mpp, a Project XML (MSPDI) file or a Primavera P6.xer, up to 22 MB. Drop the file on the box or click to pick it, then select Get my finish dates.
-
Read the result. Above the dates is the project name, its number of tasks and how many runs were made. It shows three dates and the five tasks that move the finish most, each with the share of runs in which it was on the critical path:
- P50: half the runs finished on or before this date.
- P80: 80% of the runs finished on or before it, a common commitment date.
- P90: 90% of the runs finished on or before it.
It also shows the finish date in your file and the share of runs that met it.
-
To see the full report, select See the full report and enter your email under Unlock the full report. Onplana may email you one link back to the report, and the tool sends no series of follow-up emails. The full report shows:
- How the finish dates spread: a bar for each span of finish dates, with the earliest, the latest and the P10. Darker bars finish on or before the P80 date.
- Every task that drives the finish: how closely each task’s duration tracks the project finish across the runs (1.0 means it moves the finish every time), and how often it was critical.
- Each task’s P80 finish: the planned finish beside the P50 and P80, largest slip first. The first 25 tasks show, and Show all N tasks lists the rest.
A line under the report says how many runs were made, how many tasks were varied and held, and the calendar used.
How the simulation works
Section titled “How the simulation works”
Each run varies every task that still has work left, then schedules the plan through its links, lags and constraints, as Onplana’s critical path engine does, and records the finish.
- A task’s duration is drawn from a triangular range of 10% under to 25% over its planned duration, so overruns are more likely than early finishes.
- Done tasks and milestones keep their dates. A started task varies only the work it has left when the file has a status date.
- Summary tasks are not varied: their dates come from the tasks under them.
- The tool aims for 2,000 runs, and runs fewer on a very large schedule so the answer arrives in seconds. The report says how many it ran.
- The same file always gives the same dates.
What the free tool does not do
Section titled “What the free tool does not do”- It schedules a Monday to Friday week at the hours per day in your file, without your holidays or exceptions.
- It reads task dates as whole days and does not level resources.
- It runs schedules of up to 2,000 tasks with work.
Keep the schedule in Onplana
Section titled “Keep the schedule in Onplana”From the full report, Save to Onplana creates a free workspace with the same file imported as a project. On a plan that includes it, the in-app schedule risk analysis reruns the simulation on the live project, with your own optimistic and pessimistic duration for each task and the risks on your register.
Is my file kept? The file is read on Onplana’s servers to build the schedule, and the file itself is not stored. The parsed schedule is kept for 30 days, after which it is deleted and only the analysis results remain, so your report stays readable. The analysis record itself is deleted after 12 months. After the 30 days, Save to Onplana asks you to upload the file again. No AI model reads the file. See the Privacy Policy.
Are my results in the published figures? Counts from free Risk Analyzer runs feed the schedule risk report on onplana.com/insights: counts and rates only, with no file, task or company names, and no figure drawn from fewer than 20 schedules.
Why is the chance of my own finish date so low? The date in a plan assumes every task takes exactly its planned duration. With a range that leans late, few runs do, so a chance under 50% is normal.
Was this helpful?
Thanks for your feedback!