Is a RAID log the same as a risk register?

No. A risk register focuses on uncertain events and responses. A RAID log adds actions, issues, and decisions in the same record so delivery signals stay in one place.

Should I keep both a risk register and a RAID log?

You can serve both audiences, but choose one authoritative place to update each risk. Use links, filters, or exports for the other view so scores and ownership do not diverge.

When is a risk register enough?

A risk register is enough when uncertain events are the main review question and actions, current issues, and decisions already have reliable homes. Use a RAID log when that surrounding work is getting lost.

What happens when a risk becomes an issue?

Keep the risk history, then open or link an issue for the event that has happened. Give the issue an owner, recovery step, and date; do not keep treating a current blocker as only a likelihood score.

How does PMHub handle RAID vs risk-only views?

PMHub stores all RAID types together. You can filter by type (e.g. risks only) while keeping actions and issues linked to the same project context.

RAID log vs risk register: choose the record that fits the work

A worked project example shows when to record a risk, issue, action, or decision and how to choose one authoritative source.