When is a change task for Post Implementation Review created for an unauthorized change?

The creation of a change task for a Post Implementation Review, particularly in the context of an unauthorized change, is correctly identified as occurring when the change request moves to a state of Review. At this stage, the organization is evaluating the change that has been implemented, assessing both its impact and whether it aligns with the established processes.

In the context of unauthorized changes, it's crucial to conduct a Post Implementation Review to gather insights and analyze the implementation's outcome. This helps ensure accountability and provides an opportunity for learning, ultimately improving future change management practices. Thus, moving to the Review state prompts the necessity of a change task dedicated to reflecting on the unauthorized change, its execution, and its repercussions.

Other states, such as Close or Assess, do not trigger the required review task in the same manner. Closing a change request may imply that all tasks have been completed, while the Assess stage is primarily focused on evaluating the feasibility and potential impact before any implementation occurs. Therefore, the Review state is the appropriate point for initiating a Post Implementation Review, making it clear why this answer is correct.