What colleagues do todaySource-backedVerified 2026-04-20
Project Manager / Manage the RAID log (risks, assumptions, issues, dependencies) and decision records
Maintain a RAID log by hand in Confluence or a Google Sheet
Most PMs keep their RAID log as a tab in a shared spreadsheet or a Confluence table. After each team meeting, the PM adds new rows, closes resolved items, and hopes engineers revisit it before the next steering committee. Quality varies; stale logs get ignored and surface as surprises at the worst moment.
Best for
Coordination
Confluence ≈$5/user/mo · Google Workspace ≈$6/user/mo
Setup
0 min
One-time setup estimate
Workflow
- 1Collect the source material for "Manage the RAID log (risks, assumptions, issues, dependencies) and decision records" before opening the tool.
- 2Run the starter prompt in Confluence / Google Sheets and paste in the real context.
- 3Review the output for accuracy, tone, names, numbers, and policy-sensitive details.
- 4Save the improved prompt or checklist so the next run takes less time.
Inputs you need
- - Project Manager
- - Manage the RAID log (risks, assumptions, issues, dependencies) and decision records
- - Examples, notes, files, or customer context for this task
- - Your preferred tone, constraints, and final format
Expected output
- - Maintain a RAID log by hand in Confluence or a Google Sheet
- - A usable draft or workflow for manage the raid log (risks, assumptions, issues, dependencies) and decision records
- - A repeatable prompt you can improve after each run
Ready-to-copy asset
Starter prompt
No copy-ready prompt is available for this solution yet.
Caveats
- - Do a human review before sending, publishing, filing, or making a decision.
- - Verify numbers, names, claims, citations, and compliance-sensitive details.
- - AI drafts. You decide. Final responsibility is yours.
Measurable value
40 min after setup
Before: 40 min. After: 40 min.