PMP · Question #539
A project stakeholder complained that they did not receive an important delivery that was stated in the schedule. The team member responsible for this deliverable explained that they sent an email to
The correct answer is A. Confirmed that the stakeholder was made aware of the delivery delay.. To prevent a stakeholder from missing a critical delivery, the project manager should have confirmed the stakeholder actually received and acknowledged the communication about the delay.
Question
A project stakeholder complained that they did not receive an important delivery that was stated in the schedule. The team member responsible for this deliverable explained that they sent an email to the stakeholder, advising them that the deliverable would not be delivered on time. What should the project manager have done to avoid this situation?
Options
- AConfirmed that the stakeholder was made aware of the delivery delay.
- BCommunicated with the stakeholder directly regarding the delivery delay.
- CTold the team member to send the unfinished deliverable to the stakeholder and finalize it later.
- DEnsured that the team member did not communicate directly with the project stakeholder.
How the community answered
(60 responses)- A73% (44)
- B8% (5)
- C3% (2)
- D15% (9)
Why each option
To prevent a stakeholder from missing a critical delivery, the project manager should have confirmed the stakeholder actually received and acknowledged the communication about the delay.
Effective communication involves not just sending information but also ensuring it is received and understood by the intended audience. The project manager should have confirmed that the stakeholder was aware of the delay, perhaps through a follow-up or by establishing a communication plan that requires acknowledgment for critical updates, thereby preventing miscommunication and ensuring stakeholder expectations are managed.
While the project manager communicating directly is an option, it is not always scalable or efficient; the core issue here is the lack of confirmation, not necessarily who sent the initial message.
Sending an unfinished deliverable just to meet a deadline could lead to quality issues and further stakeholder dissatisfaction, which is a poor practice.
Restricting team members from communicating with stakeholders can create bottlenecks and hinder agile collaboration; the focus should be on proper communication protocols, not isolation.
Concept tested: Effective communication management and confirmation
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/manage-communications
Topics
Community Discussion
3
Fatima Z.Dec 30, 2025A is correct, and here is your memory hook: A stands for Aware, and the PM must always Confirm the stakeholder is Aware. The team member sent the email, but the PM never closed the loop to verify it was actually received and understood, which is why the stakeholder was caught off guard.
Luis F.Jan 20, 2026Yeah A is the right call here. The PM needed to verify the stakeholder actually got the message since an email sent does not equal an email received, especially for important schedule changes.
Fatima Z.Jan 21, 2026Spot on with A, and remember the mnemonic RRR for schedule changes: Requested, Received, Read - if you cannot prove all three, you do not have communication, you have hope.