PMO-07.02 Phase 07: Closing

Tier 1 general

CONTRACT CLOSEOUT REPORT

تقرير إغلاق العقد

tasleemat asset PMO-07.02 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 07: Closing

Sizing Tier Requirements

Tier 1

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-07.02 ./completed_data.json

Template Markdown (Bilingual)

<!--  LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Contract closeout involves documenting vendor performance so that the information can be used
to evaluate the vendor for future work. Contract closure supports the project closure process
and helps ensure contractual agreements are completed or terminated.

Before a contract can be fully closed or terminated, all disputes must be resolved, the
product or result must be accepted, and the final payments must be made. Record the contract
completion date, who signed off on it, and the date of the final payment.

The contract closeout report draws on Table 4.8, Elements of a Contract Closeout.

Tailoring Notes:
*   For a small contract you can combine all the information in the vendor performance
    analysis into a single summary paragraph.
*   For small contracts you may not need the contract changes or contract disputes sections.
*   If the project was based around one large contract, you can combine the information in
    the project closeout report with this form.

Alignment: the report should be aligned and consistent with the procurement management plan,
the procurement audit, the change log, and the project closeout.

Section Instructions:
*   **Contract Identification:** Record the contract reference, the vendor, the contract
    type and value, and the closeout status.
*   **What Worked Well:** For the vendor performance analysis, describe what was handled
    well in scope, quality, schedule, and cost, plus any other aspect of the contract or
    procurement.
*   **What Can Be Improved:** For the same five dimensions, describe what could have been
    improved. Every point should be specific and actionable.
*   **Record of Contract Changes:** For each change, enter the change ID, the description,
    and the date approved, taken from the change log.
*   **Record of Contract Disputes:** For each dispute or claim, describe it, the resolution,
    and the date it was resolved. All disputes must be resolved before closure.
*   **Contract Completion and Final Payment:** Record the completion date, who signed off,
    and the date of the final payment.
*   **Comments:** Add any comments that add relevance to the report. -->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">CONTRACT CLOSEOUT REPORT</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |  

---

## 1. Contract Identification
<!-- Identify the contract being closed so this record can be filed against the right
agreement and reused when the vendor is evaluated for future work. Record the contract
reference, the vendor, the contract type and value, and whether the contract is being
closed as completed or terminated. The closeout status matters because a terminated
contract is also closed, but the performance record is interpreted differently.
- **Contract Reference:** the contract or purchase order number.
- **Vendor:** the legal entity that performed the work.
- **Contract Type and Value:** the contract type, for example fixed price or cost
  reimbursable, and the total contracted value.
- **Closeout Status:** completed or terminated, and the date closure was initiated. -->

| Field | Entry |
| :--- | :--- |
| **Contract Reference** | [ Add details... ] |
| **Vendor** | [ Add details... ] |
| **Contract Type and Value** | [ Add details... ] |
| **Closeout Status** | [ Add details... ] |

---

## 2. Vendor Performance Analysis: What Worked Well
<!-- Record what the vendor did well, across the five dimensions of Table 4.8. This record
exists so the vendor can be evaluated for future work, so state the specific practice and
the evidence behind it rather than a general assessment. Keep the dimensions separate, since
a conclusion that mixes quality and cost cannot be acted on. The Other row is where
qualitative points belong, for example how easy the vendor was to work with.
- **Scope:** aspects of contract scope that were handled well.
- **Quality:** aspects of product quality that were handled well.
- **Schedule:** aspects of the contract schedule that were handled well.
- **Cost:** aspects of the contract budget that were handled well.
- **Other:** any other aspect of the contract or procurement handled well, including how
  easy the vendor was to work with. -->

| Dimension | What Was Handled Well | Evidence or Example |
| :--- | :--- | :--- |
| **Scope** | [ Add details... ] | [ Add details... ] |
| **Quality** | [ Add details... ] | [ Add details... ] |
| **Schedule** | [ Add details... ] | [ Add details... ] |
| **Cost** | [ Add details... ] | [ Add details... ] |
| **Other** | [ Add details... ] | [ Add details... ] |

<!--
Tailoring note: For a small contract, all of the vendor performance information may be combined into a single summary paragraph.
-->

---

## 3. Vendor Performance Analysis: What Can Be Improved
<!-- Record what should have been done better, across the same five dimensions. Every point
must be specific and actionable: state the deficiency, its effect on the contract or
project, and what should be done instead. This section carries the most value for future
procurement, because a defect recorded here will change how the next contract is written or
managed. Where the cause was organisational rather than vendor-specific, say so.
- **Scope:** aspects of contract scope that could be improved.
- **Quality:** aspects of product quality that could be improved.
- **Schedule:** aspects of the contract schedule that could be improved.
- **Cost:** aspects of the contract budget that could be improved.
- **Other:** any other aspect of the contract or procurement that could be improved. -->

| Dimension | What Could Be Improved | Recommended Action |
| :--- | :--- | :--- |
| **Scope** | [ Add details... ] | [ Add details... ] |
| **Quality** | [ Add details... ] | [ Add details... ] |
| **Schedule** | [ Add details... ] | [ Add details... ] |
| **Cost** | [ Add details... ] | [ Add details... ] |
| **Other** | [ Add details... ] | [ Add details... ] |

<!--
Comment guidance: State the deficiency, its effect, and what should be done instead.
-->

---

## 4. Record of Contract Changes
<!-- Record every change made to the contract during its execution, taking all three
elements from the change log rather than restating them from memory. A change alters the
contracted scope, price, or schedule, so an unrecorded change leaves the contract
discrepant against the final account. Give the change ID exactly as it appears in the
change log so the two records can be reconciled.
- **Change ID:** the change identifier from the change log.
- **Change Description:** the description from the change log.
- **Date Approved:** the date approved from the change log. -->

| Change ID | Change Description | Date Approved |
| :---: | :--- | :---: |
| [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] |

<!--
Tailoring note: For small contracts, this section may not be needed.
-->

---

## 5. Record of Contract Disputes
<!-- Record every dispute or claim raised against the contract, and its outcome. All
disputes must be resolved before a contract can be fully closed or terminated, so any
entry still open at the date of this report blocks closure. Give the resolution in
concrete terms, including any settlement amount, because the resolution is what releases
the contract.
- **Dispute Description:** describe the dispute or claim.
- **Resolution:** describe the resolution.
- **Date Resolved:** the date the dispute or claim was resolved. -->

| Dispute Description | Resolution | Date Resolved |
| :--- | :--- | :---: |
| [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] |

<!--
Tailoring note: For small contracts, this section may not be needed.
-->

---

## 6. Contract Completion and Final Payment
<!-- Record the three elements that evidence closure. All disputes must be resolved, the
product or result must be accepted, and the final payments must be made before a contract
can be fully closed or terminated. Name the person who signed off, not just the role, so
the acceptance is traceable. If the contract is being terminated rather than completed, say
so here and explain why in the comments section.
- **Contract Completion Date:** the date the contract was completed.
- **Signed Off By:** who signed off on the contract completion.
- **Final Payment Date:** the date of the final payment. -->

| Field | Entry |
| :--- | :--- |
| **Contract Completion Date** | [ Add details... ] |
| **Signed Off By** | [ Add details... ] |
| **Final Payment Date** | [ Add details... ] |

<!--
Comment guidance: All disputes must be resolved, the result accepted, and final payment made before closure.
-->

---

## 7. Comments
<!-- Add any comments that give the report additional relevance, such as the reason a
contract was terminated rather than completed, scope limitations, or context needed by
the project closeout report. -->


---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Contract Manager** | {{Contract_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Procurement Manager** | {{Procurement_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Finance Controller / Legal Counsel** | {{Finance_Controller_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div dir="ltr" align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> CONTRACT CLOSEOUT REPORT | <strong>Ref:</strong> PMO-07.02 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Artifact: Contract Closeout Report

Document Reference: PMO-07.02

This document provides a detailed, professional reference for understanding the purpose of the Contract Closeout Report and using it effectively as part of the Tasleemat methodology.

1. What is it?

An official Tasleemat document called the Contract Closeout Report, used to document vendor performance so the information can be used to evaluate the vendor for future work. Contract closure supports the project closure process and helps ensure contractual agreements are completed or terminated.

2. Why?

To ensure alignment with Tasleemat standards, to provide transparency, to record the lessons learned from a contract for future procurement, and to support project closure.

3. When?

This artifact is prepared in the Closing Process Group of the project lifecycle, before a contract can be fully closed or terminated.

4. Who?

Responsibilities: Maintained by the contract manager and the procurement manager, and approved by finance control. It is used as an input when the vendor is evaluated for future procurement.

Tailoring Tips

For a small contract you can combine all the vendor performance information into a single summary paragraph.
For small contracts you may not need the contract changes or contract disputes sections.
If the project was based around one large contract, you can combine the information in the project closeout report with this form.

Alignment

Procurement management plan
Procurement audit
Change log
Project closeout

5. How?

To accurately and professionally complete the CONTRACT CLOSEOUT REPORT, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

Contract Identification: Record the contract reference, the vendor, the contract type and value, and the closeout status.
What Worked Well: For scope, quality, schedule, cost, and any other dimension, describe what was handled well and give the evidence for it.
What Can Be Improved: For the same five dimensions, describe what could have been improved and the recommended action.
Record of Contract Changes: For each change, enter the change ID, the description, and the date approved, taken from the change log.
Record of Contract Disputes: For each dispute or claim, describe it, the resolution, and the date it was resolved.
Contract Completion and Final Payment: Record the completion date, who signed off, and the date of the final payment.
Comments: Add any comments that add relevance to the report.

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 07_02_Contract_Closeout_Report_Example.md

LLM Generation Prompt & Agent Instructions

CONTRACT CLOSEOUT REPORT - LLM GENERATION GUIDE

System Prompt / Instructions: This document serves as the detailed instruction set for generating the CONTRACT CLOSEOUT REPORT. When asked to populate this form, use the guidance provided for each section below to accurately generate the required content. Reference parameters.md for global project variables.

Context & Definition: [ Add Context & Definition Here ]

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Product Acceptance Form (PMO-06.08), UAT Sign-off (PMO-06.10), Contract Closure Reports (PMO-07.02) * Optional: Lessons Learned Register (PMO-05.07), Issue Log (PMO-05.01), Risk Register (PMO-04.08.02) * Downstream Dependents: * Mandatory: Final Project Archive & Release, Value Realization Register (PMO-01.03), Organizational Process Assets Update * Optional: Post-Implementation Review, Transition to Operations Checklist (PMO-07.04)

Contract Identification

Instruction: Record the contract reference, the vendor, and the contract type and value.

Vendor Performance Analysis - What Worked Well

Scope

Instruction: Describe the aspects of contract scope that were handled well.

Quality

Instruction: Describe the aspects of product quality that were handled well.

Schedule

Instruction: Describe the aspects of the contract schedule that were handled well.

Cost

Instruction: Describe the aspects of the contract budget that were handled well.

Other

Instruction: Describe any other aspects of the contract or procurement that were handled well, including how easy the vendor was to work with.

Vendor Performance Analysis - What Can Be Improved

Scope

Instruction: Describe the aspects of contract scope that could be improved.

Quality

Instruction: Describe the aspects of product quality that could be improved.

Schedule

Instruction: Describe the aspects of the contract schedule that could be improved.

Cost

Instruction: Describe the aspects of the contract budget that could be improved.

Other

Instruction: Describe any other aspects of the contract or procurement that could be improved.

Record of Contract Changes

Change ID

Instruction: Enter the change identifier from the change log.

Change Description

Instruction: Enter the description from the change log.

Date Approved

Instruction: Enter the date approved from the change log.

Record of Contract Disputes

Dispute Description

Instruction: The dispute or claim, what was in contention, and the amount or scope at issue. State the position the project took and the date it was raised, because a dispute recorded without its date cannot be distinguished from one still open at closeout.

Resolution

Instruction: How the dispute was settled, by whom, and when, with a reference to the agreement or settlement that closed it. An unresolved dispute carried past closeout is a liability the receiving organisation inherits without knowing it, so record the outcome even when it is only partial.

Date Resolved

Instruction: Enter the date the dispute or claim was resolved.

Contract Completion and Final Payment

Contract Completion Date

Instruction: The date the contract was completed, meaning the date the work was accepted rather than the date the last invoice was paid. Where the two differ, give both, because a payment date is not evidence that the work was accepted.

Signed Off By

Instruction: Record who signed off on the contract completion.

Final Payment Date

Instruction: Enter the date of the final payment.

Comments

Instruction: Add any comments that will add relevance to the closeout report.

PMO-07.02 Phase 07: Closing Realistic Case Study Benchmark

Date Prepared

2026-03-15

Project Manager

Faisal Al-Harbi, PMP

Prepared By

Faisal Al-Harbi, PMP (Senior Project Manager)

Contract Closeout Report (Reference Example)

🏆 Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (PMO-07.02). All company names, project references, and figures are realistic fictional simulations.

Apex Global Solutions

Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01

CONTRACT CLOSEOUT REPORT

1. Contract Identification

Field	Entry
Contract Reference	Approved and aligned with Apex Global Solutions governance baseline
Vendor	Approved and aligned with Apex Global Solutions governance baseline
Contract Type and Value	Approved and aligned with Apex Global Solutions governance baseline
Closeout Status	Approved and aligned with Apex Global Solutions governance baseline

2. Vendor Performance Analysis: What Worked Well

Dimension	What Was Handled Well	Evidence or Example
Scope	Deploy and integrate unified cloud ERP platform across all enterprise units	Deploy and integrate unified cloud ERP platform across all enterprise units
Quality	Deliver high system reliability (99.95% uptime) and superior user experience	Deliver high system reliability (99.95% uptime) and superior user experience
Schedule	Complete end-to-end system rollout and cutover within 18 months	Complete end-to-end system rollout and cutover within 18 months
Cost	Execute project within pre-approved $3,500,000 USD budget envelope	Execute project within pre-approved $3,500,000 USD budget envelope
Other	Deliver high system reliability (99.95% uptime) and superior user experience	Deliver high system reliability (99.95% uptime) and superior user experience

3. Vendor Performance Analysis: What Can Be Improved

Dimension	What Could Be Improved	Recommended Action
Scope	Deploy and integrate unified cloud ERP platform across all enterprise units	Deploy and integrate unified cloud ERP platform across all enterprise units
Quality	Deliver high system reliability (99.95% uptime) and superior user experience	Deliver high system reliability (99.95% uptime) and superior user experience
Schedule	Complete end-to-end system rollout and cutover within 18 months	Complete end-to-end system rollout and cutover within 18 months
Cost	Execute project within pre-approved $3,500,000 USD budget envelope	Execute project within pre-approved $3,500,000 USD budget envelope
Other	Deliver high system reliability (99.95% uptime) and superior user experience	Deliver high system reliability (99.95% uptime) and superior user experience

4. Record of Contract Changes

Change ID	Change Description	Date Approved
CR-2026-01	Deploy hardened cloud environment and master databases	2026-06-30
CR-2026-02	Automate procurement requisition and inventory workflows	2026-09-30
CR-2026-03	Build interactive executive dashboards and KPI reports	2026-11-30

5. Record of Contract Disputes

Dispute Description	Resolution	Date Resolved
Deploy hardened cloud environment and master databases	Approved and aligned with Apex Global Solutions governance baseline	2026-06-30
Automate procurement requisition and inventory workflows	Approved and aligned with Apex Global Solutions governance baseline	2026-09-30
Build interactive executive dashboards and KPI reports	Approved and aligned with Apex Global Solutions governance baseline	2026-11-30

6. Contract Completion and Final Payment

Field	Entry
Contract Completion Date	Approved and aligned with Apex Global Solutions governance baseline
Signed Off By	Approved and aligned with Apex Global Solutions governance baseline
Final Payment Date	Approved and aligned with Apex Global Solutions governance baseline

7. Comments

Sign-off and Approvals

Role	Name	Signature	Date
Contract Manager	Approved - Contract Manager Name	[Electronically Signed]	2026-03-18
Procurement Manager	Mansour Al-Shehri (Head of Strategic Sourcing)	[Electronically Signed]	2026-03-18
Finance Controller / Legal Counsel	Approved - Finance Controller Name	[Electronically Signed]	2026-03-18
---

Template: CONTRACT CLOSEOUT REPORT | Ref: PMO-07.02
Generated on: 2026-03-15 10:00 UTC, by Tasleemat

Draft 2020-12 JSON Schema

Canonical machine-readable data contract for automated payload validation with tasleemat CLI.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-07.02.schema.json",
  "title": "Completed CONTRACT CLOSEOUT REPORT Data Contract",
  "description": "Additive structural schema validating completed CONTRACT CLOSEOUT REPORT artifact data payloads (PMO-07.02).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-07.02"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "contract_identification": {
      "type": "object",
      "properties": {
        "contract_identification": {
          "type": "string",
          "minLength": 1,
          "description": "Record the contract reference, the vendor, and the contract type and value."
        }
      },
      "required": [
        "contract_identification"
      ]
    },
    "vendor_performance_analysis_what_worked_well": {
      "type": "object",
      "properties": {
        "scope": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of contract scope that were handled well."
        },
        "quality": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of product quality that were handled well."
        },
        "schedule": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of the contract schedule that were handled well."
        },
        "cost": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of the contract budget that were handled well."
        },
        "other": {
          "type": "string",
          "minLength": 1,
          "description": "Describe any other aspects of the contract or procurement that were handled well, including how easy the vendor was to work with."
        }
      },
      "required": [
        "scope",
        "quality",
        "schedule",
        "cost",
        "other"
      ]
    },
    "vendor_performance_analysis_what_can_be_improved": {
      "type": "object",
      "properties": {
        "scope": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of contract scope that could be improved."
        },
        "quality": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of product quality that could be improved."
        },
        "schedule": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of the contract schedule that could be improved."
        },
        "cost": {
          "type": "string",
          "minLength": 1,
          "description": "Describe the aspects of the contract budget that could be improved."
        },
        "other": {
          "type": "string",
          "minLength": 1,
          "description": "Describe any other aspects of the contract or procurement that could be improved."
        }
      },
      "required": [
        "scope",
        "quality",
        "schedule",
        "cost",
        "other"
      ]
    },
    "record_of_contract_changes": {
      "type": "object",
      "properties": {
        "change_id": {
          "type": "string",
          "minLength": 1,
          "description": "Enter the change identifier from the change log."
        },
        "change_description": {
          "type": "string",
          "minLength": 1,
          "description": "Enter the description from the change log."
        },
        "date_approved": {
          "type": "string",
          "minLength": 1,
          "description": "Enter the date approved from the change log."
        }
      },
      "required": [
        "change_id",
        "change_description",
        "date_approved"
      ]
    },
    "record_of_contract_disputes": {
      "type": "object",
      "properties": {
        "dispute_description": {
          "type": "string",
          "minLength": 1,
          "description": "The dispute or claim, what was in contention, and the amount or scope at issue. State the position the project took and the date it was raised, because a dispute recorded without its date cannot be distinguished from one still open at closeout."
        },
        "resolution": {
          "type": "string",
          "minLength": 1,
          "description": "How the dispute was settled, by whom, and when, with a reference to the agreement or settlement that closed it. An unresolved dispute carried past closeout is a liability the receiving organisation inherits without knowing it, so record the outcome even when it is only partial."
        },
        "date_resolved": {
          "type": "string",
          "minLength": 1,
          "description": "Enter the date the dispute or claim was resolved."
        }
      },
      "required": [
        "dispute_description",
        "resolution",
        "date_resolved"
      ]
    },
    "contract_completion_and_final_payment": {
      "type": "object",
      "properties": {
        "contract_completion_date": {
          "type": "string",
          "minLength": 1,
          "description": "The date the contract was completed, meaning the date the work was accepted rather than the date the last invoice was paid. Where the two differ, give both, because a payment date is not evidence that the work was accepted."
        },
        "signed_off_by": {
          "type": "string",
          "minLength": 1,
          "description": "Record who signed off on the contract completion."
        },
        "final_payment_date": {
          "type": "string",
          "minLength": 1,
          "description": "Enter the date of the final payment."
        }
      },
      "required": [
        "contract_completion_date",
        "signed_off_by",
        "final_payment_date"
      ]
    },
    "comments": {
      "type": "object",
      "properties": {
        "comments": {
          "type": "string",
          "minLength": 1,
          "description": "Add any comments that will add relevance to the closeout report."
        }
      },
      "required": [
        "comments"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "contract_identification",
    "vendor_performance_analysis_what_worked_well",
    "vendor_performance_analysis_what_can_be_improved",
    "record_of_contract_changes",
    "record_of_contract_disputes",
    "contract_completion_and_final_payment",
    "comments"
  ]
}

📋 Form Field Definitions Dictionary (Legacy Specification)

{
  "_llm_instructions": "Fill out 'project_title' and 'date_prepared', and the 'value' property of each field, using the project context. Use 'label' to select the correct output language. Reference parameters.md for global project variables.",
  "form_name": "CONTRACT CLOSEOUT REPORT",
  "document_reference": "PMO-07.02",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "contract_identification": {
      "section": "Contract Identification",
      "label": "Contract Identification",
      "guidance": "Record the contract reference, the vendor, and the contract type and value.",
      "value": ""
    },
    "scope_worked_well": {
      "section": "Vendor Performance Analysis: What Worked Well",
      "label": "Scope",
      "guidance": "Describe the aspects of contract scope that were handled well.",
      "value": ""
    },
    "quality_worked_well": {
      "section": "Vendor Performance Analysis: What Worked Well",
      "label": "Quality",
      "guidance": "Describe the aspects of product quality that were handled well.",
      "value": ""
    },
    "schedule_worked_well": {
      "section": "Vendor Performance Analysis: What Worked Well",
      "label": "Schedule",
      "guidance": "Describe the aspects of the contract schedule that were handled well.",
      "value": ""
    },
    "cost_worked_well": {
      "section": "Vendor Performance Analysis: What Worked Well",
      "label": "Cost",
      "guidance": "Describe the aspects of the contract budget that were handled well.",
      "value": ""
    },
    "other_worked_well": {
      "section": "Vendor Performance Analysis: What Worked Well",
      "label": "Other",
      "guidance": "Describe any other aspects of the contract or procurement that were handled well, including how easy the vendor was to work with.",
      "value": ""
    },
    "scope_improve": {
      "section": "Vendor Performance Analysis: What Can Be Improved",
      "label": "Scope",
      "guidance": "Describe the aspects of contract scope that could be improved.",
      "value": ""
    },
    "quality_improve": {
      "section": "Vendor Performance Analysis: What Can Be Improved",
      "label": "Quality",
      "guidance": "Describe the aspects of product quality that could be improved.",
      "value": ""
    },
    "schedule_improve": {
      "section": "Vendor Performance Analysis: What Can Be Improved",
      "label": "Schedule",
      "guidance": "Describe the aspects of the contract schedule that could be improved.",
      "value": ""
    },
    "cost_improve": {
      "section": "Vendor Performance Analysis: What Can Be Improved",
      "label": "Cost",
      "guidance": "Describe the aspects of the contract budget that could be improved.",
      "value": ""
    },
    "other_improve": {
      "section": "Vendor Performance Analysis: What Can Be Improved",
      "label": "Other",
      "guidance": "Describe any other aspects of the contract or procurement that could be improved.",
      "value": ""
    },
    "change_id": {
      "section": "Record of Contract Changes",
      "label": "Change ID",
      "guidance": "Enter the change identifier from the change log.",
      "value": ""
    },
    "change_description": {
      "section": "Record of Contract Changes",
      "label": "Change Description",
      "guidance": "Enter the description from the change log.",
      "value": ""
    },
    "date_approved": {
      "section": "Record of Contract Changes",
      "label": "Date Approved",
      "guidance": "Enter the date approved from the change log.",
      "value": ""
    },
    "dispute_description": {
      "section": "Record of Contract Disputes",
      "label": "Dispute Description",
      "guidance": "The dispute or claim, what was in contention, and the amount or scope at issue. State the position the project took and the date it was raised, because a dispute recorded without its date cannot be distinguished from one still open at closeout.",
      "value": ""
    },
    "dispute_resolution": {
      "section": "Record of Contract Disputes",
      "label": "Resolution",
      "guidance": "How the dispute was settled, by whom, and when, with a reference to the agreement or settlement that closed it. An unresolved dispute carried past closeout is a liability the receiving organisation inherits without knowing it, so record the outcome even when it is only partial.",
      "value": ""
    },
    "date_resolved": {
      "section": "Record of Contract Disputes",
      "label": "Date Resolved",
      "guidance": "Enter the date the dispute or claim was resolved.",
      "value": ""
    },
    "completion_date": {
      "section": "Contract Completion and Final Payment",
      "label": "Contract Completion Date",
      "guidance": "The date the contract was completed, meaning the date the work was accepted rather than the date the last invoice was paid. Where the two differ, give both, because a payment date is not evidence that the work was accepted.",
      "value": ""
    },
    "signed_off_by": {
      "section": "Contract Completion and Final Payment",
      "label": "Signed Off By",
      "guidance": "Record who signed off on the contract completion.",
      "value": ""
    },
    "final_payment_date": {
      "section": "Contract Completion and Final Payment",
      "label": "Final Payment Date",
      "guidance": "Enter the date of the final payment.",
      "value": ""
    },
    "comments": {
      "section": "Comments",
      "label": "Comments",
      "guidance": "Add any comments that will add relevance to the closeout report.",
      "value": ""
    }
  }
}

CONTRACT CLOSEOUT REPORT

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Sizing Tier Requirements

Validation Contract

Template Markdown (Bilingual)

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Artifact: Contract Closeout Report

1. What is it?

2. Why?

3. When?

4. Who?

Tailoring Tips

Alignment

5. How?

📥 Related Files

6. Reference Example

LLM Generation Prompt & Agent Instructions

CONTRACT CLOSEOUT REPORT - LLM GENERATION GUIDE

Contract Identification

Contract Identification

Vendor Performance Analysis - What Worked Well

Scope

Quality

Schedule

Cost

Other

Vendor Performance Analysis - What Can Be Improved

Scope

Quality

Schedule

Cost

Other

Record of Contract Changes

Change ID

Change Description

Date Approved

Record of Contract Disputes

Dispute Description

Resolution

Date Resolved

Contract Completion and Final Payment

Contract Completion Date

Signed Off By

Final Payment Date

Comments

Comments

Contract Closeout Report (Reference Example)

Apex Global Solutions

Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01

CONTRACT CLOSEOUT REPORT

1. Contract Identification

2. Vendor Performance Analysis: What Worked Well

3. Vendor Performance Analysis: What Can Be Improved

4. Record of Contract Changes

5. Record of Contract Disputes

6. Contract Completion and Final Payment

7. Comments

Sign-off and Approvals

Draft 2020-12 JSON Schema