Mappings

A risk only matters where it lands.

Mapping is where a register becomes a model: point each risk at the activities and cost elements it actually drives, and the engine knows what to move. Walk the WBS, search by name, tick the links — undo anything.

Uncertainty across a whole branch, in one pass.

Discrete risks are only half the model — every activity also carries duration uncertainty. Group the schedule by WBS level, give each branch a percentage band, and apply it to hundreds of activities at once instead of typing ranges one by one.

Some paths only exist some of the time.

Not every relationship is certain. Give a predecessor link or a successor branch its own probability and the engine draws it per iteration — so the logic itself varies, the critical path can move between runs, and conditional scope stops being modelled as though it always happens.