A project manager is closing a major infrastructure project. The primary vendor has several pending claims and incomplete warranty documentation. The project sponsor wants to finalize administrative closure quickly. How should the project manager proceed?

Document outstanding issues and negotiate settlements before finalizing the project administrative closure.

Finalize the administrative closure and transfer the pending claims to the organizational legal department.

Release the vendor's resources and update the organizational process assets with the warranty deficiencies.

Withhold the final payment indefinitely while approving the administrative closure to satisfy the sponsor.

Warranty responsibilities must be clear after handover. Which checklist items ensure accountability during the warranty period?

Escalation contacts, decision trees, owners, and SLA commitments

Only the original project charter and scope baseline

Vendor marketing brochures and installation guides

Team member contact lists without roles or SLAs

Project closure must occur under tight deadlines with audit requirements. Which sequence integrates administrative, procurement, and archival steps defensibly?

Reconcile finances, obtain supplier evaluations, archive baselines, then release team

Release project team before completing handover of administrative responsibilities

Close financial accounts without documented sign-off from finance and procurement

Archive unversioned artifacts then release team before financial reconciliation

During project closure, the project manager notices that the final acceptance document only contains the project sponsor's signature. Operations and procurement have not yet signed. What should the project manager do next?

Navigate the sign-off matrix to secure documented approvals from all required cross-functional stakeholders.

Archive the document with the single signature and transfer remaining closure duties to the functional managers.

Release the final project funds immediately since the sponsor holds the ultimate financial decision authority.

Accept the sponsor's signature as final authorization and proceed with the decommissioning of project controls.

Distributed teams store project artifacts in multiple repositories. Which policy prevents archiving ambiguities during closeout?

Mandate baselining rules with automated version control enforcement checks

Rely on team leads to coordinate versions through weekly status meetings

Allow teams to select their own repository tools without central governance

Store all versions indefinitely and let future users determine the baseline

A new financial application has met all technical acceptance criteria and functions perfectly in the staging environment. However, during the phase closure review, the project manager discovers that the operational runbooks and support service-level agreements are entirely undocumented. What is the most appropriate course of action?

Halt the formal handover process and communicate the specific readiness gaps to the operations team.

Proceed with formal acceptance since the application meets all technical and functional requirements.

Escalate the lack of documentation to the project sponsor and release the development team resources.

Unilaterally approve the transition and assign a dedicated developer to write the operational manuals.

Sponsor delays formal sign-off. Which steps allow administrative closeout without transferring operational liability?

Complete non-liability tasks, preserve acceptance artifacts, and escalate formally

Sign off administratively before all acceptance tests are passed and documented

Interpret verbal sponsor comments as formal acceptance and close the project

Omit requirement traceability when assembling final acceptance evidence package

Key subject matter experts (SMEs) are scheduled to leave a project early for another urgent organizational initiative. The project is nearing completion, but critical operations handover activities remain. What should the project manager do to secure their tacit knowledge?

Schedule early shadowing, create runbooks, and conduct recorded walkthroughs before the experts depart.

Instruct the departing subject matter experts to write a comprehensive final project summary report.

Reassign the remaining project team members to immediately take over the departing experts' daily tasks.

Update the stakeholder engagement plan to reflect the reduced availability of the subject matter experts.

A project has complex scope deviations requiring final sponsor sign-off. Which approach best reconciles engineering evidence with sponsor expectations?

Structured evidence package with traceability matrix and sponsor walkthrough

Defect log and change requests submitted for sponsor review without evidence

Summary presentation of changes without linking to original requirements

Verbal confirmation of deliverables followed by immediate closure documentation

Multiple projects close simultaneously. Which criterion should guide prioritization of lessons for rapid ingestion?

Reuse value, risk mitigation impact, and ease of adoption

Length of the lessons-learned document

Chronological order of project completion dates only

Number of team members who attended the session

2.2.7

Domain 2 of 3 · Process · task

Project status, artifacts and closure for the PMP®

A status report is the last step of an analysis, and closure is a checklist with signatures on it. This topic covers both ends of that work: saying where the project stands in a way the numbers support, and finishing it so nothing is left without an owner.

Exam: PMP
Domain: Process
Domain weight: 41%
Packages: 17
Updated: Oct 13, 2026

01Reconcile, then report

The outline's task on evaluating project status lists metrics, analysis and reconciliation first, and only then communicating status (PMI® Examination Content Outline, paraphrased). A status color agreed in a hallway before the meeting may keep the peace; it still skips the reconciling step, the check that the schedule, the cost data, the risk log and the team's own account all say the same thing.

A familiar mismatch: the weekly report shows green while the risk log carries three open high-severity risks and the last two milestones have moved. Neither source is wrong on its own; the report is wrong for not reconciling them. When the sources need a common yardstick, earned value management supplies one. The habit to carry into the exam is simpler: a number you cannot trace is an opinion.

The rest of the task is about the artifacts themselves: tailor them to the reader, keep them versioned and findable, and retire the ones nobody opens. Who receives which report, and how often, is settled under communication and knowledge transfer.

Counting both tasks, status and closure, the topic is worth about 8.2% of the exam on our arithmetic: two of the ten Process tasks, at PMI's 41% domain weight as of October 2026.

02Three words for three different events

Acceptance, transition and closure compared

Point	Accepted	Transitioned	Closed
Question it answers	Does the deliverable meet the agreed criteria?	Can the receiving team run and support it?	Is every project obligation finished or formally handed on?
Who confirms	The customer or sponsor named in the acceptance criteria	The operations or business owner taking it over	The sponsor, against the closure criteria in the plan
Evidence	Signed acceptance against the criteria	A readiness check: support model, documentation, trained users	Approvals, closed contracts and finances, archived records
Can it be partial?	Yes, as conditional acceptance with the open items written down	Yes, with a dated plan for each gap	No. Open items move to a named owner first

03Where closure happens on a hybrid project

Every iteration
Review and retrospective
Increments are accepted against the definition of done, and the team adjusts its own way of working.
Phase gate
Phase closure
The phase's deliverables and exit criteria are checked before anyone authorizes the next phase.
Final release
Acceptance and transition
Formal sign-off, a receiving team that is ready, and every open item with an owner and a date.
Project end
Administrative closure
Contracts and accounts closed, records archived where they can be found again, people released, lessons filed.

If the archive cannot answer an auditor's question two years later, the project was finished but never closed.

04Close it out

This set runs from mid-project reporting to the last signature on the closure checklist.

Work packages 17

WP 01A project manager is closing a major infrastructure project. The primary vendor has several pending claims and incomplete warranty documentation. The project sponsor wants to finalize administrative closure quickly. How should the project manager proceed?
Debrief answer to open the notes
1. AClosing and passing claims to legal leaves the project's own open obligations unresolved.
2. BCorrect: Procurement closure requires claims settled and documentation complete, so resolve them before administrative closure.
3. CReleasing the vendor and only logging the deficiencies leaves warranty gaps open.
4. DWithholding payment indefinitely without a settlement invites disputes and is not a closure step.
More notes below ↓
WP 02Warranty responsibilities must be clear after handover. Which checklist items ensure accountability during the warranty period?
Debrief answer to open the notes
1. ACorrect: Named owners, escalation contacts, decision trees and SLA commitments make clear who acts during the warranty period and how fast.
2. BThe charter and scope baseline describe the project, not who handles warranty claims.
3. CBrochures and installation guides do not assign warranty responsibilities.
4. DA contact list without roles or SLAs shows who exists, not who is accountable.
More notes below ↓
WP 03Project closure must occur under tight deadlines with audit requirements. Which sequence integrates administrative, procurement, and archival steps defensibly?
Debrief answer to open the notes
1. AReleasing the team before handover loses the people who know the open items.
2. BClosing accounts without finance and procurement sign-off leaves the audit trail incomplete.
3. CUnversioned archives and an early team release both fail the audit requirement.
4. DCorrect: Reconcile finances, evaluate suppliers, archive baselines, then release the team; this order keeps people available until the records are complete.
More notes below ↓
WP 04During project closure, the project manager notices that the final acceptance document only contains the project sponsor's signature. Operations and procurement have not yet signed. What should the project manager do next?
Debrief answer to open the notes
1. ACorrect: Final acceptance needs every required approval, so work through the sign-off matrix until operations and procurement are on record.
2. BArchiving an incomplete acceptance and handing off duties leaves closure unfinished.
3. CReleasing funds before all sign-offs skips required approvals and removes leverage.
4. DThe sponsor's signature is necessary but not sufficient when the sign-off matrix requires others.
More notes below ↓
WP 05Distributed teams store project artifacts in multiple repositories. Which policy prevents archiving ambiguities during closeout?
Debrief answer to open the notes
1. ACoordinating through meetings relies on memory and does not prevent version conflicts.
2. BCorrect: Clear baselining rules enforced by automated version control make the authoritative version unambiguous across repositories.
3. CLetting each team pick its own tools without governance creates the ambiguity the policy should prevent.
4. DKeeping every version without marking the baseline leaves future users guessing.
More notes below ↓
WP 06A new financial application has met all technical acceptance criteria and functions perfectly in the staging environment. However, during the phase closure review, the project manager discovers that the operational runbooks and support service-level agreements are entirely undocumented. What is the most appropriate course of action?
Debrief answer to open the notes
1. AMeeting technical criteria is not the same as being ready to operate; without runbooks and SLAs, support cannot run the system.
2. BCorrect: Transition readiness is part of acceptance, so pause the handover and give operations the specific gaps to close.
3. CReleasing the developers removes the people best placed to fill the documentation gap.
4. DApproving alone bypasses operations, and one developer writing manuals after the fact is a weak fix.
More notes below ↓
WP 07Sponsor delays formal sign-off. Which steps allow administrative closeout without transferring operational liability?
Debrief answer to open the notes
1. ASigning off before acceptance tests pass removes the evidence of conformance.
2. BCorrect: Finish the tasks that carry no liability, keep the acceptance evidence intact, and escalate the delay formally, so ownership transfers only with a signature.
3. CTreating verbal comments as acceptance transfers liability without a record.
4. DDropping traceability weakens the evidence package the sponsor must sign.
More notes below ↓
WP 08Key subject matter experts (SMEs) are scheduled to leave a project early for another urgent organizational initiative. The project is nearing completion, but critical operations handover activities remain. What should the project manager do to secure their tacit knowledge?
Debrief answer to open the notes
1. AA written summary captures explicit facts but rarely the tacit know-how.
2. BShifting tasks without transferring knowledge leaves the team learning on the fly.
3. CCorrect: Tacit knowledge transfers best through practice; shadowing, runbooks and recorded walkthroughs capture it while the experts are still available.
4. DUpdating the plan records the problem without solving it.
More notes below ↓
WP 09A project has complex scope deviations requiring final sponsor sign-off. Which approach best reconciles engineering evidence with sponsor expectations?
Debrief answer to open the notes
1. ASubmitting logs and change requests without evidence leaves the sponsor unable to verify anything.
2. BA summary not linked to the original requirements cannot show which deviations were approved.
3. CVerbal confirmation followed by closure skips the reconciliation the deviations require.
4. DCorrect: A traceability matrix ties each deviation to its requirement and change record, and a walkthrough gives the sponsor confidence to sign.
More notes below ↓
WP 10Multiple projects close simultaneously. Which criterion should guide prioritization of lessons for rapid ingestion?
Debrief answer to open the notes
1. ADocument length says nothing about how useful a lesson is.
2. BCompletion order is arbitrary when the aim is to reuse the most valuable lessons first.
3. CCorrect: Lessons with high reuse value, strong risk-reduction impact and easy adoption return value fastest, so they go first.
4. DAttendance measures participation, not the value of what was learned.
More notes below ↓
WP 11Incident trends show recurring defects after recent handovers. Which remediation steps should occur before the next handover?
Debrief answer to open the notes
1. AHanding over without active SLA monitoring repeats the conditions behind the recurring defects.
2. BTraining after handover leaves operations unprepared during the riskiest window.
3. CCorrect: Recurring post-handover defects point to readiness gaps, so validate operational readiness and finish training before the next transfer.
4. DMissing support contacts and escalation paths leave incidents with no owner.
More notes below ↓
WP 12A project manager receives a report indicating operations is only partially ready to accept the project deliverables. The sponsor is pressuring the manager to close the project administratively to free up resources. What should the project manager do FIRST?
Debrief answer to open the notes
1. AClosing now and fixing readiness later transfers a product operations cannot yet support.
2. BReleasing resources and pushing issues onto operations shifts the risk instead of resolving it.
3. CCorrect: Do not close against an unready recipient; a monitored remediation plan with documented conditional acceptance protects operations and still moves closure forward.
4. DEscalating to the PMO for an extension skips the plan the project manager can put together first.
More notes below ↓
WP 13A project manager is closing a project phase and preparing for the next phase. Which of the following is NOT a typical activity during phase closure?
Debrief answer to open the notes
1. AConfirming that phase deliverables were accepted is a core closure step.
2. BCapturing lessons from the completed phase is a standard closure activity.
3. CCorrect: The WBS is built during planning; at phase closure work is reviewed, accepted and documented, not decomposed.
4. DReleasing resources that are no longer needed is a normal part of closing a phase.
More notes below ↓
WP 14A project manager is closing a construction project. All deliverables have been completed and accepted by the customer. What is the MOST important document the project manager should update before finalizing project closure?
Debrief answer to open the notes
1. ACorrect: Final lessons learned pass into the organization's knowledge base at closure, which is how future projects benefit from this one.
2. BThe WBS was settled with the scope baseline and does not need a closing update.
3. CThe risk register is closed out, but it is not the key record handed to the organization.
4. DThe schedule is finished once the work is done and gains little from an update at closure.
More notes below ↓
WP 15A project is closing and must produce reusable lessons learned. Which metadata schema and ingestion workflow ensures artifacts are tagged and discoverable across the organization?
Debrief answer to open the notes
1. ACorrect: Structured metadata makes artifacts findable and keeps them current, and an approval gate keeps low-quality entries out.
2. BWithout a review process, entries go stale and quality varies.
3. CFull-text search without structured fields returns noise and no applicability context.
4. DTags without an ingestion workflow leave quality and consistency unchecked.
More notes below ↓
WP 16A project nears handover with the acceptance criterion of 99.5 percent uptime under production load. Which single action BEST validates operational readiness?
Debrief answer to open the notes
1. AAttendance sheets show training happened, not that the system meets the uptime target.
2. BA complete user manual says nothing about behavior under production load.
3. CVerbal confirmation is not evidence and does not test the criterion.
4. DCorrect: A measurable criterion is verified with measured data; a soak test under production load shows whether 99.5% uptime is actually met.
More notes below ↓
WP 17A 12-period CPI control chart shows values clustered near 0.98 with two points above the upper control limit in periods 9 and 11. What does this indicate and what response is appropriate?
Debrief answer to open the notes
1. APoints above the limit are unusual, not proof of lasting performance; cutting contingency on them is premature.
2. BCorrect: points outside the control limits signal special-cause variation, so periods 9 and 11 are checked for an assignable cause.
3. CPoints outside the limits are not common-cause, and shifting the mean before finding the cause is tampering.
4. DTwo points beyond the upper limit mean the process is not in control, so monitoring alone is not enough.
More notes below ↓

Open a row to answer. Keys: 1–4 or A–D answer, N opens the next row.

05Closing questions

Does an agile project still need a closure task?

Yes. Iterations end with reviews and retrospectives, but the release or project still needs acceptance, a handover to whoever runs the product, contract and budget closeout, and archived records. The outline's closure task applies to every delivery approach.

Which records get archived, and why does it matter?

Plans, baselines, the change log, acceptance documents and contracts go to the organization's repository so a later audit or project can find them. The rules for what must be kept, and for how long, come from governance and compliance.

What should happen to lessons learned after closure?

They should change something the next project uses: a template, an estimating benchmark, a checklist. Turning lessons into updated process assets is a Business Environment task, covered under continuous improvement and organizational change.