Risks
A portfolio register carrying threats and opportunities, each with its own matrix and strategies, linked both ways to the schedule.
Who it is for. A consultant gets a register and a matrix. A small team gets expected value and review dates. An enterprise PMO gets portfolio roll-up across the EPS tree and quantitative analysis.
What it is for
Most risk registers are spreadsheets that score threats only, treat opportunities as an afterthought, and have no arithmetic connection to the schedule or the budget. This scores both types on their own matrices, computes expected value with PERT weighting, and links rows to activities in both directions.
Opportunities scored on their own matrix with their own strategies and their own colour semantics is rare — most registers bolt opportunities onto a threat matrix. So is a two-way schedule link plus quantitative analysis running on the register itself, which in the incumbent world means a separately purchased risk product.
Awaiting capture — WF32-BOP
Register open with the threat and opportunity matrices side by side, and a row showing its linked activity.
What it does
Every line below is in the product today.
Opportunities are first-class
Threats and opportunities each get their own response strategies — avoid, mitigate, transfer, accept against exploit, enhance, share, accept.
Two matrices, two colour semantics
Side-by-side 5×5 matrices with separate ramps, because a high-scoring opportunity is a good thing and should not be red.
Expected value with PERT weighting
The three-point cost estimate is reduced by the PERT mean and weighted by the probability band, with a documented fallback when no three-point estimate exists.
Click a matrix cell, reach the risk
A populated score cell lists exactly the risks in it, and clicking one opens the register entry.
Two-way link to the schedule
A risk reveals its activity in the Gantt, and the same model backs the Risk column in the activity table.
Portfolio scope through the EPS
The register spans every project plus portfolio-level risks belonging to none, with counts rolled up per EPS node.
Reviews that go overdue visibly
Each risk carries a review history with author, note and next review date, and overdue reviews are flagged in the register.
It reads and writes with
Monte Carlo
Re-run the critical path thousands of times over three-point durations and register risks, then commit a chosen confidence level back into the schedule as a real, rescheduled plan.
Activities
The critical-path Gantt where the schedule is actually built — a virtualised table and timeline that computes your dates from logic, calendars and constraints instead of letting you type them.
CP Crash
Find the cheapest way to pull the finish date in, see what each day actually costs, and know the exact date the critical path moves to a different chain.
See it on your own schedule.
Send an XER before the call and we will import it and show you Risks running against your data.