PMP · Question #1177
A project manager notices that the project team is unlikely to complete the development of a system on time before the testing start date, which was based on the technical complexity of the project. W
The correct answer is C. Work with the project team to evaluate the potential delay.. Before communicating a potential delay to the client, the project manager should first collaborate with the project team to thoroughly evaluate the situation and understand the potential impact and possible mitigation strategies.
Question
A project manager notices that the project team is unlikely to complete the development of a system on time before the testing start date, which was based on the technical complexity of the project. What should the project manager do before communicating with the client during the regular project progress meeting?
Options
- AAsk the project sponsor to inform the client in the next update.
- BDo not disclose the likelihood of a delay as it is yet to happen.
- CWork with the project team to evaluate the potential delay.
- DTell the client about the chance for the potential delay.
How the community answered
(18 responses)- A17% (3)
- B6% (1)
- C72% (13)
- D6% (1)
Why each option
Before communicating a potential delay to the client, the project manager should first collaborate with the project team to thoroughly evaluate the situation and understand the potential impact and possible mitigation strategies.
Delegating the communication to the project sponsor before fully understanding the situation yourself and having a plan is an abdication of the project manager's responsibility for client communication.
Hiding potential delays is a breach of transparent communication and can severely damage client trust if the delay eventually materializes.
Before communicating any potential issues to the client, the project manager must first gather all relevant information and understand the full scope of the problem. Working with the project team allows for a detailed assessment of the delay's extent, causes, and potential solutions, enabling an informed and prepared discussion with the client.
Communicating a potential delay to the client without first understanding its full impact, causes, and potential solutions is premature and can create unnecessary alarm or lead to reactive decisions.
Concept tested: Risk management and transparent communication
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/project-risk-management
Topics
Community Discussion
5
Mei-Ling H.Jun 18, 2026C is correct. The key word in the stem is before, meaning you must analyze the actual impact with the team before you say anything to the client, so D is a trap for people who rush.
Orla P.Jun 20, 2026Right call on C, and the other trap to watch for is the answer that says analyze impact but skips the team part entirely, because it looks lean and efficient but leaves you without the full picture before you escalate.
Orla P.Jul 5, 2026C. You assess the impact with the team before you tell the client anything.
Samuel O.Jun 14, 2026C is the right call here but the phrase "before communicating with the client" is what trips people up, since D sounds like the honest thing to do. In practice you never go to a client meeting without first sitting down with your team to size up the actual slip, same as I learned the hard way running integration work years ago.
Brenda K.Jul 1, 2026C is correct and it is a 30 second pick. Before you ever talk to the client you need the actual numbers, so work with the team to evaluate the potential delay and figure out the real impact on the schedule. A and D jump the gun because you communicate without doing the analysis first. B is just dishonest so cross that off immediately.