PMP · Question #1012
During a project's closing phase, the project manager identified that the client did not use one particular service. The client then asks the project manager to informally extend the service beyond…
The correct answer is B. Issue a change request and activate the formal change control process to address the situation. A client requests an informal extension of a service beyond its contractually defined end date during project closure.
Question
During a project's closing phase, the project manager identified that the client did not use one particular service. The client then asks the project manager to informally extend the service beyond the contract end date. The contract is clear about the expiration of the service. How should the project manager address this situation in order to close the project?
Options
- AEscalate the request to the functional manager to approve the additional service hours.
- BIssue a change request and activate the formal change control process to address the situation.
- CAccept the client's proposal to use the service until the additional hours are exhausted.
- DDeny the request and include it in lessons learned documentation for the next contract renewal.
How the community answered
(49 responses)- A2% (1)
- B84% (41)
- C10% (5)
- D4% (2)
Why each option
A client requests an informal extension of a service beyond its contractually defined end date during project closure.
Escalating to a functional manager bypasses the formal change control process and may not have the authority to amend contractual agreements or approve scope changes.
Any deviation from the established contract terms, such as extending a service beyond its agreed-upon expiration, constitutes a scope change and must be addressed through the formal change control process. Issuing a change request ensures that the modification is properly evaluated, approved by all necessary parties, and formally documented, maintaining contractual integrity and project governance.
Accepting an informal proposal to extend service violates the existing contractual terms and could lead to legal and financial liabilities without proper documentation and approval.
Denying the request outright without exploring formal options for resolution might damage client relations and fails to use established project governance for potential contract modifications.
Concept tested: Formal change control for contract modifications
Topics
Community Discussion
8
Orla P.Dec 11, 2025B is correct because anything that extends scope or services beyond the contract has to go through the formal change control process, no matter how casually the client frames it. Never accept an informal extension at closing, just submit the change request and let the process play out.
Samuel O.Dec 12, 2025B is right but in my experience the client often pushes back hard at closing because they thought it was implied, so document the ask in writing the same day and get your sponsor to sign off on the change request before any extra work starts.
Wei W.Dec 1, 2025I first leaned toward D because the contract is clear and denying seems straightforward, but the client is asking for something outside the agreement so you need a formal change request to evaluate and document the decision properly. B is the exam answer because any deviation from contract terms goes through change control, not informal side agreements.
Orla P.Dec 1, 2025Agreed on B and the change control reasoning, but the real trap here is that the formal contract actually makes people want to just say no, when the correct move is still routing it through the documented process so the decision and its rationale are on the record.
Samuel O.Dec 7, 2025I first leaned toward D because the contract is clear and I've seen plenty of clients try to grab free extras at closeout. But the PM's job is to run it through formal change control so the business can decide whether to absorb the cost or push back, not to unilaterally deny it.
Ingrid P.Dec 15, 2025Saw this on my exam last month, the phrase informally extend is the trigger that should scream change request to you. I almost picked D because the contract is clear, but anytime a client wants something outside the current agreement you run it through formal change control, period. Made a card for this one with a two-week review interval because the wording tricks a lot of people.
Ola B.Nov 17, 2025B is correct here because anything that deviates from the signed contract has to go through formal change control, no exceptions. D is the tempting trap since the contract is clear, but outright denying the request without running it through the process ignores how change handling actually works in the PMI mindset. Even if you suspect the change will get rejected, you still document it and let the process play out. I actually spun up a quick lab scenario last week to test this flow with a mock CCB and it really helps solidify why the process matters more than your personal read on the situation.
Samuel O.Nov 20, 2025Agreed on B, and after dealing with a couple of real contract mods over the years I can tell you the CCB process exists precisely for those moments when your gut says reject, because documenting the request protects you legally even when the answer ends up being no.