Schedule risk analysis asks a question a normal programme cannot answer: given everything that could go differently, how likely is the completion date you are quoting?
A critical path calculation produces a single date from single durations. It is a useful answer to the wrong question, because every duration in it is really a range. The drywall might take twelve days, or fifteen if manpower drops, or ten if the area is handed over clean.
Risk analysis replaces those fixed durations with ranges, adds discrete risk events that may or may not occur, and runs the schedule thousands of times. The output is not a date but a distribution: a curve showing the probability of finishing by any given day. From it you can read the confidence level attached to the date in the contract.
This matters commercially rather than academically. A team quoting a date with a twenty percent chance of being met is not optimistic. It is committing to something it will almost certainly miss, and usually nobody in the room knows that is what has happened.
Start with a schedule worth analysing. Sound logic, no unnecessary constraints, no orphan activities, a critical path that genuinely runs through the work. Running a simulation over a poorly built programme produces confident nonsense, which is worse than no analysis at all.
Assign duration ranges. For each significant activity, an optimistic, most likely and pessimistic duration. Get these from the people who perform the work, and resist the instinct to make the range symmetrical. Construction activities can go far more wrong than they can go right, so the distribution is usually skewed toward the pessimistic side.
Add discrete risk events. Things that either happen or do not: a permit refused, a key subcontractor failing, contaminated ground, a long lead item arriving damaged. Each gets a probability and an impact, and each is mapped to the activities it would hit.
Model correlation. The step most often skipped, and the one that most distorts results when it is. If a labour shortage slows one trade it usually slows several. Treating every duration as independent produces a suspiciously narrow distribution and a falsely comfortable answer.
Run the simulation and read the outputs. Monte Carlo methods sample from the ranges across thousands of iterations. The completion date distribution tells you the confidence level of any date. The criticality index tells you how often each activity landed on the critical path, which frequently reveals that the path you have been managing is not the one that actually threatens the project.
Confidence levels are usually written as P values. P50 is the date you have a fifty percent chance of meeting. P80 is the date you would meet in eighty percent of simulated outcomes.
The gap between them is the contingency the project actually needs. If P50 falls in March and P80 in May, that ten week difference is not padding invented by a cautious planner. It is the price of the confidence level the business has chosen to carry.
Framed that way, contingency becomes a commercial decision rather than an argument. Bidding at P50 to win the work is a legitimate choice, provided everyone understands it is a coin toss. The failure mode is bidding at P50 while reporting internally as though it were certain.
The criticality index is the other output worth acting on. An activity that appears on the critical path in sixty percent of runs deserves management attention even if today's deterministic critical path shows it with float. Near critical work is where projects are usually lost.
Formal quantitative analysis has a real weakness: it is a snapshot. It is typically run at tender, at contract award and perhaps quarterly, by a specialist, on a programme that was accurate the week it was exported. Between those runs the project keeps changing and the analysis silently ages.
Meanwhile the day to day risk on a live project rarely comes from the modelled uncertainty in activity durations. It comes from the operational signals nobody has connected: the approval ageing past its need by date, the trade that has not confirmed, the delivery that moved, the predecessor drifting. Those are not probability distributions. They are facts sitting in five different systems.
Both views are worth having. Quantitative analysis tells the business how much contingency the commitment requires. Continuous readiness tracking tells the project team which activity is in trouble this week. A team with only the first has a good number and a bad Monday.
This is the layer Playbook addresses. Readiness, commitments, approvals and field updates are tracked against the activities they affect, so emerging exposure is visible continuously rather than at the next formal review, with the evidence behind each flag shown rather than asserted. It does not replace a quantitative risk analysis, and it should not be sold as one. It covers the eleven weeks between them.
What is schedule risk analysis?
Schedule risk analysis replaces fixed activity durations with ranges, adds discrete risk events, and simulates the schedule many times to produce a probability distribution for the completion date rather than a single date.
What do P50 and P80 mean in scheduling?
P50 is the date with a fifty percent chance of being achieved. P80 is the date achieved in eighty percent of simulated outcomes. The difference between them represents the schedule contingency required to move from a coin toss to a reasonably safe commitment.
What is Monte Carlo simulation in scheduling?
Monte Carlo simulation samples randomly from the duration ranges and risk events across thousands of iterations of the schedule. Each run produces a completion date, and the collected results form the probability distribution used to derive confidence levels.
What is a criticality index?
The criticality index shows how often an activity appeared on the critical path across all simulation runs. It identifies near critical work that carries float in the deterministic schedule but frequently becomes critical once uncertainty is modelled.
Note to editors:
High-resolution images and interviews with PYBK leadership team members are available upon request.
Project controls is the discipline of measuring whether a project is going to hit its time and cost targets, and providing early enough warning to do something...
There is no single best construction scheduling tool, and any list that names one is answering a different question from the one you are asking. What exists...
OAC stands for Owner, Architect, Contractor. An OAC meeting brings those three parties together on a regular cycle, usually weekly or fortnightly, to review...
