HKSM

Closed procurements is the structured review and completion of all contractual obligations with a seller to formally finalize the contract. It confirms deliverables, payments, claims, and documentation are settled and archived.

Key Points

• Ensures all contracted scope is accepted, documented, and any outstanding items are resolved.
• Verifies financial closure, including final invoices, retentions, change orders, and adjustments.
• Addresses claims and disputes, secures releases, and confirms transfer of warranties and intellectual property.
• Captures supplier performance information and lessons learned for future sourcing decisions.
• Results in a formal notice of completion and release of contractual obligations for both parties.
• Archives complete, accurate records to meet audit, legal, and organizational requirements.

Purpose of Analysis

The purpose is to confirm that the seller has fulfilled the contract and that the buyer has met payment and acceptance obligations, leaving no loose ends. This analysis protects the organization legally and financially, improves vendor management, and preserves knowledge for future projects.

Method Steps

• Review contract terms, amendments, and change orders to list all closure requirements.
• Verify deliverables are complete and accepted; obtain formal acceptance from the buyer representative.
• Reconcile financials: match invoices, receipts, and approved changes; authorize final payment or retention release.
• Resolve claims and open issues; secure written waivers, releases, and settlement agreements if needed.
• Confirm transfer of warranties, licenses, intellectual property, spares, and as-built documentation.
• Complete seller performance evaluation and record lessons learned.
• Issue formal contract closure notice and communicate with stakeholders.
• Archive all procurement records in the designated repository per policy.

Inputs Needed

• Executed contract, statement of work, and all change orders.
• Acceptance criteria, test results, and completion certificates.
• Invoices, payment records, purchase orders, and receipt documents.
• Issue and claim logs, correspondence, and meeting minutes.
• Procurement management plan, legal/compliance requirements, and organizational policies.
• Performance reports, quality logs, and risk register (for residual obligations).

Outputs Produced

• Formal contract closure notice and release of obligations.
• Final payment authorization and reconciliation summary.
• Claim settlements and mutual releases, if applicable.
• Supplier performance evaluation and lessons learned entries.
• Archived procurement file, including all approvals and correspondence.
• Updated asset registers, warranty schedules, and residual risk entries.

Interpretation Tips

• Closure is not just final payment; it also confirms acceptance, releases, and documentation handover.
• Distinguish normal closure from termination for convenience or default; each follows different legal steps.
• In adaptive life cycles, close procurements incrementally per iteration or release if the contract allows.
• Address multi-vendor dependencies by sequencing closures to avoid gaps in warranties or support.
• If any obligation remains (e.g., warranty transfer), do not issue the closure notice until it is resolved.

Example

A project receives the vendor’s final deliverable and passes acceptance testing. The project manager reconciles two approved change orders, confirms that as-built documents and a 12-month warranty have been transferred, settles a minor invoice discrepancy, records the supplier’s strong schedule performance, issues the formal closure notice, and archives the complete procurement file.

Pitfalls

• Issuing final payment before confirming acceptance or resolving open claims.
• Failing to secure written releases, leading to future disputes.
• Incomplete archiving, which weakens audits and organizational learning.
• Overlooking transfer of IP, warranties, or licenses, causing support gaps.
• Skipping a performance evaluation, reducing data quality for future vendor selection.

PMP Example Question

A vendor has delivered all contracted work. Two change orders were approved, and a warranty transfer document is pending. What should the project manager do next to properly close the procurement?

1. Issue final payment and archive the procurement records.
2. Confirm acceptance, reconcile payments and change orders, obtain the warranty transfer, then issue the closure notice.
3. Release the vendor’s team and update the lessons learned register.
4. Start a detailed procurement audit before taking any other action.

Correct Answer: B - Confirm acceptance, reconcile payments and change orders, obtain the warranty transfer, then issue the closure notice.

Explanation: Closure requires verifying all obligations and documents are complete before final payment and formal closure. Issuing payment or archiving first could leave open liabilities.