Risk your project

A single finish date ("we're done May 24") hides how much could go wrong. Risking your project replaces that one date with a range and a confidence level: how likely is that date, and which risks would move it. Owl builds a risk register, ties each risk to the activities it would hit, and runs a Monte Carlo simulation to give you P10 / P50 / P80 / P90 finish dates.

Note: A Monte Carlo simulation runs the schedule many times (1,000 in the example below). In each run, every risk either happens or not (by its chance), and when it happens it stretches the activities it's linked to by an amount drawn from its range. Owl records the finish date of every run. P50 is the date you'd meet in half the runs; P90 is the date you'd meet in 90% of them, a more conservative commitment. The gap between them is your exposure.


Before you start

You need a schedule to attach risks to — built from documents or imported. Owl can write the risk register for you, so you don't need one in advance.


Step 1 — Build the risk register

The register lives under Risks in the project tree. The quickest start is the Risk specialist: click + in the chat panel to start a new thread and pick Set up a risk register. You can also ask in any chat:

Ask Owl
Build a risk register for this project from the schedule and the spec.
Here's our risk register spreadsheet — load it and link each risk to the activities it affects.
Add a risk for a regional shortage of skilled labor, 35% likely, adding 10–40% to the steam piping and startup activities.

Each risk gets a chance of happening, an impact range, and the list of activities it affects.


Step 2 — Check a single risk

Click a risk under Risks to open it.

"The Shortage of Skilled Labor risk: a 35% chance, a triangular impact of +10% to +40% on its activities, its summary, and the 15 activities it affects."12341Impact if it occurs — its chance, shape, type and Min / Likely / Max, with the spread the simulation samples from.2Summary — severity, chance, distribution, impact type and range, all editable here.3Affected tasks — the 15 activities this risk stretches.4Link task adds an activity; Mitigation plan holds what you'll do about it.

A risk has:

  • Chance — how likely it is to happen at all, as a percent. In each simulation run the risk either happens or doesn't.
  • Impact if it occurs — the shape of the uncertainty (Triangular, Uniform or Normal), whether it's a percent of each activity's duration (Relative (%)) or a fixed amount (Absolute (hours)), and its Min / Likely / Max.
  • Affected tasks — the activities it stretches. A risk only moves the finish if it's linked to activities, so this is where risking succeeds or fails.

Tip: You don't have to link risks by hand. Ask Owl: "Link the weather risks to the outdoor activities only." Then check the lists it made.


Step 3 — Run the simulation and read the result

With risks linked, run a simulation: under Risks → Simulations, make one and click Run, or in the chat panel's + menu pick Run a simulation under the Risk specialist, or ask Owl to run it. A simulation keeps its settings (the schedule it simulates, the number of iterations, its seed) and its last run, so you can come back to it, and it tells you when the schedule or the risk register has changed since it ran.

"The Monte Carlo view for Substantial Completion: deterministic May 24 2027, a 4% chance of meeting it, P50 Jul 5 and P80 Jul 30; the finish date distribution; a percentiles table; and the risks moving this date."12345671Monte Carlo sits under Risks in the project tree.2Target — the milestone the results are about.3The answer at a glance: the plan's deterministic date, the chance of meeting it, and the P50 and P80 dates.4Finish date distribution — every run's finish (bars) and the running chance of being done by each date (curve).5Percentiles — P10 to P90, each against the deterministic date, and the full range.6Risks moving this date — which risks matter, ranked.7Run for activity reports on any other activity.

Reading this example for Substantial Completion:

  • The plan says May 24, 2027 (the deterministic date: the schedule with no risks). But only 4% of runs finished by then.
  • P50 is Jul 5, 2027 (+42 days) and P80 is Jul 30 (+67 days). A May 24 commitment is very unlikely; to be 80% confident, you'd commit to the end of July.
  • The Percentiles table adds P10 (May 31) and P90 (Aug 13), and the full Range of runs (May 24 – Sep 23).

The Risks moving this date table tells you what to do about it:

ColumnWhat it means
ChanceThe risk's chance, as entered.
OccurredThe share of runs in which it actually happened.
SensitivityHow closely this date moves with the risk's impact across runs (higher = more).
Delay if it occursThe average finish when the risk happens, minus when it doesn't.
DrivingThe share of runs in which it hit an activity on this date's driving path.

Here Boiler Equipment Long-Lead Time Delay leads by far: a 50% chance, a sensitivity of 0.78, and +35 days when it occurs. It's the first risk to mitigate if you want to pull the P80 date in.

Run for activity reports the same results for another activity: type its ID (for example a mid-project milestone) and run it.

Ask Owl
Which risks contribute most to the P80 date?
If we order the boiler two months earlier, what happens to P50 and P80?
Run the simulation again now that the long-lead risk is mitigated.

Put risk in front of stakeholders

A simulation's results can be charted like anything else. An analytic over Each activity, drawn as a Range and compared with the simulation, shows each milestone's P10–P90 finish against its planned date; the example project's Risk Analysis dashboard has one, next to figures for critical and near-critical work.

Ask Owl
Add a chart of each milestone's simulated P10–P90 finish to the Project Health dashboard.

What to do next

  • Add risk to a dashboard — Create custom dashboards.
  • Try a mitigation safely — make the change in a scenario and compare the result.
  • Keep risk assignments honest — use guardrails, for example "environmental risks only on outdoor activities."