A software project stakeholder says they never received functionality test status reports. The project manager provides the reports, and the stakeholder finds an important functionality for their area was not tested. Which tool should the project manager have used to prevent this?

The stakeholder register is the correct answer because it documents key stakeholder information, including their communication requirements and expectations. By thoroughly analyzing and documenting these details, the project manager could have identified the stakeholder's need for specific functionality test status reports and ensured they were included in the communication plan. The issue log is used to track and manage project issues, not to prevent them proactively by documenting communication needs. The project scope statement defines what is and is not included in the project, but it doesn't detail individual stakeholder communication preferences. The project charter formally authorizes the project and names the project manager, but it doesn't delve into specific stakeholder communication requirements.