Capability
Risk Identification & Registers
Build and keep a live risk register that can actually feed the forecast and the programme — not a workshop slide that dies after kickoff.
C02 — The problem
The technical problem
Many projects have a risk workshop and no risk system. Items are qualitative slogans, owners are unnamed, and nothing is mapped to remaining duration or remaining cost.
Risk Identification & Registers is the operational capability: identify, describe, own, and review risks on a cycle that project controls can use. Qualitative scoring may be included. Full quantitative schedule risk is the Planning capability Schedule Risk Analysis. Mitigation programmes may be included when scoped with the register.
C03 — Engagement
When this capability is needed
-
01
Mobilisation
The project needs a register before the first month is lost.
-
02
Stale register
A kickoff list has not been updated with live issues.
-
03
Forecast challenge
Leadership asks which risks are in the EAC or the completion range.
-
04
Early warning
Emerging issues need a home before they become variance only.
C04 — Scope / method
How the work is approached
Identification, description, ownership, qualitative assessment where useful, and a maintained register. Quantitative schedule risk is a separate Planning assignment. Contingency drawdown policy sits with the parent Risk Management service.
-
01
Set the register structure
Cause, event, effect, owner, actions, and links to WBS/activities where known.
-
02
Identify from delivery
Programme, cost, contract, and site — not only a brainstorm.
-
03
Assess qualitatively if required
Likelihood and impact scales the project will actually use.
-
04
Assign actions and review dates
A cycle, not a mural.
-
05
Feed controls
Items that belong in forecast or critical-path attention.
C05 — Outputs
Typical deliverables
| Output | What it contains |
|---|---|
| Risk register | Live items, owners, and status. |
| Identification record | Sources and dates. |
| Review cycle note | When the register is updated against the reporting calendar. |
| Escalation list | Risks that need a decision this period. |
C06 — Decision value
What this work is used to decide
Which risks require action, watch, or acceptance this cycle, and which belong in the forecast conversation. Identification does not quantify a P-date.
C08 — Project environments
Relevant project environments
C09 — Who we support
Who commonly needs this capability
C10 — Boundaries
Important distinctions
A register does not guarantee that risks will not occur. Quantitative completion ranges are Schedule Risk Analysis.
C11 — Next step
Discuss your project
If this is the technical problem you are facing, talk to Value Construction about the work, the records required, and what you would receive. Outcomes are not guaranteed.