In one of the project meetings during a project execution, a new stakeholder attends and highlights a new risk. What should the project manager do next?

Testing addresses quality control for known issues, not the immediate documentation and management of a newly identified risk.

Adding the stakeholder to the stakeholder register formalizes their involvement and ensures they receive appropriate communication and engagement going forward. Adding the risk to the risk register initiates the risk management process, allowing the team to analyze, prioritize, and plan responses to the identified threat. Both registers are living documents updated throughout the project lifecycle.

Ignoring a valid risk because the stakeholder was absent earlier violates the PM's responsibility to manage all risks regardless of their source.

Lessons learned capture knowledge for future projects, but deferring a live risk to project completion leaves it unmanaged and could cause project harm.