Module · Risk Register
A risk register that does not get archived after week one.
Likelihood × impact scoring, mitigation owners, status workflow, close-out trail - the project risk register that surfaces in the Executive view and the client report pack, not the spreadsheet that gets opened twice.
Why most risk registers die
The risk register is created at week one and re-opened at the post-mortem.
When risk lives in a workbook nobody reads after kick-off, the project loses the early-warning system that would have flagged the £150k overrun two months before it lands.
Owned by no one after week one
The PM populates the register, the team nods, the workbook closes. Nobody updates it. The risks materialise and nobody notices the registers were predicting them.
Inconsistent scoring across projects
One PM scores 3×4, another 5×5, a third writes "high". Director cannot compare risk profiles across projects because the metric is invented per workbook.
No connection to actuals
When risks materialise, no one updates the risk register. The post-mortem cannot answer "did our risk scoring predict what happened?".
What's inside
A risk register that earns a Monday-morning open.
Likelihood × impact scoring
Standard 1–5 × 1–5 matrix with workspace-managed thresholds. Total score drives sort order and surfaces in the executive view.
Mitigation owners
Each risk has an owner, a mitigation, a status (Open / Mitigating / Closed) and a target close date. The register reads as a punch list for who is doing what.
Workspace-consistent scoring
Every project on the workspace uses the same scale. Cross-project risk comparison becomes possible - Director sees risk profile by sector, by client, by phase.
Close-out trail
When a risk materialises (or is mitigated), capture what happened. The post-mortem read happens against real evidence, not faulty memory.
Surfaces in executive view
Top-3 open risks per project surface on the executive intelligence card. Director sees the projects with the worst risk exposure without opening individual registers.
Client report integration
A redacted client-facing version of the risk register ships in the client report pack. Clients see what you choose to share.
Who uses it
Built for the people watching for trouble - and the people defending against it.
Project Managers
A live punch list of what could go wrong + who is mitigating it. Friday status updates become "here's what we're managing", not "everything's fine".
Construction Managers
Site risks (programme, trade clashes, sequencing) live alongside commercial risks. One register, one conversation.
Directors
Workspace-wide risk profile in seconds. Identify the projects most at risk before the cost report shows it.
See a risk register that someone opens on a Monday.
A 20-minute walkthrough on a real project - bring your existing register; see the gaps it leaves.
Frequently asked questions
Can we customise the scoring scale?
Workspace-level scoring scales (3×3, 5×5, weighted) are on the roadmap. Today the standard 5×5 likelihood × impact is enforced for cross-project comparability.
Do client portal users see the register?
A redacted client-facing version is configurable per project - toggle which risks and which fields the client sees. Internal scoring and mitigation notes stay internal by default.
Is there integration with the variations?
When a risk materialises into a variation, the variation can be linked back to the originating risk for trail purposes. Auto-linking is on the roadmap.
Connects to
Other Projavio modules that work alongside this one.
Project Workspace
The project workspace every internal user lives in. One project record - every other module hangs off it.
Site Reports
Daily site reports filed from a phone, surfaced in the project record. Photos, weather, attendance, delays.
Variations
JCT/NEC-aware variation lifecycle: instruction → cost → approval → impact on programme + cost report.
A risk register that predicts your bad weeks.
Stop running risk on a workbook nobody reads after kick-off.