Project issue log
RegisterWhat is affecting the project now — who raised it, who owns it, when it is needed by, and how it got resolved.
An issue has happened. A risk has not
This is the distinction the two tools are built around, and collapsing them is the most common thing a homemade tracker does. Something that might go wrong needs a mitigation and a review date; something that has gone wrong needs an owner and a resolution. When a risk occurs, close it over there and raise it here — the history of both stays intact.
Nothing escalates itself
No notifications, no automatic assignment, no aging color that turns red on your behalf. What the log does is order itself by what is owed, so the item nobody has touched surfaces without anybody having configured a rule. The judgment about what to do stays with a person.
Where it sits
Risks live in the risk register, changes to scope in the change request log, the reasoning behind decisions in the decision log, and the summary that goes upward is the status report.
An operational log. CompliMaint assigns nobody, escalates nothing, notifies nobody, and computes no effect on any date or cost. An issue is open or closed because somebody said so. Everything runs on your device.
Questions people ask
- What is the difference between an issue and a risk?
- An issue has happened. A risk has not. That is the whole distinction, and it is why they are two tools: the questions you ask about something happening now are different from the questions you ask about something that might. When a risk occurs it stops being a risk — mark it Occurred over there and raise it here.
- Does it escalate anything?
- No. Nothing here notifies anybody, assigns anybody or moves an issue anywhere on its own. An issue is open because somebody said so and closed because somebody said so. What the log does is sort what is owed to the top, so the thing that has been sitting for three weeks is the first thing you see.
- Does it work out the impact on the schedule?
- No. It computes no delay, no critical path effect and no cost. Whether an issue moves a date depends on the work, the sequence and what else is happening — none of which this tool knows. What it holds is the date you said you needed it by.
- Why Blocked as well as Open?
- Because an issue waiting on somebody outside your control is a different kind of open, and the two want different conversations. Blocked is colored as waiting rather than as active work, which stops a list of things you cannot progress reading as a list of things you are ignoring.