A RAID log gives a project team one place to track four different kinds of uncertainty. Risks are things that might happen. Record the likely impact, a response, and an owner. Assumptions are things you are treating as true. Identify how and when they will be checked. Issues are problems that already exist. Set an action, an owner, and a target resolution date. Dependencies are things the work needs from another task, team, or decision. Make the handoff and timing explicit. Keep the log short enough to review regularly. An item without an owner or a next action is unlikely to help your team. Review the most consequential items in your normal status meeting, and close resolved items with a short explanation.