The Issue and Change Control Procedure in PRINCE2 establishes a structured approach for capturing, evaluating, and managing issues that arise during a project. An issue can be any relevant event that has happened (problem), is currently happening (concern), or might happen (risk) that requires mana…The Issue and Change Control Procedure in PRINCE2 establishes a structured approach for capturing, evaluating, and managing issues that arise during a project. An issue can be any relevant event that has happened (problem), is currently happening (concern), or might happen (risk) that requires management attention. This procedure ensures that no potential changes to the project baseline occur without proper visibility and approval, maintaining project integrity. The procedure begins with issue capture, where team members record issues in a standardized format, providing essential information about nature, impact, and urgency. These issues are then logged in the Issue Register, creating an audit trail of all identified issues and their resolution status. Once logged, issues undergo assessment to determine their type (request for change, off-specification, or concern), priority, and severity. This evaluation considers impacts on project objectives, particularly the tolerances for time, cost, quality, scope, benefits, and risk. Based on this assessment, appropriate resolution actions are proposed, which might involve accepting, rejecting, or deferring the issue, or escalating it if it exceeds defined tolerances. The procedure establishes clear authority levels for issue resolution, specifying who can make decisions about different types of issues based on their impact. It defines how approved changes will be implemented, verified, and communicated to stakeholders. Throughout the project, the Issue Register serves as a key management tool for tracking issue status and identifying trends that might indicate underlying problems. Effective issue and change control balances the need for stability with the reality that change is inevitable, ensuring that changes are managed in a controlled manner that protects project objectives.