At a project gate review you discover a deliverable needs corrective actions to meet quality requirements. What should you do first?

When a deliverable fails to meet quality requirements, it becomes an issue that needs to be formally tracked and addressed. The first step is to update the issue log to document the problem, its impact, and its status. Identifying involved stakeholders ensures clear communication and collaboration, while assigning resources to corrective actions initiates the resolution process. Submitting a change request to update quality requirements is incorrect because the deliverable failed to meet existing requirements; the requirements themselves are not the problem. Updating the risk register is also incorrect because this is an actualized problem, not a potential future event. Identifying responsible resources and requesting a team development plan is premature and punitive; the immediate focus is on correcting the deliverable.