Business analysis glossary
RAID Log
What it is
A RAID log is one shared register of the project's Risks, Assumptions, Issues and Dependencies. Each entry has a description, an owner, a date, a rating or status and the next action. Teams review it regularly so that uncertain or blocking items are tracked in one place instead of being scattered across emails and meeting notes.
Why it matters
Projects rarely fail from one big surprise. They fail from small risks nobody owned and assumptions nobody checked. A RAID log gives every concern an owner and a date, and it feeds the status report. Business analysts add many entries, because elicitation uncovers assumptions, open questions and dependencies on other teams long before they become problems.
Example
During discovery at Deccan Freight, Priya logs an assumption that drivers will have smartphones, a dependency on the telematics vendor's new API and a risk that monsoon season delays the pilot. Each gets an owner and review date. When the vendor slips, the dependency turns into an issue that the project manager escalates the same week.