Separate Risks, Issues, and Assumptions in Your Project Log
Classify project risks, active issues, assumptions, and dependencies correctly, with examples showing how ownership and next actions differ.
Classify by what is known now
A risk concerns an uncertain event that could affect an objective. An issue is an existing problem that needs resolution. An assumption is something the plan treats as true until it is validated. These categories are useful because they imply different actions. You prepare for a risk, resolve an issue, and test an assumption. A single situation can move between categories as evidence changes.
Follow one situation through its lifecycle
Suppose a migration plan assumes a supplier exports historical records in the required format. Before checking, that belief belongs in the assumption log with a validation date. If the supplier may not support the format, record the resulting risk. Once a sample export fails validation, there is an issue to resolve. Keep links between the records so the team can trace the reasoning instead of creating disconnected entries for the same situation.
Give each record the right next action
An assumption needs an evidence owner and a test. A risk needs a response owner, trigger, and residual exposure. An issue needs a resolution owner, impact assessment, and target date. A dependency needs a supplying party, receiving party, and required handoff. The dependency mapping guide explains that fourth category. A shared log is acceptable, provided its fields make the differences clear.
Avoid duplicate reporting and premature closure
Do not retain an active risk and a matching issue with different owners who assume the other person is handling the work. Close or reclassify the uncertainty, preserve its history, and track the current problem in one place. Similarly, an assumption is not validated because someone repeated it confidently in a meeting. Attach a sample, decision, test result, or other evidence that supports the conclusion.
Review the log around upcoming decisions
Focus attention on assumptions that must be checked before commitment, issues blocking the next milestone, and risks approaching their trigger dates. Archive entries that no longer influence delivery. A short, current log is easier to use than a comprehensive but stale one. Combine it with the risk register guide and response planning method to keep uncertainty, action, and accountability connected throughout the project.
Published by AgilePro.info under our Editorial Policy. Guidance is based on established delivery practice and is general information, not professional advice for a specific project.