Which RAID items belong in a project status report?

Summarize items that materially change delivery confidence, threaten a milestone, need escalation, require stakeholder awareness, or need a decision. Routine updates and working detail can remain in the RAID log.

Should a status report copy the entire RAID log?

No. Keep the full record, owners, evidence, and next steps in RAID. The status report should explain the material change, its delivery impact, the response, and any stakeholder ask.

Does a RAID log automatically determine project RAG status?

No. Risks, issues, actions, and decisions inform the project manager’s judgment, alongside agreed measures and other evidence such as milestone progress, scope, capacity, and budget where tracked.

How should status meeting outcomes update RAID?

Record new risks, issues, actions, and decisions with an owner and next step. Update escalated items when the group agrees on a response or date, then retain the outcome so the next report can show what changed.

Use a RAID log to prepare a clear project status report

Learn which RAID items belong in a status report and how to review owners, changes, delivery impact, and decisions before writing.

Translate working RAID detail into a concise stakeholder update, then feed meeting outcomes back into the log. Project health and RAG still require PM judgment.