Risk Management · QSRA
Quantitative Schedule Risk Analysis (QSRA) Consultancy
Quantitative Schedule Risk Analysis (QSRA) is a structured way to test how likely your completion date really is. BHD models the uncertainty in your programme, runs the identified risks through it, and reports the dates you can plan to with confidence, together with the schedule contingency that sits behind them.
When is a QSRA worth commissioning?
A QSRA earns its keep whenever a date matters to money. That is usually one of five situations: you are about to commit to a completion date in a tender; a client or funder has asked you to justify the date you have given; the programme has been compressed and nobody is sure the new dates hold; delay is the largest risk on the job; or you are already carrying a fixed completion date with delay damages attached.
It is less useful as a box-ticking exercise at the end of a job.
How is the risk modelled?
A conventional programme gives each activity one duration and produces one end date. That end date looks precise and is usually wrong. QSRA replaces the single figure with a range. Each risk or uncertain activity is given two things: a likelihood of occurring, and, if it does occur, a range of possible effects on duration. Risk distributions describe how likely each outcome within that range is, so the middle of the range carries more weight than the extremes. A pessimistic guess at one end and an optimistic guess at the other is not a distribution.
Monte Carlo analysis is the calculation that follows: a computer run that plays the programme forward thousands of times, each time drawing a duration from the ranges you have set, and records the completion date that results. Across thousands of runs a picture forms of which end dates are likely and which are not.
What do P50 and P80 completion dates actually mean?
The modelled results are read as confidence levels. A P50 date has a 50 per cent chance of being met or beaten: half the modelled outcomes finish on or before it. A P80 date has an 80 per cent chance. Neither is a prediction. Each is a statement about likelihood, which is far more useful than a single date presented as fact.
Choosing the level is a commercial decision, not a technical one. P50 is a coin toss. If your contract, your funder or your own cashflow cannot absorb a late finish, P50 is the wrong number to plan to.
The gap between the P50 and the P80 is your schedule contingency in time: the allowance held to cover identified risk. Setting it from the analysis gives you a defensible figure instead of an added percentage.
How is confidence reported to a board, client or funder?
The output is built to be read in a meeting. It shows the completion date at the confidence levels you have chosen, the schedule contingency attached to it, and a ranked view of which risks move the end date most, so attention goes where it changes the outcome. It shows what mitigation would buy you, by re-running the model with the proposed response in place.
It also shows what has changed since the last run: which risks have moved, which have closed, and whether the confidence position has improved or slipped. That comparison is usually the most valuable part, because it turns risk reporting into a record of decisions rather than a restatement of the register.
What does a client actually receive?
- A programme readiness note: what we checked, what we found and any limitations that affect the result.
- A risk list with the likelihood and duration range agreed for each entry, and the basis for both.
- The model itself, with the assumptions recorded so the result can be reviewed or repeated.
- A results table of completion dates at the confidence levels you asked for, including P50 and P80.
- A recommended schedule contingency in working days, with the reasoning behind it.
- A ranked list of the risks that drive the end date, and the effect of the mitigation you are considering.
- A short written report in plain English, and a walkthrough session with the people who have to act on it.
The analysis is a snapshot. It stays useful only if it is refreshed as the programme and the risks change, which is how it connects to the wider controls rhythm.
Who you will be working with
BHD is led by a Chartered Construction Manager with 25 years across construction, defence and infrastructure. The analysis is carried out by the principal, not passed to a junior team, and it is sized to suit an SME contractor rather than a major programme.
Related analysis
Cost risk, analysed the same way.
Schedule risk rarely travels alone. Where the same project carries cost uncertainty, the companion exercise is Quantitative Cost Risk Analysis (QCRA), which quantifies the cost risks in the estimate and sets contingency on the same evidential basis. Both sit inside our wider risk management service, and feed cost engineering and contract and commercial management when entitlement or change follows.
Common questions.
What is the difference between a QSRA and a risk register?
A risk register lists and scores risks in words and ratings. A QSRA takes the risks that affect time and tests their combined effect on the programme, producing a range of completion dates and a schedule contingency. The register is the input; the analysis is what turns it into a defensible date.
Do we need a perfect programme to start?
No, but the programme has to be logical and honest. We check it first and tell you what is wrong. If the gaps are material we recommend fixing them before modelling, or we proceed and state the limitations in the report so nobody over-reads the result.
How long does a QSRA take?
It depends on the size of the programme and how ready it is. A single-project analysis is a matter of weeks rather than months. The critical path is usually the workshop where likelihoods and ranges are agreed, because that needs the people who know the work in the room.
Who owns the schedule contingency once it is set?
The project does, not the analysis. The figure is a recommendation with a stated basis; how it is held, drawn down and reported is a management decision. We recommend reviewing it on a fixed rhythm so it does not quietly become an allowance nobody tests.
Can a QSRA support extension of time discussions?
It can provide evidence of how programme risk was assessed at a point in time, which is useful context. It is not a substitute for contractual entitlement analysis, and on NEC or JCT work the notice and assessment process still governs. We will be clear about which question each piece of work answers.
Schedule risk review
Start with a schedule risk review
If you have a completion date you are not sure you can hold, or a client asking you to justify one, send us the programme and the current risk register. We will tell you what the analysis would show, what the programme needs before it can be tested properly, and whether a QSRA is the right next step. There is no obligation, and if the answer is no, we will say so.
