Notifying the CCB that an approved change “failed” is consistent with logging and escalating an issue/incident arising from change implementation. In CompTIA Project+ objectives, the change control process includes not only approval and implementation, but also validating the change implementation and communicating change deployment. If validation shows the change did not achieve the expected outcome, that result must be documented and escalated through the same governance path (often the CCB) so the project can decide whether to roll back, revise, or raise a new change request.

CompTIA also separates risk management (responses to potential future events) from issue management (handling problems that have already occurred), including issue tracking, escalation path, ownership, and a resolution plan, and it highlights “connections between issues and changes.” A failed implemented change is an issue now, so an incident report (documenting what happened, impact, and next steps) best matches the control process being followed.

“Scope creep” is unauthorized scope growth, “risk response” is for anticipated risks, and “recovery plan” could be a next action, but the process described is the reporting/documentation and escalation of the incident.