How to · guide 01 of 12 · 8 min read

A typical run — import to report

tabs 1→6 · works on the demo project · free tier

The whole method is the tab order. One pass through the six tabs takes a schedule from "the plan says 24 Aug" to a defensible P80 with the drivers ranked and a print-grade report — this is the cycle every other guide hangs off.

  1. Import the schedule. On 1 Import, drop a Primavera P6 .xer or PMXML, an MS Project .xml, or a plain CSV/TSV task list (ID, Name, Duration, Predecessors — the download CSV template link shows the exact shape; Asta users export a task list to CSV). The Fitness Gate then grades the file against the full DCMA 14-point check and prints READY for QSRA, READY WITH CAVEATS or NOT RECOMMENDED with every finding listed. The gate is advisory — you can always run — but its verdict prints in the report, so fix what you can at source.
  2. Read the schedule. The app lands on 2 Schedule: a read-only Gantt with WBS grouping, ⟶ Links, ⚡ Critical and ⟶ Longest Path overlays, look-ahead and code filters, and a detail panel on double-click. This tab is for verifying you risked the schedule the planner actually issued — durations and logic are never edited here, only re-imported. Schedule tab: Fitness Gate verdict READY for QSRA 100/100 above the WBS-grouped Gantt with critical path highlighted
    The demo passes the gate at 100/100; critical activities read amber down the register-style listing.
  3. Build the Risk Register. On 3 Risk Register, click + Add risk per discrete event: name, Owner, type (threat / opp), probability (0–1), an impact distribution (triangular, pert, trigen, uniform, normal, lognormal, discrete) with min / likely / max in working days, an optional Cost £ impact, and the activities it Maps to. Already have a register in Excel? Copy puts the table on the clipboard, pasting a tab-separated block bulk-adds by ID, and CSV ▾ exports a blank template or imports a populated one. ✨ Suggest mappings proposes register→activity links by text similarity — deterministic and explainable, no AI. Risk Register tab with five demo risks showing probability, distribution, three-point impacts and mapping modes
    The demo register: five risks with owners, P·I screening scores, quantified impacts — note the Mode column, where fragnets and branches live (guides 04–06).
  4. Set the Ranges. On 4 Ranges, pick a calibration preset — Conservative (−5/0/+10%), Typical (−10/0/+25%) or Aggressive (−15/+5/+40%) — then override any activity's three-point band or distribution in the table. (Yes, "Conservative" is the narrowest band — it's conservative about the estimate, not the outcome.) Per-group overrides let different WBS branches carry different uncertainty; the cost columns (Cost £k, C.min / C.likely / C.max) feed the QCRA layer. Ranges tab: calibration presets, per-group overrides, weather and correlation cards above the per-activity range table
    One preset applies a standard spread to everything; override where you know better. Weather and correlation (guides 07–08) live here too.
  5. Run. Set the seed (write it down — it makes every number reproducible), pick iterations, optionally tick LHS for stratified sampling, and press ▶ Run Monte Carlo or ⌘/Ctrl ↵. Two thousand iterations on the demo takes under a second.
  6. Read the results. 5 Results opens on the four tiles — Deterministic, P50, P80 ("the contractual number"), P90 — above the completion distribution and S-curve. Below: the driver tornado (six views — Risk drivers, Sensitivity, Cruciality, SSI, Cost, Variance), the criticality index, measured risk paths, milestone confidence, cost risk with the JCL football chart, and probabilistic cash flow. 📌 Snapshot this run pins any run for side-by-side comparison; the footer prints a convergence check and a reproducibility certificate anyone can Verify. Results tab: P50 10 Nov 2027 and P80 3 Jan 2028 tiles, completion distribution with S-curve, and the risk-driver tornado
    The plan said 24 Aug 2027. The simulation puts that at P2 — and names the two risks buying most of the 94-day gap.
  7. Generate the report. 6 Reports offers five deliverables, each a Generate button: the full QSRA / QCRA pack, a one-page Executive Brief, the Risk Register report (no run needed), NEC programme risk (Time Risk Allowance framed for NEC4 ECC clause 31.2), and Mitigation & Contingency. Tick sections on or off in Report contents & options, set analyst / organisation / logo in Report settings, and print to PDF from the browser. Every page carries the seed and engine version, so every number is checkable. Reports tab with five report tiles: QSRA/QCRA pack, Executive Brief, Risk Register report, NEC programme risk, Mitigation & Contingency
    Five deliverables from one run. Free-tier reports carry a DRAFT watermark; the content is identical.
Mitigation is a first-class scenario. Fill the green Post-P / Post-Lik columns (and Mit £ for the cost of the action) and the run produces pre- and post-mitigation scenarios under the same seed — the Compare view then prices what the mitigation package buys in days and pounds. That chart is the business case for the risk budget.
Load the demo and run the cycle →
All 12 guides 02 · Monthly re-link on a schedule update →