Raid Log Template
Keep a living RAID log — risks, assumptions, issues, dependencies — generated with your architecture instead of rotting in a spreadsheet.
What belongs in a RAID log
A RAID log that earns its keep lists each risk with impact, likelihood, and an owner/mitigation; assumptions with what happens if they're wrong; issues with status; dependencies with dates. It's the first place a delivery lead looks when a project wobbles — keeping it current is cheap insurance.
How Architext builds it
Architext generates a RAID scaffold as part of the solution-architecture document, tied to the same model as the diagram and decisions, so risk tracking starts populated instead of blank.
Document, export, and share
Once the document is right, compile the full solution-architecture document, generate an audience-tailored slide deck, export to PNG, SVG, Mermaid, or PowerPoint, or share a read-only link — all from the same model.
FAQ
- What does RAID stand for?
- Risks, Assumptions, Issues, Dependencies — the four things most likely to derail delivery.
- How is a RAID log different from a risk register?
- A risk register is one quadrant; RAID adds the assumptions, live issues, and dependencies that risks usually hide behind.
- How often should it be updated?
- Every review cadence — a stale RAID log is worse than none because it signals false confidence.
Raid Log Template
Free to start — paste your code or describe your system and watch the diagram build itself.
Open Architext