The Problem
Risk standards belong in one place, not scattered across ten spreadsheets.
Corporate risk standards belong in one place, not scattered across ten spreadsheets.
Risk management across projects has always required a manual workaround. Maintain a master register in Excel, distribute it to project teams, and hope each team applies it consistently.
If your programme has ten projects, you have ten versions of the same corporate risk events, maintained independently, with no shared source of truth. The same risk event gets entered with different codes, different names, different impacts, and different probabilities across projects. Every new project means another round of manual import, column mapping, and data entry before your team has done a single line of project-specific analysis.
The Decision
The Solution
Risk coverage across projects has always been an assumption. Now it is a fact.
Global Risk Register gives risk teams one place to define their corporate risk library once and apply it directly to projects in a single action. No re-entry, no duplication. Risk teams get back the time they were spending on manual entry and spend it on analysis instead.
Coverage is visible by risk event. Every risk shows which projects it has reached. One click navigates straight to that risk in the project register, pre-filtered and ready to review. For the first time, risk coverage across projects is auditable without a manual review cycle. The spreadsheet workaround is no longer necessary.
The Guide
This guide is for anyone responsible for risk on a capital programme, whether you are managing it at project level or trying to get a consistent picture across all of them.
It sets out why the problem is structural, gives a practical framework for governing risk across projects, and shows what better visibility changes for the way teams report and make decisions.
No hype, no theory. Just a clear picture of where risk management breaks down at scale and what to do about it.
Contents
Inside the guide
Why project-level registers struggle at scale
The three things that happen reliably when each project team manages risk independently: inconsistency, duplication, and invisible coverage.
The silo problem
Why risk management fails when risk data lives in the wrong place, and what fragmented tools cost capital programmes in practice.
What a programme-level risk library looks like in practice
How to define risk events once, apply them across projects without re-entry, and make coverage a fact rather than an assumption.
How to structure risk categories across a programme
A practical framework for deciding which risks belong in a shared library, with a starting structure across four categories.
How visibility feeds into reporting
What changes when risk coverage is tracked in the platform rather than reconstructed in meetings, and why it matters in regulated sectors.
How Nodes & Links approaches risk across projects
Global Risk Register, AI-powered QSRA, and auditable decision intelligence. Three capabilities that work together on a capital programme.
