Questions teams ask before they switch
Straight answers on how RiskForesight differs from legacy desktop QSRA, schedule imports, security and deployment, the AI copilot and pricing.
How is this different from legacy desktop QSRA tools?
RiskForesight is web-native and keeps the register and the Monte Carlo in one model — no export, re-keying or reconciliation. You get probabilistic links and branching, risk calendars, integrated cost + schedule (JCL) and DCMA-14 schedule health, without a Windows-only install.
Can I import my existing schedule?
Yes. Bring your programme in through the P6 XER, MSPDI and MPP import path, keep the WBS tree, activity grid and Gantt, and run the same schedule the register drives — no rebuild.
Where does it run, and is my data secure?
Row-level security is enforced in the database itself with a full, reversible audit trail, OAuth sign-in, MFA, strict CSP/HSTS and SOC 2-ready controls. Start in the cloud or self-host on-prem for data residency and air-gapped environments.
How does the AI work — is it safe to use on our data?
The copilot works through typed, permissioned product tools and every write action is confirmation-gated (human-in-the-loop). You can pin a no-egress mode so AI is disabled or routed only where your deployment allows.
Do I need to be a QSRA specialist to use it?
No. The model is transparent and interactive so risk leads, planners and decision-makers can read P50/P80, drivers and what-if comparisons in a workshop — the copilot helps draft ranges, mappings and the report narrative for review.
What does it cost?
The full engine is free during early access — build a register, import a schedule and run your first Monte Carlo with no credit card. Team and Enterprise plans (SSO, on-prem, no-egress AI) follow.
Still have a question?