PMP · Question #821
The project manager of a large construction project discovers that the blueprints received from the client appear incomplete. What should the project manager do first?
The correct answer is C. Consult with the client to determine if project execution should be continued.. When project blueprints appear incomplete, the project manager's first action should be to consult with the client to clarify the scope and determine how to proceed. This ensures alignment with client expectations and prevents rework.
Question
Options
- AContinue project execution using the current blueprints from the client.
- BEscalate this issue to the project sponsor.
- CConsult with the client to determine if project execution should be continued.
- DReschedule the project execution date.
How the community answered
(23 responses)- A4% (1)
- B13% (3)
- C78% (18)
- D4% (1)
Why each option
When project blueprints appear incomplete, the project manager's first action should be to consult with the client to clarify the scope and determine how to proceed. This ensures alignment with client expectations and prevents rework.
Continuing with incomplete blueprints would likely lead to rework, scope creep, or a product that does not meet client expectations, incurring additional costs and delays.
Escalating to the project sponsor before consulting the client bypasses the direct stakeholder responsible for the blueprints and might lead to premature or misinformed decisions.
The project manager must first consult with the client because the blueprints are client-provided deliverables, and any perceived incompleteness directly impacts the project scope and client expectations. Engaging the client directly allows for clarification of requirements and joint decision-making on whether to proceed, pause, or update the plans, which is crucial for maintaining project integrity and stakeholder alignment.
Rescheduling project execution without first understanding the client's perspective or the true extent of the incompleteness is an overreaction and may not be necessary.
Concept tested: Stakeholder communication and scope clarification
Topics
Community Discussion
6C is correct here. My senior always says incomplete blueprints are a scope question, and scope questions go straight to the client before you touch anything else. You need to talk with the client to confirm whether the missing pieces affect execution now or if you can proceed with what you have. A and D are just charging ahead blindly, and B is premature because you escalate to the sponsor only after trying to resolve it with the client first.
C is right but B tempts you; client owns the blueprints so consult them first.
One of the seniors on my team said the same thing, that the blueprint is the client's baby, but he also mentioned you should check if there is an existing deviation log before you even bring it up with them, since that might already answer the question.
Leaned toward B, but incomplete blueprints mean consult the client first per Stakeholder domain.
B is the only call here. Incomplete blueprints from the client signal a scope and requirements gap that the PM cannot resolve unilaterally, so escalating to the sponsor ensures governance visibility before execution burns budget against flawed inputs.
Actually it is C because incomplete blueprints point to a quality and completeness gap in the deliverables themselves, which the PM should address through the scope management plan and requirements traceability before escalating. My senior always says escalation is for when you are blocked by authority, not when the work product is just unfinished, so I would double check that distinction.