In production on UK strategic infrastructure.
Multiple schemes in active production on a major UK infrastructure delivery programme, run by a Tier‑1 delivery partner across multi‑period reporting cycles.
On UK strategic infrastructure.
Risk Studio is in active production on a major UK infrastructure delivery programme, running across multiple schemes through quarterly reporting cycles. Specific scheme names and delivery‑partner brands are reserved for direct conversations under NDA.
75 checks across four published frameworks. Badges shown are SOMA‑designed monograms representing each public framework, not the standards bodies' own marks. Compare them →
An active UK infrastructure delivery programme.
Want the long form? Read the anonymised case brief — 4 weeks to 4 days →
The challenge
A major UK infrastructure delivery programme runs across multiple junctions and bypasses on major UK road infrastructure. Each scheme runs its own quantitative schedule risk analysis. Each is reviewed against different frameworks at different periods. Each must produce defensible outputs for the client, for the assurance team, and increasingly for the regulator.
The legacy workflow ran on Safran round-trips and per-analyst spreadsheets. Validation was manual. Different schemes ended up assessed against different bars. Periods slipped because the toolchain was the bottleneck, not the analysis.
What SOMA Risk Studio delivers
- One toolkit across multiple schemes — same validators, same Monte Carlo, same deliverables, same audit chain.
- Multi-framework validation — SOMA QSRA Readiness, DCMA 14-Point, CIOB PP21, Acumen Fuse SQI on every scheme, every period.
- Excel report (configurable templates) — the team's existing macro-enabled template, populated automatically. Cells hold literal values so SharePoint previews and macros-disabled viewers display correctly.
- Analyst Briefing PPTX — 12-slide deck with auto-generated speaker notes addressed to the PM, Planner, Risk Manager, RAM and RRM.
- Audit-replay archive — every run captured. Cryptographic chain. Re-run any historic period byte-identically.
By the numbers
We sit in the same chair as the people who use Risk Studio every day. That's the only reason it works.— Adam O'Neill, founder, SOMA Project Controls
Built for five roles. Each gets what they need.
Project Managers
Headline P50 / P80 dates, mitigation effectiveness, next-period actions. Briefed in plain English in the PPTX deck.
Planners
Schedule Lens with WBS tree, per-activity diagnostic trace, every check that failed and why. Conversation-ready.
Risk Managers
Tornados, decile attribution, mitigation deltas, the risk register laid out the way they think about it.
Risk Analysis Managers
Full audit chain, sign-off workflow, multi-user file locks, accept-with-reason workflow.
Regional Risk Managers
Programme rollup, heat map across schemes, baseline compare. Portfolio-level visibility.
Other roles welcome
If your team's roles don't fit this list, tell us about them. We've added briefing audiences before.
What changes between periods.
UK infrastructure schemes typically run on a quarterly reporting cadence. Risk Studio is shaped around it. Here's what a period looks like once Risk Studio is in place.
- Day 1 — fresh XER and updated risk register land. Validator fires automatically; the analyst sees the delta against last period in minutes.
- Day 2–3 — workshop with the planner inside Schedule Lens. Pinned issues become the agenda. Most close out the same morning.
- Mid‑period, the Monte Carlo runs against the updated register. P‑values shift, mitigation delta is plotted, decile attribution flags any new tail risks.
- Day 5 — four deliverables generated automatically and reviewed. Per‑finding accept‑with‑reason where the team needs to override.
- By the period board, the analyst is ready to brief the PM, Planner, Risk Manager, RAM and RRM — each gets the slide that's written for them.
Read the case brief. Then ask us what we'd run on yours.
Two‑page write‑up on how Risk Studio fits a quarterly reporting cadence on UK infrastructure programmes. What we run, what we deliver, what changes between periods. We'll share it before the call.