Tip

Write RAID entries a sponsor will actually read

Short answer

Write every RAID entry as cause, event and impact in one sentence, give it one owner and a date, and say what decision you need. If an entry asks nothing of anyone, it is a note, not a risk.

1. Use cause, event, impact

Weak: “Vendor risk.” Strong: “Because the vendor has not confirmed API access (cause), integration testing may start late (event), delaying go-live by two to three weeks (impact).”

2. One owner, a named person

A team is not an owner. If nobody will lose sleep over it, nobody will act on it.

3. A date, always

A review date for risks, a resolve-by date for issues. Entries without dates get read once and then never again.

4. Say what you need

End with the ask: “Decision needed: approve 40,000 (in our budget currency) for a second vendor by 30 Oct.” Sponsors act on asks, not on descriptions.

5. Close entries out loud

When a risk is closed or becomes an issue, say so in the next report. Silent closures make the log look like a graveyard and teach people to ignore it.

See your portfolio the way your sponsor should

SprintPM opens soon, in English and Arabic. Join the waitlist to be among the first in.