#2: RAID Log
Status: Open
Things the plan depends on being true that nobody has actually confirmed.
This is the quadrant teams skip, and it is the one that causes the nastiest surprises. Every schedule contains assumptions. Writing them down is what turns "we thought someone had checked" into a named owner and a date.
Use the Validated status once an assumption is confirmed. If it turns out to be false, close it and raise the consequence as a Risk or an Issue — see A-01 below for a worked example.
Created by Vicky Aug 7, 2026
- Legacy customer records are clean enough to migrate without manual repair #12
- The client's IT team will provide the UAT environment by 1 June #13
- Support volume will rise by no more than 15% in the first month after launch #14
Current API rate limits are sufficient for portal traffic #15- No security audit is needed beyond the annual SOC 2 review #16