How often should you update a RAID log?

Capture new information as it emerges, update items after meetings while context is fresh, and review open items at least weekly on active projects. Check urgent items more often and before status reporting.

How can you identify stale RAID entries?

Look for missing owners or next steps, overdue dates, no recent update or review date, and scores or statuses that no longer match current evidence. Ask the item owner to confirm progress.

What should happen when a risk becomes an issue?

Record the event as an issue, update the risk response or status, and preserve the relationship and history so the team can see how the uncertainty materialized and what was done.

Should resolved RAID items be deleted?

Close items with a short outcome and retain useful decisions and context according to the project’s recordkeeping practice. Archive the log when active review ends instead of deleting history just to shorten the list.

How to keep a RAID log up to date throughout a project

Learn when to capture new risks, actions, issues, and decisions; how to run a weekly review; and how to carry accurate RAID updates into status reporting and project closure.

Use practical checks for owners, overdue next steps, stale entries, changed risk scores, and risks that have become issues.