Blog
Risk Registers Work Only When Linked to the Plan
Creating a risk register at project kickoff is the easy part. Its value for project control tends to fade quietly: the schedule changes, response measures never make it into the plan as activities, and risks that have already materialised are still marked as “open” or “not occurred”.
On 11 November 2026, a GPM practice article showed this using a constructed project with eight risks. The author compared a manual review against two AI-assisted approaches, one working from exported data and one with direct access to project data. Given complete data, both AI approaches identified the same gaps. The standard export alone was not enough; the full comparison required two views containing 34 columns. This is no general proof of effectiveness, but it is a useful practical test.
The register must connect to project control
The data relationship matters more than the AI itself. A risk only becomes controllable when it is linked to the affected schedule activity, a response measure, an owner and a visible early indicator. This also reflects ISO 31000 and the PMI standards: risk management is a continuous part of project control, not a document you create once.
In software projects, I regularly use AI for plausibility checks. It exposes inconsistencies faster than a manual pass, but it must not determine probability or response on its own. That decision belongs to the team and the named risk owner.
The weekly review can follow a practical pattern:
- Schedule link: Each material risk points to the milestones or activities it affects.
- Response: Mitigation measures are in the project plan, with dates and owners.
- Early indicator: A measurable signal shows whether the risk is materialising.
- Evidence: Planned and actual values back the assessment; changes go into the decision log.
In a data migration, a growing reconciliation variance can serve as the early indicator. Once it crosses the agreed threshold, updating the register is no longer enough; a specific analysis and correction package has to appear in the plan.
What project owners should do now
In your next risk review, do not begin with the traffic-light colour. Begin with the link to the current plan. Take the ten risks most likely to affect schedule, budget or acceptance, and close any gaps in ownership, responses and early indicators.
The modification date alone does not make a risk register current. What matters is whether its entries have consequences in the project plan.