CAPM Practice: Determine how to conduct stakeholder communication

A decision log records important decisions with context (the situation, options considered, decision made, rationale, date, and decision-maker). It prevents teams from repeatedly re-litigating settled questions and provides context for future team members.

**Why not A:** A decision log records decisions that were actually made, not meetings where decisions failed to happen. Tracking unmade decisions would be an action item or risk log concern. The value of a decision log lies in providing a clear audit trail of choices and their reasoning.

**Why not B:** While budget decisions might appear in a decision log, limiting it to a project manager's budget allocation tool is far too narrow. A decision log captures requirements decisions, design choices, scope decisions, and trade-offs made by various stakeholders — not just financial decisions by one role.

**Why not D:** Restricting the decision log to technical team decisions misses its broader purpose. A decision log supports stakeholder communication by recording decisions across all project domains — business, technical, and organizational. It ensures all stakeholders can reference why decisions were made, regardless of who made them.