This clause sets out the purpose of issue management, which is to settle issues so that the project's objectives are not harmed, and establishes that issues are raised by all concerned with an escalation route to the right management level. Issues should be spotted as they arise, defined with the surrounding facts, and understood by those involved. The project should give stakeholders a safe and dependable way to raise them and capture them at every level for the team to manage. Each issue should be logged and analysed promptly so the most damaging are tackled first, with someone made responsible for taking it to resolution, and the record typically notes title, type, date raised, description, priority, impact, actions and status. Resolving an issue means recording and dealing with an event or problem that endangers success or offers a chance to gain. There should be an escalation path to the right management level for decisions, and the method for evaluating and addressing issues belongs in the governance and management framework. Decisions and the reasoning behind them must be shared with the team, the originator and stakeholders, and outcomes recorded for later reference and learning, with escalation available where resolution stalls or is unacceptable. Resolution may require a plan deviation or baseline change.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.